From 76e03a5db89d2b6c6a0cbcbb64c833bc72c6c52c Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Thu, 31 Jul 2025 12:44:42 -0500 Subject: [PATCH] Fix Exchange content for new pipeline --- .openpublishing.redirection.exchange.json | 9649 ++++++++++++++--- .../Add-ADPermission.md | 93 +- .../Add-AttachmentFilterEntry.md | 31 +- .../Add-AvailabilityAddressSpace.md | 55 +- .../Add-ComplianceCaseMember.md | 27 +- .../Add-ContentFilterPhrase.md | 31 +- .../Add-DatabaseAvailabilityGroupServer.md | 35 +- .../Add-DistributionGroupMember.md | 35 +- .../Add-FederatedDomain.md | 31 +- .../Add-GlobalMonitoringOverride.md | 55 +- .../Add-IPAllowListEntry.md | 39 +- .../Add-IPAllowListProvider.md | 51 +- .../Add-IPBlockListEntry.md | 39 +- .../Add-IPBlockListProvider.md | 55 +- .../Add-MailboxDatabaseCopy.md | 55 +- .../Add-MailboxFolderPermission.md | 43 +- .../Add-MailboxPermission.md | 102 +- .../Add-ManagementRoleEntry.md | 59 +- ...dd-PublicFolderAdministrativePermission.md | 94 +- .../Add-PublicFolderClientPermission.md | 39 +- .../Add-RecipientPermission.md | 31 +- .../Add-ResubmitRequest.md | 63 +- .../Add-RoleGroupMember.md | 35 +- .../Add-ServerMonitoringOverride.md | 47 +- .../Add-UnifiedGroupLinks.md | 31 +- .../Add-VivaModuleFeaturePolicy.md | 60 +- .../Add-VivaOrgInsightsDelegatedRole.md | 22 +- .../Add-eDiscoveryCaseAdmin.md | 23 +- .../Check-PurviewConfig.md | 67 +- .../Clean-MailboxDatabase.md | 27 +- .../Clear-ActiveSyncDevice.md | 35 +- .../Clear-MobileDevice.md | 39 +- .../Clear-TextMessagingAccount.md | 31 +- .../Compare-TextMessagingVerificationCode.md | 31 +- .../Complete-MigrationBatch.md | 43 +- .../Connect-ExchangeOnline.md | 156 +- .../Connect-IPPSSession.md | 84 +- .../Connect-Mailbox.md | 99 +- .../Delete-QuarantineMessage.md | 52 +- .../Disable-ATPProtectionPolicyRule.md | 23 +- .../Disable-AddressListPaging.md | 23 +- .../Disable-AntiPhishRule.md | 23 +- .../Disable-App.md | 31 +- .../Disable-CmdletExtensionAgent.md | 27 +- .../Disable-DistributionGroup.md | 31 +- .../Disable-DnssecForVerifiedDomain.md | 23 +- .../Disable-EOPProtectionPolicyRule.md | 23 +- .../Disable-HostedContentFilterRule.md | 23 +- .../Disable-HostedOutboundSpamFilterRule.md | 23 +- .../Disable-IPv6ForAcceptedDomain.md | 22 +- .../Disable-InboxRule.md | 39 +- .../Disable-JournalArchiving.md | 27 +- .../Disable-JournalRule.md | 27 +- .../Disable-MailContact.md | 31 +- .../Disable-MailPublicFolder.md | 31 +- .../Disable-MailUser.md | 35 +- .../Disable-Mailbox.md | 63 +- .../Disable-MailboxQuarantine.md | 60 +- .../Disable-MalwareFilterRule.md | 27 +- .../Disable-MetaCacheDatabase.md | 23 +- .../Disable-OutlookAnywhere.md | 31 +- .../Disable-OutlookProtectionRule.md | 27 +- .../Disable-PushNotificationProxy.md | 19 +- .../Disable-RemoteMailbox.md | 39 +- .../Disable-ReportSubmissionRule.md | 23 +- .../Disable-SafeAttachmentRule.md | 23 +- .../Disable-SafeLinksRule.md | 23 +- .../Disable-ServiceEmailChannel.md | 27 +- .../Disable-SmtpDaneInbound.md | 23 +- .../Disable-SweepRule.md | 31 +- .../Disable-TransportAgent.md | 31 +- .../Disable-TransportRule.md | 27 +- .../Disable-UMAutoAttendant.md | 27 +- .../Disable-UMCallAnsweringRule.md | 31 +- .../Disable-UMIPGateway.md | 31 +- .../Disable-UMMailbox.md | 35 +- .../Disable-UMServer.md | 31 +- .../Disable-UMService.md | 31 +- .../Disconnect-ExchangeOnline.md | 28 +- .../Dismount-Database.md | 27 +- .../Dump-ProvisioningCache.md | 43 +- .../Enable-ATPProtectionPolicyRule.md | 23 +- .../Enable-AddressListPaging.md | 23 +- .../Enable-AntiPhishRule.md | 23 +- .../Enable-AntispamUpdates.md | 27 +- .../Enable-App.md | 31 +- .../Enable-CmdletExtensionAgent.md | 27 +- .../Enable-ComplianceTagStorage.md | 23 +- .../Enable-DistributionGroup.md | 39 +- .../Enable-DnssecForVerifiedDomain.md | 23 +- .../Enable-EOPProtectionPolicyRule.md | 23 +- .../Enable-ExchangeCertificate.md | 51 +- .../Enable-HostedContentFilterRule.md | 23 +- .../Enable-HostedOutboundSpamFilterRule.md | 23 +- .../Enable-IPv6ForAcceptedDomain.md | 22 +- .../Enable-InboxRule.md | 39 +- .../Enable-JournalRule.md | 27 +- .../Enable-MailContact.md | 59 +- .../Enable-MailPublicFolder.md | 39 +- .../Enable-MailUser.md | 72 +- .../Enable-Mailbox.md | 147 +- .../Enable-MailboxQuarantine.md | 56 +- .../Enable-MalwareFilterRule.md | 27 +- .../Enable-MetaCacheDatabase.md | 23 +- .../Enable-OrganizationCustomization.md | 19 +- .../Enable-OutlookAnywhere.md | 59 +- .../Enable-OutlookProtectionRule.md | 27 +- .../Enable-PushNotificationProxy.md | 27 +- .../Enable-RemoteMailbox.md | 67 +- .../Enable-ReportSubmissionRule.md | 23 +- .../Enable-SafeAttachmentRule.md | 23 +- .../Enable-SafeLinksRule.md | 23 +- .../Enable-ServiceEmailChannel.md | 27 +- .../Enable-SmtpDaneInbound.md | 23 +- .../Enable-SweepRule.md | 31 +- .../Enable-TransportAgent.md | 31 +- .../Enable-TransportRule.md | 31 +- .../Enable-UMAutoAttendant.md | 27 +- .../Enable-UMCallAnsweringRule.md | 31 +- .../Enable-UMIPGateway.md | 27 +- .../Enable-UMMailbox.md | 88 +- .../Enable-UMServer.md | 27 +- .../Enable-UMService.md | 27 +- .../ExchangePowerShell.md} | 21 +- .../Execute-AzureADLabelSync.md | 11 +- .../Expedite-Delicensing.md | 15 +- .../Export-ActiveSyncLog.md | 47 +- .../Export-ActivityExplorerData.md | 51 +- .../Export-AutoDiscoverConfig.md | 47 +- .../Export-ContentExplorerData.md | 47 +- .../Export-DlpPolicyCollection.md | 27 +- .../Export-ExchangeCertificate.md | 47 +- .../Export-FilePlanProperty.md | 18 +- .../Export-JournalRuleCollection.md | 31 +- .../Export-MailboxDiagnosticLogs.md | 55 +- .../Export-Message.md | 23 +- .../Export-MigrationReport.md | 43 +- .../Export-QuarantineMessage.md | 60 +- .../Export-RecipientDataProperty.md | 35 +- .../Export-TransportRuleCollection.md | 35 +- .../Export-UMCallDataRecord.md | 39 +- .../Export-UMPrompt.md | 35 +- .../Get-ADPermission.md | 27 +- .../Get-ADServerSettings.md | 11 +- .../Get-ADSite.md | 19 +- .../Get-ATPBuiltInProtectionRule.md | 19 +- .../Get-ATPProtectionPolicyRule.md | 19 +- .../Get-ATPTotalTrafficReport.md | 51 +- .../Get-AcceptedDomain.md | 23 +- .../Get-AccessToCustomerDataRequest.md | 23 +- .../Get-ActiveSyncDevice.md | 43 +- .../Get-ActiveSyncDeviceAccessRule.md | 19 +- .../Get-ActiveSyncDeviceAutoblockThreshold.md | 19 +- .../Get-ActiveSyncDeviceClass.md | 27 +- .../Get-ActiveSyncDeviceStatistics.md | 35 +- .../Get-ActiveSyncMailboxPolicy.md | 19 +- .../Get-ActiveSyncOrganizationSettings.md | 19 +- .../Get-ActiveSyncVirtualDirectory.md | 31 +- .../Get-AdSiteLink.md | 19 +- .../Get-AdaptiveScope.md | 23 +- .../Get-AddressBookPolicy.md | 19 +- .../Get-AddressList.md | 27 +- .../Get-AddressRewriteEntry.md | 19 +- .../Get-AdminAuditLogConfig.md | 15 +- .../Get-AdministrativeUnit.md | 27 +- .../Get-AgentLog.md | 27 +- .../Get-AggregateZapReport.md | 27 +- .../Get-AntiPhishPolicy.md | 27 +- .../Get-AntiPhishRule.md | 19 +- .../Get-App.md | 31 +- .../Get-AppRetentionCompliancePolicy.md | 27 +- .../Get-AppRetentionComplianceRule.md | 19 +- .../Get-ApplicationAccessPolicy.md | 15 +- .../Get-ArcConfig.md | 11 +- .../Get-AtpPolicyForO365.md | 15 +- .../Get-AttachmentFilterEntry.md | 19 +- .../Get-AttachmentFilterListConfig.md | 15 +- .../Get-AuditConfig.md | 15 +- .../Get-AuditLogSearch.md | 31 +- .../Get-AuthConfig.md | 15 +- .../Get-AuthRedirect.md | 19 +- .../Get-AuthServer.md | 19 +- .../Get-AuthenticationPolicy.md | 23 +- .../Get-AutoSensitivityLabelPolicy.md | 31 +- .../Get-AutoSensitivityLabelRule.md | 39 +- .../Get-AutodiscoverVirtualDirectory.md | 31 +- .../Get-AvailabilityAddressSpace.md | 19 +- .../Get-AvailabilityConfig.md | 19 +- .../Get-AvailabilityReportOutage.md | 27 +- .../Get-BlockedConnector.md | 15 +- .../Get-BlockedSenderAddress.md | 15 +- .../Get-CASMailbox.md | 79 +- .../Get-CASMailboxPlan.md | 39 +- .../Get-CalendarDiagnosticAnalysis.md | 31 +- .../Get-CalendarDiagnosticLog.md | 110 +- .../Get-CalendarDiagnosticObjects.md | 95 +- .../Get-CalendarNotification.md | 31 +- .../Get-CalendarProcessing.md | 27 +- .../Get-CaseHoldPolicy.md | 31 +- .../Get-CaseHoldRule.md | 19 +- .../Get-ClassificationRuleCollection.md | 19 +- .../Get-ClientAccessArray.md | 23 +- .../Get-ClientAccessRule.md | 27 +- .../Get-ClientAccessServer.md | 27 +- .../Get-ClientAccessService.md | 27 +- .../Get-Clutter.md | 19 +- .../Get-CmdletExtensionAgent.md | 27 +- .../Get-ComplianceCase.md | 31 +- .../Get-ComplianceCaseMember.md | 27 +- .../Get-ComplianceRetentionEvent.md | 31 +- .../Get-ComplianceRetentionEventType.md | 19 +- .../Get-ComplianceSearch.md | 27 +- .../Get-ComplianceSearchAction.md | 51 +- .../Get-ComplianceSecurityFilter.md | 31 +- .../Get-ComplianceTag.md | 23 +- .../Get-ComplianceTagStorage.md | 19 +- .../Get-CompromisedUserAggregateReport.md | 31 +- .../Get-CompromisedUserDetailReport.md | 31 +- .../Get-ConfigAnalyzerPolicyRecommendation.md | 23 +- .../Get-ConnectionInformation.md | 20 +- .../Get-Contact.md | 55 +- .../Get-ContentFilterConfig.md | 15 +- .../Get-ContentFilterPhrase.md | 23 +- .../Get-ContentMalwareMdoAggregateReport.md | 35 +- .../Get-ContentMalwareMdoDetailReport.md | 35 +- .../Get-DataClassification.md | 23 +- .../Get-DataClassificationConfig.md | 11 +- .../Get-DataEncryptionPolicy.md | 27 +- .../Get-DataRetentionReport.md | 27 +- .../Get-DatabaseAvailabilityGroup.md | 23 +- .../Get-DatabaseAvailabilityGroupNetwork.md | 23 +- .../Get-DefaultTenantBriefingConfig.md | 16 +- ...t-DefaultTenantMyAnalyticsFeatureConfig.md | 16 +- .../Get-DeliveryAgentConnector.md | 19 +- .../Get-DetailZapReport.md | 27 +- .../Get-DetailsTemplate.md | 27 +- .../Get-DeviceConditionalAccessPolicy.md | 15 +- .../Get-DeviceConditionalAccessRule.md | 23 +- .../Get-DeviceConfigurationPolicy.md | 15 +- .../Get-DeviceConfigurationRule.md | 23 +- .../Get-DevicePolicy.md | 15 +- .../Get-DeviceTenantPolicy.md | 15 +- .../Get-DeviceTenantRule.md | 19 +- .../Get-DistributionGroup.md | 87 +- .../Get-DistributionGroupMember.md | 39 +- .../Get-DkimSigningConfig.md | 15 +- .../Get-DlpCompliancePolicy.md | 47 +- .../Get-DlpComplianceRule.md | 27 +- .../Get-DlpDetailReport.md | 51 +- .../Get-DlpDetectionsReport.md | 59 +- .../Get-DlpEdmSchema.md | 15 +- .../Get-DlpIncidentDetailReport.md | 51 +- .../Get-DlpKeywordDictionary.md | 15 +- .../Get-DlpPolicy.md | 19 +- .../Get-DlpPolicyTemplate.md | 19 +- .../Get-DlpSensitiveInformationType.md | 31 +- ...-DlpSensitiveInformationTypeRulePackage.md | 19 +- .../Get-DlpSiDetectionsReport.md | 19 +- .../Get-DnssecStatusForVerifiedDomain.md | 35 +- .../Get-DomainController.md | 27 +- .../Get-DynamicDistributionGroup.md | 87 +- .../Get-DynamicDistributionGroupMember.md | 27 +- .../Get-EOPProtectionPolicyRule.md | 19 +- .../Get-EXOCasMailbox.md | 80 +- .../Get-EXOMailbox.md | 92 +- .../Get-EXOMailboxFolderPermission.md | 36 +- .../Get-EXOMailboxFolderStatistics.md | 52 +- .../Get-EXOMailboxPermission.md | 44 +- .../Get-EXOMailboxStatistics.md | 56 +- .../Get-EXOMobileDeviceStatistics.md | 60 +- .../Get-EXORecipient.md | 68 +- .../Get-EXORecipientPermission.md | 40 +- .../Get-EcpVirtualDirectory.md | 31 +- .../Get-EdgeSubscription.md | 19 +- .../Get-EdgeSyncServiceConfig.md | 23 +- ...t-EligibleDistributionGroupForMigration.md | 27 +- .../Get-EmailAddressPolicy.md | 23 +- .../Get-EmailTenantSettings.md | 15 +- .../Get-EtrLimits.md | 11 +- .../Get-EventLogLevel.md | 23 +- .../Get-EventsFromEmailConfiguration.md | 15 +- .../Get-ExchangeAssistanceConfig.md | 19 +- .../Get-ExchangeCertificate.md | 35 +- .../Get-ExchangeDiagnosticInfo.md | 31 +- .../Get-ExchangeFeature.md | 26 +- .../Get-ExchangeServer.md | 27 +- .../Get-ExchangeServerAccessLicense.md | 11 +- .../Get-ExchangeServerAccessLicenseUser.md | 15 +- .../Get-ExchangeSettings.md | 67 +- .../Get-ExoInformationBarrierPolicy.md | 19 +- .../Get-ExoInformationBarrierRelationship.md | 19 +- .../Get-ExoInformationBarrierSegment.md | 19 +- .../Get-ExoPhishSimOverrideRule.md | 31 +- .../Get-ExoSecOpsOverrideRule.md | 31 +- .../Get-ExternalInOutlook.md | 15 +- .../Get-FailedContentIndexDocuments.md | 59 +- .../Get-FeatureConfiguration.md | 22 +- .../Get-FederatedDomainProof.md | 23 +- .../Get-FederatedOrganizationIdentifier.md | 23 +- .../Get-FederationInformation.md | 27 +- .../Get-FederationTrust.md | 19 +- .../Get-FilePlanPropertyAuthority.md | 10 +- .../Get-FilePlanPropertyCategory.md | 12 +- .../Get-FilePlanPropertyCitation.md | 10 +- .../Get-FilePlanPropertyDepartment.md | 10 +- .../Get-FilePlanPropertyReferenceId.md | 10 +- .../Get-FilePlanPropertyStructure.md | 10 +- .../Get-FilePlanPropertySubCategory.md | 10 +- .../Get-FocusedInbox.md | 19 +- .../Get-ForeignConnector.md | 19 +- .../Get-FrontendTransportService.md | 19 +- .../Get-GlobalAddressList.md | 23 +- .../Get-GlobalMonitoringOverride.md | 15 +- .../Get-Group.md | 55 +- .../Get-HealthReport.md | 35 +- .../Get-HistoricalSearch.md | 15 +- .../Get-HoldCompliancePolicy.md | 19 +- .../Get-HoldComplianceRule.md | 19 +- .../Get-HostedConnectionFilterPolicy.md | 15 +- .../Get-HostedContentFilterPolicy.md | 15 +- .../Get-HostedContentFilterRule.md | 23 +- .../Get-HostedOutboundSpamFilterPolicy.md | 15 +- .../Get-HostedOutboundSpamFilterRule.md | 19 +- .../Get-HybridConfiguration.md | 15 +- .../Get-HybridMailflowDatacenterIPs.md | 11 +- .../Get-IPAllowListConfig.md | 15 +- .../Get-IPAllowListEntry.md | 27 +- .../Get-IPAllowListProvider.md | 19 +- .../Get-IPAllowListProvidersConfig.md | 15 +- .../Get-IPBlockListConfig.md | 15 +- .../Get-IPBlockListEntry.md | 27 +- .../Get-IPBlockListProvider.md | 19 +- .../Get-IPBlockListProvidersConfig.md | 15 +- .../Get-IPv6StatusForAcceptedDomain.md | 22 +- .../Get-IRMConfiguration.md | 15 +- .../Get-ImapSettings.md | 19 +- .../Get-InboundConnector.md | 19 +- .../Get-InboxRule.md | 55 +- ...rmationBarrierPoliciesApplicationStatus.md | 19 +- .../Get-InformationBarrierPolicy.md | 19 +- .../Get-InformationBarrierRecipientStatus.md | 19 +- .../Get-IntraOrganizationConfiguration.md | 15 +- .../Get-IntraOrganizationConnector.md | 19 +- .../Get-JournalRule.md | 19 +- .../Get-Label.md | 27 +- .../Get-LabelPolicy.md | 19 +- .../Get-LinkedUser.md | 35 +- .../Get-LogonStatistics.md | 27 +- .../Get-M365DataAtRestEncryptionPolicy.md | 27 +- ...365DataAtRestEncryptionPolicyAssignment.md | 13 +- .../Get-MailContact.md | 55 +- .../Get-MailDetailATPReport.md | 67 +- .../Get-MailDetailDlpPolicyReport.md | 71 +- .../Get-MailDetailEncryptionReport.md | 59 +- .../Get-MailDetailTransportRuleReport.md | 67 +- .../Get-MailFilterListReport.md | 27 +- .../Get-MailPublicFolder.md | 55 +- .../Get-MailTrafficATPReport.md | 67 +- .../Get-MailTrafficEncryptionReport.md | 55 +- .../Get-MailTrafficPolicyReport.md | 63 +- .../Get-MailTrafficSummaryReport.md | 47 +- .../Get-MailUser.md | 67 +- .../Get-Mailbox.md | 143 +- .../Get-MailboxAuditBypassAssociation.md | 23 +- .../Get-MailboxAutoReplyConfiguration.md | 35 +- .../Get-MailboxCalendarConfiguration.md | 36 +- .../Get-MailboxCalendarFolder.md | 23 +- .../Get-MailboxDatabase.md | 43 +- .../Get-MailboxDatabaseCopyStatus.md | 43 +- .../Get-MailboxExportRequest.md | 68 +- .../Get-MailboxExportRequestStatistics.md | 51 +- .../Get-MailboxFolder.md | 35 +- .../Get-MailboxFolderPermission.md | 39 +- .../Get-MailboxFolderStatistics.md | 80 +- .../Get-MailboxIRMAccess.md | 19 +- .../Get-MailboxImportRequest.md | 68 +- .../Get-MailboxImportRequestStatistics.md | 55 +- .../Get-MailboxJunkEmailConfiguration.md | 31 +- .../Get-MailboxLocation.md | 43 +- .../Get-MailboxMessageConfiguration.md | 39 +- .../Get-MailboxPermission.md | 63 +- .../Get-MailboxPlan.md | 39 +- .../Get-MailboxRegionalConfiguration.md | 48 +- .../Get-MailboxRepairRequest.md | 39 +- .../Get-MailboxRestoreRequest.md | 59 +- .../Get-MailboxRestoreRequestStatistics.md | 55 +- .../Get-MailboxSearch.md | 44 +- .../Get-MailboxSentItemsConfiguration.md | 19 +- .../Get-MailboxServer.md | 23 +- .../Get-MailboxSpellingConfiguration.md | 19 +- .../Get-MailboxStatistics.md | 71 +- .../Get-MailboxTransportService.md | 19 +- .../Get-MailboxUserConfiguration.md | 31 +- .../Get-MailflowStatusReport.md | 43 +- .../Get-MalwareFilterPolicy.md | 19 +- .../Get-MalwareFilterRule.md | 23 +- .../Get-MalwareFilteringServer.md | 19 +- .../Get-ManagedContentSettings.md | 23 +- .../Get-ManagedFolder.md | 23 +- .../Get-ManagedFolderMailboxPolicy.md | 19 +- .../Get-ManagementRole.md | 60 +- .../Get-ManagementRoleAssignment.md | 99 +- .../Get-ManagementRoleEntry.md | 35 +- .../Get-ManagementScope.md | 27 +- .../Get-MapiVirtualDirectory.md | 31 +- .../Get-Message.md | 63 +- .../Get-MessageCategory.md | 23 +- .../Get-MessageClassification.md | 23 +- .../Get-MessageTrace.md | 59 +- .../Get-MessageTraceDetail.md | 55 +- .../Get-MessageTraceDetailV2.md | 43 +- .../Get-MessageTraceV2.md | 63 +- .../Get-MessageTrackingLog.md | 71 +- .../Get-MessageTrackingReport.md | 55 +- .../Get-MigrationBatch.md | 51 +- .../Get-MigrationConfig.md | 27 +- .../Get-MigrationEndpoint.md | 43 +- .../Get-MigrationStatistics.md | 31 +- .../Get-MigrationUser.md | 51 +- .../Get-MigrationUserStatistics.md | 55 +- .../Get-MobileDevice.md | 59 +- .../Get-MobileDeviceMailboxPolicy.md | 19 +- .../Get-MobileDeviceStatistics.md | 55 +- .../Get-MonitoringItemHelp.md | 19 +- .../Get-MonitoringItemIdentity.md | 19 +- .../Get-MoveRequest.md | 91 +- .../Get-MoveRequestStatistics.md | 63 +- .../Get-MxRecordReport.md | 19 +- .../Get-MyAnalyticsFeatureConfig.md | 19 +- .../Get-NetworkConnectionInfo.md | 19 +- .../Get-Notification.md | 52 +- .../Get-OMEConfiguration.md | 15 +- .../Get-OMEMessageStatus.md | 15 +- .../Get-OabVirtualDirectory.md | 31 +- .../Get-OfflineAddressBook.md | 23 +- .../Get-OnPremisesOrganization.md | 15 +- .../Get-OnlineMeetingConfiguration.md | 19 +- .../Get-OrganizationConfig.md | 15 +- .../Get-OrganizationRelationship.md | 19 +- .../Get-OrganizationSegment.md | 15 +- .../Get-OrganizationalUnit.md | 35 +- .../Get-OutboundConnector.md | 27 +- .../Get-OutboundConnectorReport.md | 19 +- .../Get-OutlookAnywhere.md | 31 +- .../Get-OutlookProtectionRule.md | 19 +- .../Get-OutlookProvider.md | 19 +- .../Get-OwaMailboxPolicy.md | 19 +- .../Get-OwaVirtualDirectory.md | 31 +- .../Get-PartnerApplication.md | 23 +- .../Get-PendingDelicenseUser.md | 23 +- .../Get-PendingFederatedDomain.md | 11 +- .../Get-PerimeterConfig.md | 15 +- .../Get-PhishSimOverridePolicy.md | 19 +- .../Get-Place.md | 31 +- .../Get-PolicyConfig.md | 15 +- .../Get-PolicyTipConfig.md | 31 +- .../Get-PopSettings.md | 19 +- .../Get-PowerShellVirtualDirectory.md | 31 +- .../Get-ProtectionAlert.md | 19 +- .../Get-PublicFolder.md | 51 +- ...et-PublicFolderAdministrativePermission.md | 31 +- .../Get-PublicFolderClientPermission.md | 35 +- .../Get-PublicFolderDatabase.md | 35 +- .../Get-PublicFolderItemStatistics.md | 31 +- .../Get-PublicFolderMailboxDiagnostics.md | 35 +- ...Get-PublicFolderMailboxMigrationRequest.md | 47 +- ...FolderMailboxMigrationRequestStatistics.md | 51 +- .../Get-PublicFolderMigrationRequest.md | 47 +- ...-PublicFolderMigrationRequestStatistics.md | 43 +- .../Get-PublicFolderMoveRequest.md | 55 +- .../Get-PublicFolderMoveRequestStatistics.md | 51 +- .../Get-PublicFolderStatistics.md | 31 +- .../Get-QuarantineMessage.md | 107 +- .../Get-QuarantineMessageHeader.md | 23 +- .../Get-QuarantinePolicy.md | 19 +- .../Get-Queue.md | 59 +- .../Get-QueueDigest.md | 47 +- .../Get-RMSTemplate.md | 31 +- .../Get-ReceiveConnector.md | 23 +- .../Get-Recipient.md | 99 +- .../Get-RecipientFilterConfig.md | 19 +- .../Get-RecipientPermission.md | 31 +- .../Get-RecipientStatisticsReport.md | 11 +- ...-RecordReviewNotificationTemplateConfig.md | 11 +- .../Get-RecoverableItems.md | 72 +- .../Get-RegulatoryComplianceUI.md | 6 +- .../Get-RemoteDomain.md | 23 +- .../Get-RemoteMailbox.md | 55 +- .../Get-ReportExecutionInstance.md | 19 +- .../Get-ReportSubmissionPolicy.md | 15 +- .../Get-ReportSubmissionRule.md | 19 +- .../Get-ResourceConfig.md | 19 +- .../Get-ResubmitRequest.md | 19 +- .../Get-RetentionCompliancePolicy.md | 43 +- .../Get-RetentionComplianceRule.md | 23 +- .../Get-RetentionEvent.md | 23 +- .../Get-RetentionPolicy.md | 19 +- .../Get-RetentionPolicyTag.md | 35 +- .../Get-ReviewItems.md | 27 +- .../Get-RoleAssignmentPolicy.md | 19 +- .../Get-RoleGroup.md | 39 +- .../Get-RoleGroupMember.md | 27 +- .../Get-RoutingGroupConnector.md | 19 +- .../Get-RpcClientAccess.md | 19 +- .../Get-SCInsights.md | 15 +- .../Get-SafeAttachmentPolicy.md | 15 +- .../Get-SafeAttachmentRule.md | 19 +- .../Get-SafeLinksAggregateReport.md | 31 +- .../Get-SafeLinksDetailReport.md | 43 +- .../Get-SafeLinksPolicy.md | 15 +- .../Get-SafeLinksRule.md | 19 +- .../Get-SearchDocumentFormat.md | 19 +- .../Get-SecOpsOverridePolicy.md | 19 +- .../Get-SecurityPrincipal.md | 43 +- .../Get-SendConnector.md | 19 +- .../Get-SenderFilterConfig.md | 19 +- .../Get-SenderIdConfig.md | 15 +- .../Get-SenderReputationConfig.md | 15 +- .../Get-ServerComponentState.md | 23 +- .../Get-ServerHealth.md | 23 +- .../Get-ServerMonitoringOverride.md | 15 +- .../Get-ServiceDeliveryReport.md | 19 +- .../Get-ServicePrincipal.md | 19 +- .../Get-SettingOverride.md | 19 +- .../Get-SharingPolicy.md | 19 +- .../Get-SiteMailbox.md | 39 +- .../Get-SiteMailboxDiagnostics.md | 31 +- .../Get-SiteMailboxProvisioningPolicy.md | 19 +- .../Get-SmimeConfig.md | 15 +- .../Get-SmtpDaneInboundStatus.md | 15 +- .../Get-SpoofIntelligenceInsight.md | 15 +- .../Get-SpoofMailReport.md | 43 +- .../Get-StoreUsageStatistics.md | 39 +- .../Get-SupervisoryReviewActivity.md | 23 +- ...-SupervisoryReviewOverallProgressReport.md | 27 +- .../Get-SupervisoryReviewPolicyReport.md | 31 +- .../Get-SupervisoryReviewPolicyV2.md | 15 +- .../Get-SupervisoryReviewReport.md | 35 +- .../Get-SupervisoryReviewRule.md | 23 +- .../Get-SupervisoryReviewTopCasesReport.md | 27 +- .../Get-SweepRule.md | 39 +- .../Get-SystemMessage.md | 23 +- .../Get-TeamsProtectionPolicy.md | 15 +- .../Get-TeamsProtectionPolicyRule.md | 19 +- .../Get-TenantAllowBlockListItems.md | 43 +- .../Get-TenantAllowBlockListSpoofItems.md | 23 +- .../Get-TextMessagingAccount.md | 31 +- .../Get-ThrottlingPolicy.md | 31 +- .../Get-ThrottlingPolicyAssociation.md | 35 +- .../Get-TransportAgent.md | 23 +- .../Get-TransportConfig.md | 19 +- .../Get-TransportPipeline.md | 15 +- .../Get-TransportRule.md | 39 +- .../Get-TransportRuleAction.md | 15 +- .../Get-TransportRulePredicate.md | 15 +- .../Get-TransportServer.md | 19 +- .../Get-TransportService.md | 19 +- .../Get-Trust.md | 15 +- .../Get-UMActiveCalls.md | 31 +- .../Get-UMAutoAttendant.md | 23 +- .../Get-UMCallAnsweringRule.md | 23 +- .../Get-UMCallDataRecord.md | 19 +- .../Get-UMCallRouterSettings.md | 19 +- .../Get-UMCallSummaryReport.md | 27 +- .../Get-UMDialPlan.md | 19 +- .../Get-UMHuntGroup.md | 23 +- .../Get-UMIPGateway.md | 23 +- .../Get-UMMailbox.md | 51 +- .../Get-UMMailboxPIN.md | 39 +- .../Get-UMMailboxPolicy.md | 23 +- .../Get-UMService.md | 19 +- .../Get-UmServer.md | 19 +- .../Get-UnifiedAuditLogRetentionPolicy.md | 27 +- .../Get-UnifiedGroup.md | 59 +- .../Get-UnifiedGroupLinks.md | 23 +- .../Get-User.md | 83 +- .../Get-UserBriefingConfig.md | 19 +- .../Get-UserPhoto.md | 63 +- .../Get-UserPrincipalNamesSuffix.md | 15 +- .../Get-VivaInsightsSettings.md | 23 +- .../Get-VivaModuleFeature.md | 24 +- .../Get-VivaModuleFeatureEnablement.md | 12 +- .../Get-VivaModuleFeaturePolicy.md | 47 +- .../Get-VivaOrgInsightsDelegatedRole.md | 18 +- .../Get-WebServicesVirtualDirectory.md | 31 +- .../Get-X400AuthoritativeDomain.md | 19 +- .../Get-eDiscoveryCaseAdmin.md | 19 +- .../Import-DlpPolicyCollection.md | 35 +- .../Import-DlpPolicyTemplate.md | 23 +- .../Import-ExchangeCertificate.md | 51 +- .../Import-FilePlanProperty.md | 30 +- .../Import-JournalRuleCollection.md | 31 +- .../Import-RecipientDataProperty.md | 39 +- .../Import-TransportRuleCollection.md | 35 +- .../Import-UMPrompt.md | 43 +- .../Install-TransportAgent.md | 39 +- .../Install-UnifiedCompliancePrerequisite.md | 23 +- .../Invoke-ComplianceSearchActionStep.md | 23 +- .../Invoke-ComplianceSecurityFilterAction.md | 39 +- .../Invoke-HoldRemovalAction.md | 39 +- .../Invoke-MonitoringProbe.md | 55 +- .../Mount-Database.md | 39 +- .../Move-ActiveMailboxDatabase.md | 87 +- .../Move-AddressList.md | 31 +- .../Move-DatabasePath.md | 47 +- .../Move-OfflineAddressBook.md | 31 +- .../New-ATPBuiltInProtectionRule.md | 47 +- .../New-ATPProtectionPolicyRule.md | 67 +- .../New-AcceptedDomain.md | 35 +- .../New-ActiveSyncDeviceAccessRule.md | 35 +- .../New-ActiveSyncMailboxPolicy.md | 239 +- .../New-ActiveSyncVirtualDirectory.md | 79 +- .../New-AdaptiveScope.md | 35 +- .../New-AddressBookPolicy.md | 43 +- .../New-AddressList.md | 119 +- .../New-AddressRewriteEntry.md | 43 +- .../New-AdminAuditLogSearch.md | 59 +- .../New-AntiPhishPolicy.md | 179 +- .../New-AntiPhishRule.md | 63 +- .../New-App.md | 123 +- .../New-AppRetentionCompliancePolicy.md | 67 +- .../New-AppRetentionComplianceRule.md | 63 +- .../New-ApplicationAccessPolicy.md | 35 +- .../New-AuthRedirect.md | 31 +- .../New-AuthServer.md | 51 +- .../New-AuthenticationPolicy.md | 135 +- .../New-AutoSensitivityLabelPolicy.md | 143 +- .../New-AutoSensitivityLabelRule.md | 251 +- .../New-AutodiscoverVirtualDirectory.md | 87 +- .../New-AvailabilityConfig.md | 27 +- .../New-AvailabilityReportOutage.md | 47 +- .../New-CaseHoldPolicy.md | 51 +- .../New-CaseHoldRule.md | 39 +- .../New-ClassificationRuleCollection.md | 27 +- .../New-ClientAccessArray.md | 35 +- .../New-ClientAccessRule.md | 95 +- .../New-ComplianceCase.md | 47 +- .../New-ComplianceRetentionEvent.md | 59 +- .../New-ComplianceRetentionEventType.md | 27 +- .../New-ComplianceSearch.md | 91 +- .../New-ComplianceSearchAction.md | 130 +- .../New-ComplianceSecurityFilter.md | 43 +- .../New-ComplianceTag.md | 130 +- .../New-DataClassification.md | 43 +- .../New-DataEncryptionPolicy.md | 39 +- .../New-DatabaseAvailabilityGroup.md | 55 +- .../New-DatabaseAvailabilityGroupNetwork.md | 47 +- .../New-DeliveryAgentConnector.md | 63 +- .../New-DeviceConditionalAccessPolicy.md | 35 +- .../New-DeviceConditionalAccessRule.md | 223 +- .../New-DeviceConfigurationPolicy.md | 35 +- .../New-DeviceConfigurationRule.md | 219 +- .../New-DeviceTenantPolicy.md | 31 +- .../New-DeviceTenantRule.md | 35 +- .../New-DistributionGroup.md | 119 +- .../New-DkimSigningConfig.md | 43 +- .../New-DlpCompliancePolicy.md | 191 +- .../New-DlpComplianceRule.md | 627 +- .../New-DlpEdmSchema.md | 23 +- .../New-DlpFingerprint.md | 35 +- .../New-DlpKeywordDictionary.md | 39 +- .../New-DlpPolicy.md | 51 +- .../New-DlpSensitiveInformationType.md | 47 +- ...-DlpSensitiveInformationTypeRulePackage.md | 27 +- .../New-DynamicDistributionGroup.md | 147 +- .../New-EOPProtectionPolicyRule.md | 71 +- .../New-EcpVirtualDirectory.md | 63 +- .../New-EdgeSubscription.md | 51 +- .../New-EdgeSyncServiceConfig.md | 79 +- .../New-EmailAddressPolicy.md | 135 +- .../New-ExchangeCertificate.md | 91 +- .../New-ExchangeSettings.md | 31 +- .../New-ExoPhishSimOverrideRule.md | 43 +- .../New-ExoSecOpsOverrideRule.md | 35 +- .../New-FeatureConfiguration.md | 38 +- .../New-FederationTrust.md | 59 +- .../New-FilePlanPropertyAuthority.md | 18 +- .../New-FilePlanPropertyCategory.md | 18 +- .../New-FilePlanPropertyCitation.md | 26 +- .../New-FilePlanPropertyDepartment.md | 18 +- .../New-FilePlanPropertyReferenceId.md | 18 +- .../New-FilePlanPropertySubCategory.md | 22 +- .../New-Fingerprint.md | 27 +- .../New-ForeignConnector.md | 39 +- .../New-GlobalAddressList.md | 111 +- .../New-HoldCompliancePolicy.md | 47 +- .../New-HoldComplianceRule.md | 55 +- .../New-HostedContentFilterPolicy.md | 242 +- .../New-HostedContentFilterRule.md | 63 +- .../New-HostedOutboundSpamFilterPolicy.md | 59 +- .../New-HostedOutboundSpamFilterRule.md | 63 +- .../New-HybridConfiguration.md | 71 +- .../New-InboundConnector.md | 107 +- .../New-InboxRule.md | 295 +- .../New-InformationBarrierPolicy.md | 55 +- .../New-IntraOrganizationConnector.md | 43 +- .../New-JournalRule.md | 43 +- .../New-Label.md | 331 +- .../New-LabelPolicy.md | 99 +- .../New-M365DataAtRestEncryptionPolicy.md | 39 +- .../New-MailContact.md | 91 +- .../New-MailMessage.md | 35 +- .../New-MailUser.md | 161 +- .../New-Mailbox.md | 336 +- .../New-MailboxAuditLogSearch.md | 67 +- .../New-MailboxDatabase.md | 84 +- .../New-MailboxExportRequest.md | 169 +- .../New-MailboxFolder.md | 31 +- .../New-MailboxImportRequest.md | 172 +- .../New-MailboxRepairRequest.md | 51 +- .../New-MailboxRestoreRequest.md | 192 +- .../New-MailboxSearch.md | 123 +- .../New-MalwareFilterPolicy.md | 123 +- .../New-MalwareFilterRule.md | 67 +- .../New-ManagedContentSettings.md | 71 +- .../New-ManagedFolder.md | 59 +- .../New-ManagedFolderMailboxPolicy.md | 31 +- .../New-ManagementRole.md | 47 +- .../New-ManagementRoleAssignment.md | 99 +- .../New-ManagementScope.md | 59 +- .../New-MapiVirtualDirectory.md | 59 +- .../New-MessageClassification.md | 59 +- .../New-MigrationBatch.md | 304 +- .../New-MigrationEndpoint.md | 211 +- .../New-MobileDeviceMailboxPolicy.md | 243 +- .../New-MoveRequest.md | 238 +- .../New-OMEConfiguration.md | 67 +- .../New-OabVirtualDirectory.md | 71 +- .../New-OfflineAddressBook.md | 79 +- .../New-OnPremisesOrganization.md | 51 +- .../New-OrganizationRelationship.md | 107 +- .../New-OrganizationSegment.md | 27 +- .../New-OutboundConnector.md | 87 +- .../New-OutlookProtectionRule.md | 59 +- .../New-OutlookProvider.md | 27 +- .../New-OwaMailboxPolicy.md | 31 +- .../New-OwaVirtualDirectory.md | 75 +- .../New-PartnerApplication.md | 71 +- .../New-PhishSimOverridePolicy.md | 39 +- .../New-PolicyTipConfig.md | 31 +- .../New-PowerShellVirtualDirectory.md | 67 +- .../New-ProtectionAlert.md | 135 +- .../New-PublicFolder.md | 43 +- .../New-PublicFolderDatabase.md | 39 +- .../New-PublicFolderDatabaseRepairRequest.md | 35 +- .../New-PublicFolderMigrationRequest.md | 95 +- .../New-PublicFolderMoveRequest.md | 83 +- .../New-QuarantinePermissions.md | 43 +- .../New-QuarantinePolicy.md | 103 +- .../New-ReceiveConnector.md | 281 +- .../New-RemoteDomain.md | 31 +- .../New-RemoteMailbox.md | 145 +- .../New-ReportSubmissionPolicy.md | 199 +- .../New-ReportSubmissionRule.md | 39 +- .../New-RetentionCompliancePolicy.md | 131 +- .../New-RetentionComplianceRule.md | 79 +- .../New-RetentionPolicy.md | 43 +- .../New-RetentionPolicyTag.md | 99 +- .../New-RoleAssignmentPolicy.md | 39 +- .../New-RoleGroup.md | 87 +- .../New-RoutingGroupConnector.md | 47 +- .../New-RpcClientAccess.md | 39 +- .../New-SafeAttachmentPolicy.md | 55 +- .../New-SafeAttachmentRule.md | 63 +- .../New-SafeLinksPolicy.md | 87 +- .../New-SafeLinksRule.md | 63 +- .../New-SearchDocumentFormat.md | 43 +- .../New-SecOpsOverridePolicy.md | 43 +- .../New-SendConnector.md | 175 +- .../New-ServicePrincipal.md | 39 +- .../New-SettingOverride.md | 59 +- .../New-SharingPolicy.md | 39 +- .../New-SiteMailbox.md | 55 +- .../New-SiteMailboxProvisioningPolicy.md | 51 +- .../New-SupervisoryReviewPolicyV2.md | 51 +- .../New-SupervisoryReviewRule.md | 107 +- .../New-SweepRule.md | 71 +- .../New-SyncMailPublicFolder.md | 159 +- .../New-SystemMessage.md | 43 +- .../New-TeamsProtectionPolicy.md | 43 +- .../New-TeamsProtectionPolicyRule.md | 51 +- .../New-TenantAllowBlockListItems.md | 59 +- .../New-TenantAllowBlockListSpoofItems.md | 39 +- .../New-ThrottlingPolicy.md | 603 +- .../New-TransportRule.md | 719 +- .../New-UMAutoAttendant.md | 47 +- .../New-UMCallAnsweringRule.md | 63 +- .../New-UMDialPlan.md | 59 +- .../New-UMHuntGroup.md | 39 +- .../New-UMIPGateway.md | 39 +- .../New-UMMailboxPolicy.md | 31 +- .../New-UnifiedAuditLogRetentionPolicy.md | 47 +- .../New-UnifiedGroup.md | 127 +- .../New-WebServicesVirtualDirectory.md | 111 +- .../New-X400AuthoritativeDomain.md | 35 +- .../Preview-QuarantineMessage.md | 23 +- .../Redirect-Message.md | 27 +- .../Release-QuarantineMessage.md | 81 +- .../Remove-ADPermission.md | 89 +- .../Remove-ATPProtectionPolicyRule.md | 23 +- .../Remove-AcceptedDomain.md | 27 +- .../Remove-ActiveSyncDevice.md | 27 +- .../Remove-ActiveSyncDeviceAccessRule.md | 27 +- .../Remove-ActiveSyncDeviceClass.md | 27 +- .../Remove-ActiveSyncMailboxPolicy.md | 31 +- .../Remove-ActiveSyncVirtualDirectory.md | 27 +- .../Remove-AdaptiveScope.md | 27 +- .../Remove-AddressBookPolicy.md | 27 +- .../Remove-AddressList.md | 31 +- .../Remove-AddressRewriteEntry.md | 27 +- .../Remove-AntiPhishPolicy.md | 27 +- .../Remove-AntiPhishRule.md | 23 +- .../Remove-App.md | 43 +- .../Remove-AppRetentionCompliancePolicy.md | 27 +- .../Remove-AppRetentionComplianceRule.md | 27 +- .../Remove-ApplicationAccessPolicy.md | 23 +- .../Remove-AttachmentFilterEntry.md | 27 +- .../Remove-AuthRedirect.md | 27 +- .../Remove-AuthServer.md | 27 +- .../Remove-AuthenticationPolicy.md | 31 +- .../Remove-AutoSensitivityLabelPolicy.md | 23 +- .../Remove-AutoSensitivityLabelRule.md | 23 +- .../Remove-AutodiscoverVirtualDirectory.md | 27 +- .../Remove-AvailabilityAddressSpace.md | 27 +- .../Remove-AvailabilityConfig.md | 23 +- .../Remove-AvailabilityReportOutage.md | 39 +- .../Remove-BlockedConnector.md | 19 +- .../Remove-BlockedSenderAddress.md | 19 +- .../Remove-CalendarEvents.md | 43 +- .../Remove-CaseHoldPolicy.md | 27 +- .../Remove-CaseHoldRule.md | 27 +- .../Remove-ClassificationRuleCollection.md | 27 +- .../Remove-ClientAccessArray.md | 27 +- .../Remove-ClientAccessRule.md | 27 +- .../Remove-ComplianceCase.md | 27 +- .../Remove-ComplianceCaseMember.md | 27 +- .../Remove-ComplianceRetentionEventType.md | 27 +- .../Remove-ComplianceSearch.md | 23 +- .../Remove-ComplianceSearchAction.md | 23 +- .../Remove-ComplianceSecurityFilter.md | 23 +- .../Remove-ComplianceTag.md | 31 +- .../Remove-ContentFilterPhrase.md | 31 +- .../Remove-DataClassification.md | 27 +- .../Remove-DatabaseAvailabilityGroup.md | 27 +- ...Remove-DatabaseAvailabilityGroupNetwork.md | 27 +- .../Remove-DatabaseAvailabilityGroupServer.md | 39 +- .../Remove-DeliveryAgentConnector.md | 27 +- .../Remove-DeviceConditionalAccessPolicy.md | 23 +- .../Remove-DeviceConditionalAccessRule.md | 23 +- .../Remove-DeviceConfigurationPolicy.md | 23 +- .../Remove-DeviceConfigurationRule.md | 23 +- .../Remove-DeviceTenantPolicy.md | 23 +- .../Remove-DeviceTenantRule.md | 23 +- .../Remove-DistributionGroup.md | 35 +- .../Remove-DistributionGroupMember.md | 35 +- .../Remove-DlpCompliancePolicy.md | 23 +- .../Remove-DlpComplianceRule.md | 23 +- .../Remove-DlpEdmSchema.md | 23 +- .../Remove-DlpKeywordDictionary.md | 23 +- .../Remove-DlpPolicy.md | 27 +- .../Remove-DlpPolicyTemplate.md | 27 +- .../Remove-DlpSensitiveInformationType.md | 23 +- ...-DlpSensitiveInformationTypeRulePackage.md | 23 +- .../Remove-DynamicDistributionGroup.md | 31 +- .../Remove-EOPProtectionPolicyRule.md | 23 +- .../Remove-EcpVirtualDirectory.md | 27 +- .../Remove-EdgeSubscription.md | 31 +- .../Remove-EmailAddressPolicy.md | 27 +- .../Remove-ExchangeCertificate.md | 35 +- .../Remove-ExoPhishSimOverrideRule.md | 27 +- .../Remove-ExoSecOpsOverrideRule.md | 27 +- .../Remove-FeatureConfiguration.md | 18 +- .../Remove-FederatedDomain.md | 35 +- .../Remove-FederationTrust.md | 27 +- .../Remove-FilePlanPropertyAuthority.md | 22 +- .../Remove-FilePlanPropertyCategory.md | 22 +- .../Remove-FilePlanPropertyCitation.md | 22 +- .../Remove-FilePlanPropertyDepartment.md | 22 +- .../Remove-FilePlanPropertyReferenceId.md | 22 +- .../Remove-FilePlanPropertySubCategory.md | 22 +- .../Remove-ForeignConnector.md | 27 +- .../Remove-GlobalAddressList.md | 27 +- .../Remove-GlobalMonitoringOverride.md | 43 +- .../Remove-HoldCompliancePolicy.md | 27 +- .../Remove-HoldComplianceRule.md | 27 +- .../Remove-HostedContentFilterPolicy.md | 23 +- .../Remove-HostedContentFilterRule.md | 23 +- .../Remove-HostedOutboundSpamFilterPolicy.md | 19 +- .../Remove-HostedOutboundSpamFilterRule.md | 23 +- .../Remove-HybridConfiguration.md | 23 +- .../Remove-IPAllowListEntry.md | 27 +- .../Remove-IPAllowListProvider.md | 27 +- .../Remove-IPBlockListEntry.md | 27 +- .../Remove-IPBlockListProvider.md | 27 +- .../Remove-InboundConnector.md | 23 +- .../Remove-InboxRule.md | 39 +- .../Remove-InformationBarrierPolicy.md | 27 +- .../Remove-IntraOrganizationConnector.md | 27 +- .../Remove-JournalRule.md | 27 +- .../Remove-Label.md | 23 +- .../Remove-LabelPolicy.md | 23 +- .../Remove-MailContact.md | 31 +- .../Remove-MailUser.md | 39 +- .../Remove-Mailbox.md | 91 +- .../Remove-MailboxDatabase.md | 27 +- .../Remove-MailboxDatabaseCopy.md | 27 +- .../Remove-MailboxExportRequest.md | 39 +- .../Remove-MailboxFolderPermission.md | 43 +- .../Remove-MailboxIRMAccess.md | 19 +- .../Remove-MailboxImportRequest.md | 39 +- .../Remove-MailboxPermission.md | 110 +- .../Remove-MailboxRepairRequest.md | 27 +- .../Remove-MailboxRestoreRequest.md | 39 +- .../Remove-MailboxSearch.md | 27 +- .../Remove-MailboxUserConfiguration.md | 31 +- .../Remove-MalwareFilterPolicy.md | 31 +- .../Remove-MalwareFilterRule.md | 27 +- .../Remove-ManagedContentSettings.md | 27 +- .../Remove-ManagedFolder.md | 27 +- .../Remove-ManagedFolderMailboxPolicy.md | 31 +- .../Remove-ManagementRole.md | 39 +- .../Remove-ManagementRoleAssignment.md | 31 +- .../Remove-ManagementRoleEntry.md | 31 +- .../Remove-ManagementScope.md | 31 +- .../Remove-MapiVirtualDirectory.md | 27 +- .../Remove-Message.md | 35 +- .../Remove-MessageClassification.md | 29 +- .../Remove-MigrationBatch.md | 35 +- .../Remove-MigrationEndpoint.md | 31 +- .../Remove-MigrationUser.md | 35 +- .../Remove-MobileDevice.md | 27 +- .../Remove-MobileDeviceMailboxPolicy.md | 31 +- .../Remove-MoveRequest.md | 43 +- .../Remove-OMEConfiguration.md | 23 +- .../Remove-OabVirtualDirectory.md | 31 +- .../Remove-OfflineAddressBook.md | 31 +- .../Remove-OnPremisesOrganization.md | 23 +- .../Remove-OrganizationRelationship.md | 27 +- .../Remove-OrganizationSegment.md | 23 +- .../Remove-OutboundConnector.md | 23 +- .../Remove-OutlookProtectionRule.md | 27 +- .../Remove-OutlookProvider.md | 27 +- .../Remove-OwaMailboxPolicy.md | 31 +- .../Remove-OwaVirtualDirectory.md | 27 +- .../Remove-PartnerApplication.md | 27 +- .../Remove-PhishSimOverridePolicy.md | 31 +- .../Remove-PolicyTipConfig.md | 27 +- .../Remove-PowerShellVirtualDirectory.md | 27 +- .../Remove-ProtectionAlert.md | 27 +- .../Remove-PublicFolder.md | 39 +- ...ve-PublicFolderAdministrativePermission.md | 90 +- .../Remove-PublicFolderClientPermission.md | 39 +- .../Remove-PublicFolderDatabase.md | 31 +- ...ove-PublicFolderMailboxMigrationRequest.md | 39 +- .../Remove-PublicFolderMigrationRequest.md | 39 +- .../Remove-PublicFolderMoveRequest.md | 39 +- .../Remove-QuarantinePolicy.md | 19 +- .../Remove-ReceiveConnector.md | 27 +- .../Remove-RecipientPermission.md | 51 +- .../Remove-RemoteDomain.md | 27 +- .../Remove-RemoteMailbox.md | 35 +- .../Remove-ReportSubmissionPolicy.md | 15 +- .../Remove-ReportSubmissionRule.md | 23 +- .../Remove-ResubmitRequest.md | 27 +- .../Remove-RetentionCompliancePolicy.md | 31 +- .../Remove-RetentionComplianceRule.md | 31 +- .../Remove-RetentionPolicy.md | 31 +- .../Remove-RetentionPolicyTag.md | 27 +- .../Remove-RoleAssignmentPolicy.md | 27 +- .../Remove-RoleGroup.md | 35 +- .../Remove-RoleGroupMember.md | 35 +- .../Remove-RoutingGroupConnector.md | 27 +- .../Remove-RpcClientAccess.md | 27 +- .../Remove-SafeAttachmentPolicy.md | 27 +- .../Remove-SafeAttachmentRule.md | 23 +- .../Remove-SafeLinksPolicy.md | 27 +- .../Remove-SafeLinksRule.md | 23 +- .../Remove-SearchDocumentFormat.md | 27 +- .../Remove-SecOpsOverridePolicy.md | 31 +- .../Remove-SendConnector.md | 27 +- .../Remove-ServerMonitoringOverride.md | 35 +- .../Remove-ServicePrincipal.md | 23 +- .../Remove-SettingOverride.md | 27 +- .../Remove-SharingPolicy.md | 27 +- .../Remove-SiteMailboxProvisioningPolicy.md | 27 +- .../Remove-StoreMailbox.md | 31 +- .../Remove-SupervisoryReviewPolicyV2.md | 27 +- .../Remove-SweepRule.md | 31 +- .../Remove-SyncMailPublicFolder.md | 27 +- .../Remove-SystemMessage.md | 27 +- .../Remove-TenantAllowBlockListItems.md | 31 +- .../Remove-TenantAllowBlockListSpoofItems.md | 27 +- .../Remove-ThrottlingPolicy.md | 31 +- .../Remove-TransportRule.md | 27 +- .../Remove-UMAutoAttendant.md | 27 +- .../Remove-UMCallAnsweringRule.md | 31 +- .../Remove-UMDialPlan.md | 27 +- .../Remove-UMHuntGroup.md | 27 +- .../Remove-UMIPGateway.md | 27 +- .../Remove-UMMailboxPolicy.md | 27 +- .../Remove-UnifiedAuditLogRetentionPolicy.md | 31 +- .../Remove-UnifiedGroup.md | 27 +- .../Remove-UnifiedGroupLinks.md | 31 +- .../Remove-UserPhoto.md | 43 +- .../Remove-VivaModuleFeaturePolicy.md | 36 +- .../Remove-VivaOrgInsightsDelegatedRole.md | 22 +- .../Remove-WebServicesVirtualDirectory.md | 31 +- .../Remove-X400AuthoritativeDomain.md | 27 +- .../Remove-eDiscoveryCaseAdmin.md | 23 +- .../Reset-ProvisioningCache.md | 43 +- .../Restore-DatabaseAvailabilityGroup.md | 43 +- .../Restore-DetailsTemplate.md | 27 +- .../Restore-Mailbox.md | 99 +- .../Restore-RecoverableItems.md | 76 +- .../Resume-MailboxDatabaseCopy.md | 39 +- .../Resume-MailboxExportRequest.md | 27 +- .../Resume-MailboxImportRequest.md | 27 +- .../Resume-MailboxRestoreRequest.md | 27 +- .../Resume-Message.md | 31 +- .../Resume-MoveRequest.md | 35 +- .../Resume-PublicFolderMigrationRequest.md | 27 +- .../Resume-PublicFolderMoveRequest.md | 27 +- .../Resume-PublicFolderReplication.md | 23 +- .../Resume-Queue.md | 31 +- .../Retry-Queue.md | 35 +- .../Rotate-DkimSigningConfig.md | 27 +- .../Search-AdminAuditLog.md | 55 +- .../Search-Mailbox.md | 75 +- .../Search-MailboxAuditLog.md | 63 +- .../Search-MessageTrackingReport.md | 63 +- .../Search-UnifiedAuditLog.md | 71 +- .../Send-TextMessagingVerificationCode.md | 27 +- .../Set-ADServerSettings.md | 47 +- .../Set-ADSite.md | 39 +- .../Set-ATPBuiltInProtectionRule.md | 39 +- .../Set-ATPProtectionPolicyRule.md | 59 +- .../Set-AcceptedDomain.md | 75 +- .../Set-AccessToCustomerDataRequest.md | 27 +- .../Set-ActiveSyncDeviceAccessRule.md | 31 +- .../Set-ActiveSyncDeviceAutoblockThreshold.md | 43 +- .../Set-ActiveSyncMailboxPolicy.md | 243 +- .../Set-ActiveSyncOrganizationSettings.md | 59 +- .../Set-ActiveSyncVirtualDirectory.md | 119 +- .../Set-AdSiteLink.md | 39 +- .../Set-AdaptiveScope.md | 44 +- .../Set-AddressBookPolicy.md | 47 +- .../Set-AddressList.md | 123 +- .../Set-AddressRewriteEntry.md | 47 +- .../Set-AdminAuditLogConfig.md | 67 +- .../Set-AntiPhishPolicy.md | 167 +- .../Set-AntiPhishRule.md | 63 +- .../Set-App.md | 51 +- .../Set-AppRetentionCompliancePolicy.md | 95 +- .../Set-AppRetentionComplianceRule.md | 63 +- .../Set-ApplicationAccessPolicy.md | 27 +- .../Set-ArcConfig.md | 27 +- .../Set-AtpPolicyForO365.md | 35 +- .../Set-AttachmentFilterListConfig.md | 39 +- .../Set-AuditConfig.md | 27 +- .../Set-AuthConfig.md | 63 +- .../Set-AuthRedirect.md | 31 +- .../Set-AuthServer.md | 59 +- .../Set-AuthenticationPolicy.md | 147 +- .../Set-AutoSensitivityLabelPolicy.md | 179 +- .../Set-AutoSensitivityLabelRule.md | 247 +- .../Set-AutodiscoverVirtualDirectory.md | 67 +- .../Set-AvailabilityConfig.md | 35 +- .../Set-AvailabilityReportOutage.md | 51 +- .../Set-CASMailbox.md | 231 +- .../Set-CASMailboxPlan.md | 55 +- .../Set-CalendarNotification.md | 59 +- .../Set-CalendarProcessing.md | 183 +- .../Set-CaseHoldPolicy.md | 63 +- .../Set-CaseHoldRule.md | 35 +- .../Set-ClassificationRuleCollection.md | 27 +- .../Set-ClientAccessArray.md | 39 +- .../Set-ClientAccessRule.md | 99 +- .../Set-ClientAccessServer.md | 75 +- .../Set-ClientAccessService.md | 51 +- .../Set-Clutter.md | 23 +- .../Set-CmdletExtensionAgent.md | 35 +- .../Set-ComplianceCase.md | 51 +- .../Set-ComplianceRetentionEventType.md | 27 +- .../Set-ComplianceSearch.md | 119 +- .../Set-ComplianceSearchAction.md | 31 +- .../Set-ComplianceSecurityFilter.md | 43 +- .../Set-ComplianceTag.md | 71 +- .../Set-Contact.md | 179 +- .../Set-ContentFilterConfig.md | 83 +- .../Set-DataClassification.md | 47 +- .../Set-DataEncryptionPolicy.md | 72 +- .../Set-DatabaseAvailabilityGroup.md | 147 +- .../Set-DatabaseAvailabilityGroupNetwork.md | 47 +- .../Set-DefaultTenantBriefingConfig.md | 20 +- ...t-DefaultTenantMyAnalyticsFeatureConfig.md | 28 +- .../Set-DeliveryAgentConnector.md | 71 +- .../Set-DetailsTemplate.md | 31 +- .../Set-DeviceConditionalAccessPolicy.md | 39 +- .../Set-DeviceConditionalAccessRule.md | 223 +- .../Set-DeviceConfigurationPolicy.md | 39 +- .../Set-DeviceConfigurationRule.md | 219 +- .../Set-DeviceTenantPolicy.md | 39 +- .../Set-DeviceTenantRule.md | 39 +- .../Set-DistributionGroup.md | 295 +- .../Set-DkimSigningConfig.md | 43 +- .../Set-DlpCompliancePolicy.md | 255 +- .../Set-DlpComplianceRule.md | 615 +- .../Set-DlpEdmSchema.md | 23 +- .../Set-DlpKeywordDictionary.md | 39 +- .../Set-DlpPolicy.md | 43 +- .../Set-DlpSensitiveInformationType.md | 55 +- ...-DlpSensitiveInformationTypeRulePackage.md | 23 +- .../Set-DynamicDistributionGroup.md | 351 +- .../Set-EOPProtectionPolicyRule.md | 59 +- .../Set-EcpVirtualDirectory.md | 87 +- .../Set-EdgeSyncServiceConfig.md | 83 +- .../Set-EmailAddressPolicy.md | 135 +- .../Set-EmailTenantSettings.md | 35 +- .../Set-EventLogLevel.md | 27 +- .../Set-EventsFromEmailConfiguration.md | 55 +- .../Set-ExchangeAssistanceConfig.md | 95 +- .../Set-ExchangeFeature.md | 34 +- .../Set-ExchangeServer.md | 87 +- .../Set-ExchangeSettings.md | 157 +- .../Set-ExoPhishSimOverrideRule.md | 47 +- .../Set-ExoSecOpsOverrideRule.md | 31 +- .../Set-ExternalInOutlook.md | 23 +- .../Set-FeatureConfiguration.md | 34 +- .../Set-FederatedOrganizationIdentifier.md | 47 +- .../Set-FederationTrust.md | 51 +- .../Set-FilePlanPropertyAuthority.md | 22 +- .../Set-FilePlanPropertyCategory.md | 22 +- .../Set-FilePlanPropertyCitation.md | 30 +- .../Set-FilePlanPropertyDepartment.md | 22 +- .../Set-FilePlanPropertyReferenceId.md | 22 +- .../Set-FilePlanPropertySubCategory.md | 22 +- .../Set-FocusedInbox.md | 23 +- .../Set-ForeignConnector.md | 71 +- .../Set-FrontendTransportService.md | 187 +- .../Set-GlobalAddressList.md | 119 +- .../Set-Group.md | 79 +- .../Set-HoldCompliancePolicy.md | 63 +- .../Set-HoldComplianceRule.md | 51 +- .../Set-HostedConnectionFilterPolicy.md | 47 +- .../Set-HostedContentFilterPolicy.md | 243 +- .../Set-HostedContentFilterRule.md | 63 +- .../Set-HostedOutboundSpamFilterPolicy.md | 63 +- .../Set-HostedOutboundSpamFilterRule.md | 63 +- .../Set-HybridConfiguration.md | 75 +- .../Set-IPAllowListConfig.md | 35 +- .../Set-IPAllowListProvider.md | 55 +- .../Set-IPAllowListProvidersConfig.md | 35 +- .../Set-IPBlockListConfig.md | 43 +- .../Set-IPBlockListProvider.md | 59 +- .../Set-IPBlockListProvidersConfig.md | 39 +- .../Set-IRMConfiguration.md | 107 +- .../Set-ImapSettings.md | 135 +- .../Set-InboundConnector.md | 107 +- .../Set-InboxRule.md | 291 +- .../Set-InformationBarrierPolicy.md | 51 +- .../Set-IntraOrganizationConnector.md | 43 +- .../Set-JournalRule.md | 43 +- .../Set-Label.md | 327 +- .../Set-LabelPolicy.md | 159 +- .../Set-LinkedUser.md | 27 +- .../Set-M365DataAtRestEncryptionPolicy.md | 47 +- ...365DataAtRestEncryptionPolicyAssignment.md | 15 +- .../Set-MailContact.md | 279 +- .../Set-MailPublicFolder.md | 263 +- .../Set-MailUser.md | 399 +- .../Set-Mailbox.md | 835 +- .../Set-MailboxAuditBypassAssociation.md | 31 +- .../Set-MailboxAutoReplyConfiguration.md | 83 +- .../Set-MailboxCalendarConfiguration.md | 215 +- .../Set-MailboxCalendarFolder.md | 63 +- .../Set-MailboxDatabase.md | 159 +- .../Set-MailboxDatabaseCopy.md | 47 +- .../Set-MailboxExportRequest.md | 75 +- .../Set-MailboxFolderPermission.md | 43 +- .../Set-MailboxIRMAccess.md | 23 +- .../Set-MailboxImportRequest.md | 79 +- .../Set-MailboxJunkEmailConfiguration.md | 63 +- .../Set-MailboxMessageConfiguration.md | 275 +- .../Set-MailboxPlan.md | 67 +- .../Set-MailboxRegionalConfiguration.md | 59 +- .../Set-MailboxRestoreRequest.md | 87 +- .../Set-MailboxSearch.md | 127 +- .../Set-MailboxSentItemsConfiguration.md | 35 +- .../Set-MailboxServer.md | 431 +- .../Set-MailboxSpellingConfiguration.md | 43 +- .../Set-MailboxTransportService.md | 187 +- .../Set-MalwareFilterPolicy.md | 127 +- .../Set-MalwareFilterRule.md | 67 +- .../Set-MalwareFilteringServer.md | 71 +- .../Set-ManagedContentSettings.md | 67 +- .../Set-ManagedFolder.md | 59 +- .../Set-ManagedFolderMailboxPolicy.md | 35 +- .../Set-ManagementRoleAssignment.md | 71 +- .../Set-ManagementRoleEntry.md | 47 +- .../Set-ManagementScope.md | 51 +- .../Set-MapiVirtualDirectory.md | 55 +- .../Set-MessageClassification.md | 59 +- .../Set-MigrationBatch.md | 107 +- .../Set-MigrationConfig.md | 39 +- .../Set-MigrationEndpoint.md | 107 +- .../Set-MigrationUser.md | 55 +- .../Set-MobileDeviceMailboxPolicy.md | 247 +- .../Set-MoveRequest.md | 127 +- .../Set-MyAnalyticsFeatureConfig.md | 31 +- .../Set-Notification.md | 35 +- .../Set-OMEConfiguration.md | 67 +- .../Set-OMEMessageRevocation.md | 19 +- .../Set-OabVirtualDirectory.md | 67 +- .../Set-OfflineAddressBook.md | 111 +- .../Set-OnPremisesOrganization.md | 47 +- .../Set-OrganizationConfig.md | 695 +- .../Set-OrganizationRelationship.md | 115 +- .../Set-OrganizationSegment.md | 19 +- .../Set-OutboundConnector.md | 99 +- .../Set-OutlookAnywhere.md | 83 +- .../Set-OutlookProtectionRule.md | 59 +- .../Set-OutlookProvider.md | 51 +- .../Set-OwaMailboxPolicy.md | 551 +- .../Set-OwaVirtualDirectory.md | 515 +- .../Set-PartnerApplication.md | 79 +- .../Set-PendingFederatedDomain.md | 35 +- .../Set-PerimeterConfig.md | 27 +- .../Set-PhishSimOverridePolicy.md | 39 +- .../Set-Place.md | 103 +- .../Set-PolicyConfig.md | 135 +- .../Set-PolicyTipConfig.md | 31 +- .../Set-PopSettings.md | 135 +- .../Set-PowerShellVirtualDirectory.md | 63 +- .../Set-ProtectionAlert.md | 115 +- .../Set-PublicFolder.md | 115 +- .../Set-PublicFolderDatabase.md | 103 +- .../Set-PublicFolderMigrationRequest.md | 71 +- .../Set-PublicFolderMoveRequest.md | 59 +- .../Set-QuarantinePermissions.md | 47 +- .../Set-QuarantinePolicy.md | 107 +- .../Set-RMSTemplate.md | 27 +- .../Set-ReceiveConnector.md | 239 +- .../Set-RecipientFilterConfig.md | 47 +- ...-RecordReviewNotificationTemplateConfig.md | 27 +- .../Set-RegulatoryComplianceUI.md | 10 +- .../Set-RemoteDomain.md | 127 +- .../Set-RemoteMailbox.md | 255 +- .../Set-ReportSubmissionPolicy.md | 211 +- .../Set-ReportSubmissionRule.md | 39 +- .../Set-ResourceConfig.md | 27 +- .../Set-ResubmitRequest.md | 31 +- .../Set-RetentionCompliancePolicy.md | 199 +- .../Set-RetentionComplianceRule.md | 75 +- .../Set-RetentionPolicy.md | 51 +- .../Set-RetentionPolicyTag.md | 103 +- .../Set-RoleAssignmentPolicy.md | 39 +- .../Set-RoleGroup.md | 67 +- .../Set-RoutingGroupConnector.md | 51 +- .../Set-RpcClientAccess.md | 43 +- .../Set-SafeAttachmentPolicy.md | 47 +- .../Set-SafeAttachmentRule.md | 63 +- .../Set-SafeLinksPolicy.md | 79 +- .../Set-SafeLinksRule.md | 63 +- .../Set-SearchDocumentFormat.md | 31 +- .../Set-SecOpsOverridePolicy.md | 47 +- .../Set-SendConnector.md | 159 +- .../Set-SenderFilterConfig.md | 59 +- .../Set-SenderIdConfig.md | 51 +- .../Set-SenderReputationConfig.md | 63 +- .../Set-ServerComponentState.md | 51 +- .../Set-ServerMonitor.md | 35 +- .../Set-ServicePrincipal.md | 26 +- .../Set-SettingOverride.md | 51 +- .../Set-SharingPolicy.md | 43 +- .../Set-SiteMailbox.md | 63 +- .../Set-SiteMailboxProvisioningPolicy.md | 55 +- .../Set-SmimeConfig.md | 127 +- .../Set-SupervisoryReviewPolicyV2.md | 67 +- .../Set-SupervisoryReviewRule.md | 103 +- .../Set-SweepRule.md | 75 +- .../Set-SystemMessage.md | 39 +- .../Set-TeamsProtectionPolicy.md | 43 +- .../Set-TeamsProtectionPolicyRule.md | 39 +- .../Set-TenantAllowBlockListItems.md | 55 +- .../Set-TenantAllowBlockListSpoofItems.md | 31 +- .../Set-TextMessagingAccount.md | 43 +- .../Set-ThrottlingPolicy.md | 595 +- .../Set-ThrottlingPolicyAssociation.md | 31 +- .../Set-TransportAgent.md | 35 +- .../Set-TransportConfig.md | 275 +- .../Set-TransportRule.md | 715 +- .../Set-TransportServer.md | 391 +- .../Set-TransportService.md | 567 +- .../Set-UMAutoAttendant.md | 195 +- .../Set-UMCallAnsweringRule.md | 67 +- .../Set-UMCallRouterSettings.md | 55 +- .../Set-UMDialPlan.md | 215 +- .../Set-UMIPGateway.md | 67 +- .../Set-UMMailbox.md | 103 +- .../Set-UMMailboxPIN.md | 55 +- .../Set-UMMailboxPolicy.md | 207 +- .../Set-UMService.md | 79 +- .../Set-UmServer.md | 83 +- .../Set-UnifiedAuditLogRetentionPolicy.md | 47 +- .../Set-UnifiedGroup.md | 235 +- .../Set-User.md | 283 +- .../Set-UserBriefingConfig.md | 23 +- .../Set-UserPhoto.md | 85 +- .../Set-VivaInsightsSettings.md | 27 +- .../Set-WebServicesVirtualDirectory.md | 91 +- .../Set-X400AuthoritativeDomain.md | 39 +- .../Start-ComplianceSearch.md | 31 +- .../Start-DatabaseAvailabilityGroup.md | 39 +- .../Start-EdgeSynchronization.md | 35 +- .../Start-HistoricalSearch.md | 103 +- ...t-InformationBarrierPoliciesApplication.md | 27 +- .../Start-MailboxAssistant.md | 39 +- .../Start-MailboxSearch.md | 39 +- .../Start-ManagedFolderAssistant.md | 67 +- .../Start-MigrationBatch.md | 35 +- .../Start-MigrationUser.md | 31 +- .../Start-RetentionAutoTagLearning.md | 43 +- .../Stop-ComplianceSearch.md | 23 +- .../Stop-DatabaseAvailabilityGroup.md | 39 +- .../Stop-HistoricalSearch.md | 15 +- ...p-InformationBarrierPoliciesApplication.md | 23 +- .../Stop-MailboxSearch.md | 27 +- .../Stop-ManagedFolderAssistant.md | 27 +- .../Stop-MigrationBatch.md | 31 +- .../Stop-MigrationUser.md | 31 +- .../Suspend-MailboxDatabaseCopy.md | 39 +- .../Suspend-MailboxExportRequest.md | 31 +- .../Suspend-MailboxImportRequest.md | 31 +- .../Suspend-MailboxRestoreRequest.md | 31 +- .../Suspend-Message.md | 31 +- .../Suspend-MoveRequest.md | 35 +- ...end-PublicFolderMailboxMigrationRequest.md | 31 +- .../Suspend-PublicFolderMigrationRequest.md | 31 +- .../Suspend-PublicFolderMoveRequest.md | 31 +- .../Suspend-PublicFolderReplication.md | 23 +- .../Suspend-Queue.md | 31 +- .../Test-ActiveSyncConnectivity.md | 71 +- .../Test-ApplicationAccessPolicy.md | 19 +- .../Test-ArchiveConnectivity.md | 31 +- .../Test-AssistantHealth.md | 43 +- .../Test-CalendarConnectivity.md | 59 +- .../Test-ClientAccessRule.md | 43 +- .../Test-DataClassification.md | 31 +- .../Test-EcpConnectivity.md | 63 +- .../Test-EdgeSynchronization.md | 47 +- .../Test-ExchangeSearch.md | 47 +- .../Test-FederationTrust.md | 31 +- .../Test-FederationTrustCertificate.md | 23 +- .../Test-IPAllowListProvider.md | 35 +- .../Test-IPBlockListProvider.md | 35 +- .../Test-IRMConfiguration.md | 39 +- .../Test-ImapConnectivity.md | 67 +- .../Test-M365DataAtRestEncryptionPolicy.md | 27 +- .../Test-MAPIConnectivity.md | 63 +- .../Test-MRSHealth.md | 43 +- .../Test-Mailflow.md | 75 +- .../Test-Message.md | 60 +- .../Test-MigrationServerAvailability.md | 175 +- .../Test-OAuthConnectivity.md | 43 +- .../Test-OrganizationRelationship.md | 31 +- .../Test-OutlookConnectivity.md | 103 +- .../Test-OutlookWebServices.md | 51 +- .../Test-OwaConnectivity.md | 75 +- .../Test-PopConnectivity.md | 67 +- .../Test-PowerShellConnectivity.md | 63 +- .../Test-ReplicationHealth.md | 47 +- .../Test-SenderId.md | 39 +- .../Test-ServiceHealth.md | 35 +- .../Test-ServicePrincipalAuthorization.md | 27 +- .../Test-SiteMailbox.md | 39 +- .../Test-SmtpConnectivity.md | 31 +- .../Test-SystemHealth.md | 99 +- .../Test-TextExtraction.md | 27 +- .../Test-UMConnectivity.md | 107 +- .../Test-WebServicesConnectivity.md | 84 +- .../Undo-SoftDeletedMailbox.md | 43 +- .../Undo-SoftDeletedUnifiedGroup.md | 23 +- .../Uninstall-TransportAgent.md | 31 +- .../Update-AddressList.md | 27 +- .../Update-ComplianceCaseMember.md | 27 +- .../Update-DatabaseSchema.md | 31 +- .../Update-DistributionGroupMember.md | 35 +- .../Update-EmailAddressPolicy.md | 35 +- .../Update-ExchangeHelp.md | 15 +- .../Update-FileDistributionService.md | 31 +- .../Update-GlobalAddressList.md | 27 +- .../Update-HybridConfiguration.md | 39 +- .../Update-MailboxDatabaseCopy.md | 95 +- .../Update-OfflineAddressBook.md | 31 +- .../Update-PublicFolder.md | 31 +- .../Update-PublicFolderHierarchy.md | 27 +- .../Update-PublicFolderMailbox.md | 68 +- .../Update-Recipient.md | 31 +- .../Update-RoleGroupMember.md | 35 +- .../Update-SafeList.md | 39 +- .../Update-SiteMailbox.md | 43 +- .../Update-StoreMailboxState.md | 27 +- .../Update-VivaModuleFeaturePolicy.md | 64 +- .../Update-eDiscoveryCaseAdmin.md | 23 +- .../Upgrade-DistributionGroup.md | 27 +- .../Validate-OutboundConnector.md | 27 +- .../Validate-RetentionRuleQuery.md | 15 +- .../Write-AdminAuditLog.md | 27 +- 1408 files changed, 61475 insertions(+), 24198 deletions(-) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ADPermission.md (85%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-AttachmentFilterEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-AvailabilityAddressSpace.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ComplianceCaseMember.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ContentFilterPhrase.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-DatabaseAvailabilityGroupServer.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-DistributionGroupMember.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-FederatedDomain.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-GlobalMonitoringOverride.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-IPAllowListEntry.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-IPAllowListProvider.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-IPBlockListEntry.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-IPBlockListProvider.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-MailboxDatabaseCopy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-MailboxFolderPermission.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-MailboxPermission.md (84%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ManagementRoleEntry.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-PublicFolderAdministrativePermission.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-PublicFolderClientPermission.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-RecipientPermission.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ResubmitRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-RoleGroupMember.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-ServerMonitoringOverride.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-UnifiedGroupLinks.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-VivaModuleFeaturePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-VivaOrgInsightsDelegatedRole.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Add-eDiscoveryCaseAdmin.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Check-PurviewConfig.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Clean-MailboxDatabase.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Clear-ActiveSyncDevice.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Clear-MobileDevice.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Clear-TextMessagingAccount.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Compare-TextMessagingVerificationCode.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Complete-MigrationBatch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Connect-ExchangeOnline.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Connect-IPPSSession.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Connect-Mailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Delete-QuarantineMessage.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-AddressListPaging.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-AntiPhishRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-App.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-CmdletExtensionAgent.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-DistributionGroup.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-DnssecForVerifiedDomain.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-EOPProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-HostedContentFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-HostedOutboundSpamFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-IPv6ForAcceptedDomain.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-InboxRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-JournalArchiving.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-JournalRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MailContact.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MailPublicFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MailUser.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-Mailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MailboxQuarantine.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MalwareFilterRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-MetaCacheDatabase.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-OutlookAnywhere.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-OutlookProtectionRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-PushNotificationProxy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-RemoteMailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-SafeAttachmentRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-ServiceEmailChannel.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-SmtpDaneInbound.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-SweepRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-TransportAgent.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-TransportRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMAutoAttendant.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMCallAnsweringRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMIPGateway.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMMailbox.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMServer.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disable-UMService.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Disconnect-ExchangeOnline.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Dismount-Database.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Dump-ProvisioningCache.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-AddressListPaging.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-AntiPhishRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-AntispamUpdates.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-App.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-CmdletExtensionAgent.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-ComplianceTagStorage.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-DistributionGroup.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-DnssecForVerifiedDomain.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-EOPProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-ExchangeCertificate.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-HostedContentFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-HostedOutboundSpamFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-IPv6ForAcceptedDomain.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-InboxRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-JournalRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MailContact.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MailPublicFolder.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MailUser.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-Mailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MailboxQuarantine.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MalwareFilterRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-MetaCacheDatabase.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-OrganizationCustomization.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-OutlookAnywhere.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-OutlookProtectionRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-PushNotificationProxy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-RemoteMailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-SafeAttachmentRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-ServiceEmailChannel.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-SmtpDaneInbound.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-SweepRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-TransportAgent.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-TransportRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMAutoAttendant.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMCallAnsweringRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMIPGateway.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMMailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMServer.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Enable-UMService.md (94%) rename exchange/exchange-ps/{exchange/exchange.md => ExchangePowerShell/ExchangePowerShell.md} (99%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Execute-AzureADLabelSync.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Expedite-Delicensing.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-ActiveSyncLog.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-ActivityExplorerData.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-AutoDiscoverConfig.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-ContentExplorerData.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-DlpPolicyCollection.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-ExchangeCertificate.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-FilePlanProperty.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-JournalRuleCollection.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-MailboxDiagnosticLogs.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-Message.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-MigrationReport.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-QuarantineMessage.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-RecipientDataProperty.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-TransportRuleCollection.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-UMCallDataRecord.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Export-UMPrompt.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ADPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ADServerSettings.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ADSite.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ATPBuiltInProtectionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ATPTotalTrafficReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AcceptedDomain.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AccessToCustomerDataRequest.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncDevice.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncDeviceAccessRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncDeviceAutoblockThreshold.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncDeviceClass.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncDeviceStatistics.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncMailboxPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncOrganizationSettings.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ActiveSyncVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AdSiteLink.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AdaptiveScope.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AddressBookPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AddressList.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AddressRewriteEntry.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AdminAuditLogConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AdministrativeUnit.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AgentLog.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AggregateZapReport.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AntiPhishPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AntiPhishRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-App.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AppRetentionCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AppRetentionComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ApplicationAccessPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ArcConfig.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AtpPolicyForO365.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AttachmentFilterEntry.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AttachmentFilterListConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuditConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuditLogSearch.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuthConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuthRedirect.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuthServer.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AuthenticationPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AutoSensitivityLabelPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AutoSensitivityLabelRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AutodiscoverVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AvailabilityAddressSpace.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AvailabilityConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-AvailabilityReportOutage.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-BlockedConnector.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-BlockedSenderAddress.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CASMailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CASMailboxPlan.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CalendarDiagnosticAnalysis.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CalendarDiagnosticLog.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CalendarDiagnosticObjects.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CalendarNotification.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CalendarProcessing.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CaseHoldPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CaseHoldRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ClassificationRuleCollection.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ClientAccessArray.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ClientAccessRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ClientAccessServer.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ClientAccessService.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Clutter.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CmdletExtensionAgent.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceCase.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceCaseMember.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceRetentionEvent.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceRetentionEventType.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceSearch.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceSearchAction.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceSecurityFilter.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceTag.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ComplianceTagStorage.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CompromisedUserAggregateReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-CompromisedUserDetailReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ConfigAnalyzerPolicyRecommendation.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ConnectionInformation.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Contact.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ContentFilterConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ContentFilterPhrase.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ContentMalwareMdoAggregateReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ContentMalwareMdoDetailReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DataClassification.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DataClassificationConfig.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DataEncryptionPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DataRetentionReport.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DatabaseAvailabilityGroup.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DatabaseAvailabilityGroupNetwork.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DefaultTenantBriefingConfig.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DefaultTenantMyAnalyticsFeatureConfig.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeliveryAgentConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DetailZapReport.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DetailsTemplate.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceConditionalAccessPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceConditionalAccessRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceConfigurationPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceConfigurationRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DevicePolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceTenantPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DeviceTenantRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DistributionGroup.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DistributionGroupMember.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DkimSigningConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpCompliancePolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpDetailReport.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpDetectionsReport.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpEdmSchema.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpIncidentDetailReport.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpKeywordDictionary.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpPolicyTemplate.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpSensitiveInformationType.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpSensitiveInformationTypeRulePackage.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DlpSiDetectionsReport.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DnssecStatusForVerifiedDomain.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DomainController.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DynamicDistributionGroup.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-DynamicDistributionGroupMember.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EOPProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOCasMailbox.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMailbox.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMailboxFolderPermission.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMailboxFolderStatistics.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMailboxPermission.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMailboxStatistics.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXOMobileDeviceStatistics.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXORecipient.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EXORecipientPermission.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EcpVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EdgeSubscription.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EdgeSyncServiceConfig.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EligibleDistributionGroupForMigration.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EmailAddressPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EmailTenantSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EtrLimits.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EventLogLevel.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-EventsFromEmailConfiguration.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeAssistanceConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeCertificate.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeDiagnosticInfo.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeFeature.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeServer.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeServerAccessLicense.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeServerAccessLicenseUser.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExchangeSettings.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExoInformationBarrierPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExoInformationBarrierRelationship.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExoInformationBarrierSegment.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExoPhishSimOverrideRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExoSecOpsOverrideRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ExternalInOutlook.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FailedContentIndexDocuments.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FeatureConfiguration.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FederatedDomainProof.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FederatedOrganizationIdentifier.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FederationInformation.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FederationTrust.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyAuthority.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyCategory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyCitation.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyDepartment.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyReferenceId.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertyStructure.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FilePlanPropertySubCategory.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FocusedInbox.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ForeignConnector.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-FrontendTransportService.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-GlobalAddressList.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-GlobalMonitoringOverride.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Group.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HealthReport.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HistoricalSearch.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HoldCompliancePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HoldComplianceRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HostedConnectionFilterPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HostedContentFilterPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HostedContentFilterRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HostedOutboundSpamFilterPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HostedOutboundSpamFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HybridConfiguration.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-HybridMailflowDatacenterIPs.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPAllowListConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPAllowListEntry.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPAllowListProvider.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPAllowListProvidersConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPBlockListConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPBlockListEntry.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPBlockListProvider.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPBlockListProvidersConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IPv6StatusForAcceptedDomain.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IRMConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ImapSettings.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-InboundConnector.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-InboxRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-InformationBarrierPoliciesApplicationStatus.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-InformationBarrierPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-InformationBarrierRecipientStatus.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IntraOrganizationConfiguration.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-IntraOrganizationConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-JournalRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Label.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-LabelPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-LinkedUser.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-LogonStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-M365DataAtRestEncryptionPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-M365DataAtRestEncryptionPolicyAssignment.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailContact.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailDetailATPReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailDetailDlpPolicyReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailDetailEncryptionReport.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailDetailTransportRuleReport.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailFilterListReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailPublicFolder.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailTrafficATPReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailTrafficEncryptionReport.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailTrafficPolicyReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailTrafficSummaryReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailUser.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Mailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxAuditBypassAssociation.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxAutoReplyConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxCalendarConfiguration.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxCalendarFolder.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxDatabase.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxDatabaseCopyStatus.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxExportRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxExportRequestStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxFolderPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxFolderStatistics.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxIRMAccess.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxImportRequest.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxImportRequestStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxJunkEmailConfiguration.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxLocation.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxMessageConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxPlan.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxRegionalConfiguration.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxRepairRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxRestoreRequest.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxRestoreRequestStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxSearch.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxSentItemsConfiguration.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxServer.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxSpellingConfiguration.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxTransportService.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailboxUserConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MailflowStatusReport.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MalwareFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MalwareFilterRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MalwareFilteringServer.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagedContentSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagedFolder.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagedFolderMailboxPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagementRole.md (83%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagementRoleAssignment.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagementRoleEntry.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ManagementScope.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MapiVirtualDirectory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Message.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageCategory.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageClassification.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTrace.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTraceDetail.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTraceDetailV2.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTraceV2.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTrackingLog.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MessageTrackingReport.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationBatch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationConfig.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationEndpoint.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationStatistics.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationUser.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MigrationUserStatistics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MobileDevice.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MobileDeviceMailboxPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MobileDeviceStatistics.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MonitoringItemHelp.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MonitoringItemIdentity.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MoveRequest.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MoveRequestStatistics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MxRecordReport.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-MyAnalyticsFeatureConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-NetworkConnectionInfo.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Notification.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OMEConfiguration.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OMEMessageStatus.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OabVirtualDirectory.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OfflineAddressBook.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OnPremisesOrganization.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OnlineMeetingConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OrganizationConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OrganizationRelationship.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OrganizationSegment.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OrganizationalUnit.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OutboundConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OutboundConnectorReport.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OutlookAnywhere.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OutlookProtectionRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OutlookProvider.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OwaMailboxPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-OwaVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PartnerApplication.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PendingDelicenseUser.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PendingFederatedDomain.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PerimeterConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PhishSimOverridePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Place.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PolicyConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PolicyTipConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PopSettings.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PowerShellVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ProtectionAlert.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderAdministrativePermission.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderClientPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderDatabase.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderItemStatistics.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMailboxDiagnostics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMailboxMigrationRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMailboxMigrationRequestStatistics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMigrationRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMigrationRequestStatistics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMoveRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderMoveRequestStatistics.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-PublicFolderStatistics.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-QuarantineMessage.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-QuarantineMessageHeader.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-QuarantinePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Queue.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-QueueDigest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RMSTemplate.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ReceiveConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Recipient.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RecipientFilterConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RecipientPermission.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RecipientStatisticsReport.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RecordReviewNotificationTemplateConfig.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RecoverableItems.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RegulatoryComplianceUI.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RemoteDomain.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RemoteMailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ReportExecutionInstance.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ReportSubmissionPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ResourceConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ResubmitRequest.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RetentionCompliancePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RetentionComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RetentionEvent.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RetentionPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RetentionPolicyTag.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ReviewItems.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RoleAssignmentPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RoleGroup.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RoleGroupMember.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RoutingGroupConnector.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-RpcClientAccess.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SCInsights.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeAttachmentPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeAttachmentRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeLinksAggregateReport.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeLinksDetailReport.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeLinksPolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SearchDocumentFormat.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SecOpsOverridePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SecurityPrincipal.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SendConnector.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SenderFilterConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SenderIdConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SenderReputationConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ServerComponentState.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ServerHealth.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ServerMonitoringOverride.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ServiceDeliveryReport.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ServicePrincipal.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SettingOverride.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SharingPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SiteMailbox.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SiteMailboxDiagnostics.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SiteMailboxProvisioningPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SmimeConfig.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SmtpDaneInboundStatus.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SpoofIntelligenceInsight.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SpoofMailReport.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-StoreUsageStatistics.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewActivity.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewOverallProgressReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewPolicyReport.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewPolicyV2.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewReport.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SupervisoryReviewTopCasesReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SweepRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-SystemMessage.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TeamsProtectionPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TeamsProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TenantAllowBlockListItems.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TenantAllowBlockListSpoofItems.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TextMessagingAccount.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ThrottlingPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-ThrottlingPolicyAssociation.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportAgent.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportConfig.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportPipeline.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportRuleAction.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportRulePredicate.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportServer.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-TransportService.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-Trust.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMActiveCalls.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMAutoAttendant.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMCallAnsweringRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMCallDataRecord.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMCallRouterSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMCallSummaryReport.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMDialPlan.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMHuntGroup.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMIPGateway.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMMailbox.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMMailboxPIN.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMMailboxPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UMService.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UmServer.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UnifiedAuditLogRetentionPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UnifiedGroup.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UnifiedGroupLinks.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-User.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UserBriefingConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UserPhoto.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-UserPrincipalNamesSuffix.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-VivaInsightsSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-VivaModuleFeature.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-VivaModuleFeatureEnablement.md (98%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-VivaModuleFeaturePolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-VivaOrgInsightsDelegatedRole.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-WebServicesVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-X400AuthoritativeDomain.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Get-eDiscoveryCaseAdmin.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-DlpPolicyCollection.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-DlpPolicyTemplate.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-ExchangeCertificate.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-FilePlanProperty.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-JournalRuleCollection.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-RecipientDataProperty.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-TransportRuleCollection.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Import-UMPrompt.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Install-TransportAgent.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Install-UnifiedCompliancePrerequisite.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Invoke-ComplianceSearchActionStep.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Invoke-ComplianceSecurityFilterAction.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Invoke-HoldRemovalAction.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Invoke-MonitoringProbe.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Mount-Database.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Move-ActiveMailboxDatabase.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Move-AddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Move-DatabasePath.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Move-OfflineAddressBook.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ATPBuiltInProtectionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AcceptedDomain.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ActiveSyncDeviceAccessRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ActiveSyncMailboxPolicy.md (81%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ActiveSyncVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AdaptiveScope.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AddressBookPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AddressList.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AddressRewriteEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AdminAuditLogSearch.md (84%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AntiPhishPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AntiPhishRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-App.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AppRetentionCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AppRetentionComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ApplicationAccessPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AuthRedirect.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AuthServer.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AuthenticationPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AutoSensitivityLabelPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AutoSensitivityLabelRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AutodiscoverVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AvailabilityConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-AvailabilityReportOutage.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-CaseHoldPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-CaseHoldRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ClassificationRuleCollection.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ClientAccessArray.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ClientAccessRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceCase.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceRetentionEvent.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceRetentionEventType.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceSearch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceSearchAction.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceSecurityFilter.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ComplianceTag.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DataClassification.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DataEncryptionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DatabaseAvailabilityGroup.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DatabaseAvailabilityGroupNetwork.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeliveryAgentConnector.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceConditionalAccessPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceConditionalAccessRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceConfigurationPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceConfigurationRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceTenantPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DeviceTenantRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DistributionGroup.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DkimSigningConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpEdmSchema.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpFingerprint.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpKeywordDictionary.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpSensitiveInformationType.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DlpSensitiveInformationTypeRulePackage.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-DynamicDistributionGroup.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-EOPProtectionPolicyRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-EcpVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-EdgeSubscription.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-EdgeSyncServiceConfig.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-EmailAddressPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ExchangeCertificate.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ExchangeSettings.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ExoPhishSimOverrideRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ExoSecOpsOverrideRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FeatureConfiguration.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FederationTrust.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertyAuthority.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertyCategory.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertyCitation.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertyDepartment.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertyReferenceId.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-FilePlanPropertySubCategory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-Fingerprint.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ForeignConnector.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-GlobalAddressList.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HoldCompliancePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HoldComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HostedContentFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HostedContentFilterRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HostedOutboundSpamFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HostedOutboundSpamFilterRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-HybridConfiguration.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-InboundConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-InboxRule.md (85%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-InformationBarrierPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-IntraOrganizationConnector.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-JournalRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-Label.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-LabelPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-M365DataAtRestEncryptionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailContact.md (85%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailMessage.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailUser.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-Mailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxAuditLogSearch.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxDatabase.md (84%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxExportRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxImportRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxRepairRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxRestoreRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MailboxSearch.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MalwareFilterPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MalwareFilterRule.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagedContentSettings.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagedFolder.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagedFolderMailboxPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagementRole.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagementRoleAssignment.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ManagementScope.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MapiVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MessageClassification.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MigrationBatch.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MigrationEndpoint.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MobileDeviceMailboxPolicy.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-MoveRequest.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OMEConfiguration.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OabVirtualDirectory.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OfflineAddressBook.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OnPremisesOrganization.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OrganizationRelationship.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OrganizationSegment.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OutboundConnector.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OutlookProtectionRule.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OutlookProvider.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OwaMailboxPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-OwaVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PartnerApplication.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PhishSimOverridePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PolicyTipConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PowerShellVirtualDirectory.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ProtectionAlert.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PublicFolder.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PublicFolderDatabase.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PublicFolderDatabaseRepairRequest.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PublicFolderMigrationRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-PublicFolderMoveRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-QuarantinePermissions.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-QuarantinePolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ReceiveConnector.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RemoteDomain.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RemoteMailbox.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ReportSubmissionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RetentionCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RetentionComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RetentionPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RetentionPolicyTag.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RoleAssignmentPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RoleGroup.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RoutingGroupConnector.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-RpcClientAccess.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SafeAttachmentPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SafeAttachmentRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SafeLinksPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SearchDocumentFormat.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SecOpsOverridePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SendConnector.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ServicePrincipal.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SettingOverride.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SharingPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SiteMailbox.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SiteMailboxProvisioningPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SupervisoryReviewPolicyV2.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SupervisoryReviewRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SweepRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SyncMailPublicFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-SystemMessage.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-TeamsProtectionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-TeamsProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-TenantAllowBlockListItems.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-TenantAllowBlockListSpoofItems.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-ThrottlingPolicy.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-TransportRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMAutoAttendant.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMCallAnsweringRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMDialPlan.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMHuntGroup.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMIPGateway.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UMMailboxPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UnifiedAuditLogRetentionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-UnifiedGroup.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-WebServicesVirtualDirectory.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/New-X400AuthoritativeDomain.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Preview-QuarantineMessage.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Redirect-Message.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Release-QuarantineMessage.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ADPermission.md (84%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AcceptedDomain.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ActiveSyncDevice.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ActiveSyncDeviceAccessRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ActiveSyncDeviceClass.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ActiveSyncMailboxPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ActiveSyncVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AdaptiveScope.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AddressBookPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AddressRewriteEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AntiPhishPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AntiPhishRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-App.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AppRetentionCompliancePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AppRetentionComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ApplicationAccessPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AttachmentFilterEntry.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AuthRedirect.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AuthServer.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AuthenticationPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AutoSensitivityLabelPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AutoSensitivityLabelRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AutodiscoverVirtualDirectory.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AvailabilityAddressSpace.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AvailabilityConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-AvailabilityReportOutage.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-BlockedConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-BlockedSenderAddress.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-CalendarEvents.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-CaseHoldPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-CaseHoldRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ClassificationRuleCollection.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ClientAccessArray.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ClientAccessRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceCase.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceCaseMember.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceRetentionEventType.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceSearch.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceSearchAction.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceSecurityFilter.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ComplianceTag.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ContentFilterPhrase.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DataClassification.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DatabaseAvailabilityGroup.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DatabaseAvailabilityGroupNetwork.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DatabaseAvailabilityGroupServer.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeliveryAgentConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceConditionalAccessPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceConditionalAccessRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceConfigurationPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceConfigurationRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceTenantPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DeviceTenantRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DistributionGroup.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DistributionGroupMember.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpEdmSchema.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpKeywordDictionary.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpPolicyTemplate.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpSensitiveInformationType.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DlpSensitiveInformationTypeRulePackage.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-DynamicDistributionGroup.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-EOPProtectionPolicyRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-EcpVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-EdgeSubscription.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-EmailAddressPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ExchangeCertificate.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ExoPhishSimOverrideRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ExoSecOpsOverrideRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FeatureConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FederatedDomain.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FederationTrust.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertyAuthority.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertyCategory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertyCitation.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertyDepartment.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertyReferenceId.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-FilePlanPropertySubCategory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ForeignConnector.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-GlobalAddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-GlobalMonitoringOverride.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HoldCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HoldComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HostedContentFilterPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HostedContentFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HostedOutboundSpamFilterPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HostedOutboundSpamFilterRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-HybridConfiguration.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-IPAllowListEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-IPAllowListProvider.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-IPBlockListEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-IPBlockListProvider.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-InboundConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-InboxRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-InformationBarrierPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-IntraOrganizationConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-JournalRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-Label.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-LabelPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailContact.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailUser.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-Mailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxDatabase.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxDatabaseCopy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxExportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxFolderPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxIRMAccess.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxImportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxPermission.md (85%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxRepairRequest.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxRestoreRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxSearch.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MailboxUserConfiguration.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MalwareFilterPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MalwareFilterRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagedContentSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagedFolder.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagedFolderMailboxPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagementRole.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagementRoleAssignment.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagementRoleEntry.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ManagementScope.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MapiVirtualDirectory.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-Message.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MessageClassification.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MigrationBatch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MigrationEndpoint.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MigrationUser.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MobileDevice.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MobileDeviceMailboxPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-MoveRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OMEConfiguration.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OabVirtualDirectory.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OfflineAddressBook.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OnPremisesOrganization.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OrganizationRelationship.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OrganizationSegment.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OutboundConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OutlookProtectionRule.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OutlookProvider.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OwaMailboxPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-OwaVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PartnerApplication.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PhishSimOverridePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PolicyTipConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PowerShellVirtualDirectory.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ProtectionAlert.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolder.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderAdministrativePermission.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderClientPermission.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderDatabase.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderMailboxMigrationRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderMigrationRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-PublicFolderMoveRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-QuarantinePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ReceiveConnector.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RecipientPermission.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RemoteDomain.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RemoteMailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ReportSubmissionPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ResubmitRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RetentionCompliancePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RetentionComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RetentionPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RetentionPolicyTag.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RoleAssignmentPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RoleGroup.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RoleGroupMember.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RoutingGroupConnector.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-RpcClientAccess.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SafeAttachmentPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SafeAttachmentRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SafeLinksPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SearchDocumentFormat.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SecOpsOverridePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SendConnector.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ServerMonitoringOverride.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ServicePrincipal.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SettingOverride.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SharingPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SiteMailboxProvisioningPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-StoreMailbox.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SupervisoryReviewPolicyV2.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SweepRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SyncMailPublicFolder.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-SystemMessage.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-TenantAllowBlockListItems.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-TenantAllowBlockListSpoofItems.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-ThrottlingPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-TransportRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMAutoAttendant.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMCallAnsweringRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMDialPlan.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMHuntGroup.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMIPGateway.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UMMailboxPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UnifiedAuditLogRetentionPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UnifiedGroup.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UnifiedGroupLinks.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-UserPhoto.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-VivaModuleFeaturePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-VivaOrgInsightsDelegatedRole.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-WebServicesVirtualDirectory.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-X400AuthoritativeDomain.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Remove-eDiscoveryCaseAdmin.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Reset-ProvisioningCache.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Restore-DatabaseAvailabilityGroup.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Restore-DetailsTemplate.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Restore-Mailbox.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Restore-RecoverableItems.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-MailboxDatabaseCopy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-MailboxExportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-MailboxImportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-MailboxRestoreRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-Message.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-MoveRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-PublicFolderMigrationRequest.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-PublicFolderMoveRequest.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-PublicFolderReplication.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Resume-Queue.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Retry-Queue.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Rotate-DkimSigningConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Search-AdminAuditLog.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Search-Mailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Search-MailboxAuditLog.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Search-MessageTrackingReport.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Search-UnifiedAuditLog.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Send-TextMessagingVerificationCode.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ADServerSettings.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ADSite.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ATPBuiltInProtectionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ATPProtectionPolicyRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AcceptedDomain.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AccessToCustomerDataRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ActiveSyncDeviceAccessRule.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ActiveSyncDeviceAutoblockThreshold.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ActiveSyncMailboxPolicy.md (81%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ActiveSyncOrganizationSettings.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ActiveSyncVirtualDirectory.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AdSiteLink.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AdaptiveScope.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AddressBookPolicy.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AddressRewriteEntry.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AdminAuditLogConfig.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AntiPhishPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AntiPhishRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-App.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AppRetentionCompliancePolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AppRetentionComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ApplicationAccessPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ArcConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AtpPolicyForO365.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AttachmentFilterListConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AuditConfig.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AuthConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AuthRedirect.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AuthServer.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AuthenticationPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AutoSensitivityLabelPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AutoSensitivityLabelRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AutodiscoverVirtualDirectory.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AvailabilityConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-AvailabilityReportOutage.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CASMailbox.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CASMailboxPlan.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CalendarNotification.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CalendarProcessing.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CaseHoldPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CaseHoldRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ClassificationRuleCollection.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ClientAccessArray.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ClientAccessRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ClientAccessServer.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ClientAccessService.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Clutter.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-CmdletExtensionAgent.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceCase.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceRetentionEventType.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceSearch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceSearchAction.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceSecurityFilter.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ComplianceTag.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Contact.md (78%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ContentFilterConfig.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DataClassification.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DataEncryptionPolicy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DatabaseAvailabilityGroup.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DatabaseAvailabilityGroupNetwork.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DefaultTenantBriefingConfig.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DefaultTenantMyAnalyticsFeatureConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeliveryAgentConnector.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DetailsTemplate.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceConditionalAccessPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceConditionalAccessRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceConfigurationPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceConfigurationRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceTenantPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DeviceTenantRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DistributionGroup.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DkimSigningConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpEdmSchema.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpKeywordDictionary.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpSensitiveInformationType.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DlpSensitiveInformationTypeRulePackage.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-DynamicDistributionGroup.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EOPProtectionPolicyRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EcpVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EdgeSyncServiceConfig.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EmailAddressPolicy.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EmailTenantSettings.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EventLogLevel.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-EventsFromEmailConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExchangeAssistanceConfig.md (82%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExchangeFeature.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExchangeServer.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExchangeSettings.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExoPhishSimOverrideRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExoSecOpsOverrideRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ExternalInOutlook.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FeatureConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FederatedOrganizationIdentifier.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FederationTrust.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertyAuthority.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertyCategory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertyCitation.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertyDepartment.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertyReferenceId.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FilePlanPropertySubCategory.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FocusedInbox.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ForeignConnector.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-FrontendTransportService.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-GlobalAddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Group.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HoldCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HoldComplianceRule.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HostedConnectionFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HostedContentFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HostedContentFilterRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HostedOutboundSpamFilterPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HostedOutboundSpamFilterRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-HybridConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPAllowListConfig.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPAllowListProvider.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPAllowListProvidersConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPBlockListConfig.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPBlockListProvider.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IPBlockListProvidersConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IRMConfiguration.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ImapSettings.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-InboundConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-InboxRule.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-InformationBarrierPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-IntraOrganizationConnector.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-JournalRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Label.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-LabelPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-LinkedUser.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-M365DataAtRestEncryptionPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-M365DataAtRestEncryptionPolicyAssignment.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailContact.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailPublicFolder.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailUser.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Mailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxAuditBypassAssociation.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxAutoReplyConfiguration.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxCalendarConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxCalendarFolder.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxDatabase.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxDatabaseCopy.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxExportRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxFolderPermission.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxIRMAccess.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxImportRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxJunkEmailConfiguration.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxMessageConfiguration.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxPlan.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxRegionalConfiguration.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxRestoreRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxSearch.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxSentItemsConfiguration.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxServer.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxSpellingConfiguration.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MailboxTransportService.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MalwareFilterPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MalwareFilterRule.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MalwareFilteringServer.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagedContentSettings.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagedFolder.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagedFolderMailboxPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagementRoleAssignment.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagementRoleEntry.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ManagementScope.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MapiVirtualDirectory.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MessageClassification.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MigrationBatch.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MigrationConfig.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MigrationEndpoint.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MigrationUser.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MobileDeviceMailboxPolicy.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MoveRequest.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-MyAnalyticsFeatureConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Notification.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OMEConfiguration.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OMEMessageRevocation.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OabVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OfflineAddressBook.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OnPremisesOrganization.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OrganizationConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OrganizationRelationship.md (84%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OrganizationSegment.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OutboundConnector.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OutlookAnywhere.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OutlookProtectionRule.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OutlookProvider.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OwaMailboxPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-OwaVirtualDirectory.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PartnerApplication.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PendingFederatedDomain.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PerimeterConfig.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PhishSimOverridePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-Place.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PolicyConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PolicyTipConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PopSettings.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PowerShellVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ProtectionAlert.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PublicFolder.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PublicFolderDatabase.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PublicFolderMigrationRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-PublicFolderMoveRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-QuarantinePermissions.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-QuarantinePolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RMSTemplate.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ReceiveConnector.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RecipientFilterConfig.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RecordReviewNotificationTemplateConfig.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RegulatoryComplianceUI.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RemoteDomain.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RemoteMailbox.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ReportSubmissionPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ReportSubmissionRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ResourceConfig.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ResubmitRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RetentionCompliancePolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RetentionComplianceRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RetentionPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RetentionPolicyTag.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RoleAssignmentPolicy.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RoleGroup.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RoutingGroupConnector.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-RpcClientAccess.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SafeAttachmentPolicy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SafeAttachmentRule.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SafeLinksPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SafeLinksRule.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SearchDocumentFormat.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SecOpsOverridePolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SendConnector.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SenderFilterConfig.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SenderIdConfig.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SenderReputationConfig.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ServerComponentState.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ServerMonitor.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ServicePrincipal.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SettingOverride.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SharingPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SiteMailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SiteMailboxProvisioningPolicy.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SmimeConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SupervisoryReviewPolicyV2.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SupervisoryReviewRule.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SweepRule.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-SystemMessage.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TeamsProtectionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TeamsProtectionPolicyRule.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TenantAllowBlockListItems.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TenantAllowBlockListSpoofItems.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TextMessagingAccount.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ThrottlingPolicy.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-ThrottlingPolicyAssociation.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TransportAgent.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TransportConfig.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TransportRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TransportServer.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-TransportService.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMAutoAttendant.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMCallAnsweringRule.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMCallRouterSettings.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMDialPlan.md (86%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMIPGateway.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMMailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMMailboxPIN.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMMailboxPolicy.md (87%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UMService.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UmServer.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UnifiedAuditLogRetentionPolicy.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UnifiedGroup.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-User.md (82%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UserBriefingConfig.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-UserPhoto.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-VivaInsightsSettings.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-WebServicesVirtualDirectory.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Set-X400AuthoritativeDomain.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-ComplianceSearch.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-DatabaseAvailabilityGroup.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-EdgeSynchronization.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-HistoricalSearch.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-InformationBarrierPoliciesApplication.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-MailboxAssistant.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-MailboxSearch.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-ManagedFolderAssistant.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-MigrationBatch.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-MigrationUser.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Start-RetentionAutoTagLearning.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-ComplianceSearch.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-DatabaseAvailabilityGroup.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-HistoricalSearch.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-InformationBarrierPoliciesApplication.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-MailboxSearch.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-ManagedFolderAssistant.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-MigrationBatch.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Stop-MigrationUser.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-MailboxDatabaseCopy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-MailboxExportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-MailboxImportRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-MailboxRestoreRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-Message.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-MoveRequest.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-PublicFolderMailboxMigrationRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-PublicFolderMigrationRequest.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-PublicFolderMoveRequest.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-PublicFolderReplication.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Suspend-Queue.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ActiveSyncConnectivity.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ApplicationAccessPolicy.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ArchiveConnectivity.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-AssistantHealth.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-CalendarConnectivity.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ClientAccessRule.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-DataClassification.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-EcpConnectivity.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-EdgeSynchronization.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ExchangeSearch.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-FederationTrust.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-FederationTrustCertificate.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-IPAllowListProvider.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-IPBlockListProvider.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-IRMConfiguration.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ImapConnectivity.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-M365DataAtRestEncryptionPolicy.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-MAPIConnectivity.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-MRSHealth.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-Mailflow.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-Message.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-MigrationServerAvailability.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-OAuthConnectivity.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-OrganizationRelationship.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-OutlookConnectivity.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-OutlookWebServices.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-OwaConnectivity.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-PopConnectivity.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-PowerShellConnectivity.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ReplicationHealth.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-SenderId.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ServiceHealth.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-ServicePrincipalAuthorization.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-SiteMailbox.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-SmtpConnectivity.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-SystemHealth.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-TextExtraction.md (92%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-UMConnectivity.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Test-WebServicesConnectivity.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Undo-SoftDeletedMailbox.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Undo-SoftDeletedUnifiedGroup.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Uninstall-TransportAgent.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-AddressList.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-ComplianceCaseMember.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-DatabaseSchema.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-DistributionGroupMember.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-EmailAddressPolicy.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-ExchangeHelp.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-FileDistributionService.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-GlobalAddressList.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-HybridConfiguration.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-MailboxDatabaseCopy.md (88%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-OfflineAddressBook.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-PublicFolder.md (95%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-PublicFolderHierarchy.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-PublicFolderMailbox.md (89%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-Recipient.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-RoleGroupMember.md (90%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-SafeList.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-SiteMailbox.md (91%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-StoreMailboxState.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-VivaModuleFeaturePolicy.md (97%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Update-eDiscoveryCaseAdmin.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Upgrade-DistributionGroup.md (93%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Validate-OutboundConnector.md (94%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Validate-RetentionRuleQuery.md (96%) rename exchange/exchange-ps/{exchange => ExchangePowerShell}/Write-AdminAuditLog.md (89%) diff --git a/.openpublishing.redirection.exchange.json b/.openpublishing.redirection.exchange.json index 7eb756dfc2..76b0dd1c7e 100644 --- a/.openpublishing.redirection.exchange.json +++ b/.openpublishing.redirection.exchange.json @@ -2,72 +2,72 @@ "redirections": [ { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md", - "redirect_url": "/powershell/module/exchange/new-dlpedmschema", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpedmschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/get-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/get-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/new-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/remove-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/remove-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/set-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpComplianceRuleV2.md", - "redirect_url": "/powershell/module/exchange/get-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRuleV2.md", - "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRuleV2.md", - "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpComplianceRuleV2.md", - "redirect_url": "/powershell/module/exchange/set-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/exchange-ps-v2-module/connect-exchangeonline.md", - "redirect_url": "/powershell/module/exchange/connect-exchangeonline", + "redirect_url": "/powershell/module/exchangepowershell/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/exchange/add-adpermission", + "redirect_url": "/powershell/module/exchangepowershell/add-adpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Dump-ProvisioningCache.md", - "redirect_url": "/powershell/module/exchange/dump-provisioningcache", + "redirect_url": "/powershell/module/exchangepowershell/dump-provisioningcache", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADPermission.md", - "redirect_url": "/powershell/module/exchange/get-adpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-adpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADServerSettings.md", - "redirect_url": "/powershell/module/exchange/get-adserversettings", + "redirect_url": "/powershell/module/exchangepowershell/get-adserversettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADSite.md", - "redirect_url": "/powershell/module/exchange/get-adsite", + "redirect_url": "/powershell/module/exchangepowershell/get-adsite", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-AdSiteLink.md", - "redirect_url": "/powershell/module/exchange/get-adsitelink", + "redirect_url": "/powershell/module/exchangepowershell/get-adsitelink", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-DomainController.md", - "redirect_url": "/powershell/module/exchange/get-domaincontroller", + "redirect_url": "/powershell/module/exchangepowershell/get-domaincontroller", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-OrganizationalUnit.md", - "redirect_url": "/powershell/module/exchange/get-organizationalunit", + "redirect_url": "/powershell/module/exchangepowershell/get-organizationalunit", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-Trust.md", - "redirect_url": "/powershell/module/exchange/get-trust", + "redirect_url": "/powershell/module/exchangepowershell/get-trust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Get-UserPrincipalNamesSuffix.md", - "redirect_url": "/powershell/module/exchange/get-userprincipalnamessuffix", + "redirect_url": "/powershell/module/exchangepowershell/get-userprincipalnamessuffix", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Remove-ADPermission.md", - "redirect_url": "/powershell/module/exchange/remove-adpermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-adpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Reset-ProvisioningCache.md", - "redirect_url": "/powershell/module/exchange/reset-provisioningcache", + "redirect_url": "/powershell/module/exchangepowershell/reset-provisioningcache", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADServerSettings.md", - "redirect_url": "/powershell/module/exchange/set-adserversettings", + "redirect_url": "/powershell/module/exchangepowershell/set-adserversettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADSite.md", - "redirect_url": "/powershell/module/exchange/set-adsite", + "redirect_url": "/powershell/module/exchangepowershell/set-adsite", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/active-directory/Set-AdSiteLink.md", - "redirect_url": "/powershell/module/exchange/set-adsitelink", + "redirect_url": "/powershell/module/exchangepowershell/set-adsitelink", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/disable-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/disable-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/disable-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/enable-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/enable-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/enable-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md", - "redirect_url": "/powershell/module/exchange/get-advancedthreatprotectiondocumentdetail", + "redirect_url": "/powershell/module/exchangepowershell/get-advancedthreatprotectiondocumentdetail", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md", - "redirect_url": "/powershell/module/exchange/get-advancedthreatprotectiondocumentreport", + "redirect_url": "/powershell/module/exchangepowershell/get-advancedthreatprotectiondocumentreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionTrafficReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md", - "redirect_url": "/powershell/module/exchange/get-antiphishpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-antiphishpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/get-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/get-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md", - "redirect_url": "/powershell/module/exchange/get-atppolicyforo365", + "redirect_url": "/powershell/module/exchangepowershell/get-atppolicyforo365", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailDetailATPReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems", + "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md", - "redirect_url": "/powershell/module/exchange/get-safeattachmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/get-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeLinksPolicy.md", - "redirect_url": "/powershell/module/exchange/get-safelinkspolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-safelinkspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/get-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/get-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SpoofMailReport.md", - "redirect_url": "/powershell/module/exchange/get-spoofmailreport", + "redirect_url": "/powershell/module/exchangepowershell/get-spoofmailreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-UrlTrace.md", - "redirect_url": "/powershell/module/exchange/get-safelinksaggregatereport", + "redirect_url": "/powershell/module/exchangepowershell/get-safelinksaggregatereport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishPolicy.md", - "redirect_url": "/powershell/module/exchange/new-antiphishpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-antiphishpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/new-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/new-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeAttachmentPolicy.md", - "redirect_url": "/powershell/module/exchange/new-safeattachmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/new-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeLinksPolicy.md", - "redirect_url": "/powershell/module/exchange/new-safelinkspolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-safelinkspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/new-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/new-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-antiphishpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/remove-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeAttachmentPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-safeattachmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/remove-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-safelinkspolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-safelinkspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/remove-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md", - "redirect_url": "/powershell/module/exchange/set-antiphishpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-antiphishpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishRule.md", - "redirect_url": "/powershell/module/exchange/set-antiphishrule", + "redirect_url": "/powershell/module/exchangepowershell/set-antiphishrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md", - "redirect_url": "/powershell/module/exchange/set-atppolicyforo365", + "redirect_url": "/powershell/module/exchangepowershell/set-atppolicyforo365", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems", + "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistspoofitems", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md", - "redirect_url": "/powershell/module/exchange/set-safeattachmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeAttachmentRule.md", - "redirect_url": "/powershell/module/exchange/set-safeattachmentrule", + "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md", - "redirect_url": "/powershell/module/exchange/set-safelinkspolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-safelinkspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksRule.md", - "redirect_url": "/powershell/module/exchange/set-safelinksrule", + "redirect_url": "/powershell/module/exchangepowershell/set-safelinksrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-AttachmentFilterEntry.md", - "redirect_url": "/powershell/module/exchange/add-attachmentfilterentry", + "redirect_url": "/powershell/module/exchangepowershell/add-attachmentfilterentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-ContentFilterPhrase.md", - "redirect_url": "/powershell/module/exchange/add-contentfilterphrase", + "redirect_url": "/powershell/module/exchangepowershell/add-contentfilterphrase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPAllowListEntry.md", - "redirect_url": "/powershell/module/exchange/add-ipallowlistentry", + "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPAllowListProvider.md", - "redirect_url": "/powershell/module/exchange/add-ipallowlistprovider", + "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListEntry.md", - "redirect_url": "/powershell/module/exchange/add-ipblocklistentry", + "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListProvider.md", - "redirect_url": "/powershell/module/exchange/add-ipblocklistprovider", + "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Delete-QuarantineMessage.md", - "redirect_url": "/powershell/module/exchange/delete-quarantinemessage", + "redirect_url": "/powershell/module/exchangepowershell/delete-quarantinemessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/disable-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/disable-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/disable-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-AntispamUpdates.md", - "redirect_url": "/powershell/module/exchange/enable-antispamupdates", + "redirect_url": "/powershell/module/exchangepowershell/enable-antispamupdates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/enable-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/enable-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/enable-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Export-QuarantineMessage.md", - "redirect_url": "/powershell/module/exchange/export-quarantinemessage", + "redirect_url": "/powershell/module/exchangepowershell/export-quarantinemessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AgentLog.md", - "redirect_url": "/powershell/module/exchange/get-agentlog", + "redirect_url": "/powershell/module/exchangepowershell/get-agentlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md", - "redirect_url": "/powershell/module/exchange/get-attachmentfilterentry", + "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md", - "redirect_url": "/powershell/module/exchange/get-attachmentfilterlistconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterlistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-BlockedSenderAddress.md", - "redirect_url": "/powershell/module/exchange/get-blockedsenderaddress", + "redirect_url": "/powershell/module/exchangepowershell/get-blockedsenderaddress", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterConfig.md", - "redirect_url": "/powershell/module/exchange/get-contentfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterPhrase.md", - "redirect_url": "/powershell/module/exchange/get-contentfilterphrase", + "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterphrase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-DkimSigningConfig.md", - "redirect_url": "/powershell/module/exchange/get-dkimsigningconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-dkimsigningconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-hostedconnectionfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-hostedconnectionfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-hostedcontentfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/get-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-hostedoutboundspamfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/get-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListConfig.md", - "redirect_url": "/powershell/module/exchange/get-ipallowlistconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListEntry.md", - "redirect_url": "/powershell/module/exchange/get-ipallowlistentry", + "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListProvider.md", - "redirect_url": "/powershell/module/exchange/get-ipallowlistprovider", + "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListProvidersConfig.md", - "redirect_url": "/powershell/module/exchange/get-ipallowlistprovidersconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovidersconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListConfig.md", - "redirect_url": "/powershell/module/exchange/get-ipblocklistconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListEntry.md", - "redirect_url": "/powershell/module/exchange/get-ipblocklistentry", + "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListProvider.md", - "redirect_url": "/powershell/module/exchange/get-ipblocklistprovider", + "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md", - "redirect_url": "/powershell/module/exchange/get-ipblocklistprovidersconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovidersconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxjunkemailconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxjunkemailconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilteringServer.md", - "redirect_url": "/powershell/module/exchange/get-malwarefilteringserver", + "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilteringserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-malwarefilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/get-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-QuarantineMessage.md", - "redirect_url": "/powershell/module/exchange/get-quarantinemessage", + "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-QuarantineMessageHeader.md", - "redirect_url": "/powershell/module/exchange/get-quarantinemessageheader", + "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessageheader", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-RecipientFilterConfig.md", - "redirect_url": "/powershell/module/exchange/get-recipientfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-recipientfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderFilterConfig.md", - "redirect_url": "/powershell/module/exchange/get-senderfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-senderfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderIdConfig.md", - "redirect_url": "/powershell/module/exchange/get-senderidconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-senderidconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderReputationConfig.md", - "redirect_url": "/powershell/module/exchange/get-senderreputationconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-senderreputationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-DkimSigningConfig.md", - "redirect_url": "/powershell/module/exchange/new-dkimsigningconfig", + "redirect_url": "/powershell/module/exchangepowershell/new-dkimsigningconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/new-hostedcontentfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/new-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedOutboundSpamFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/new-hostedoutboundspamfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/new-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-MalwareFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/new-malwarefilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/new-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Preview-QuarantineMessage.md", - "redirect_url": "/powershell/module/exchange/preview-quarantinemessage", + "redirect_url": "/powershell/module/exchangepowershell/preview-quarantinemessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Release-QuarantineMessage.md", - "redirect_url": "/powershell/module/exchange/release-quarantinemessage", + "redirect_url": "/powershell/module/exchangepowershell/release-quarantinemessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-AttachmentFilterEntry.md", - "redirect_url": "/powershell/module/exchange/remove-attachmentfilterentry", + "redirect_url": "/powershell/module/exchangepowershell/remove-attachmentfilterentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-BlockedSenderAddress.md", - "redirect_url": "/powershell/module/exchange/remove-blockedsenderaddress", + "redirect_url": "/powershell/module/exchangepowershell/remove-blockedsenderaddress", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md", - "redirect_url": "/powershell/module/exchange/remove-contentfilterphrase", + "redirect_url": "/powershell/module/exchangepowershell/remove-contentfilterphrase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedContentFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-hostedcontentfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/remove-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-hostedoutboundspamfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/remove-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListEntry.md", - "redirect_url": "/powershell/module/exchange/remove-ipallowlistentry", + "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListProvider.md", - "redirect_url": "/powershell/module/exchange/remove-ipallowlistprovider", + "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPBlockListEntry.md", - "redirect_url": "/powershell/module/exchange/remove-ipblocklistentry", + "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPBlockListProvider.md", - "redirect_url": "/powershell/module/exchange/remove-ipblocklistprovider", + "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-malwarefilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/remove-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md", - "redirect_url": "/powershell/module/exchange/rotate-dkimsigningconfig", + "redirect_url": "/powershell/module/exchangepowershell/rotate-dkimsigningconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md", - "redirect_url": "/powershell/module/exchange/set-attachmentfilterlistconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-attachmentfilterlistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-ContentFilterConfig.md", - "redirect_url": "/powershell/module/exchange/set-contentfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-contentfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-DkimSigningConfig.md", - "redirect_url": "/powershell/module/exchange/set-dkimsigningconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-dkimsigningconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-hostedconnectionfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-hostedconnectionfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-hostedcontentfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedContentFilterRule.md", - "redirect_url": "/powershell/module/exchange/set-hostedcontentfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-hostedoutboundspamfilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterRule.md", - "redirect_url": "/powershell/module/exchange/set-hostedoutboundspamfilterrule", + "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListConfig.md", - "redirect_url": "/powershell/module/exchange/set-ipallowlistconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListProvider.md", - "redirect_url": "/powershell/module/exchange/set-ipallowlistprovider", + "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListProvidersConfig.md", - "redirect_url": "/powershell/module/exchange/set-ipallowlistprovidersconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovidersconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListConfig.md", - "redirect_url": "/powershell/module/exchange/set-ipblocklistconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListProvider.md", - "redirect_url": "/powershell/module/exchange/set-ipblocklistprovider", + "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListProvidersConfig.md", - "redirect_url": "/powershell/module/exchange/set-ipblocklistprovidersconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovidersconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxjunkemailconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxjunkemailconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilteringServer.md", - "redirect_url": "/powershell/module/exchange/set-malwarefilteringserver", + "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilteringserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-malwarefilterpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilterRule.md", - "redirect_url": "/powershell/module/exchange/set-malwarefilterrule", + "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-RecipientFilterConfig.md", - "redirect_url": "/powershell/module/exchange/set-recipientfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-recipientfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderFilterConfig.md", - "redirect_url": "/powershell/module/exchange/set-senderfilterconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-senderfilterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderIdConfig.md", - "redirect_url": "/powershell/module/exchange/set-senderidconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-senderidconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderReputationConfig.md", - "redirect_url": "/powershell/module/exchange/set-senderreputationconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-senderreputationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-IPAllowListProvider.md", - "redirect_url": "/powershell/module/exchange/test-ipallowlistprovider", + "redirect_url": "/powershell/module/exchangepowershell/test-ipallowlistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-IPBlockListProvider.md", - "redirect_url": "/powershell/module/exchange/test-ipblocklistprovider", + "redirect_url": "/powershell/module/exchangepowershell/test-ipblocklistprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-SenderId.md", - "redirect_url": "/powershell/module/exchange/test-senderid", + "redirect_url": "/powershell/module/exchangepowershell/test-senderid", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Update-SafeList.md", - "redirect_url": "/powershell/module/exchange/update-safelist", + "redirect_url": "/powershell/module/exchangepowershell/update-safelist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Clear-TextMessagingAccount.md", - "redirect_url": "/powershell/module/exchange/clear-textmessagingaccount", + "redirect_url": "/powershell/module/exchangepowershell/clear-textmessagingaccount", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Compare-TextMessagingVerificationCode.md", - "redirect_url": "/powershell/module/exchange/compare-textmessagingverificationcode", + "redirect_url": "/powershell/module/exchangepowershell/compare-textmessagingverificationcode", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Disable-PushNotificationProxy.md", - "redirect_url": "/powershell/module/exchange/disable-pushnotificationproxy", + "redirect_url": "/powershell/module/exchangepowershell/disable-pushnotificationproxy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Enable-PushNotificationProxy.md", - "redirect_url": "/powershell/module/exchange/enable-pushnotificationproxy", + "redirect_url": "/powershell/module/exchangepowershell/enable-pushnotificationproxy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Export-AutoDiscoverConfig.md", - "redirect_url": "/powershell/module/exchange/export-autodiscoverconfig", + "redirect_url": "/powershell/module/exchangepowershell/export-autodiscoverconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-CASMailbox.md", - "redirect_url": "/powershell/module/exchange/get-casmailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-casmailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-CASMailboxPlan.md", - "redirect_url": "/powershell/module/exchange/get-casmailboxplan", + "redirect_url": "/powershell/module/exchangepowershell/get-casmailboxplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-ClientAccessRule.md", - "redirect_url": "/powershell/module/exchange/get-clientaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-ImapSettings.md", - "redirect_url": "/powershell/module/exchange/get-imapsettings", + "redirect_url": "/powershell/module/exchangepowershell/get-imapsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxCalendarConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxcalendarconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxMessageConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxmessageconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxmessageconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxRegionalConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxregionalconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxregionalconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxSpellingConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxspellingconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxspellingconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-OutlookProvider.md", - "redirect_url": "/powershell/module/exchange/get-outlookprovider", + "redirect_url": "/powershell/module/exchangepowershell/get-outlookprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-OwaMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/get-owamailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-owamailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-PopSettings.md", - "redirect_url": "/powershell/module/exchange/get-popsettings", + "redirect_url": "/powershell/module/exchangepowershell/get-popsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Get-TextMessagingAccount.md", - "redirect_url": "/powershell/module/exchange/get-textmessagingaccount", + "redirect_url": "/powershell/module/exchangepowershell/get-textmessagingaccount", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/New-ClientAccessRule.md", - "redirect_url": "/powershell/module/exchange/new-clientaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/New-OutlookProvider.md", - "redirect_url": "/powershell/module/exchange/new-outlookprovider", + "redirect_url": "/powershell/module/exchangepowershell/new-outlookprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/New-OwaMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/new-owamailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-owamailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Remove-ClientAccessRule.md", - "redirect_url": "/powershell/module/exchange/remove-clientaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Remove-OutlookProvider.md", - "redirect_url": "/powershell/module/exchange/remove-outlookprovider", + "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Remove-OwaMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-owamailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-owamailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Send-TextMessagingVerificationCode.md", - "redirect_url": "/powershell/module/exchange/send-textmessagingverificationcode", + "redirect_url": "/powershell/module/exchangepowershell/send-textmessagingverificationcode", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-CASMailbox.md", - "redirect_url": "/powershell/module/exchange/set-casmailbox", + "redirect_url": "/powershell/module/exchangepowershell/set-casmailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/set-CASMailboxPlan.md", - "redirect_url": "/powershell/module/exchange/set-casmailboxplan", + "redirect_url": "/powershell/module/exchangepowershell/set-casmailboxplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-ClientAccessRule.md", - "redirect_url": "/powershell/module/exchange/set-clientaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-ImapSettings.md", - "redirect_url": "/powershell/module/exchange/set-imapsettings", + "redirect_url": "/powershell/module/exchangepowershell/set-imapsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxCalendarConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxcalendarconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxMessageConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxmessageconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxmessageconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxRegionalConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxregionalconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxregionalconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxSpellingConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxspellingconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxspellingconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-OutlookProvider.md", - "redirect_url": "/powershell/module/exchange/set-outlookprovider", + "redirect_url": "/powershell/module/exchangepowershell/set-outlookprovider", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-OwaMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/set-owamailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-owamailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-PopSettings.md", - "redirect_url": "/powershell/module/exchange/set-popsettings", + "redirect_url": "/powershell/module/exchangepowershell/set-popsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Set-TextMessagingAccount.md", - "redirect_url": "/powershell/module/exchange/set-textmessagingaccount", + "redirect_url": "/powershell/module/exchangepowershell/set-textmessagingaccount", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-CalendarConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-calendarconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-calendarconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-ClientAccessRule.md", - "redirect_url": "/powershell/module/exchange/test-clientaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/test-clientaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-EcpConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-ecpconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-ecpconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-ImapConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-imapconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-imapconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-OutlookConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-outlookconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-outlookconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-OutlookWebServices.md", - "redirect_url": "/powershell/module/exchange/test-outlookwebservices", + "redirect_url": "/powershell/module/exchangepowershell/test-outlookwebservices", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-OwaConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-owaconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-owaconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-PopConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-popconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-popconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-PowerShellConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-powershellconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-powershellconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access/Test-WebServicesConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-webservicesconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-webservicesconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Disable-OutlookAnywhere.md", - "redirect_url": "/powershell/module/exchange/disable-outlookanywhere", + "redirect_url": "/powershell/module/exchangepowershell/disable-outlookanywhere", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Enable-OutlookAnywhere.md", - "redirect_url": "/powershell/module/exchange/enable-outlookanywhere", + "redirect_url": "/powershell/module/exchangepowershell/enable-outlookanywhere", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-activesyncvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-AuthRedirect.md", - "redirect_url": "/powershell/module/exchange/get-authredirect", + "redirect_url": "/powershell/module/exchangepowershell/get-authredirect", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-AutodiscoverVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-autodiscovervirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-autodiscovervirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessArray.md", - "redirect_url": "/powershell/module/exchange/get-clientaccessarray", + "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessarray", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessServer.md", - "redirect_url": "/powershell/module/exchange/get-clientaccessserver", + "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessService.md", - "redirect_url": "/powershell/module/exchange/get-clientaccessservice", + "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-EcpVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-ecpvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-ecpvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-MapiVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-mapivirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-mapivirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-OutlookAnywhere.md", - "redirect_url": "/powershell/module/exchange/get-outlookanywhere", + "redirect_url": "/powershell/module/exchangepowershell/get-outlookanywhere", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-OwaVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-owavirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-owavirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-powershellvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-powershellvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-RpcClientAccess.md", - "redirect_url": "/powershell/module/exchange/get-rpcclientaccess", + "redirect_url": "/powershell/module/exchangepowershell/get-rpcclientaccess", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-webservicesvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-webservicesvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-activesyncvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-activesyncvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-AuthRedirect.md", - "redirect_url": "/powershell/module/exchange/new-authredirect", + "redirect_url": "/powershell/module/exchangepowershell/new-authredirect", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-autodiscovervirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-autodiscovervirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ClientAccessArray.md", - "redirect_url": "/powershell/module/exchange/new-clientaccessarray", + "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessarray", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-EcpVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-ecpvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-ecpvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-MapiVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-mapivirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-mapivirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-OwaVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-owavirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-owavirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-PowerShellVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-powershellvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-powershellvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-RpcClientAccess.md", - "redirect_url": "/powershell/module/exchange/new-rpcclientaccess", + "redirect_url": "/powershell/module/exchangepowershell/new-rpcclientaccess", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/New-WebServicesVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-webservicesvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-webservicesvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-ActiveSyncVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-activesyncvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AuthRedirect.md", - "redirect_url": "/powershell/module/exchange/remove-authredirect", + "redirect_url": "/powershell/module/exchangepowershell/remove-authredirect", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-autodiscovervirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-autodiscovervirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-ClientAccessArray.md", - "redirect_url": "/powershell/module/exchange/remove-clientaccessarray", + "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessarray", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-EcpVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-ecpvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-ecpvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-MapiVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-mapivirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-mapivirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-OwaVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-owavirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-owavirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-powershellvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-powershellvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-RpcClientAccess.md", - "redirect_url": "/powershell/module/exchange/remove-rpcclientaccess", + "redirect_url": "/powershell/module/exchangepowershell/remove-rpcclientaccess", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-WebServicesVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-webservicesvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-webservicesvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-activesyncvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-activesyncvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-AuthRedirect.md", - "redirect_url": "/powershell/module/exchange/set-authredirect", + "redirect_url": "/powershell/module/exchangepowershell/set-authredirect", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-AutodiscoverVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-autodiscovervirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-autodiscovervirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessArray.md", - "redirect_url": "/powershell/module/exchange/set-clientaccessarray", + "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessarray", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessServer.md", - "redirect_url": "/powershell/module/exchange/set-clientaccessserver", + "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessService.md", - "redirect_url": "/powershell/module/exchange/set-clientaccessservice", + "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-EcpVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-ecpvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-ecpvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-MapiVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-mapivirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-mapivirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-OutlookAnywhere.md", - "redirect_url": "/powershell/module/exchange/set-outlookanywhere", + "redirect_url": "/powershell/module/exchangepowershell/set-outlookanywhere", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-OwaVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-owavirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-owavirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-PowerShellVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-powershellvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-powershellvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-RpcClientAccess.md", - "redirect_url": "/powershell/module/exchange/set-rpcclientaccess", + "redirect_url": "/powershell/module/exchangepowershell/set-rpcclientaccess", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-webservicesvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-webservicesvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md", - "redirect_url": "/powershell/module/exchange/add-databaseavailabilitygroupserver", + "redirect_url": "/powershell/module/exchangepowershell/add-databaseavailabilitygroupserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Add-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/add-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/add-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/get-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md", - "redirect_url": "/powershell/module/exchange/get-databaseavailabilitygroupnetwork", + "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroupnetwork", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md", - "redirect_url": "/powershell/module/exchange/get-mailboxdatabasecopystatus", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabasecopystatus", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/move-activemailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/move-activemailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/new-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/New-DatabaseAvailabilityGroupNetwork.md", - "redirect_url": "/powershell/module/exchange/new-databaseavailabilitygroupnetwork", + "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroupnetwork", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md", - "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroupnetwork", + "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupnetwork", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md", - "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroupserver", + "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/restore-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/restore-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Resume-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/resume-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/set-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md", - "redirect_url": "/powershell/module/exchange/set-databaseavailabilitygroupnetwork", + "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroupnetwork", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/set-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/start-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/start-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md", - "redirect_url": "/powershell/module/exchange/stop-databaseavailabilitygroup", + "redirect_url": "/powershell/module/exchangepowershell/stop-databaseavailabilitygroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Suspend-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/suspend-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Test-ReplicationHealth.md", - "redirect_url": "/powershell/module/exchange/test-replicationhealth", + "redirect_url": "/powershell/module/exchangepowershell/test-replicationhealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/database-availability-groups/Update-MailboxDatabaseCopy.md", - "redirect_url": "/powershell/module/exchange/update-mailboxdatabasecopy", + "redirect_url": "/powershell/module/exchangepowershell/update-mailboxdatabasecopy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Clear-ActiveSyncDevice.md", - "redirect_url": "/powershell/module/exchange/clear-activesyncdevice", + "redirect_url": "/powershell/module/exchangepowershell/clear-activesyncdevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Clear-MobileDevice.md", - "redirect_url": "/powershell/module/exchange/clear-mobiledevice", + "redirect_url": "/powershell/module/exchangepowershell/clear-mobiledevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Export-ActiveSyncLog.md", - "redirect_url": "/powershell/module/exchange/export-activesynclog", + "redirect_url": "/powershell/module/exchangepowershell/export-activesynclog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDevice.md", - "redirect_url": "/powershell/module/exchange/get-activesyncdevice", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAccessRule.md", - "redirect_url": "/powershell/module/exchange/get-activesyncdeviceaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md", - "redirect_url": "/powershell/module/exchange/get-activesyncdeviceautoblockthreshold", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceautoblockthreshold", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceClass.md", - "redirect_url": "/powershell/module/exchange/get-activesyncdeviceclass", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceclass", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceStatistics.md", - "redirect_url": "/powershell/module/exchange/get-activesyncdevicestatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevicestatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/get-activesyncmailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncmailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncOrganizationSettings.md", - "redirect_url": "/powershell/module/exchange/get-activesyncorganizationsettings", + "redirect_url": "/powershell/module/exchangepowershell/get-activesyncorganizationsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessRule.md", - "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/get-deviceconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/get-deviceconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DevicePolicy.md", - "redirect_url": "/powershell/module/exchange/get-devicepolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-devicepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantPolicy.md", - "redirect_url": "/powershell/module/exchange/get-devicetenantpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantRule.md", - "redirect_url": "/powershell/module/exchange/get-devicetenantrule", + "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDevice.md", - "redirect_url": "/powershell/module/exchange/get-mobiledevice", + "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/get-mobiledevicemailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicemailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mobiledevicestatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicestatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncDeviceAccessRule.md", - "redirect_url": "/powershell/module/exchange/new-activesyncdeviceaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/new-activesyncdeviceaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/new-activesyncmailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-activesyncmailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessRule.md", - "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/new-deviceconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/new-deviceconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantPolicy.md", - "redirect_url": "/powershell/module/exchange/new-devicetenantpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantRule.md", - "redirect_url": "/powershell/module/exchange/new-devicetenantrule", + "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/New-MobileDeviceMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/new-mobiledevicemailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-mobiledevicemailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDevice.md", - "redirect_url": "/powershell/module/exchange/remove-activesyncdevice", + "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md", - "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceClass.md", - "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceclass", + "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceclass", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-activesyncmailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncmailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessRule.md", - "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-devicetenantpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantRule.md", - "redirect_url": "/powershell/module/exchange/remove-devicetenantrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDevice.md", - "redirect_url": "/powershell/module/exchange/remove-mobiledevice", + "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDeviceMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-mobiledevicemailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevicemailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAccessRule.md", - "redirect_url": "/powershell/module/exchange/set-activesyncdeviceaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md", - "redirect_url": "/powershell/module/exchange/set-activesyncdeviceautoblockthreshold", + "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceautoblockthreshold", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/set-activesyncmailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-activesyncmailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncOrganizationSettings.md", - "redirect_url": "/powershell/module/exchange/set-activesyncorganizationsettings", + "redirect_url": "/powershell/module/exchangepowershell/set-activesyncorganizationsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessRule.md", - "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccessrule", + "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccessrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/set-deviceconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/set-deviceconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantPolicy.md", - "redirect_url": "/powershell/module/exchange/set-devicetenantpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantRule.md", - "redirect_url": "/powershell/module/exchange/set-devicetenantrule", + "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Set-MobileDeviceMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/set-mobiledevicemailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-mobiledevicemailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/devices/Test-ActiveSyncConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-activesyncconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-activesyncconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md", - "redirect_url": "/powershell/module/exchange/disable-addresslistpaging", + "redirect_url": "/powershell/module/exchangepowershell/disable-addresslistpaging", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md", - "redirect_url": "/powershell/module/exchange/enable-addresslistpaging", + "redirect_url": "/powershell/module/exchangepowershell/enable-addresslistpaging", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md", - "redirect_url": "/powershell/module/exchange/get-addressbookpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-addressbookpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressList.md", - "redirect_url": "/powershell/module/exchange/get-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/get-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md", - "redirect_url": "/powershell/module/exchange/get-detailstemplate", + "redirect_url": "/powershell/module/exchangepowershell/get-detailstemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md", - "redirect_url": "/powershell/module/exchange/get-emailaddresspolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-emailaddresspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md", - "redirect_url": "/powershell/module/exchange/get-globaladdresslist", + "redirect_url": "/powershell/module/exchangepowershell/get-globaladdresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/get-oabvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/get-oabvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/get-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/get-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-AddressList.md", - "redirect_url": "/powershell/module/exchange/move-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/move-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/move-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/move-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md", - "redirect_url": "/powershell/module/exchange/new-addressbookpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-addressbookpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressList.md", - "redirect_url": "/powershell/module/exchange/new-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/new-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md", - "redirect_url": "/powershell/module/exchange/new-emailaddresspolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-emailaddresspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-GlobalAddressList.md", - "redirect_url": "/powershell/module/exchange/new-globaladdresslist", + "redirect_url": "/powershell/module/exchangepowershell/new-globaladdresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/new-oabvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/new-oabvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/new-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/new-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-addressbookpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-addressbookpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressList.md", - "redirect_url": "/powershell/module/exchange/remove-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/remove-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-emailaddresspolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-emailaddresspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md", - "redirect_url": "/powershell/module/exchange/remove-globaladdresslist", + "redirect_url": "/powershell/module/exchangepowershell/remove-globaladdresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/remove-oabvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/remove-oabvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/remove-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/remove-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md", - "redirect_url": "/powershell/module/exchange/restore-detailstemplate", + "redirect_url": "/powershell/module/exchangepowershell/restore-detailstemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md", - "redirect_url": "/powershell/module/exchange/set-addressbookpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-addressbookpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressList.md", - "redirect_url": "/powershell/module/exchange/set-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/set-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md", - "redirect_url": "/powershell/module/exchange/set-detailstemplate", + "redirect_url": "/powershell/module/exchangepowershell/set-detailstemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-EmailAddressPolicy.md", - "redirect_url": "/powershell/module/exchange/set-emailaddresspolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-emailaddresspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md", - "redirect_url": "/powershell/module/exchange/set-globaladdresslist", + "redirect_url": "/powershell/module/exchangepowershell/set-globaladdresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md", - "redirect_url": "/powershell/module/exchange/set-oabvirtualdirectory", + "redirect_url": "/powershell/module/exchangepowershell/set-oabvirtualdirectory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/set-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/set-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-AddressList.md", - "redirect_url": "/powershell/module/exchange/update-addresslist", + "redirect_url": "/powershell/module/exchangepowershell/update-addresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md", - "redirect_url": "/powershell/module/exchange/update-emailaddresspolicy", + "redirect_url": "/powershell/module/exchangepowershell/update-emailaddresspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md", - "redirect_url": "/powershell/module/exchange/update-globaladdresslist", + "redirect_url": "/powershell/module/exchangepowershell/update-globaladdresslist", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md", - "redirect_url": "/powershell/module/exchange/update-offlineaddressbook", + "redirect_url": "/powershell/module/exchangepowershell/update-offlineaddressbook", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Enable-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/enable-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/enable-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Export-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/export-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/export-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-DataEncryptionPolicy.md", - "redirect_url": "/powershell/module/exchange/get-dataencryptionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-dataencryptionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/get-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-IRMConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-irmconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-irmconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-OMEConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-omeconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-omeconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-OMEMessageStatus.md", - "redirect_url": "/powershell/module/exchange/get-omemessagestatus", + "redirect_url": "/powershell/module/exchangepowershell/get-omemessagestatus", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTemplate.md", - "redirect_url": "/powershell/module/exchange/get-rmstemplate", + "redirect_url": "/powershell/module/exchangepowershell/get-rmstemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-SmimeConfig.md", - "redirect_url": "/powershell/module/exchange/get-smimeconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-smimeconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/import-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/import-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-DataEncryptionPolicy.md", - "redirect_url": "/powershell/module/exchange/new-dataencryptionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-dataencryptionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/new-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/new-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-OMEConfiguration.md", - "redirect_url": "/powershell/module/exchange/new-omeconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/new-omeconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-ExchangeCertificate.md", - "redirect_url": "/powershell/module/exchange/remove-exchangecertificate", + "redirect_url": "/powershell/module/exchangepowershell/remove-exchangecertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-OMEConfiguration.md", - "redirect_url": "/powershell/module/exchange/remove-omeconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/remove-omeconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-DataEncryptionPolicy.md", - "redirect_url": "/powershell/module/exchange/set-dataencryptionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-dataencryptionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-IRMConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-irmconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-irmconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-OMEConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-omeconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-omeconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-OMEMessageRevocation.md", - "redirect_url": "/powershell/module/exchange/set-omemessagerevocation", + "redirect_url": "/powershell/module/exchangepowershell/set-omemessagerevocation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTemplate.md", - "redirect_url": "/powershell/module/exchange/set-rmstemplate", + "redirect_url": "/powershell/module/exchangepowershell/set-rmstemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-SmimeConfig.md", - "redirect_url": "/powershell/module/exchange/set-smimeconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-smimeconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Test-IRMConfiguration.md", - "redirect_url": "/powershell/module/exchange/test-irmconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/test-irmconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Add-FederatedDomain.md", - "redirect_url": "/powershell/module/exchange/add-federateddomain", + "redirect_url": "/powershell/module/exchangepowershell/add-federateddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Disable-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/disable-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/disable-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Enable-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/enable-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/enable-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederatedDomainProof.md", - "redirect_url": "/powershell/module/exchange/get-federateddomainproof", + "redirect_url": "/powershell/module/exchangepowershell/get-federateddomainproof", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederatedOrganizationIdentifier.md", - "redirect_url": "/powershell/module/exchange/get-federatedorganizationidentifier", + "redirect_url": "/powershell/module/exchangepowershell/get-federatedorganizationidentifier", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationInformation.md", - "redirect_url": "/powershell/module/exchange/get-federationinformation", + "redirect_url": "/powershell/module/exchangepowershell/get-federationinformation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationTrust.md", - "redirect_url": "/powershell/module/exchange/get-federationtrust", + "redirect_url": "/powershell/module/exchangepowershell/get-federationtrust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-hybridconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-hybridconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflow.md", - "redirect_url": "/powershell/module/exchange/get-hybridmailflow", + "redirect_url": "/powershell/module/exchangepowershell/get-hybridmailflow", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md", - "redirect_url": "/powershell/module/exchange/get-hybridmailflowdatacenterips", + "redirect_url": "/powershell/module/exchangepowershell/get-hybridmailflowdatacenterips", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-IntraOrganizationConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-intraorganizationconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md", - "redirect_url": "/powershell/module/exchange/get-intraorganizationconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-OnPremisesOrganization.md", - "redirect_url": "/powershell/module/exchange/get-onpremisesorganization", + "redirect_url": "/powershell/module/exchangepowershell/get-onpremisesorganization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-PendingFederatedDomain.md", - "redirect_url": "/powershell/module/exchange/get-pendingfederateddomain", + "redirect_url": "/powershell/module/exchangepowershell/get-pendingfederateddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/get-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-FederationTrust.md", - "redirect_url": "/powershell/module/exchange/new-federationtrust", + "redirect_url": "/powershell/module/exchangepowershell/new-federationtrust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-HybridConfiguration.md", - "redirect_url": "/powershell/module/exchange/new-hybridconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/new-hybridconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md", - "redirect_url": "/powershell/module/exchange/new-intraorganizationconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-intraorganizationconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-OnPremisesOrganization.md", - "redirect_url": "/powershell/module/exchange/new-onpremisesorganization", + "redirect_url": "/powershell/module/exchangepowershell/new-onpremisesorganization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/new-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/new-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederatedDomain.md", - "redirect_url": "/powershell/module/exchange/remove-federateddomain", + "redirect_url": "/powershell/module/exchangepowershell/remove-federateddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederationTrust.md", - "redirect_url": "/powershell/module/exchange/remove-federationtrust", + "redirect_url": "/powershell/module/exchangepowershell/remove-federationtrust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-HybridConfiguration.md", - "redirect_url": "/powershell/module/exchange/remove-hybridconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/remove-hybridconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md", - "redirect_url": "/powershell/module/exchange/remove-intraorganizationconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-intraorganizationconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md", - "redirect_url": "/powershell/module/exchange/remove-onpremisesorganization", + "redirect_url": "/powershell/module/exchangepowershell/remove-onpremisesorganization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/remove-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/remove-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md", - "redirect_url": "/powershell/module/exchange/set-federatedorganizationidentifier", + "redirect_url": "/powershell/module/exchangepowershell/set-federatedorganizationidentifier", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederationTrust.md", - "redirect_url": "/powershell/module/exchange/set-federationtrust", + "redirect_url": "/powershell/module/exchangepowershell/set-federationtrust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-HybridConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-hybridconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-hybridconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-HybridMailflow.md", - "redirect_url": "/powershell/module/exchange/set-hybridmailflow", + "redirect_url": "/powershell/module/exchangepowershell/set-hybridmailflow", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md", - "redirect_url": "/powershell/module/exchange/set-intraorganizationconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-intraorganizationconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-OnPremisesOrganization.md", - "redirect_url": "/powershell/module/exchange/set-onpremisesorganization", + "redirect_url": "/powershell/module/exchangepowershell/set-onpremisesorganization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md", - "redirect_url": "/powershell/module/exchange/set-pendingfederateddomain", + "redirect_url": "/powershell/module/exchangepowershell/set-pendingfederateddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-RemoteMailbox.md", - "redirect_url": "/powershell/module/exchange/set-remotemailbox", + "redirect_url": "/powershell/module/exchangepowershell/set-remotemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Test-FederationTrust.md", - "redirect_url": "/powershell/module/exchange/test-federationtrust", + "redirect_url": "/powershell/module/exchangepowershell/test-federationtrust", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md", - "redirect_url": "/powershell/module/exchange/test-federationtrustcertificate", + "redirect_url": "/powershell/module/exchangepowershell/test-federationtrustcertificate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Update-HybridConfiguration.md", - "redirect_url": "/powershell/module/exchange/update-hybridconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/update-hybridconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Update-Recipient.md", - "redirect_url": "/powershell/module/exchange/update-recipient", + "redirect_url": "/powershell/module/exchangepowershell/update-recipient", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Add-ResubmitRequest.md", - "redirect_url": "/powershell/module/exchange/add-resubmitrequest", + "redirect_url": "/powershell/module/exchangepowershell/add-resubmitrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Disable-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/disable-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/disable-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Enable-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/enable-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/enable-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Export-Message.md", - "redirect_url": "/powershell/module/exchange/export-message", + "redirect_url": "/powershell/module/exchangepowershell/export-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-AcceptedDomain.md", - "redirect_url": "/powershell/module/exchange/get-accepteddomain", + "redirect_url": "/powershell/module/exchangepowershell/get-accepteddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-AddressRewriteEntry.md", - "redirect_url": "/powershell/module/exchange/get-addressrewriteentry", + "redirect_url": "/powershell/module/exchangepowershell/get-addressrewriteentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-DeliveryAgentConnector.md", - "redirect_url": "/powershell/module/exchange/get-deliveryagentconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-deliveryagentconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-EdgeSubscription.md", - "redirect_url": "/powershell/module/exchange/get-edgesubscription", + "redirect_url": "/powershell/module/exchangepowershell/get-edgesubscription", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-EdgeSyncServiceConfig.md", - "redirect_url": "/powershell/module/exchange/get-edgesyncserviceconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-edgesyncserviceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ForeignConnector.md", - "redirect_url": "/powershell/module/exchange/get-foreignconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-foreignconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-FrontendTransportService.md", - "redirect_url": "/powershell/module/exchange/get-frontendtransportservice", + "redirect_url": "/powershell/module/exchangepowershell/get-frontendtransportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-InboundConnector.md", - "redirect_url": "/powershell/module/exchange/get-inboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-inboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MailboxTransportService.md", - "redirect_url": "/powershell/module/exchange/get-mailboxtransportservice", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxtransportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-Message.md", - "redirect_url": "/powershell/module/exchange/get-message", + "redirect_url": "/powershell/module/exchangepowershell/get-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrace.md", - "redirect_url": "/powershell/module/exchange/get-messagetrace", + "redirect_url": "/powershell/module/exchangepowershell/get-messagetrace", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTraceDetail.md", - "redirect_url": "/powershell/module/exchange/get-messagetracedetail", + "redirect_url": "/powershell/module/exchangepowershell/get-messagetracedetail", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrackingLog.md", - "redirect_url": "/powershell/module/exchange/get-messagetrackinglog", + "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackinglog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrackingReport.md", - "redirect_url": "/powershell/module/exchange/get-messagetrackingreport", + "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackingreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-NetworkConnectionInfo.md", - "redirect_url": "/powershell/module/exchange/get-networkconnectioninfo", + "redirect_url": "/powershell/module/exchangepowershell/get-networkconnectioninfo", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-OutboundConnector.md", - "redirect_url": "/powershell/module/exchange/get-outboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-Queue.md", - "redirect_url": "/powershell/module/exchange/get-queue", + "redirect_url": "/powershell/module/exchangepowershell/get-queue", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-QueueDigest.md", - "redirect_url": "/powershell/module/exchange/get-queuedigest", + "redirect_url": "/powershell/module/exchangepowershell/get-queuedigest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ReceiveConnector.md", - "redirect_url": "/powershell/module/exchange/get-receiveconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-receiveconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-RemoteDomain.md", - "redirect_url": "/powershell/module/exchange/get-remotedomain", + "redirect_url": "/powershell/module/exchangepowershell/get-remotedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ResubmitRequest.md", - "redirect_url": "/powershell/module/exchange/get-resubmitrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-resubmitrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-RoutingGroupConnector.md", - "redirect_url": "/powershell/module/exchange/get-routinggroupconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-routinggroupconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-SendConnector.md", - "redirect_url": "/powershell/module/exchange/get-sendconnector", + "redirect_url": "/powershell/module/exchangepowershell/get-sendconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-SystemMessage.md", - "redirect_url": "/powershell/module/exchange/get-systemmessage", + "redirect_url": "/powershell/module/exchangepowershell/get-systemmessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/get-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/get-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportConfig.md", - "redirect_url": "/powershell/module/exchange/get-transportconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-transportconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportPipeline.md", - "redirect_url": "/powershell/module/exchange/get-transportpipeline", + "redirect_url": "/powershell/module/exchangepowershell/get-transportpipeline", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportServer.md", - "redirect_url": "/powershell/module/exchange/get-transportserver", + "redirect_url": "/powershell/module/exchangepowershell/get-transportserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportService.md", - "redirect_url": "/powershell/module/exchange/get-transportservice", + "redirect_url": "/powershell/module/exchangepowershell/get-transportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Get-X400AuthoritativeDomain.md", - "redirect_url": "/powershell/module/exchange/get-x400authoritativedomain", + "redirect_url": "/powershell/module/exchangepowershell/get-x400authoritativedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Install-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/install-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/install-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-AcceptedDomain.md", - "redirect_url": "/powershell/module/exchange/new-accepteddomain", + "redirect_url": "/powershell/module/exchangepowershell/new-accepteddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-AddressRewriteEntry.md", - "redirect_url": "/powershell/module/exchange/new-addressrewriteentry", + "redirect_url": "/powershell/module/exchangepowershell/new-addressrewriteentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-DeliveryAgentConnector.md", - "redirect_url": "/powershell/module/exchange/new-deliveryagentconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-deliveryagentconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-EdgeSubscription.md", - "redirect_url": "/powershell/module/exchange/new-edgesubscription", + "redirect_url": "/powershell/module/exchangepowershell/new-edgesubscription", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-EdgeSyncServiceConfig.md", - "redirect_url": "/powershell/module/exchange/new-edgesyncserviceconfig", + "redirect_url": "/powershell/module/exchangepowershell/new-edgesyncserviceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-ForeignConnector.md", - "redirect_url": "/powershell/module/exchange/new-foreignconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-foreignconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-InboundConnector.md", - "redirect_url": "/powershell/module/exchange/new-inboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-inboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-OutboundConnector.md", - "redirect_url": "/powershell/module/exchange/new-outboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-outboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-ReceiveConnector.md", - "redirect_url": "/powershell/module/exchange/new-receiveconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-receiveconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-RemoteDomain.md", - "redirect_url": "/powershell/module/exchange/new-remotedomain", + "redirect_url": "/powershell/module/exchangepowershell/new-remotedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-RoutingGroupConnector.md", - "redirect_url": "/powershell/module/exchange/new-routinggroupconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-routinggroupconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-SendConnector.md", - "redirect_url": "/powershell/module/exchange/new-sendconnector", + "redirect_url": "/powershell/module/exchangepowershell/new-sendconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-SystemMessage.md", - "redirect_url": "/powershell/module/exchange/new-systemmessage", + "redirect_url": "/powershell/module/exchangepowershell/new-systemmessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/New-X400AuthoritativeDomain.md", - "redirect_url": "/powershell/module/exchange/new-x400authoritativedomain", + "redirect_url": "/powershell/module/exchangepowershell/new-x400authoritativedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Redirect-Message.md", - "redirect_url": "/powershell/module/exchange/redirect-message", + "redirect_url": "/powershell/module/exchangepowershell/redirect-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-AcceptedDomain.md", - "redirect_url": "/powershell/module/exchange/remove-accepteddomain", + "redirect_url": "/powershell/module/exchangepowershell/remove-accepteddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-AddressRewriteEntry.md", - "redirect_url": "/powershell/module/exchange/remove-addressrewriteentry", + "redirect_url": "/powershell/module/exchangepowershell/remove-addressrewriteentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-DeliveryAgentConnector.md", - "redirect_url": "/powershell/module/exchange/remove-deliveryagentconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-deliveryagentconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-EdgeSubscription.md", - "redirect_url": "/powershell/module/exchange/remove-edgesubscription", + "redirect_url": "/powershell/module/exchangepowershell/remove-edgesubscription", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ForeignConnector.md", - "redirect_url": "/powershell/module/exchange/remove-foreignconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-foreignconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-InboundConnector.md", - "redirect_url": "/powershell/module/exchange/remove-inboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-inboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-Message.md", - "redirect_url": "/powershell/module/exchange/remove-message", + "redirect_url": "/powershell/module/exchangepowershell/remove-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-OutboundConnector.md", - "redirect_url": "/powershell/module/exchange/remove-outboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-outboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ReceiveConnector.md", - "redirect_url": "/powershell/module/exchange/remove-receiveconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-receiveconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-RemoteDomain.md", - "redirect_url": "/powershell/module/exchange/remove-remotedomain", + "redirect_url": "/powershell/module/exchangepowershell/remove-remotedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ResubmitRequest.md", - "redirect_url": "/powershell/module/exchange/remove-resubmitrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-resubmitrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-RoutingGroupConnector.md", - "redirect_url": "/powershell/module/exchange/remove-routinggroupconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-routinggroupconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-SendConnector.md", - "redirect_url": "/powershell/module/exchange/remove-sendconnector", + "redirect_url": "/powershell/module/exchangepowershell/remove-sendconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-SystemMessage.md", - "redirect_url": "/powershell/module/exchange/remove-systemmessage", + "redirect_url": "/powershell/module/exchangepowershell/remove-systemmessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-X400AuthoritativeDomain.md", - "redirect_url": "/powershell/module/exchange/remove-x400authoritativedomain", + "redirect_url": "/powershell/module/exchangepowershell/remove-x400authoritativedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Resume-Message.md", - "redirect_url": "/powershell/module/exchange/resume-message", + "redirect_url": "/powershell/module/exchangepowershell/resume-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Resume-Queue.md", - "redirect_url": "/powershell/module/exchange/resume-queue", + "redirect_url": "/powershell/module/exchangepowershell/resume-queue", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Retry-Queue.md", - "redirect_url": "/powershell/module/exchange/retry-queue", + "redirect_url": "/powershell/module/exchangepowershell/retry-queue", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Search-MessageTrackingReport.md", - "redirect_url": "/powershell/module/exchange/search-messagetrackingreport", + "redirect_url": "/powershell/module/exchangepowershell/search-messagetrackingreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AcceptedDomain.md", - "redirect_url": "/powershell/module/exchange/set-accepteddomain", + "redirect_url": "/powershell/module/exchangepowershell/set-accepteddomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AddressRewriteEntry.md", - "redirect_url": "/powershell/module/exchange/set-addressrewriteentry", + "redirect_url": "/powershell/module/exchangepowershell/set-addressrewriteentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-DeliveryAgentConnector.md", - "redirect_url": "/powershell/module/exchange/set-deliveryagentconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-deliveryagentconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-EdgeSyncServiceConfig.md", - "redirect_url": "/powershell/module/exchange/set-edgesyncserviceconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-edgesyncserviceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ForeignConnector.md", - "redirect_url": "/powershell/module/exchange/set-foreignconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-foreignconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-FrontendTransportService.md", - "redirect_url": "/powershell/module/exchange/set-frontendtransportservice", + "redirect_url": "/powershell/module/exchangepowershell/set-frontendtransportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-InboundConnector.md", - "redirect_url": "/powershell/module/exchange/set-inboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-inboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-MailboxTransportService.md", - "redirect_url": "/powershell/module/exchange/set-mailboxtransportservice", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxtransportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-OutboundConnector.md", - "redirect_url": "/powershell/module/exchange/set-outboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-outboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ReceiveConnector.md", - "redirect_url": "/powershell/module/exchange/set-receiveconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-receiveconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RemoteDomain.md", - "redirect_url": "/powershell/module/exchange/set-remotedomain", + "redirect_url": "/powershell/module/exchangepowershell/set-remotedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ResubmitRequest.md", - "redirect_url": "/powershell/module/exchange/set-resubmitrequest", + "redirect_url": "/powershell/module/exchangepowershell/set-resubmitrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RoutingGroupConnector.md", - "redirect_url": "/powershell/module/exchange/set-routinggroupconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-routinggroupconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-SendConnector.md", - "redirect_url": "/powershell/module/exchange/set-sendconnector", + "redirect_url": "/powershell/module/exchangepowershell/set-sendconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-SystemMessage.md", - "redirect_url": "/powershell/module/exchange/set-systemmessage", + "redirect_url": "/powershell/module/exchangepowershell/set-systemmessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/set-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/set-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportConfig.md", - "redirect_url": "/powershell/module/exchange/set-transportconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-transportconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportServer.md", - "redirect_url": "/powershell/module/exchange/set-transportserver", + "redirect_url": "/powershell/module/exchangepowershell/set-transportserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportService.md", - "redirect_url": "/powershell/module/exchange/set-transportservice", + "redirect_url": "/powershell/module/exchangepowershell/set-transportservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Set-X400AuthoritativeDomain.md", - "redirect_url": "/powershell/module/exchange/set-x400authoritativedomain", + "redirect_url": "/powershell/module/exchangepowershell/set-x400authoritativedomain", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Start-EdgeSynchronization.md", - "redirect_url": "/powershell/module/exchange/start-edgesynchronization", + "redirect_url": "/powershell/module/exchangepowershell/start-edgesynchronization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Start-HistoricalSearch.md", - "redirect_url": "/powershell/module/exchange/start-historicalsearch", + "redirect_url": "/powershell/module/exchangepowershell/start-historicalsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Stop-HistoricalSearch.md", - "redirect_url": "/powershell/module/exchange/stop-historicalsearch", + "redirect_url": "/powershell/module/exchangepowershell/stop-historicalsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Suspend-Message.md", - "redirect_url": "/powershell/module/exchange/suspend-message", + "redirect_url": "/powershell/module/exchangepowershell/suspend-message", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Suspend-Queue.md", - "redirect_url": "/powershell/module/exchange/suspend-queue", + "redirect_url": "/powershell/module/exchangepowershell/suspend-queue", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Test-EdgeSynchronization.md", - "redirect_url": "/powershell/module/exchange/test-edgesynchronization", + "redirect_url": "/powershell/module/exchangepowershell/test-edgesynchronization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Test-Mailflow.md", - "redirect_url": "/powershell/module/exchange/test-mailflow", + "redirect_url": "/powershell/module/exchangepowershell/test-mailflow", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Test-SmtpConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-smtpconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-smtpconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Uninstall-TransportAgent.md", - "redirect_url": "/powershell/module/exchange/uninstall-transportagent", + "redirect_url": "/powershell/module/exchangepowershell/uninstall-transportagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mail-flow/Validate-OutboundConnector.md", - "redirect_url": "/powershell/module/exchange/validate-outboundconnector", + "redirect_url": "/powershell/module/exchangepowershell/validate-outboundconnector", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/clean-mailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/clean-mailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md", - "redirect_url": "/powershell/module/exchange/disable-mailboxquarantine", + "redirect_url": "/powershell/module/exchangepowershell/disable-mailboxquarantine", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Disable-MetaCacheDatabase.md", - "redirect_url": "/powershell/module/exchange/disable-metacachedatabase", + "redirect_url": "/powershell/module/exchangepowershell/disable-metacachedatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Dismount-Database.md", - "redirect_url": "/powershell/module/exchange/dismount-database", + "redirect_url": "/powershell/module/exchangepowershell/dismount-database", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md", - "redirect_url": "/powershell/module/exchange/enable-mailboxquarantine", + "redirect_url": "/powershell/module/exchangepowershell/enable-mailboxquarantine", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Enable-MetaCacheDatabase.md", - "redirect_url": "/powershell/module/exchange/enable-metacachedatabase", + "redirect_url": "/powershell/module/exchangepowershell/enable-metacachedatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md", - "redirect_url": "/powershell/module/exchange/get-failedcontentindexdocuments", + "redirect_url": "/powershell/module/exchangepowershell/get-failedcontentindexdocuments", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/get-mailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxRepairRequest.md", - "redirect_url": "/powershell/module/exchange/get-mailboxrepairrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrepairrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxServer.md", - "redirect_url": "/powershell/module/exchange/get-mailboxserver", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md", - "redirect_url": "/powershell/module/exchange/get-searchdocumentformat", + "redirect_url": "/powershell/module/exchangepowershell/get-searchdocumentformat", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-StoreUsageStatistics.md", - "redirect_url": "/powershell/module/exchange/get-storeusagestatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-storeusagestatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Mount-Database.md", - "redirect_url": "/powershell/module/exchange/mount-database", + "redirect_url": "/powershell/module/exchangepowershell/mount-database", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Move-DatabasePath.md", - "redirect_url": "/powershell/module/exchange/move-databasepath", + "redirect_url": "/powershell/module/exchangepowershell/move-databasepath", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/new-mailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md", - "redirect_url": "/powershell/module/exchange/new-mailboxrepairrequest", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrepairrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md", - "redirect_url": "/powershell/module/exchange/new-searchdocumentformat", + "redirect_url": "/powershell/module/exchangepowershell/new-searchdocumentformat", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-MailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxrepairrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrepairrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md", - "redirect_url": "/powershell/module/exchange/remove-searchdocumentformat", + "redirect_url": "/powershell/module/exchangepowershell/remove-searchdocumentformat", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-StoreMailbox.md", - "redirect_url": "/powershell/module/exchange/remove-storemailbox", + "redirect_url": "/powershell/module/exchangepowershell/remove-storemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxDatabase.md", - "redirect_url": "/powershell/module/exchange/set-mailboxdatabase", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxServer.md", - "redirect_url": "/powershell/module/exchange/set-mailboxserver", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-SearchDocumentFormat.md", - "redirect_url": "/powershell/module/exchange/set-searchdocumentformat", + "redirect_url": "/powershell/module/exchangepowershell/set-searchdocumentformat", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md", - "redirect_url": "/powershell/module/exchange/test-assistanthealth", + "redirect_url": "/powershell/module/exchangepowershell/test-assistanthealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md", - "redirect_url": "/powershell/module/exchange/test-exchangesearch", + "redirect_url": "/powershell/module/exchangepowershell/test-exchangesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-MRSHealth.md", - "redirect_url": "/powershell/module/exchange/test-mrshealth", + "redirect_url": "/powershell/module/exchangepowershell/test-mrshealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md", - "redirect_url": "/powershell/module/exchange/update-databaseschema", + "redirect_url": "/powershell/module/exchangepowershell/update-databaseschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md", - "redirect_url": "/powershell/module/exchange/update-filedistributionservice", + "redirect_url": "/powershell/module/exchangepowershell/update-filedistributionservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-StoreMailboxState.md", - "redirect_url": "/powershell/module/exchange/update-storemailboxstate", + "redirect_url": "/powershell/module/exchangepowershell/update-storemailboxstate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxFolderPermission.md", - "redirect_url": "/powershell/module/exchange/add-mailboxfolderpermission", + "redirect_url": "/powershell/module/exchangepowershell/add-mailboxfolderpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxPermission.md", - "redirect_url": "/powershell/module/exchange/add-mailboxpermission", + "redirect_url": "/powershell/module/exchangepowershell/add-mailboxpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Add-RecipientPermission.md", - "redirect_url": "/powershell/module/exchange/add-recipientpermission", + "redirect_url": "/powershell/module/exchangepowershell/add-recipientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Connect-Mailbox.md", - "redirect_url": "/powershell/module/exchange/connect-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/connect-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-App.md", - "redirect_url": "/powershell/module/exchange/disable-app", + "redirect_url": "/powershell/module/exchangepowershell/disable-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-InboxRule.md", - "redirect_url": "/powershell/module/exchange/disable-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-Mailbox.md", - "redirect_url": "/powershell/module/exchange/disable-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/disable-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-ServiceEmailChannel.md", - "redirect_url": "/powershell/module/exchange/disable-serviceemailchannel", + "redirect_url": "/powershell/module/exchangepowershell/disable-serviceemailchannel", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-SweepRule.md", - "redirect_url": "/powershell/module/exchange/disable-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/disable-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-App.md", - "redirect_url": "/powershell/module/exchange/enable-app", + "redirect_url": "/powershell/module/exchangepowershell/enable-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-InboxRule.md", - "redirect_url": "/powershell/module/exchange/enable-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-Mailbox.md", - "redirect_url": "/powershell/module/exchange/enable-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/enable-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-ServiceEmailChannel.md", - "redirect_url": "/powershell/module/exchange/enable-serviceemailchannel", + "redirect_url": "/powershell/module/exchangepowershell/enable-serviceemailchannel", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-SweepRule.md", - "redirect_url": "/powershell/module/exchange/enable-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/enable-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Export-MailboxDiagnosticLogs.md", - "redirect_url": "/powershell/module/exchange/export-mailboxdiagnosticlogs", + "redirect_url": "/powershell/module/exchangepowershell/export-mailboxdiagnosticlogs", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Export-RecipientDataProperty.md", - "redirect_url": "/powershell/module/exchange/export-recipientdataproperty", + "redirect_url": "/powershell/module/exchangepowershell/export-recipientdataproperty", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-App.md", - "redirect_url": "/powershell/module/exchange/get-app", + "redirect_url": "/powershell/module/exchangepowershell/get-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticAnalysis.md", - "redirect_url": "/powershell/module/exchange/get-calendardiagnosticanalysis", + "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticanalysis", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticLog.md", - "redirect_url": "/powershell/module/exchange/get-calendardiagnosticlog", + "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticObjects.md", - "redirect_url": "/powershell/module/exchange/get-calendardiagnosticobjects", + "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticobjects", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarNotification.md", - "redirect_url": "/powershell/module/exchange/get-calendarnotification", + "redirect_url": "/powershell/module/exchangepowershell/get-calendarnotification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarProcessing.md", - "redirect_url": "/powershell/module/exchange/get-calendarprocessing", + "redirect_url": "/powershell/module/exchangepowershell/get-calendarprocessing", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Clutter.md", - "redirect_url": "/powershell/module/exchange/get-clutter", + "redirect_url": "/powershell/module/exchangepowershell/get-clutter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-FocusedInbox.md", - "redirect_url": "/powershell/module/exchange/get-focusedinbox", + "redirect_url": "/powershell/module/exchangepowershell/get-focusedinbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-InboxRule.md", - "redirect_url": "/powershell/module/exchange/get-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/get-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Mailbox.md", - "redirect_url": "/powershell/module/exchange/get-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxAutoReplyConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxautoreplyconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxautoreplyconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxCalendarFolder.md", - "redirect_url": "/powershell/module/exchange/get-mailboxcalendarfolder", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/get-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mailboxexportrequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolder.md", - "redirect_url": "/powershell/module/exchange/get-mailboxfolder", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderPermission.md", - "redirect_url": "/powershell/module/exchange/get-mailboxfolderpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mailboxfolderstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/get-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mailboximportrequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxLocation.md", - "redirect_url": "/powershell/module/exchange/get-mailboxlocation", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxlocation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPermission.md", - "redirect_url": "/powershell/module/exchange/get-mailboxpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPlan.md", - "redirect_url": "/powershell/module/exchange/get-mailboxplan", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxsentitemsconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsentitemsconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxStatistics.md", - "redirect_url": "/powershell/module/exchange/get-mailboxstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxUserConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-mailboxuserconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxuserconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MessageCategory.md", - "redirect_url": "/powershell/module/exchange/get-messagecategory", + "redirect_url": "/powershell/module/exchangepowershell/get-messagecategory", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Place.md", - "redirect_url": "/powershell/module/exchange/get-place", + "redirect_url": "/powershell/module/exchangepowershell/get-place", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecipientPermission.md", - "redirect_url": "/powershell/module/exchange/get-recipientpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-recipientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecoverableItems.md", - "redirect_url": "/powershell/module/exchange/get-recoverableitems", + "redirect_url": "/powershell/module/exchangepowershell/get-recoverableitems", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-ResourceConfig.md", - "redirect_url": "/powershell/module/exchange/get-resourceconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-resourceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-SweepRule.md", - "redirect_url": "/powershell/module/exchange/get-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/get-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Get-UserPhoto.md", - "redirect_url": "/powershell/module/exchange/get-userphoto", + "redirect_url": "/powershell/module/exchangepowershell/get-userphoto", "redirect_document_id": false }, { @@ -3152,1987 +3152,1987 @@ }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Import-RecipientDataProperty.md", - "redirect_url": "/powershell/module/exchange/import-recipientdataproperty", + "redirect_url": "/powershell/module/exchangepowershell/import-recipientdataproperty", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-App.md", - "redirect_url": "/powershell/module/exchange/new-app", + "redirect_url": "/powershell/module/exchangepowershell/new-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-InboxRule.md", - "redirect_url": "/powershell/module/exchange/new-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/new-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-Mailbox.md", - "redirect_url": "/powershell/module/exchange/new-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/new-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/new-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxFolder.md", - "redirect_url": "/powershell/module/exchange/new-mailboxfolder", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/new-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/new-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailMessage.md", - "redirect_url": "/powershell/module/exchange/new-mailmessage", + "redirect_url": "/powershell/module/exchangepowershell/new-mailmessage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-SiteMailbox.md", - "redirect_url": "/powershell/module/exchange/new-sitemailbox", + "redirect_url": "/powershell/module/exchangepowershell/new-sitemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/New-SweepRule.md", - "redirect_url": "/powershell/module/exchange/new-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/new-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-App.md", - "redirect_url": "/powershell/module/exchange/remove-app", + "redirect_url": "/powershell/module/exchangepowershell/remove-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-CalendarEvents.md", - "redirect_url": "/powershell/module/exchange/remove-calendarevents", + "redirect_url": "/powershell/module/exchangepowershell/remove-calendarevents", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-InboxRule.md", - "redirect_url": "/powershell/module/exchange/remove-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-Mailbox.md", - "redirect_url": "/powershell/module/exchange/remove-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxFolderPermission.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxfolderpermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxfolderpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/remove-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxPermission.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxpermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxUserConfiguration.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxuserconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxuserconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-RecipientPermission.md", - "redirect_url": "/powershell/module/exchange/remove-recipientpermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-recipientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-SweepRule.md", - "redirect_url": "/powershell/module/exchange/remove-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/remove-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-UserPhoto.md", - "redirect_url": "/powershell/module/exchange/remove-userphoto", + "redirect_url": "/powershell/module/exchangepowershell/remove-userphoto", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-Mailbox.md", - "redirect_url": "/powershell/module/exchange/restore-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/restore-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-RecoverableItems.md", - "redirect_url": "/powershell/module/exchange/restore-recoverableitems", + "redirect_url": "/powershell/module/exchangepowershell/restore-recoverableitems", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/resume-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/resume-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/resume-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Search-Mailbox.md", - "redirect_url": "/powershell/module/exchange/search-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/search-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-App.md", - "redirect_url": "/powershell/module/exchange/set-app", + "redirect_url": "/powershell/module/exchangepowershell/set-app", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarNotification.md", - "redirect_url": "/powershell/module/exchange/set-calendarnotification", + "redirect_url": "/powershell/module/exchangepowershell/set-calendarnotification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarProcessing.md", - "redirect_url": "/powershell/module/exchange/set-calendarprocessing", + "redirect_url": "/powershell/module/exchangepowershell/set-calendarprocessing", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Clutter.md", - "redirect_url": "/powershell/module/exchange/set-clutter", + "redirect_url": "/powershell/module/exchangepowershell/set-clutter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-FocusedInbox.md", - "redirect_url": "/powershell/module/exchange/set-focusedinbox", + "redirect_url": "/powershell/module/exchangepowershell/set-focusedinbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-InboxRule.md", - "redirect_url": "/powershell/module/exchange/set-inboxrule", + "redirect_url": "/powershell/module/exchangepowershell/set-inboxrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Mailbox.md", - "redirect_url": "/powershell/module/exchange/set-mailbox", + "redirect_url": "/powershell/module/exchangepowershell/set-mailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxautoreplyconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxautoreplyconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxCalendarFolder.md", - "redirect_url": "/powershell/module/exchange/set-mailboxcalendarfolder", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/set-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxFolderPermission.md", - "redirect_url": "/powershell/module/exchange/set-mailboxfolderpermission", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxfolderpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/set-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxPlan.md", - "redirect_url": "/powershell/module/exchange/set-mailboxplan", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/set-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md", - "redirect_url": "/powershell/module/exchange/set-mailboxsentitemsconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsentitemsconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Place.md", - "redirect_url": "/powershell/module/exchange/set-place", + "redirect_url": "/powershell/module/exchangepowershell/set-place", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-ResourceConfig.md", - "redirect_url": "/powershell/module/exchange/set-resourceconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-resourceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-SweepRule.md", - "redirect_url": "/powershell/module/exchange/set-sweeprule", + "redirect_url": "/powershell/module/exchangepowershell/set-sweeprule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Set-UserPhoto.md", - "redirect_url": "/powershell/module/exchange/set-userphoto", + "redirect_url": "/powershell/module/exchangepowershell/set-userphoto", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxExportRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-mailboxexportrequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxexportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxImportRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-mailboximportrequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboximportrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxRestoreRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-mailboxrestorerequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxrestorerequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Test-MAPIConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-mapiconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-mapiconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/mailboxes/Undo-SoftDeletedMailbox.md", - "redirect_url": "/powershell/module/exchange/undo-softdeletedmailbox", + "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedmailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Complete-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/complete-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/complete-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Export-MigrationReport.md", - "redirect_url": "/powershell/module/exchange/export-migrationreport", + "redirect_url": "/powershell/module/exchangepowershell/export-migrationreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/get-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationConfig.md", - "redirect_url": "/powershell/module/exchange/get-migrationconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationEndpoint.md", - "redirect_url": "/powershell/module/exchange/get-migrationendpoint", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationendpoint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationStatistics.md", - "redirect_url": "/powershell/module/exchange/get-migrationstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationUser.md", - "redirect_url": "/powershell/module/exchange/get-migrationuser", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationUserStatistics.md", - "redirect_url": "/powershell/module/exchange/get-migrationuserstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-migrationuserstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/get-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/get-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MoveRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-moverequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-moverequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxmigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxmigrationrequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMigrationRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermigrationrequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMoveRequestStatistics.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermoverequeststatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequeststatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/new-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/new-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationEndpoint.md", - "redirect_url": "/powershell/module/exchange/new-migrationendpoint", + "redirect_url": "/powershell/module/exchangepowershell/new-migrationendpoint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/new-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/new-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/new-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/new-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/remove-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/remove-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationEndpoint.md", - "redirect_url": "/powershell/module/exchange/remove-migrationendpoint", + "redirect_url": "/powershell/module/exchangepowershell/remove-migrationendpoint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationUser.md", - "redirect_url": "/powershell/module/exchange/remove-migrationuser", + "redirect_url": "/powershell/module/exchangepowershell/remove-migrationuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/remove-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/remove-publicfoldermailboxmigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermailboxmigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/remove-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/remove-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/resume-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/resume-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/resume-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/set-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/set-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationConfig.md", - "redirect_url": "/powershell/module/exchange/set-migrationconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-migrationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationEndpoint.md", - "redirect_url": "/powershell/module/exchange/set-migrationendpoint", + "redirect_url": "/powershell/module/exchangepowershell/set-migrationendpoint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationUser.md", - "redirect_url": "/powershell/module/exchange/set-migrationuser", + "redirect_url": "/powershell/module/exchangepowershell/set-migrationuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/set-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/set-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/set-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/set-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Start-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/start-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/start-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Start-MigrationUser.md", - "redirect_url": "/powershell/module/exchange/start-migrationuser", + "redirect_url": "/powershell/module/exchangepowershell/start-migrationuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationBatch.md", - "redirect_url": "/powershell/module/exchange/stop-migrationbatch", + "redirect_url": "/powershell/module/exchangepowershell/stop-migrationbatch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationUser.md", - "redirect_url": "/powershell/module/exchange/stop-migrationuser", + "redirect_url": "/powershell/module/exchangepowershell/stop-migrationuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-MoveRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-moverequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-moverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-publicfoldermailboxmigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermailboxmigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-publicfoldermigrationrequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermigrationrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMoveRequest.md", - "redirect_url": "/powershell/module/exchange/suspend-publicfoldermoverequest", + "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermoverequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/move-and-migration/Test-MigrationServerAvailability.md", - "redirect_url": "/powershell/module/exchange/test-migrationserveravailability", + "redirect_url": "/powershell/module/exchangepowershell/test-migrationserveravailability", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Disable-CmdletExtensionAgent.md", - "redirect_url": "/powershell/module/exchange/disable-cmdletextensionagent", + "redirect_url": "/powershell/module/exchangepowershell/disable-cmdletextensionagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Enable-CmdletExtensionAgent.md", - "redirect_url": "/powershell/module/exchange/enable-cmdletextensionagent", + "redirect_url": "/powershell/module/exchangepowershell/enable-cmdletextensionagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Enable-OrganizationCustomization.md", - "redirect_url": "/powershell/module/exchange/enable-organizationcustomization", + "redirect_url": "/powershell/module/exchangepowershell/enable-organizationcustomization", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-AccessToCustomerDataRequest.md", - "redirect_url": "/powershell/module/exchange/get-accesstocustomerdatarequest", + "redirect_url": "/powershell/module/exchangepowershell/get-accesstocustomerdatarequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ApplicationAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/get-applicationaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-applicationaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthConfig.md", - "redirect_url": "/powershell/module/exchange/get-authconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-authconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthenticationPolicy.md", - "redirect_url": "/powershell/module/exchange/get-authenticationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-authenticationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-AuthServer.md", - "redirect_url": "/powershell/module/exchange/get-authserver", + "redirect_url": "/powershell/module/exchangepowershell/get-authserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-CmdletExtensionAgent.md", - "redirect_url": "/powershell/module/exchange/get-cmdletextensionagent", + "redirect_url": "/powershell/module/exchangepowershell/get-cmdletextensionagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeAssistanceConfig.md", - "redirect_url": "/powershell/module/exchange/get-exchangeassistanceconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangeassistanceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeDiagnosticInfo.md", - "redirect_url": "/powershell/module/exchange/get-exchangediagnosticinfo", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangediagnosticinfo", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServer.md", - "redirect_url": "/powershell/module/exchange/get-exchangeserver", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicense.md", - "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicense", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicense", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicenseUser.md", - "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicenseuser", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicenseuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeSettings.md", - "redirect_url": "/powershell/module/exchange/get-exchangesettings", + "redirect_url": "/powershell/module/exchangepowershell/get-exchangesettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-Notification.md", - "redirect_url": "/powershell/module/exchange/get-notification", + "redirect_url": "/powershell/module/exchangepowershell/get-notification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-OrganizationConfig.md", - "redirect_url": "/powershell/module/exchange/get-organizationconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-organizationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-PartnerApplication.md", - "redirect_url": "/powershell/module/exchange/get-partnerapplication", + "redirect_url": "/powershell/module/exchangepowershell/get-partnerapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-PerimeterConfig.md", - "redirect_url": "/powershell/module/exchange/get-perimeterconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-perimeterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Get-SettingOverride.md", - "redirect_url": "/powershell/module/exchange/get-settingoverride", + "redirect_url": "/powershell/module/exchangepowershell/get-settingoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-ApplicationAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/new-applicationaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-applicationaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-AuthenticationPolicy.md", - "redirect_url": "/powershell/module/exchange/new-authenticationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-authenticationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-AuthServer.md", - "redirect_url": "/powershell/module/exchange/new-authserver", + "redirect_url": "/powershell/module/exchangepowershell/new-authserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-ExchangeSettings.md", - "redirect_url": "/powershell/module/exchange/new-exchangesettings", + "redirect_url": "/powershell/module/exchangepowershell/new-exchangesettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-PartnerApplication.md", - "redirect_url": "/powershell/module/exchange/new-partnerapplication", + "redirect_url": "/powershell/module/exchangepowershell/new-partnerapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/New-SettingOverride.md", - "redirect_url": "/powershell/module/exchange/new-settingoverride", + "redirect_url": "/powershell/module/exchangepowershell/new-settingoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Remove-ApplicationAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-applicationaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-applicationaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthenticationPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-authenticationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-authenticationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthServer.md", - "redirect_url": "/powershell/module/exchange/remove-authserver", + "redirect_url": "/powershell/module/exchangepowershell/remove-authserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Remove-PartnerApplication.md", - "redirect_url": "/powershell/module/exchange/remove-partnerapplication", + "redirect_url": "/powershell/module/exchangepowershell/remove-partnerapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Remove-SettingOverride.md", - "redirect_url": "/powershell/module/exchange/remove-settingoverride", + "redirect_url": "/powershell/module/exchangepowershell/remove-settingoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-AccessToCustomerDataRequest.md", - "redirect_url": "/powershell/module/exchange/set-accesstocustomerdatarequest", + "redirect_url": "/powershell/module/exchangepowershell/set-accesstocustomerdatarequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-ApplicationAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/set-applicationaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-applicationaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthConfig.md", - "redirect_url": "/powershell/module/exchange/set-authconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-authconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthenticationPolicy.md", - "redirect_url": "/powershell/module/exchange/set-authenticationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-authenticationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-AuthServer.md", - "redirect_url": "/powershell/module/exchange/set-authserver", + "redirect_url": "/powershell/module/exchangepowershell/set-authserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-CmdletExtensionAgent.md", - "redirect_url": "/powershell/module/exchange/set-cmdletextensionagent", + "redirect_url": "/powershell/module/exchangepowershell/set-cmdletextensionagent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeAssistanceConfig.md", - "redirect_url": "/powershell/module/exchange/set-exchangeassistanceconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-exchangeassistanceconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeServer.md", - "redirect_url": "/powershell/module/exchange/set-exchangeserver", + "redirect_url": "/powershell/module/exchangepowershell/set-exchangeserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeSettings.md", - "redirect_url": "/powershell/module/exchange/set-exchangesettings", + "redirect_url": "/powershell/module/exchangepowershell/set-exchangesettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-Notification.md", - "redirect_url": "/powershell/module/exchange/set-notification", + "redirect_url": "/powershell/module/exchangepowershell/set-notification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-OrganizationConfig.md", - "redirect_url": "/powershell/module/exchange/set-organizationconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-organizationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-PartnerApplication.md", - "redirect_url": "/powershell/module/exchange/set-partnerapplication", + "redirect_url": "/powershell/module/exchangepowershell/set-partnerapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-PerimeterConfig.md", - "redirect_url": "/powershell/module/exchange/set-perimeterconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-perimeterconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Set-SettingOverride.md", - "redirect_url": "/powershell/module/exchange/set-settingoverride", + "redirect_url": "/powershell/module/exchangepowershell/set-settingoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Test-ApplicationAccessPolicy.md", - "redirect_url": "/powershell/module/exchange/test-applicationaccesspolicy", + "redirect_url": "/powershell/module/exchangepowershell/test-applicationaccesspolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Test-OAuthConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-oauthconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-oauthconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Test-SystemHealth.md", - "redirect_url": "/powershell/module/exchange/test-systemhealth", + "redirect_url": "/powershell/module/exchangepowershell/test-systemhealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/organization/Update-ExchangeHelp.md", - "redirect_url": "/powershell/module/exchange/update-exchangehelp", + "redirect_url": "/powershell/module/exchangepowershell/update-exchangehelp", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-JournalArchiving.md", - "redirect_url": "/powershell/module/exchange/disable-journalarchiving", + "redirect_url": "/powershell/module/exchangepowershell/disable-journalarchiving", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-JournalRule.md", - "redirect_url": "/powershell/module/exchange/disable-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/disable-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-TransportRule.md", - "redirect_url": "/powershell/module/exchange/disable-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-JournalRule.md", - "redirect_url": "/powershell/module/exchange/enable-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/enable-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-TransportRule.md", - "redirect_url": "/powershell/module/exchange/enable-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-JournalRuleCollection.md", - "redirect_url": "/powershell/module/exchange/export-journalrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/export-journalrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-TransportRuleCollection.md", - "redirect_url": "/powershell/module/exchange/export-transportrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/export-transportrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/get-activityalert", + "redirect_url": "/powershell/module/exchangepowershell/get-activityalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-AdministrativeUnit.md", - "redirect_url": "/powershell/module/exchange/get-administrativeunit", + "redirect_url": "/powershell/module/exchangepowershell/get-administrativeunit", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md", - "redirect_url": "/powershell/module/exchange/get-informationbarrierpoliciesapplicationstatus", + "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpoliciesapplicationstatus", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md", - "redirect_url": "/powershell/module/exchange/get-informationbarrierpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md", - "redirect_url": "/powershell/module/exchange/get-informationbarrierrecipientstatus", + "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierrecipientstatus", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-JournalRule.md", - "redirect_url": "/powershell/module/exchange/get-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/get-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-Label.md", - "redirect_url": "/powershell/module/exchange/get-label", + "redirect_url": "/powershell/module/exchangepowershell/get-label", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-LabelPolicy.md", - "redirect_url": "/powershell/module/exchange/get-labelpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-labelpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-MessageClassification.md", - "redirect_url": "/powershell/module/exchange/get-messageclassification", + "redirect_url": "/powershell/module/exchangepowershell/get-messageclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-OrganizationSegment.md", - "redirect_url": "/powershell/module/exchange/get-organizationsegment", + "redirect_url": "/powershell/module/exchangepowershell/get-organizationsegment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/get-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/get-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-ProtectionAlert.md", - "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-SupervisoryReviewPolicyV2.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewpolicyv2", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyv2", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewrule", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRule.md", - "redirect_url": "/powershell/module/exchange/get-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/get-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRuleAction.md", - "redirect_url": "/powershell/module/exchange/get-transportruleaction", + "redirect_url": "/powershell/module/exchangepowershell/get-transportruleaction", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRulePredicate.md", - "redirect_url": "/powershell/module/exchange/get-transportrulepredicate", + "redirect_url": "/powershell/module/exchangepowershell/get-transportrulepredicate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Import-JournalRuleCollection.md", - "redirect_url": "/powershell/module/exchange/import-journalrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/import-journalrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Import-TransportRuleCollection.md", - "redirect_url": "/powershell/module/exchange/import-transportrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/import-transportrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md", - "redirect_url": "/powershell/module/exchange/install-unifiedcomplianceprerequisite", + "redirect_url": "/powershell/module/exchangepowershell/install-unifiedcomplianceprerequisite", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/new-activityalert", + "redirect_url": "/powershell/module/exchangepowershell/new-activityalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-InformationBarrierPolicy.md", - "redirect_url": "/powershell/module/exchange/new-informationbarrierpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-informationbarrierpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-JournalRule.md", - "redirect_url": "/powershell/module/exchange/new-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/new-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-Label.md", - "redirect_url": "/powershell/module/exchange/new-label", + "redirect_url": "/powershell/module/exchangepowershell/new-label", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-LabelPolicy.md", - "redirect_url": "/powershell/module/exchange/new-labelpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-labelpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-MessageClassification.md", - "redirect_url": "/powershell/module/exchange/new-messageclassification", + "redirect_url": "/powershell/module/exchangepowershell/new-messageclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-OrganizationSegment.md", - "redirect_url": "/powershell/module/exchange/new-organizationsegment", + "redirect_url": "/powershell/module/exchangepowershell/new-organizationsegment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/new-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/new-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ProtectionAlert.md", - "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md", - "redirect_url": "/powershell/module/exchange/new-supervisoryreviewpolicyv2", + "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewpolicyv2", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-SupervisoryReviewRule.md", - "redirect_url": "/powershell/module/exchange/new-supervisoryreviewrule", + "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-TransportRule.md", - "redirect_url": "/powershell/module/exchange/new-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/new-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/remove-activityalert", + "redirect_url": "/powershell/module/exchangepowershell/remove-activityalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-InformationBarrierPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-informationbarrierpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-informationbarrierpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-JournalRule.md", - "redirect_url": "/powershell/module/exchange/remove-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-Label.md", - "redirect_url": "/powershell/module/exchange/remove-label", + "redirect_url": "/powershell/module/exchangepowershell/remove-label", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-LabelPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-labelpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-labelpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-MessageClassification.md", - "redirect_url": "/powershell/module/exchange/remove-messageclassification", + "redirect_url": "/powershell/module/exchangepowershell/remove-messageclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-OrganizationSegment.md", - "redirect_url": "/powershell/module/exchange/remove-organizationsegment", + "redirect_url": "/powershell/module/exchangepowershell/remove-organizationsegment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/remove-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ProtectionAlert.md", - "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md", - "redirect_url": "/powershell/module/exchange/remove-supervisoryreviewpolicyv2", + "redirect_url": "/powershell/module/exchangepowershell/remove-supervisoryreviewpolicyv2", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-TransportRule.md", - "redirect_url": "/powershell/module/exchange/remove-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/set-activityalert", + "redirect_url": "/powershell/module/exchangepowershell/set-activityalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md", - "redirect_url": "/powershell/module/exchange/set-informationbarrierpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-informationbarrierpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-JournalRule.md", - "redirect_url": "/powershell/module/exchange/set-journalrule", + "redirect_url": "/powershell/module/exchangepowershell/set-journalrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-Label.md", - "redirect_url": "/powershell/module/exchange/set-label", + "redirect_url": "/powershell/module/exchangepowershell/set-label", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-LabelPolicy.md", - "redirect_url": "/powershell/module/exchange/set-labelpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-labelpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-MessageClassification.md", - "redirect_url": "/powershell/module/exchange/set-messageclassification", + "redirect_url": "/powershell/module/exchangepowershell/set-messageclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OrganizationSegment.md", - "redirect_url": "/powershell/module/exchange/set-organizationsegment", + "redirect_url": "/powershell/module/exchangepowershell/set-organizationsegment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OutlookProtectionRule.md", - "redirect_url": "/powershell/module/exchange/set-outlookprotectionrule", + "redirect_url": "/powershell/module/exchangepowershell/set-outlookprotectionrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-ProtectionAlert.md", - "redirect_url": "/powershell/module/exchange/set-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md", - "redirect_url": "/powershell/module/exchange/set-supervisoryreviewpolicyv2", + "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewpolicyv2", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md", - "redirect_url": "/powershell/module/exchange/set-supervisoryreviewrule", + "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-TransportRule.md", - "redirect_url": "/powershell/module/exchange/set-transportrule", + "redirect_url": "/powershell/module/exchangepowershell/set-transportrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md", - "redirect_url": "/powershell/module/exchange/start-informationbarrierpoliciesapplication", + "redirect_url": "/powershell/module/exchangepowershell/start-informationbarrierpoliciesapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md", - "redirect_url": "/powershell/module/exchange/stop-informationbarrierpoliciesapplication", + "redirect_url": "/powershell/module/exchangepowershell/stop-informationbarrierpoliciesapplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Test-ArchiveConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-archiveconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-archiveconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AdminAuditLogConfig.md", - "redirect_url": "/powershell/module/exchange/get-adminauditlogconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-adminauditlogconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfig.md", - "redirect_url": "/powershell/module/exchange/get-auditconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-auditconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/get-auditconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-auditconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/get-auditconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/get-auditconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md", - "redirect_url": "/powershell/module/exchange/get-auditlogsearch", + "redirect_url": "/powershell/module/exchangepowershell/get-auditlogsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-MailboxAuditBypassAssociation.md", - "redirect_url": "/powershell/module/exchange/get-mailboxauditbypassassociation", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxauditbypassassociation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/get-unifiedauditlogretentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-unifiedauditlogretentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md", - "redirect_url": "/powershell/module/exchange/new-adminauditlogsearch", + "redirect_url": "/powershell/module/exchangepowershell/new-adminauditlogsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/new-auditconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-auditconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/new-auditconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/new-auditconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md", - "redirect_url": "/powershell/module/exchange/new-mailboxauditlogsearch", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxauditlogsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-UnifiedAuditLogRetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/new-unifiedauditlogretentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-unifiedauditlogretentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-auditconfigurationpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-auditconfigurationpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/remove-auditconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-auditconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-UnifiedAuditLogRetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-unifiedauditlogretentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedauditlogretentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md", - "redirect_url": "/powershell/module/exchange/search-adminauditlog", + "redirect_url": "/powershell/module/exchangepowershell/search-adminauditlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md", - "redirect_url": "/powershell/module/exchange/search-mailboxauditlog", + "redirect_url": "/powershell/module/exchangepowershell/search-mailboxauditlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md", - "redirect_url": "/powershell/module/exchange/search-unifiedauditlog", + "redirect_url": "/powershell/module/exchangepowershell/search-unifiedauditlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md", - "redirect_url": "/powershell/module/exchange/set-adminauditlogconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-adminauditlogconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AuditConfig.md", - "redirect_url": "/powershell/module/exchange/set-auditconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-auditconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/set-auditconfigurationrule", + "redirect_url": "/powershell/module/exchangepowershell/set-auditconfigurationrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md", - "redirect_url": "/powershell/module/exchange/set-mailboxauditbypassassociation", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxauditbypassassociation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/set-unifiedauditlogretentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-unifiedauditlogretentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Write-AdminAuditLog.md", - "redirect_url": "/powershell/module/exchange/write-adminauditlog", + "redirect_url": "/powershell/module/exchangepowershell/write-adminauditlog", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/get-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSearchAction.md", - "redirect_url": "/powershell/module/exchange/get-compliancesearchaction", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearchaction", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSecurityFilter.md", - "redirect_url": "/powershell/module/exchange/get-compliancesecurityfilter", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancesecurityfilter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/get-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Invoke-ComplianceSearchActionStep.md", - "redirect_url": "/powershell/module/exchange/invoke-compliancesearchactionstep", + "redirect_url": "/powershell/module/exchangepowershell/invoke-compliancesearchactionstep", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/new-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md", - "redirect_url": "/powershell/module/exchange/new-compliancesearchaction", + "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearchaction", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSecurityFilter.md", - "redirect_url": "/powershell/module/exchange/new-compliancesecurityfilter", + "redirect_url": "/powershell/module/exchangepowershell/new-compliancesecurityfilter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/new-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/new-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/remove-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSearchAction.md", - "redirect_url": "/powershell/module/exchange/remove-compliancesearchaction", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearchaction", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSecurityFilter.md", - "redirect_url": "/powershell/module/exchange/remove-compliancesecurityfilter", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesecurityfilter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/remove-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/set-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSearchAction.md", - "redirect_url": "/powershell/module/exchange/set-compliancesearchaction", + "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearchaction", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSecurityFilter.md", - "redirect_url": "/powershell/module/exchange/set-compliancesecurityfilter", + "redirect_url": "/powershell/module/exchangepowershell/set-compliancesecurityfilter", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/set-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/start-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/start-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Start-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/start-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/start-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Stop-ComplianceSearch.md", - "redirect_url": "/powershell/module/exchange/stop-compliancesearch", + "redirect_url": "/powershell/module/exchangepowershell/stop-compliancesearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Stop-MailboxSearch.md", - "redirect_url": "/powershell/module/exchange/stop-mailboxsearch", + "redirect_url": "/powershell/module/exchangepowershell/stop-mailboxsearch", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md", - "redirect_url": "/powershell/module/exchange/export-dlppolicycollection", + "redirect_url": "/powershell/module/exchangepowershell/export-dlppolicycollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md", - "redirect_url": "/powershell/module/exchange/get-classificationrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/get-classificationrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DataClassification.md", - "redirect_url": "/powershell/module/exchange/get-dataclassification", + "redirect_url": "/powershell/module/exchangepowershell/get-dataclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md", - "redirect_url": "/powershell/module/exchange/get-dataclassificationconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-dataclassificationconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/get-dlpcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md", - "redirect_url": "/powershell/module/exchange/get-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md", - "redirect_url": "/powershell/module/exchange/get-dlpdetailreport", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetailreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md", - "redirect_url": "/powershell/module/exchange/get-dlpdetectionsreport", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetectionsreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md", - "redirect_url": "/powershell/module/exchange/get-dlpedmschema", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpedmschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md", - "redirect_url": "/powershell/module/exchange/get-dlpkeyworddictionary", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpkeyworddictionary", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md", - "redirect_url": "/powershell/module/exchange/get-dlppolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpPolicyTemplate.md", - "redirect_url": "/powershell/module/exchange/get-dlppolicytemplate", + "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicytemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md", - "redirect_url": "/powershell/module/exchange/get-dlpsensitiveinformationtype", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md", - "redirect_url": "/powershell/module/exchange/get-dlpsensitiveinformationtyperulepackage", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtyperulepackage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSiDetectionsReport.md", - "redirect_url": "/powershell/module/exchange/get-dlpsidetectionsreport", + "redirect_url": "/powershell/module/exchangepowershell/get-dlpsidetectionsreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md", - "redirect_url": "/powershell/module/exchange/get-policytipconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-policytipconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md", - "redirect_url": "/powershell/module/exchange/import-dlppolicycollection", + "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicycollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Import-DlpPolicyTemplate.md", - "redirect_url": "/powershell/module/exchange/import-dlppolicytemplate", + "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicytemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md", - "redirect_url": "/powershell/module/exchange/new-classificationrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/new-classificationrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DataClassification.md", - "redirect_url": "/powershell/module/exchange/new-dataclassification", + "redirect_url": "/powershell/module/exchangepowershell/new-dataclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/new-dlpcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md", - "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md", - "redirect_url": "/powershell/module/exchange/new-dlpedmschema", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpedmschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpFingerprint.md", - "redirect_url": "/powershell/module/exchange/new-dlpfingerprint", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpfingerprint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md", - "redirect_url": "/powershell/module/exchange/new-dlpkeyworddictionary", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpkeyworddictionary", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpPolicy.md", - "redirect_url": "/powershell/module/exchange/new-dlppolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-dlppolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationType.md", - "redirect_url": "/powershell/module/exchange/new-dlpsensitiveinformationtype", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md", - "redirect_url": "/powershell/module/exchange/new-dlpsensitiveinformationtyperulepackage", + "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtyperulepackage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-Fingerprint.md", - "redirect_url": "/powershell/module/exchange/new-fingerprint", + "redirect_url": "/powershell/module/exchangepowershell/new-fingerprint", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-PolicyTipConfig.md", - "redirect_url": "/powershell/module/exchange/new-policytipconfig", + "redirect_url": "/powershell/module/exchangepowershell/new-policytipconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md", - "redirect_url": "/powershell/module/exchange/remove-classificationrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/remove-classificationrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DataClassification.md", - "redirect_url": "/powershell/module/exchange/remove-dataclassification", + "redirect_url": "/powershell/module/exchangepowershell/remove-dataclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/remove-dlpcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md", - "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md", - "redirect_url": "/powershell/module/exchange/remove-dlpedmschema", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpedmschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpKeywordDictionary.md", - "redirect_url": "/powershell/module/exchange/remove-dlpkeyworddictionary", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpkeyworddictionary", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-dlppolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md", - "redirect_url": "/powershell/module/exchange/remove-dlppolicytemplate", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicytemplate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationType.md", - "redirect_url": "/powershell/module/exchange/remove-dlpsensitiveinformationtype", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md", - "redirect_url": "/powershell/module/exchange/remove-dlpsensitiveinformationtyperulepackage", + "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtyperulepackage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md", - "redirect_url": "/powershell/module/exchange/remove-policytipconfig", + "redirect_url": "/powershell/module/exchangepowershell/remove-policytipconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-ClassificationRuleCollection.md", - "redirect_url": "/powershell/module/exchange/set-classificationrulecollection", + "redirect_url": "/powershell/module/exchangepowershell/set-classificationrulecollection", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DataClassification.md", - "redirect_url": "/powershell/module/exchange/set-dataclassification", + "redirect_url": "/powershell/module/exchangepowershell/set-dataclassification", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/set-dlpcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md", - "redirect_url": "/powershell/module/exchange/set-dlpcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md", - "redirect_url": "/powershell/module/exchange/set-dlpedmschema", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpedmschema", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md", - "redirect_url": "/powershell/module/exchange/set-dlpkeyworddictionary", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpkeyworddictionary", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpPolicy.md", - "redirect_url": "/powershell/module/exchange/set-dlppolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-dlppolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md", - "redirect_url": "/powershell/module/exchange/set-dlpsensitiveinformationtype", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md", - "redirect_url": "/powershell/module/exchange/set-dlpsensitiveinformationtyperulepackage", + "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtyperulepackage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-PolicyTipConfig.md", - "redirect_url": "/powershell/module/exchange/set-policytipconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-policytipconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md", - "redirect_url": "/powershell/module/exchange/add-compliancecasemember", + "redirect_url": "/powershell/module/exchangepowershell/add-compliancecasemember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md", - "redirect_url": "/powershell/module/exchange/add-ediscoverycaseadmin", + "redirect_url": "/powershell/module/exchangepowershell/add-ediscoverycaseadmin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-CaseHoldPolicy.md", - "redirect_url": "/powershell/module/exchange/get-caseholdpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-caseholdpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md", - "redirect_url": "/powershell/module/exchange/get-caseholdrule", + "redirect_url": "/powershell/module/exchangepowershell/get-caseholdrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md", - "redirect_url": "/powershell/module/exchange/get-compliancecase", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancecase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-ComplianceCaseMember.md", - "redirect_url": "/powershell/module/exchange/get-compliancecasemember", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancecasemember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md", - "redirect_url": "/powershell/module/exchange/get-ediscoverycaseadmin", + "redirect_url": "/powershell/module/exchangepowershell/get-ediscoverycaseadmin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md", - "redirect_url": "/powershell/module/exchange/new-caseholdpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-caseholdpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md", - "redirect_url": "/powershell/module/exchange/new-caseholdrule", + "redirect_url": "/powershell/module/exchangepowershell/new-caseholdrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md", - "redirect_url": "/powershell/module/exchange/new-compliancecase", + "redirect_url": "/powershell/module/exchangepowershell/new-compliancecase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-caseholdpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldRule.md", - "redirect_url": "/powershell/module/exchange/remove-caseholdrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md", - "redirect_url": "/powershell/module/exchange/remove-compliancecase", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md", - "redirect_url": "/powershell/module/exchange/remove-compliancecasemember", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecasemember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-eDiscoveryCaseAdmin.md", - "redirect_url": "/powershell/module/exchange/remove-ediscoverycaseadmin", + "redirect_url": "/powershell/module/exchangepowershell/remove-ediscoverycaseadmin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md", - "redirect_url": "/powershell/module/exchange/set-caseholdpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-caseholdpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md", - "redirect_url": "/powershell/module/exchange/set-caseholdrule", + "redirect_url": "/powershell/module/exchangepowershell/set-caseholdrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-ComplianceCase.md", - "redirect_url": "/powershell/module/exchange/set-compliancecase", + "redirect_url": "/powershell/module/exchangepowershell/set-compliancecase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md", - "redirect_url": "/powershell/module/exchange/update-compliancecasemember", + "redirect_url": "/powershell/module/exchangepowershell/update-compliancecasemember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md", - "redirect_url": "/powershell/module/exchange/update-ediscoverycaseadmin", + "redirect_url": "/powershell/module/exchangepowershell/update-ediscoverycaseadmin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Enable-ComplianceTagStorage.md", - "redirect_url": "/powershell/module/exchange/enable-compliancetagstorage", + "redirect_url": "/powershell/module/exchangepowershell/enable-compliancetagstorage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md", - "redirect_url": "/powershell/module/exchange/get-complianceretentionevent", + "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentionevent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md", - "redirect_url": "/powershell/module/exchange/get-complianceretentioneventtype", + "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentioneventtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceTag.md", - "redirect_url": "/powershell/module/exchange/get-compliancetag", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancetag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md", - "redirect_url": "/powershell/module/exchange/get-compliancetagstorage", + "redirect_url": "/powershell/module/exchangepowershell/get-compliancetagstorage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md", - "redirect_url": "/powershell/module/exchange/get-dataretentionreport", + "redirect_url": "/powershell/module/exchangepowershell/get-dataretentionreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-HoldCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/get-holdcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md", - "redirect_url": "/powershell/module/exchange/get-holdcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md", - "redirect_url": "/powershell/module/exchange/get-managedcontentsettings", + "redirect_url": "/powershell/module/exchangepowershell/get-managedcontentsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedFolder.md", - "redirect_url": "/powershell/module/exchange/get-managedfolder", + "redirect_url": "/powershell/module/exchangepowershell/get-managedfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/get-managedfoldermailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-managedfoldermailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/get-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/get-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionEvent.md", - "redirect_url": "/powershell/module/exchange/get-retentionevent", + "redirect_url": "/powershell/module/exchangepowershell/get-retentionevent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/get-retentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionPolicyTag.md", - "redirect_url": "/powershell/module/exchange/get-retentionpolicytag", + "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicytag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md", - "redirect_url": "/powershell/module/exchange/new-complianceretentionevent", + "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentionevent", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md", - "redirect_url": "/powershell/module/exchange/new-complianceretentioneventtype", + "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentioneventtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceTag.md", - "redirect_url": "/powershell/module/exchange/new-compliancetag", + "redirect_url": "/powershell/module/exchangepowershell/new-compliancetag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/new-holdcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md", - "redirect_url": "/powershell/module/exchange/new-holdcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedContentSettings.md", - "redirect_url": "/powershell/module/exchange/new-managedcontentsettings", + "redirect_url": "/powershell/module/exchangepowershell/new-managedcontentsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolder.md", - "redirect_url": "/powershell/module/exchange/new-managedfolder", + "redirect_url": "/powershell/module/exchangepowershell/new-managedfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/new-managedfoldermailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-managedfoldermailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/new-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/new-retentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionPolicyTag.md", - "redirect_url": "/powershell/module/exchange/new-retentionpolicytag", + "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicytag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md", - "redirect_url": "/powershell/module/exchange/remove-complianceretentioneventtype", + "redirect_url": "/powershell/module/exchangepowershell/remove-complianceretentioneventtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md", - "redirect_url": "/powershell/module/exchange/remove-compliancetag", + "redirect_url": "/powershell/module/exchangepowershell/remove-compliancetag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-HoldCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/remove-holdcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md", - "redirect_url": "/powershell/module/exchange/remove-holdcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md", - "redirect_url": "/powershell/module/exchange/remove-managedcontentsettings", + "redirect_url": "/powershell/module/exchangepowershell/remove-managedcontentsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedFolder.md", - "redirect_url": "/powershell/module/exchange/remove-managedfolder", + "redirect_url": "/powershell/module/exchangepowershell/remove-managedfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-managedfoldermailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-managedfoldermailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/remove-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/remove-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-retentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md", - "redirect_url": "/powershell/module/exchange/remove-retentionpolicytag", + "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicytag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType.md", - "redirect_url": "/powershell/module/exchange/set-complianceretentioneventtype", + "redirect_url": "/powershell/module/exchangepowershell/set-complianceretentioneventtype", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ComplianceTag.md", - "redirect_url": "/powershell/module/exchange/set-compliancetag", + "redirect_url": "/powershell/module/exchangepowershell/set-compliancetag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/set-holdcompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-HoldComplianceRule.md", - "redirect_url": "/powershell/module/exchange/set-holdcompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md", - "redirect_url": "/powershell/module/exchange/set-managedcontentsettings", + "redirect_url": "/powershell/module/exchangepowershell/set-managedcontentsettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedFolder.md", - "redirect_url": "/powershell/module/exchange/set-managedfolder", + "redirect_url": "/powershell/module/exchangepowershell/set-managedfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedFolderMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/set-managedfoldermailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-managedfoldermailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md", - "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancepolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md", - "redirect_url": "/powershell/module/exchange/set-retentioncompliancerule", + "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancerule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionPolicy.md", - "redirect_url": "/powershell/module/exchange/set-retentionpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionPolicyTag.md", - "redirect_url": "/powershell/module/exchange/set-retentionpolicytag", + "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicytag", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md", - "redirect_url": "/powershell/module/exchange/start-managedfolderassistant", + "redirect_url": "/powershell/module/exchangepowershell/start-managedfolderassistant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Start-RetentionAutoTagLearning.md", - "redirect_url": "/powershell/module/exchange/start-retentionautotaglearning", + "redirect_url": "/powershell/module/exchangepowershell/start-retentionautotaglearning", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md", - "redirect_url": "/powershell/module/exchange/stop-managedfolderassistant", + "redirect_url": "/powershell/module/exchangepowershell/stop-managedfolderassistant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md", - "redirect_url": "/powershell/module/exchange/validate-retentionrulequery", + "redirect_url": "/powershell/module/exchangepowershell/validate-retentionrulequery", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Connect-ExchangeOnline.md", - "redirect_url": "/powershell/module/exchange/connect-exchangeonline", + "redirect_url": "/powershell/module/exchangepowershell/connect-exchangeonline", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOCasMailbox.md", - "redirect_url": "/powershell/module/exchange/get-exocasmailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-exocasmailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailbox.md", - "redirect_url": "/powershell/module/exchange/get-exomailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-exomailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxFolderPermission.md", - "redirect_url": "/powershell/module/exchange/get-exomailboxfolderpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md", - "redirect_url": "/powershell/module/exchange/get-exomailboxfolderstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxPermission.md", - "redirect_url": "/powershell/module/exchange/get-exomailboxpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxStatistics.md", - "redirect_url": "/powershell/module/exchange/get-exomailboxstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md", - "redirect_url": "/powershell/module/exchange/get-exomobiledevicestatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-exomobiledevicestatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXORecipient.md", - "redirect_url": "/powershell/module/exchange/get-exorecipient", + "redirect_url": "/powershell/module/exchangepowershell/get-exorecipient", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXORecipientPermission.md", - "redirect_url": "/powershell/module/exchange/get-exorecipientpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-exorecipientpermission", "redirect_document_id": false }, { @@ -5207,7 +5207,7 @@ }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-HistoricalSearch.md", - "redirect_url": "/powershell/module/exchange/get-historicalsearch", + "redirect_url": "/powershell/module/exchangepowershell/get-historicalsearch", "redirect_document_id": false }, { @@ -5217,7 +5217,7 @@ }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-LogonStatistics.md", - "redirect_url": "/powershell/module/exchange/get-logonstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-logonstatistics", "redirect_document_id": false }, { @@ -5237,52 +5237,52 @@ }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailDlpPolicyReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetaildlppolicyreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetaildlppolicyreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailMalwareReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailSpamReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailTransportRuleReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailtransportrulereport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailtransportrulereport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailFilterListReport.md", - "redirect_url": "/powershell/module/exchange/get-mailfilterlistreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailfilterlistreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficPolicyReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficpolicyreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficpolicyreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficSummaryReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficTopReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-MxRecordReport.md", - "redirect_url": "/powershell/module/exchange/get-mxrecordreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mxrecordreport", "redirect_document_id": false }, { @@ -5307,27 +5307,27 @@ }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-OutboundConnectorReport.md", - "redirect_url": "/powershell/module/exchange/get-outboundconnectorreport", + "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnectorreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-RecipientStatisticsReport.md", - "redirect_url": "/powershell/module/exchange/get-recipientstatisticsreport", + "redirect_url": "/powershell/module/exchangepowershell/get-recipientstatisticsreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-ReportExecutionInstance.md", - "redirect_url": "/powershell/module/exchange/get-reportexecutioninstance", + "redirect_url": "/powershell/module/exchangepowershell/get-reportexecutioninstance", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SCInsights.md", - "redirect_url": "/powershell/module/exchange/get-scinsights", + "redirect_url": "/powershell/module/exchangepowershell/get-scinsights", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-ServiceDeliveryReport.md", - "redirect_url": "/powershell/module/exchange/get-servicedeliveryreport", + "redirect_url": "/powershell/module/exchangepowershell/get-servicedeliveryreport", "redirect_document_id": false }, { @@ -5372,1127 +5372,1127 @@ }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewActivity.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewactivity", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewactivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewOverallProgressReport.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewoverallprogressreport", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewoverallprogressreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewPolicyReport.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewpolicyreport", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewReport.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewreport", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md", - "redirect_url": "/powershell/module/exchange/get-supervisoryreviewtopcasesreport", + "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewtopcasesreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-TenantAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Get-UserAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Set-TenantAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/reporting/Set-UserAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Add-ManagementRoleEntry.md", - "redirect_url": "/powershell/module/exchange/add-managementroleentry", + "redirect_url": "/powershell/module/exchangepowershell/add-managementroleentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Add-RoleGroupMember.md", - "redirect_url": "/powershell/module/exchange/add-rolegroupmember", + "redirect_url": "/powershell/module/exchangepowershell/add-rolegroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRole.md", - "redirect_url": "/powershell/module/exchange/get-managementrole", + "redirect_url": "/powershell/module/exchangepowershell/get-managementrole", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRoleAssignment.md", - "redirect_url": "/powershell/module/exchange/get-managementroleassignment", + "redirect_url": "/powershell/module/exchangepowershell/get-managementroleassignment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRoleEntry.md", - "redirect_url": "/powershell/module/exchange/get-managementroleentry", + "redirect_url": "/powershell/module/exchangepowershell/get-managementroleentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementScope.md", - "redirect_url": "/powershell/module/exchange/get-managementscope", + "redirect_url": "/powershell/module/exchangepowershell/get-managementscope", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md", - "redirect_url": "/powershell/module/exchange/get-roleassignmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-roleassignmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleGroup.md", - "redirect_url": "/powershell/module/exchange/get-rolegroup", + "redirect_url": "/powershell/module/exchangepowershell/get-rolegroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleGroupMember.md", - "redirect_url": "/powershell/module/exchange/get-rolegroupmember", + "redirect_url": "/powershell/module/exchangepowershell/get-rolegroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementRole.md", - "redirect_url": "/powershell/module/exchange/new-managementrole", + "redirect_url": "/powershell/module/exchangepowershell/new-managementrole", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementRoleAssignment.md", - "redirect_url": "/powershell/module/exchange/new-managementroleassignment", + "redirect_url": "/powershell/module/exchangepowershell/new-managementroleassignment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementScope.md", - "redirect_url": "/powershell/module/exchange/new-managementscope", + "redirect_url": "/powershell/module/exchangepowershell/new-managementscope", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-RoleAssignmentPolicy.md", - "redirect_url": "/powershell/module/exchange/new-roleassignmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-roleassignmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-RoleGroup.md", - "redirect_url": "/powershell/module/exchange/new-rolegroup", + "redirect_url": "/powershell/module/exchangepowershell/new-rolegroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRole.md", - "redirect_url": "/powershell/module/exchange/remove-managementrole", + "redirect_url": "/powershell/module/exchangepowershell/remove-managementrole", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md", - "redirect_url": "/powershell/module/exchange/remove-managementroleassignment", + "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleassignment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRoleEntry.md", - "redirect_url": "/powershell/module/exchange/remove-managementroleentry", + "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementScope.md", - "redirect_url": "/powershell/module/exchange/remove-managementscope", + "redirect_url": "/powershell/module/exchangepowershell/remove-managementscope", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-roleassignmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-roleassignmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleGroup.md", - "redirect_url": "/powershell/module/exchange/remove-rolegroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleGroupMember.md", - "redirect_url": "/powershell/module/exchange/remove-rolegroupmember", + "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementRoleAssignment.md", - "redirect_url": "/powershell/module/exchange/set-managementroleassignment", + "redirect_url": "/powershell/module/exchangepowershell/set-managementroleassignment", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementRoleEntry.md", - "redirect_url": "/powershell/module/exchange/set-managementroleentry", + "redirect_url": "/powershell/module/exchangepowershell/set-managementroleentry", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementScope.md", - "redirect_url": "/powershell/module/exchange/set-managementscope", + "redirect_url": "/powershell/module/exchangepowershell/set-managementscope", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md", - "redirect_url": "/powershell/module/exchange/set-roleassignmentpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-roleassignmentpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-RoleGroup.md", - "redirect_url": "/powershell/module/exchange/set-rolegroup", + "redirect_url": "/powershell/module/exchangepowershell/set-rolegroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/role-based-access-control/Update-RoleGroupMember.md", - "redirect_url": "/powershell/module/exchange/update-rolegroupmember", + "redirect_url": "/powershell/module/exchangepowershell/update-rolegroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/add-globalmonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/add-globalmonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Add-ServerMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/add-servermonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/add-servermonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-AvailabilityReportOutage.md", - "redirect_url": "/powershell/module/exchange/get-availabilityreportoutage", + "redirect_url": "/powershell/module/exchangepowershell/get-availabilityreportoutage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-EventLogLevel.md", - "redirect_url": "/powershell/module/exchange/get-eventloglevel", + "redirect_url": "/powershell/module/exchangepowershell/get-eventloglevel", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-GlobalMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/get-globalmonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/get-globalmonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-HealthReport.md", - "redirect_url": "/powershell/module/exchange/get-healthreport", + "redirect_url": "/powershell/module/exchangepowershell/get-healthreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-MonitoringItemHelp.md", - "redirect_url": "/powershell/module/exchange/get-monitoringitemhelp", + "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemhelp", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-MonitoringItemIdentity.md", - "redirect_url": "/powershell/module/exchange/get-monitoringitemidentity", + "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemidentity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerComponentState.md", - "redirect_url": "/powershell/module/exchange/get-servercomponentstate", + "redirect_url": "/powershell/module/exchangepowershell/get-servercomponentstate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerHealth.md", - "redirect_url": "/powershell/module/exchange/get-serverhealth", + "redirect_url": "/powershell/module/exchangepowershell/get-serverhealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/get-servermonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/get-servermonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicy.md", - "redirect_url": "/powershell/module/exchange/get-throttlingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md", - "redirect_url": "/powershell/module/exchange/get-throttlingpolicyassociation", + "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicyassociation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Invoke-MonitoringProbe.md", - "redirect_url": "/powershell/module/exchange/invoke-monitoringprobe", + "redirect_url": "/powershell/module/exchangepowershell/invoke-monitoringprobe", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-AvailabilityReportOutage.md", - "redirect_url": "/powershell/module/exchange/new-availabilityreportoutage", + "redirect_url": "/powershell/module/exchangepowershell/new-availabilityreportoutage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-ThrottlingPolicy.md", - "redirect_url": "/powershell/module/exchange/new-throttlingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-throttlingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-AvailabilityReportOutage.md", - "redirect_url": "/powershell/module/exchange/remove-availabilityreportoutage", + "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityreportoutage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/remove-globalmonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/remove-globalmonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md", - "redirect_url": "/powershell/module/exchange/remove-servermonitoringoverride", + "redirect_url": "/powershell/module/exchangepowershell/remove-servermonitoringoverride", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-ThrottlingPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-throttlingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-throttlingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-AvailabilityReportOutage.md", - "redirect_url": "/powershell/module/exchange/set-availabilityreportoutage", + "redirect_url": "/powershell/module/exchangepowershell/set-availabilityreportoutage", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-EventLogLevel.md", - "redirect_url": "/powershell/module/exchange/set-eventloglevel", + "redirect_url": "/powershell/module/exchangepowershell/set-eventloglevel", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ServerComponentState.md", - "redirect_url": "/powershell/module/exchange/set-servercomponentstate", + "redirect_url": "/powershell/module/exchangepowershell/set-servercomponentstate", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ServerMonitor.md", - "redirect_url": "/powershell/module/exchange/set-servermonitor", + "redirect_url": "/powershell/module/exchangepowershell/set-servermonitor", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ThrottlingPolicy.md", - "redirect_url": "/powershell/module/exchange/set-throttlingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ThrottlingPolicyAssociation.md", - "redirect_url": "/powershell/module/exchange/set-throttlingpolicyassociation", + "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicyassociation", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Test-ServiceHealth.md", - "redirect_url": "/powershell/module/exchange/test-servicehealth", + "redirect_url": "/powershell/module/exchangepowershell/test-servicehealth", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-AvailabilityAddressSpace.md", - "redirect_url": "/powershell/module/exchange/add-availabilityaddressspace", + "redirect_url": "/powershell/module/exchangepowershell/add-availabilityaddressspace", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-PublicFolderAdministrativePermission.md", - "redirect_url": "/powershell/module/exchange/add-publicfolderadministrativepermission", + "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderadministrativepermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md", - "redirect_url": "/powershell/module/exchange/add-publicfolderclientpermission", + "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderclientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/disable-mailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/disable-mailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Enable-MailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/enable-mailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/enable-mailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md", - "redirect_url": "/powershell/module/exchange/get-availabilityaddressspace", + "redirect_url": "/powershell/module/exchangepowershell/get-availabilityaddressspace", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityConfig.md", - "redirect_url": "/powershell/module/exchange/get-availabilityconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-availabilityconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-MailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/get-mailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/get-mailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md", - "redirect_url": "/powershell/module/exchange/get-organizationrelationship", + "redirect_url": "/powershell/module/exchangepowershell/get-organizationrelationship", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolder.md", - "redirect_url": "/powershell/module/exchange/get-publicfolder", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderAdministrativePermission.md", - "redirect_url": "/powershell/module/exchange/get-publicfolderadministrativepermission", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderadministrativepermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md", - "redirect_url": "/powershell/module/exchange/get-publicfolderclientpermission", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderclientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md", - "redirect_url": "/powershell/module/exchange/get-publicfolderdatabase", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md", - "redirect_url": "/powershell/module/exchange/get-publicfolderitemstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderitemstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md", - "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxdiagnostics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxdiagnostics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md", - "redirect_url": "/powershell/module/exchange/get-publicfolderstatistics", + "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderstatistics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SharingPolicy.md", - "redirect_url": "/powershell/module/exchange/get-sharingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-sharingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailbox.md", - "redirect_url": "/powershell/module/exchange/get-sitemailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-sitemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md", - "redirect_url": "/powershell/module/exchange/get-sitemailboxdiagnostics", + "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxdiagnostics", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailboxProvisioningPolicy.md", - "redirect_url": "/powershell/module/exchange/get-sitemailboxprovisioningpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxprovisioningpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-AvailabilityConfig.md", - "redirect_url": "/powershell/module/exchange/new-availabilityconfig", + "redirect_url": "/powershell/module/exchangepowershell/new-availabilityconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-OrganizationRelationship.md", - "redirect_url": "/powershell/module/exchange/new-organizationrelationship", + "redirect_url": "/powershell/module/exchangepowershell/new-organizationrelationship", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolder.md", - "redirect_url": "/powershell/module/exchange/new-publicfolder", + "redirect_url": "/powershell/module/exchangepowershell/new-publicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md", - "redirect_url": "/powershell/module/exchange/new-publicfolderdatabase", + "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md", - "redirect_url": "/powershell/module/exchange/new-publicfolderdatabaserepairrequest", + "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabaserepairrequest", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SharingPolicy.md", - "redirect_url": "/powershell/module/exchange/new-sharingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-sharingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md", - "redirect_url": "/powershell/module/exchange/new-sitemailboxprovisioningpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-sitemailboxprovisioningpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/new-syncmailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/new-syncmailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-AvailabilityAddressSpace.md", - "redirect_url": "/powershell/module/exchange/remove-availabilityaddressspace", + "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityaddressspace", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md", - "redirect_url": "/powershell/module/exchange/remove-availabilityconfig", + "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md", - "redirect_url": "/powershell/module/exchange/remove-organizationrelationship", + "redirect_url": "/powershell/module/exchangepowershell/remove-organizationrelationship", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolder.md", - "redirect_url": "/powershell/module/exchange/remove-publicfolder", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md", - "redirect_url": "/powershell/module/exchange/remove-publicfolderadministrativepermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderadministrativepermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md", - "redirect_url": "/powershell/module/exchange/remove-publicfolderclientpermission", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderclientpermission", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderDatabase.md", - "redirect_url": "/powershell/module/exchange/remove-publicfolderdatabase", + "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SharingPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-sharingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-sharingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-sitemailboxprovisioningpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-sitemailboxprovisioningpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SyncMailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/remove-syncmailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/remove-syncmailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md", - "redirect_url": "/powershell/module/exchange/resume-publicfolderreplication", + "redirect_url": "/powershell/module/exchangepowershell/resume-publicfolderreplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-AvailabilityConfig.md", - "redirect_url": "/powershell/module/exchange/set-availabilityconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-availabilityconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-MailPublicFolder.md", - "redirect_url": "/powershell/module/exchange/set-mailpublicfolder", + "redirect_url": "/powershell/module/exchangepowershell/set-mailpublicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-OrganizationRelationship.md", - "redirect_url": "/powershell/module/exchange/set-organizationrelationship", + "redirect_url": "/powershell/module/exchangepowershell/set-organizationrelationship", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-PublicFolder.md", - "redirect_url": "/powershell/module/exchange/set-publicfolder", + "redirect_url": "/powershell/module/exchangepowershell/set-publicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-PublicFolderDatabase.md", - "redirect_url": "/powershell/module/exchange/set-publicfolderdatabase", + "redirect_url": "/powershell/module/exchangepowershell/set-publicfolderdatabase", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SharingPolicy.md", - "redirect_url": "/powershell/module/exchange/set-sharingpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-sharingpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SiteMailbox.md", - "redirect_url": "/powershell/module/exchange/set-sitemailbox", + "redirect_url": "/powershell/module/exchangepowershell/set-sitemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md", - "redirect_url": "/powershell/module/exchange/set-sitemailboxprovisioningpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-sitemailboxprovisioningpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md", - "redirect_url": "/powershell/module/exchange/suspend-publicfolderreplication", + "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfolderreplication", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md", - "redirect_url": "/powershell/module/exchange/test-organizationrelationship", + "redirect_url": "/powershell/module/exchangepowershell/test-organizationrelationship", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Test-SiteMailbox.md", - "redirect_url": "/powershell/module/exchange/test-sitemailbox", + "redirect_url": "/powershell/module/exchangepowershell/test-sitemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolder.md", - "redirect_url": "/powershell/module/exchange/update-publicfolder", + "redirect_url": "/powershell/module/exchangepowershell/update-publicfolder", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md", - "redirect_url": "/powershell/module/exchange/update-publicfolderhierarchy", + "redirect_url": "/powershell/module/exchangepowershell/update-publicfolderhierarchy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolderMailbox.md", - "redirect_url": "/powershell/module/exchange/update-publicfoldermailbox", + "redirect_url": "/powershell/module/exchangepowershell/update-publicfoldermailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-SiteMailbox.md", - "redirect_url": "/powershell/module/exchange/update-sitemailbox", + "redirect_url": "/powershell/module/exchangepowershell/update-sitemailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/disable-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/disable-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/disable-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/disable-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/disable-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/disable-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMMailbox.md", - "redirect_url": "/powershell/module/exchange/disable-ummailbox", + "redirect_url": "/powershell/module/exchangepowershell/disable-ummailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMServer.md", - "redirect_url": "/powershell/module/exchange/disable-umserver", + "redirect_url": "/powershell/module/exchangepowershell/disable-umserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMService.md", - "redirect_url": "/powershell/module/exchange/disable-umservice", + "redirect_url": "/powershell/module/exchangepowershell/disable-umservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/enable-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/enable-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/enable-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/enable-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/enable-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/enable-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMMailbox.md", - "redirect_url": "/powershell/module/exchange/enable-ummailbox", + "redirect_url": "/powershell/module/exchangepowershell/enable-ummailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMServer.md", - "redirect_url": "/powershell/module/exchange/enable-umserver", + "redirect_url": "/powershell/module/exchangepowershell/enable-umserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMService.md", - "redirect_url": "/powershell/module/exchange/enable-umservice", + "redirect_url": "/powershell/module/exchangepowershell/enable-umservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Export-UMCallDataRecord.md", - "redirect_url": "/powershell/module/exchange/export-umcalldatarecord", + "redirect_url": "/powershell/module/exchangepowershell/export-umcalldatarecord", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Export-UMPrompt.md", - "redirect_url": "/powershell/module/exchange/export-umprompt", + "redirect_url": "/powershell/module/exchangepowershell/export-umprompt", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-OnlineMeetingConfiguration.md", - "redirect_url": "/powershell/module/exchange/get-onlinemeetingconfiguration", + "redirect_url": "/powershell/module/exchangepowershell/get-onlinemeetingconfiguration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMActiveCalls.md", - "redirect_url": "/powershell/module/exchange/get-umactivecalls", + "redirect_url": "/powershell/module/exchangepowershell/get-umactivecalls", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/get-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/get-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/get-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/get-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallDataRecord.md", - "redirect_url": "/powershell/module/exchange/get-umcalldatarecord", + "redirect_url": "/powershell/module/exchangepowershell/get-umcalldatarecord", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallRouterSettings.md", - "redirect_url": "/powershell/module/exchange/get-umcallroutersettings", + "redirect_url": "/powershell/module/exchangepowershell/get-umcallroutersettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallSummaryReport.md", - "redirect_url": "/powershell/module/exchange/get-umcallsummaryreport", + "redirect_url": "/powershell/module/exchangepowershell/get-umcallsummaryreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMDialPlan.md", - "redirect_url": "/powershell/module/exchange/get-umdialplan", + "redirect_url": "/powershell/module/exchangepowershell/get-umdialplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMHuntGroup.md", - "redirect_url": "/powershell/module/exchange/get-umhuntgroup", + "redirect_url": "/powershell/module/exchangepowershell/get-umhuntgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/get-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/get-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailbox.md", - "redirect_url": "/powershell/module/exchange/get-ummailbox", + "redirect_url": "/powershell/module/exchangepowershell/get-ummailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailboxPIN.md", - "redirect_url": "/powershell/module/exchange/get-ummailboxpin", + "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/get-ummailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UmServer.md", - "redirect_url": "/powershell/module/exchange/get-umserver", + "redirect_url": "/powershell/module/exchangepowershell/get-umserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMService.md", - "redirect_url": "/powershell/module/exchange/get-umservice", + "redirect_url": "/powershell/module/exchangepowershell/get-umservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Import-UMPrompt.md", - "redirect_url": "/powershell/module/exchange/import-umprompt", + "redirect_url": "/powershell/module/exchangepowershell/import-umprompt", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/new-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/new-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/new-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/new-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMDialPlan.md", - "redirect_url": "/powershell/module/exchange/new-umdialplan", + "redirect_url": "/powershell/module/exchangepowershell/new-umdialplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMHuntGroup.md", - "redirect_url": "/powershell/module/exchange/new-umhuntgroup", + "redirect_url": "/powershell/module/exchangepowershell/new-umhuntgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/new-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/new-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/new-ummailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/new-ummailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/remove-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/remove-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/remove-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/remove-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMDialPlan.md", - "redirect_url": "/powershell/module/exchange/remove-umdialplan", + "redirect_url": "/powershell/module/exchangepowershell/remove-umdialplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMHuntGroup.md", - "redirect_url": "/powershell/module/exchange/remove-umhuntgroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-umhuntgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/remove-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/remove-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-ummailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/remove-ummailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMAutoAttendant.md", - "redirect_url": "/powershell/module/exchange/set-umautoattendant", + "redirect_url": "/powershell/module/exchangepowershell/set-umautoattendant", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMCallAnsweringRule.md", - "redirect_url": "/powershell/module/exchange/set-umcallansweringrule", + "redirect_url": "/powershell/module/exchangepowershell/set-umcallansweringrule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMCallRouterSettings.md", - "redirect_url": "/powershell/module/exchange/set-umcallroutersettings", + "redirect_url": "/powershell/module/exchangepowershell/set-umcallroutersettings", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMDialPlan.md", - "redirect_url": "/powershell/module/exchange/set-umdialplan", + "redirect_url": "/powershell/module/exchangepowershell/set-umdialplan", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMIPGateway.md", - "redirect_url": "/powershell/module/exchange/set-umipgateway", + "redirect_url": "/powershell/module/exchangepowershell/set-umipgateway", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailbox.md", - "redirect_url": "/powershell/module/exchange/set-ummailbox", + "redirect_url": "/powershell/module/exchangepowershell/set-ummailbox", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailboxPIN.md", - "redirect_url": "/powershell/module/exchange/set-ummailboxpin", + "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpin", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailboxPolicy.md", - "redirect_url": "/powershell/module/exchange/set-ummailboxpolicy", + "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpolicy", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UmServer.md", - "redirect_url": "/powershell/module/exchange/set-umserver", + "redirect_url": "/powershell/module/exchangepowershell/set-umserver", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMService.md", - "redirect_url": "/powershell/module/exchange/set-umservice", + "redirect_url": "/powershell/module/exchangepowershell/set-umservice", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/unified-messaging/Test-UMConnectivity.md", - "redirect_url": "/powershell/module/exchange/test-umconnectivity", + "redirect_url": "/powershell/module/exchangepowershell/test-umconnectivity", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-DistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/add-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/add-distributiongroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-UnifiedGroupLinks.md", - "redirect_url": "/powershell/module/exchange/add-unifiedgrouplinks", + "redirect_url": "/powershell/module/exchangepowershell/add-unifiedgrouplinks", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/disable-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/disable-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailContact.md", - "redirect_url": "/powershell/module/exchange/disable-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/disable-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailUser.md", - "redirect_url": "/powershell/module/exchange/disable-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/disable-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/enable-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/enable-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailContact.md", - "redirect_url": "/powershell/module/exchange/enable-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/enable-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailUser.md", - "redirect_url": "/powershell/module/exchange/enable-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/enable-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Contact.md", - "redirect_url": "/powershell/module/exchange/get-contact", + "redirect_url": "/powershell/module/exchangepowershell/get-contact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/get-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/get-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DynamicDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/get-dynamicdistributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/get-dynamicdistributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md", - "redirect_url": "/powershell/module/exchange/get-eligibledistributiongroupformigration", + "redirect_url": "/powershell/module/exchangepowershell/get-eligibledistributiongroupformigration", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Group.md", - "redirect_url": "/powershell/module/exchange/get-group", + "redirect_url": "/powershell/module/exchangepowershell/get-group", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-LinkedUser.md", - "redirect_url": "/powershell/module/exchange/get-linkeduser", + "redirect_url": "/powershell/module/exchangepowershell/get-linkeduser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailContact.md", - "redirect_url": "/powershell/module/exchange/get-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/get-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailUser.md", - "redirect_url": "/powershell/module/exchange/get-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/get-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Recipient.md", - "redirect_url": "/powershell/module/exchange/get-recipient", + "redirect_url": "/powershell/module/exchangepowershell/get-recipient", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-SecurityPrincipal.md", - "redirect_url": "/powershell/module/exchange/get-securityprincipal", + "redirect_url": "/powershell/module/exchangepowershell/get-securityprincipal", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-UnifiedGroup.md", - "redirect_url": "/powershell/module/exchange/get-unifiedgroup", + "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-UnifiedGroupLinks.md", - "redirect_url": "/powershell/module/exchange/get-unifiedgrouplinks", + "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgrouplinks", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-User.md", - "redirect_url": "/powershell/module/exchange/get-user", + "redirect_url": "/powershell/module/exchangepowershell/get-user", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/new-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-DynamicDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/new-dynamicdistributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/new-dynamicdistributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/new-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/new-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/new-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-MailContact.md", - "redirect_url": "/powershell/module/exchange/new-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/new-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-MailUser.md", - "redirect_url": "/powershell/module/exchange/new-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/new-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/New-UnifiedGroup.md", - "redirect_url": "/powershell/module/exchange/new-unifiedgroup", + "redirect_url": "/powershell/module/exchangepowershell/new-unifiedgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/remove-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/remove-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DynamicDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/remove-dynamicdistributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-dynamicdistributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/remove-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/remove-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-MailContact.md", - "redirect_url": "/powershell/module/exchange/remove-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-MailUser.md", - "redirect_url": "/powershell/module/exchange/remove-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroup.md", - "redirect_url": "/powershell/module/exchange/remove-unifiedgroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroupLinks.md", - "redirect_url": "/powershell/module/exchange/remove-unifiedgrouplinks", + "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgrouplinks", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-Contact.md", - "redirect_url": "/powershell/module/exchange/set-contact", + "redirect_url": "/powershell/module/exchangepowershell/set-contact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/set-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DynamicDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/set-dynamicdistributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/set-dynamicdistributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/set-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPGroup.md", - "redirect_url": "/powershell/module/exchange/set-group", + "redirect_url": "/powershell/module/exchangepowershell/set-group", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/set-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/set-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPUser.md", - "redirect_url": "/powershell/module/exchange/set-user", + "redirect_url": "/powershell/module/exchangepowershell/set-user", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-Group.md", - "redirect_url": "/powershell/module/exchange/set-group", + "redirect_url": "/powershell/module/exchangepowershell/set-group", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-LinkedUser.md", - "redirect_url": "/powershell/module/exchange/set-linkeduser", + "redirect_url": "/powershell/module/exchangepowershell/set-linkeduser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-MailContact.md", - "redirect_url": "/powershell/module/exchange/set-mailcontact", + "redirect_url": "/powershell/module/exchangepowershell/set-mailcontact", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-MailUser.md", - "redirect_url": "/powershell/module/exchange/set-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/set-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-UnifiedGroup.md", - "redirect_url": "/powershell/module/exchange/set-unifiedgroup", + "redirect_url": "/powershell/module/exchangepowershell/set-unifiedgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-User.md", - "redirect_url": "/powershell/module/exchange/set-user", + "redirect_url": "/powershell/module/exchangepowershell/set-user", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md", - "redirect_url": "/powershell/module/exchange/undo-softdeletedunifiedgroup", + "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedunifiedgroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Update-DistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/update-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Update-EOPDistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/update-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/users-and-groups/Upgrade-DistributionGroup.md", - "redirect_url": "/powershell/module/exchange/upgrade-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/upgrade-distributiongroup", "redirect_document_id": false }, { @@ -6622,47 +6622,47 @@ }, { "source_path": "exchange/virtual-folder/exchange/Get-TenantAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-TenantAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-UserAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-UserAnalyticsConfig.md", - "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig", + "redirect_url": "/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-MailDetailMalwareReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-MailDetailSpamReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionTrafficReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-UrlTrace.md", - "redirect_url": "/powershell/module/exchange/get-safelinksaggregatereport", + "redirect_url": "/powershell/module/exchangepowershell/get-safelinksaggregatereport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-MailTrafficReport.md", - "redirect_url": "/powershell/module/exchange/get-maildetailatpreport", + "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport", "redirect_document_id": false }, { @@ -6757,87 +6757,87 @@ }, { "source_path": "exchange/virtual-folder/exchange/Get-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Import-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-RMSTrustedPublishingDomain.md", - "redirect_url": "/powershell/module/exchange/#encryption-and-certificates", + "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-CustomNudge.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeAssignment.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeSettings.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-CustomNudge.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-CustomNudgeAssignment.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-CustomNudge.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-CustomNudgeAssignment.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-CustomNudge.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeAssignment.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeSettings.md", - "redirect_url": "/powershell/module/exchange/", + "redirect_url": "/powershell/module/exchangepowershell/", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-MailTrafficTopReport.md", - "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport", + "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-PhishFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems", + "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-PhishFilterPolicy.md", - "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems", + "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistspoofitems", "redirect_document_id": false }, { @@ -6862,47 +6862,47 @@ }, { "source_path": "exchange/virtual-folder/exchange/New-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/new-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/new-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/new-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/remove-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/remove-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-EOPDistributionGroup.md", - "redirect_url": "/powershell/module/exchange/set-distributiongroup", + "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-EOPGroup.md", - "redirect_url": "/powershell/module/exchange/set-group", + "redirect_url": "/powershell/module/exchangepowershell/set-group", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-EOPMailUser.md", - "redirect_url": "/powershell/module/exchange/set-mailuser", + "redirect_url": "/powershell/module/exchangepowershell/set-mailuser", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-EOPUser.md", - "redirect_url": "/powershell/module/exchange/set-user", + "redirect_url": "/powershell/module/exchangepowershell/set-user", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Update-EOPDistributionGroupMember.md", - "redirect_url": "/powershell/module/exchange/update-distributiongroupmember", + "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember", "redirect_document_id": false }, { @@ -6922,42 +6922,42 @@ }, { "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentDetail.md", - "redirect_url": "/powershell/module/exchange/get-contentmalwaremdodetailreport", + "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdodetailreport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentReport.md", - "redirect_url": "/powershell/module/exchange/get-contentmalwaremdoaggregatereport", + "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdoaggregatereport", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-SecOpsOverrideRule.md", - "redirect_url": "/powershell/module/exchange/new-exosecopsoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/new-exosecopsoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-SecOpsOverrideRule.md", - "redirect_url": "/powershell/module/exchange/remove-exosecopsoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/remove-exosecopsoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-SecOpsOverrideRule.md", - "redirect_url": "/powershell/module/exchange/set-exosecopsoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/set-exosecopsoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-PhishSimOverrideRule.md", - "redirect_url": "/powershell/module/exchange/new-exophishsimoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/new-exophishsimoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-PhishSimOverrideRule.md", - "redirect_url": "/powershell/module/exchange/remove-exophishsimoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/remove-exophishsimoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-PhishSimOverrideRule.md", - "redirect_url": "/powershell/module/exchange/set-exophishsimoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/set-exophishsimoverriderule", "redirect_document_id": false }, { @@ -7122,12 +7122,12 @@ }, { "source_path": "exchange/virtual-folder/exchange/Get-PhishSimOverrideRule.md", - "redirect_url": "/powershell/module/exchange/get-exophishsimoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/get-exophishsimoverriderule", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-SecOpsOverrideRule.md", - "redirect_url": "/powershell/module/exchange/get-exosecopsoverriderule", + "redirect_url": "/powershell/module/exchangepowershell/get-exosecopsoverriderule", "redirect_document_id": false }, { @@ -7137,68 +7137,7103 @@ }, { "source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationPolicy.md", - "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-AuditConfigurationRule.md", - "redirect_url": "/powershell/module/exchange/set-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Get-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/get-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/New-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/new-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/remove-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Set-ActivityAlert.md", - "redirect_url": "/powershell/module/exchange/set-protectionalert", + "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert", "redirect_document_id": false }, { "source_path": "exchange/virtual-folder/exchange/Remove-RecordLabel.md", - "redirect_url": "/powershell/module/exchange/remove-label", + "redirect_url": "/powershell/module/exchangepowershell/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/exchange/exchange-ps/exchange/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md similarity index 85% rename from exchange/exchange-ps/exchange/Add-ADPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md index c1daf4b98b..9ed00e87d0 100644 --- a/exchange/exchange-ps/exchange/Add-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-adpermission +schema: 2.0.0 +title: Add-ADPermission --- # Add-ADPermission @@ -88,13 +89,15 @@ 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 +Parameter Sets: AccessRights, Owner, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -103,27 +106,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: ADRawEntryIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Instance -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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 @@ -133,6 +125,9 @@ 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 @@ -158,7 +153,6 @@ 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 @@ -168,6 +162,9 @@ 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 @@ -196,9 +193,8 @@ You can't use this parameter with the Owner parameter. ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -207,20 +203,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -AccessRights -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -AccessRights The AccessRights parameter specifies the rights that you want to add for the user on the Active Directory object. Valid values include: - AccessSystemSecurity @@ -251,7 +237,6 @@ 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 @@ -261,6 +246,9 @@ 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. @@ -269,7 +257,6 @@ 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 @@ -279,6 +266,9 @@ 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`. @@ -288,7 +278,6 @@ 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 @@ -298,13 +287,15 @@ 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 @@ -314,6 +305,9 @@ 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. @@ -322,7 +316,6 @@ 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 @@ -332,13 +325,15 @@ 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 @@ -348,6 +343,9 @@ 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 @@ -360,7 +358,6 @@ 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 @@ -370,13 +367,15 @@ 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 @@ -386,6 +385,9 @@ 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. @@ -394,7 +396,6 @@ 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 @@ -404,13 +405,15 @@ 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/exchange/Add-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md index 000fae4281..270b4986ed 100644 --- a/exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-attachmentfilterentry +schema: 2.0.0 +title: Add-AttachmentFilterEntry --- # Add-AttachmentFilterEntry @@ -52,6 +53,9 @@ 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. @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +107,6 @@ 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,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md rename to exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md index aedd7aee1a..e555d980bf 100644 --- a/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-availabilityaddressspace +schema: 2.0.0 +title: Add-AvailabilityAddressSpace --- # Add-AvailabilityAddressSpace @@ -74,6 +75,9 @@ 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. @@ -86,7 +90,6 @@ 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 @@ -96,13 +99,15 @@ 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 @@ -112,6 +117,9 @@ 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`. @@ -121,7 +129,6 @@ 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 @@ -131,6 +138,9 @@ 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). @@ -139,7 +149,6 @@ 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 @@ -149,6 +158,9 @@ 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,7 +169,6 @@ 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,6 +178,9 @@ 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. @@ -177,7 +191,6 @@ This parameter required that you created the proper trust relationships and shar Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -187,13 +200,15 @@ 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 @@ -203,6 +218,9 @@ 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: @@ -215,7 +233,6 @@ 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 @@ -225,6 +242,9 @@ 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. @@ -233,7 +253,6 @@ 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 @@ -243,6 +262,9 @@ 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 @@ -254,7 +276,6 @@ 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 @@ -264,13 +285,15 @@ 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/exchange/Add-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md similarity index 95% rename from exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md index ddec608aad..96b7a223ab 100644 --- a/exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-compliancecasemember +schema: 2.0.0 +title: Add-ComplianceCaseMember --- # Add-ComplianceCaseMember @@ -50,6 +51,9 @@ 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. @@ -58,7 +62,6 @@ To see the available eDiscovery cases, use the Get-ComplianceCase cmdlet. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -68,6 +71,9 @@ 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 @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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,13 +115,15 @@ 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/exchange/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md similarity index 91% rename from exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md index 72bcef12ec..707a3731ae 100644 --- a/exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-contentfilterphrase +schema: 2.0.0 +title: Add-ContentFilterPhrase --- # Add-ContentFilterPhrase @@ -45,13 +46,15 @@ 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 @@ -61,6 +64,9 @@ 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. @@ -69,7 +75,6 @@ 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 @@ -79,6 +84,9 @@ 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,7 +96,6 @@ 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,6 +105,9 @@ 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,7 +116,6 @@ 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,13 +125,15 @@ 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/exchange/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md similarity index 91% rename from exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md rename to exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md index d1e4a31542..8b04a3b6de 100644 --- a/exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-databaseavailabilitygroupserver +schema: 2.0.0 +title: Add-DatabaseAvailabilityGroupServer --- # Add-DatabaseAvailabilityGroupServer @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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 @@ -77,7 +83,6 @@ 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 @@ -87,6 +92,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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 @@ -122,13 +131,15 @@ 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 @@ -138,13 +149,15 @@ 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/exchange/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md similarity index 88% rename from exchange/exchange-ps/exchange/Add-DistributionGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md index 90029ad72b..2bafee5eef 100644 --- a/exchange/exchange-ps/exchange/Add-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-distributiongroupmember +schema: 2.0.0 +title: Add-DistributionGroupMember --- # Add-DistributionGroupMember @@ -45,6 +46,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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: @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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,7 +126,6 @@ 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 @@ -126,6 +135,9 @@ 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 @@ -141,7 +153,6 @@ 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 @@ -151,13 +162,15 @@ 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/exchange/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-FederatedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md index 1a193dfead..258eccf137 100644 --- a/exchange/exchange-ps/exchange/Add-FederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-federateddomain +schema: 2.0.0 +title: Add-FederatedDomain --- # Add-FederatedDomain @@ -49,13 +50,15 @@ 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 @@ -65,13 +68,15 @@ 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 @@ -81,6 +86,9 @@ 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`. @@ -90,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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,13 +125,15 @@ 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/exchange/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md index 975a6bf632..45000f6bae 100644 --- a/exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-globalmonitoringoverride +schema: 2.0.0 +title: Add-GlobalMonitoringOverride --- # Add-GlobalMonitoringOverride @@ -64,13 +65,15 @@ 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 @@ -80,6 +83,9 @@ 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. @@ -90,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ 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 @@ -110,7 +118,6 @@ 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 @@ -120,13 +127,15 @@ 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 @@ -136,13 +145,15 @@ 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 @@ -152,6 +163,9 @@ 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`. @@ -161,7 +175,6 @@ 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 @@ -171,6 +184,9 @@ 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. @@ -179,7 +195,6 @@ 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 @@ -189,6 +204,9 @@ 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. @@ -201,7 +219,6 @@ 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 @@ -211,13 +228,15 @@ 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 @@ -227,13 +246,15 @@ 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 @@ -243,13 +264,15 @@ 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/exchange/Add-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/Add-IPAllowListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md index d987ed4c56..1f0ce538fa 100644 --- a/exchange/exchange-ps/exchange/Add-IPAllowListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-ipallowlistentry +schema: 2.0.0 +title: Add-IPAllowListEntry --- # Add-IPAllowListEntry @@ -65,13 +66,15 @@ 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 @@ -81,6 +84,9 @@ 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. @@ -90,7 +96,6 @@ 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 @@ -100,13 +105,15 @@ 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 @@ -116,6 +123,9 @@ 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`. @@ -125,7 +135,6 @@ 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 @@ -135,6 +144,9 @@ 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". @@ -143,7 +155,6 @@ 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 @@ -153,6 +164,9 @@ 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 @@ -168,7 +182,6 @@ 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 @@ -178,13 +191,15 @@ 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/exchange/Add-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/Add-IPAllowListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md index 9b528293bd..25c85afbbd 100644 --- a/exchange/exchange-ps/exchange/Add-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-ipallowlistprovider +schema: 2.0.0 +title: Add-IPAllowListProvider --- # Add-IPAllowListProvider @@ -55,13 +56,15 @@ 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 @@ -71,13 +74,15 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,13 +110,15 @@ 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 @@ -119,6 +128,9 @@ 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`. @@ -128,7 +140,6 @@ 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 @@ -138,6 +149,9 @@ 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. @@ -146,7 +160,6 @@ 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 @@ -156,13 +169,15 @@ 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 @@ -172,13 +187,15 @@ 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 @@ -188,6 +205,9 @@ 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. @@ -196,7 +216,6 @@ 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 @@ -206,13 +225,15 @@ 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/exchange/Add-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/Add-IPBlockListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md index 35072b31fd..cd7d09d12d 100644 --- a/exchange/exchange-ps/exchange/Add-IPBlockListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-ipblocklistentry +schema: 2.0.0 +title: Add-IPBlockListEntry --- # Add-IPBlockListEntry @@ -64,13 +65,15 @@ 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 @@ -80,6 +83,9 @@ 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. @@ -89,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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`. @@ -124,7 +134,6 @@ 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 @@ -134,6 +143,9 @@ 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". @@ -142,7 +154,6 @@ 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 @@ -152,6 +163,9 @@ 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 @@ -167,7 +181,6 @@ 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 @@ -177,13 +190,15 @@ 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/exchange/Add-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/Add-IPBlockListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md index 29ca57a584..9a367d2622 100644 --- a/exchange/exchange-ps/exchange/Add-IPBlockListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-ipblocklistprovider +schema: 2.0.0 +title: Add-IPBlockListProvider --- # Add-IPBlockListProvider @@ -56,13 +57,15 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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 @@ -120,6 +129,9 @@ 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,7 +141,6 @@ 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,6 +150,9 @@ 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. @@ -147,7 +161,6 @@ 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 @@ -157,13 +170,15 @@ 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 @@ -173,13 +188,15 @@ 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 @@ -189,6 +206,9 @@ 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. @@ -197,7 +217,6 @@ 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 @@ -207,6 +226,9 @@ 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". @@ -215,7 +237,6 @@ 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 @@ -225,13 +246,15 @@ 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/exchange/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md similarity index 91% rename from exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md index df90710452..8ec87ebf8e 100644 --- a/exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxdatabasecopy +schema: 2.0.0 +title: Add-MailboxDatabaseCopy --- # Add-MailboxDatabaseCopy @@ -72,6 +73,9 @@ 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 @@ -82,7 +86,6 @@ 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 @@ -92,13 +95,15 @@ 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 @@ -108,13 +113,15 @@ 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 @@ -124,6 +131,9 @@ 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. @@ -132,7 +142,6 @@ 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 @@ -142,6 +151,9 @@ 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`. @@ -151,7 +163,6 @@ 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 @@ -161,13 +172,15 @@ 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 @@ -177,6 +190,9 @@ 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. @@ -189,7 +205,6 @@ 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 @@ -199,6 +214,9 @@ 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. @@ -209,7 +227,6 @@ 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 @@ -219,13 +236,15 @@ 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 @@ -235,6 +254,9 @@ 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. @@ -245,7 +267,6 @@ 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 @@ -255,13 +276,15 @@ 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/exchange/Add-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md similarity index 93% rename from exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md index bda1bfce49..c2020ecc14 100644 --- a/exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission +schema: 2.0.0 +title: Add-MailboxFolderPermission --- # Add-MailboxFolderPermission @@ -61,6 +62,9 @@ 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: @@ -82,7 +86,6 @@ 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 @@ -92,6 +95,9 @@ 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. @@ -132,7 +138,6 @@ 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 @@ -142,6 +147,9 @@ 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 @@ -166,7 +174,6 @@ 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 @@ -176,6 +183,9 @@ 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`. @@ -185,7 +195,6 @@ 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 @@ -195,6 +204,9 @@ 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. @@ -203,7 +215,6 @@ 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 @@ -213,6 +224,9 @@ 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: @@ -231,7 +245,6 @@ 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 @@ -241,6 +254,9 @@ 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: @@ -257,7 +273,6 @@ You can specify multiple values separated by commas. Type: MailboxFolderPermissionFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -267,13 +282,15 @@ 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/exchange/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md similarity index 84% rename from exchange/exchange-ps/exchange/Add-MailboxPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md index 07ab0e946e..44d6d82200 100644 --- a/exchange/exchange-ps/exchange/Add-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxpermission +schema: 2.0.0 +title: Add-MailboxPermission --- # Add-MailboxPermission @@ -101,6 +102,9 @@ 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 @@ -116,9 +120,8 @@ The Identity parameter specifies the mailbox where you want to assign permission ```yaml Type: MailboxIdParameter -Parameter Sets: AccessRights, Owner +Parameter Sets: AccessRights, Owner, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -127,20 +130,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: MailboxIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -AccessRights -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -AccessRights The AccessRights parameter specifies the permission that you want to add for the user on the mailbox. Valid values are: - ChangeOwner @@ -156,9 +149,8 @@ You can't use this parameter with the Owner parameter. ```yaml Type: MailboxRights[] -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -167,20 +159,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxRights[] -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Instance -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Instance This parameter is available only in on-premises Exchange. This parameter has been deprecated and is no longer used. @@ -189,7 +171,6 @@ 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 @@ -199,6 +180,9 @@ 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 @@ -226,7 +210,6 @@ 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 @@ -236,6 +219,9 @@ 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 @@ -266,9 +252,8 @@ You can't use this parameter with the Owner parameter. ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -277,20 +262,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -AutoMapping -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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. @@ -302,7 +277,6 @@ 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 @@ -312,6 +286,9 @@ 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`. @@ -321,7 +298,6 @@ 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 @@ -331,13 +307,15 @@ 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 @@ -347,6 +325,9 @@ 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. @@ -355,7 +336,6 @@ 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 @@ -365,6 +345,9 @@ 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. @@ -373,7 +356,6 @@ 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 @@ -383,6 +365,9 @@ 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: @@ -394,7 +379,6 @@ 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 @@ -404,6 +388,9 @@ 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 @@ -416,7 +403,6 @@ 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 @@ -426,13 +412,15 @@ 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/exchange/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md similarity index 88% rename from exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md index 6b98323cb7..0583db2607 100644 --- a/exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-managementroleentry +schema: 2.0.0 +title: Add-ManagementRoleEntry --- # Add-ManagementRoleEntry @@ -88,6 +89,9 @@ 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). @@ -98,7 +102,6 @@ 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 @@ -108,13 +111,15 @@ 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 @@ -124,13 +129,15 @@ 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 @@ -140,6 +147,9 @@ 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`. @@ -149,7 +159,6 @@ 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 @@ -159,6 +168,9 @@ 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. @@ -167,7 +179,6 @@ 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 @@ -177,6 +188,9 @@ 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. @@ -187,7 +201,6 @@ 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 @@ -197,13 +210,15 @@ 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 @@ -213,13 +228,15 @@ 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 @@ -229,6 +246,9 @@ 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. @@ -237,7 +257,6 @@ 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 @@ -247,13 +266,15 @@ 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 @@ -263,6 +284,9 @@ 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). @@ -277,7 +301,6 @@ 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 @@ -287,13 +310,15 @@ 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/exchange/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md index 153ba0c086..1ffb682492 100644 --- a/exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-publicfolderadministrativepermission +schema: 2.0.0 +title: Add-PublicFolderAdministrativePermission --- # Add-PublicFolderAdministrativePermission @@ -78,15 +79,17 @@ 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 +Parameter Sets: Identity, Owner, Instance Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -95,20 +98,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: PublicFolderIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 +### -AccessRights -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -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. @@ -128,9 +121,8 @@ You can't use this parameter with the Owner parameter. ```yaml Type: MultiValuedProperty -Parameter Sets: Identity +Parameter Sets: Identity, Instance Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -139,27 +131,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MultiValuedProperty -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 +### -Instance -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -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 @@ -169,6 +150,9 @@ 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 @@ -194,7 +178,6 @@ 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 @@ -204,6 +187,9 @@ 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 @@ -227,9 +213,8 @@ You can't use this parameter with the Owner parameter. ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: Identity +Parameter Sets: Identity, Instance Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -238,20 +223,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 +### -Confirm -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -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`. @@ -261,7 +236,6 @@ 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 @@ -271,13 +245,15 @@ 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 @@ -287,13 +263,15 @@ 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 @@ -303,6 +281,9 @@ Accept wildcard characters: False ``` ### -InheritanceType + +> Applicable: Exchange Server 2010 + The InheritanceType parameter specifies how permissions are inherited. Valid values are: - None @@ -315,7 +296,6 @@ 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 @@ -325,6 +305,9 @@ 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 @@ -338,7 +321,6 @@ 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 @@ -348,13 +330,15 @@ 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/exchange/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md similarity index 91% rename from exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md index 059bc10445..47891eaff5 100644 --- a/exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-publicfolderclientpermission +schema: 2.0.0 +title: Add-PublicFolderClientPermission --- # Add-PublicFolderClientPermission @@ -51,6 +52,9 @@ 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. @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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. @@ -102,7 +108,6 @@ 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 @@ -112,6 +117,9 @@ 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: @@ -123,7 +131,6 @@ 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 @@ -133,6 +140,9 @@ 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`. @@ -142,7 +152,6 @@ 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 @@ -152,6 +161,9 @@ 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,7 +172,6 @@ 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 @@ -170,6 +181,9 @@ 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: @@ -185,7 +199,6 @@ 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 @@ -195,13 +208,15 @@ 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/exchange/Add-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md similarity index 96% rename from exchange/exchange-ps/exchange/Add-RecipientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md index 06dfc9280a..009eb45b7f 100644 --- a/exchange/exchange-ps/exchange/Add-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-recipientpermission +schema: 2.0.0 +title: Add-RecipientPermission --- # Add-RecipientPermission @@ -44,6 +45,9 @@ 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: @@ -67,7 +71,6 @@ 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 @@ -77,13 +80,15 @@ 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 @@ -93,6 +98,9 @@ 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 @@ -116,7 +124,6 @@ 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 @@ -126,6 +133,9 @@ 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`. @@ -137,7 +147,6 @@ 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 @@ -147,13 +156,15 @@ 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/exchange/Add-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-ResubmitRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md index d1801a114d..be254547ac 100644 --- a/exchange/exchange-ps/exchange/Add-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-resubmitrequest +schema: 2.0.0 +title: Add-ResubmitRequest --- # Add-ResubmitRequest @@ -64,6 +65,9 @@ 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". @@ -74,7 +78,6 @@ 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 @@ -84,6 +87,9 @@ 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". @@ -94,7 +100,6 @@ 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 @@ -104,6 +109,9 @@ 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,7 +121,6 @@ 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 @@ -123,13 +130,15 @@ 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 @@ -139,6 +148,9 @@ 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. @@ -147,7 +159,6 @@ 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 @@ -157,13 +168,15 @@ 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 @@ -173,6 +186,9 @@ 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. @@ -181,7 +197,6 @@ 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 @@ -191,13 +206,15 @@ 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 @@ -207,6 +224,9 @@ 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. @@ -215,7 +235,6 @@ 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 @@ -225,6 +244,9 @@ 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 @@ -238,7 +260,6 @@ 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 @@ -248,13 +269,15 @@ 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 @@ -264,13 +287,15 @@ 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 @@ -280,13 +305,15 @@ 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/exchange/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-RoleGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md index 5f64ff5636..eb375c01ff 100644 --- a/exchange/exchange-ps/exchange/Add-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-rolegroupmember +schema: 2.0.0 +title: Add-RoleGroupMember --- # Add-RoleGroupMember @@ -73,13 +74,15 @@ 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 @@ -89,6 +92,9 @@ 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 @@ -113,7 +119,6 @@ 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 @@ -123,6 +128,9 @@ 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: @@ -134,7 +142,6 @@ 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 @@ -144,6 +151,9 @@ 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`. @@ -153,7 +163,6 @@ 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 @@ -163,6 +172,9 @@ 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. @@ -171,7 +183,6 @@ 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,6 +192,9 @@ 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. @@ -189,7 +203,6 @@ 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/exchange/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md index 97858e26e8..ca3c575423 100644 --- a/exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-servermonitoringoverride +schema: 2.0.0 +title: Add-ServerMonitoringOverride --- # Add-ServerMonitoringOverride @@ -52,6 +53,9 @@ 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. @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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 @@ -100,7 +108,6 @@ 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 @@ -110,13 +117,15 @@ 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 @@ -126,13 +135,15 @@ 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 @@ -142,6 +153,9 @@ 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 @@ -155,7 +169,6 @@ 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 @@ -165,6 +178,9 @@ 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`. @@ -174,7 +190,6 @@ 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,6 +199,9 @@ 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. @@ -196,7 +214,6 @@ 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 @@ -206,13 +223,15 @@ 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/exchange/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md similarity index 95% rename from exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md rename to exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md index e58e810aba..5fb2861587 100644 --- a/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-unifiedgrouplinks +schema: 2.0.0 +title: Add-UnifiedGroupLinks --- # Add-UnifiedGroupLinks @@ -60,6 +61,9 @@ 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 @@ -73,7 +77,6 @@ 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 @@ -83,6 +86,9 @@ 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: @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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. @@ -128,7 +136,6 @@ 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 @@ -138,6 +145,9 @@ 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`. @@ -147,7 +157,6 @@ 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 @@ -157,13 +166,15 @@ 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/exchange/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md index 340921a576..9fb59952c4 100644 --- a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-vivamodulefeaturepolicy +schema: 2.0.0 +title: Add-VivaModuleFeaturePolicy --- # Add-VivaModuleFeaturePolicy @@ -95,6 +95,9 @@ 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. @@ -103,7 +106,6 @@ 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 @@ -113,6 +115,9 @@ 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. @@ -122,7 +127,6 @@ 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 @@ -132,13 +136,15 @@ 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 @@ -148,6 +154,9 @@ 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. @@ -156,7 +165,6 @@ Valid characters are English letters, numbers, commas, periods, and spaces. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -166,6 +174,9 @@ 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`. @@ -177,7 +188,6 @@ 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 @@ -187,6 +197,9 @@ 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. @@ -195,7 +208,6 @@ Don't use this switch with the GroupIds or UserIds parameters. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -205,6 +217,9 @@ 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.). @@ -217,7 +232,6 @@ 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 @@ -227,6 +241,9 @@ 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: @@ -240,7 +257,6 @@ 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 @@ -250,6 +266,9 @@ 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: @@ -265,7 +284,6 @@ 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 @@ -275,13 +293,15 @@ 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 @@ -291,6 +311,9 @@ 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.). @@ -301,7 +324,6 @@ 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 @@ -311,13 +333,15 @@ 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/exchange/Add-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md similarity index 96% rename from exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md rename to exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md index 0bd5527745..d1f99ef3f0 100644 --- a/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md @@ -1,12 +1,12 @@ --- +author: chrisda external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement +Locale: en-US +Module Name: ExchangePowerShell +ms.author: chrisda 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: +title: Add-VivaOrgInsightsDelegatedRole --- # Add-VivaOrgInsightsDelegatedRole @@ -47,6 +47,9 @@ 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. @@ -55,7 +58,6 @@ 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 @@ -65,6 +67,9 @@ 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. @@ -73,7 +78,6 @@ 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 @@ -83,13 +87,15 @@ 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/exchange/Add-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md similarity index 96% rename from exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md rename to exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md index ddb6eb30ff..5f753b9240 100644 --- a/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/add-ediscoverycaseadmin +schema: 2.0.0 +title: Add-eDiscoveryCaseAdmin --- # Add-eDiscoveryCaseAdmin @@ -46,6 +47,9 @@ 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 @@ -57,7 +61,6 @@ 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 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ 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/exchange/Check-PurviewConfig.md b/exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/Check-PurviewConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md index 831bdea8cb..361f32b9bb 100644 --- a/exchange/exchange-ps/exchange/Check-PurviewConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/check-purviewconfig +schema: 2.0.0 +title: Check-PurviewConfig --- # Check-PurviewConfig @@ -89,6 +90,9 @@ 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 @@ -100,7 +104,6 @@ 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 @@ -110,6 +113,9 @@ 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`. @@ -119,7 +125,6 @@ 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,6 +134,9 @@ 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: @@ -140,7 +148,6 @@ This parameter is required for the following TestCases values: Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 1 @@ -150,13 +157,15 @@ 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 @@ -166,6 +175,9 @@ 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. @@ -176,7 +188,6 @@ This parameter is required for the TestCases value DlpAlerts_FindAlertForActivit Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 3 @@ -186,13 +197,15 @@ 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 @@ -202,13 +215,15 @@ 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 @@ -218,6 +233,9 @@ 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. @@ -228,7 +246,6 @@ This parameter is optional with the TestCases value DlpAlerts_FindAlertForActivi Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 6 @@ -238,6 +255,9 @@ 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. @@ -246,7 +266,6 @@ This parameter is optional with the TestCases value DlpAlerts_CheckAlertsCreated Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 7 @@ -256,6 +275,9 @@ 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. @@ -272,7 +294,6 @@ You can specify multiple values separated by commas. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 8 @@ -282,6 +303,9 @@ 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 @@ -292,7 +316,6 @@ 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 @@ -302,6 +325,9 @@ 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. @@ -311,7 +337,6 @@ 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 @@ -321,13 +346,15 @@ 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 @@ -337,6 +364,9 @@ Accept wildcard characters: False ``` ### -Workload + +> Applicable: Security & Compliance + The Workload parameter specifies the service workload. Value values are: - EndpointDevices @@ -351,7 +381,6 @@ 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/exchange/Clean-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md similarity index 96% rename from exchange/exchange-ps/exchange/Clean-MailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md index 9e3829eb4e..9347056865 100644 --- a/exchange/exchange-ps/exchange/Clean-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/clean-mailboxdatabase +schema: 2.0.0 +title: Clean-MailboxDatabase --- # Clean-MailboxDatabase @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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. @@ -96,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ 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/exchange/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md similarity index 89% rename from exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md index f729195ad5..0c6d7f793f 100644 --- a/exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/clear-activesyncdevice +schema: 2.0.0 +title: Clear-ActiveSyncDevice --- # Clear-ActiveSyncDevice @@ -65,13 +66,15 @@ 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 @@ -81,13 +84,15 @@ 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 @@ -97,6 +102,9 @@ 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`. @@ -108,7 +116,6 @@ 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 @@ -118,6 +125,9 @@ 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,7 +136,6 @@ 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 @@ -136,13 +145,15 @@ 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 @@ -152,13 +163,15 @@ 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/exchange/Clear-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md similarity index 91% rename from exchange/exchange-ps/exchange/Clear-MobileDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md index 9a5eda7425..e51a2f74c1 100644 --- a/exchange/exchange-ps/exchange/Clear-MobileDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/clear-mobiledevice +schema: 2.0.0 +title: Clear-MobileDevice --- # Clear-MobileDevice @@ -64,6 +65,9 @@ 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`) @@ -74,7 +78,6 @@ 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 @@ -84,6 +87,9 @@ 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. @@ -92,7 +98,6 @@ 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 @@ -102,13 +107,15 @@ 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 @@ -118,6 +125,9 @@ 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`. @@ -129,7 +139,6 @@ 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 @@ -139,6 +148,9 @@ 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. @@ -147,7 +159,6 @@ 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 @@ -157,13 +168,15 @@ 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 @@ -173,13 +186,15 @@ 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/exchange/Clear-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md similarity index 90% rename from exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md rename to exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md index 0cfbdb03d1..22280e9806 100644 --- a/exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md +++ b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/clear-textmessagingaccount +schema: 2.0.0 +title: Clear-TextMessagingAccount --- # Clear-TextMessagingAccount @@ -46,6 +47,9 @@ 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 @@ -63,7 +67,6 @@ 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 @@ -73,6 +76,9 @@ 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,7 +88,6 @@ 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 @@ -92,6 +97,9 @@ 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,7 +108,6 @@ 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,6 +117,9 @@ 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: @@ -121,7 +131,6 @@ 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 @@ -131,13 +140,15 @@ 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/exchange/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md similarity index 90% rename from exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md rename to exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md index c536c48908..2041baad2f 100644 --- a/exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/compare-textmessagingverificationcode +schema: 2.0.0 +title: Compare-TextMessagingVerificationCode --- # Compare-TextMessagingVerificationCode @@ -61,6 +62,9 @@ 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 @@ -78,7 +82,6 @@ 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 @@ -88,13 +91,15 @@ 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 @@ -104,6 +109,9 @@ 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`. @@ -113,7 +121,6 @@ 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 @@ -123,6 +130,9 @@ 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,7 +141,6 @@ 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 @@ -141,13 +150,15 @@ 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/exchange/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md similarity index 92% rename from exchange/exchange-ps/exchange/Complete-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md index 922eeca5b8..fb198d2b5a 100644 --- a/exchange/exchange-ps/exchange/Complete-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/complete-migrationbatch +schema: 2.0.0 +title: Complete-MigrationBatch --- # Complete-MigrationBatch @@ -59,13 +60,15 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -83,7 +89,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -93,6 +98,9 @@ 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`. @@ -104,7 +112,6 @@ 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 @@ -114,6 +121,9 @@ 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. @@ -122,7 +132,6 @@ 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 @@ -132,6 +141,9 @@ 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. @@ -142,7 +154,6 @@ 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 @@ -152,6 +163,9 @@ 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. @@ -160,7 +174,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -170,13 +183,15 @@ 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 @@ -186,13 +201,15 @@ 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/exchange/Connect-ExchangeOnline.md b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md similarity index 96% rename from exchange/exchange-ps/exchange/Connect-ExchangeOnline.md rename to exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md index 241205492f..ac7809d480 100644 --- a/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/connect-exchangeonline +schema: 2.0.0 +title: Connect-ExchangeOnline --- # Connect-ExchangeOnline @@ -111,6 +111,9 @@ 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: @@ -125,7 +128,6 @@ The ConnectionUri parameter specifies the connection endpoint for the PowerShell Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -135,6 +137,9 @@ 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: @@ -151,7 +156,6 @@ 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 @@ -161,6 +165,9 @@ 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. @@ -173,7 +180,6 @@ The ExchangeEnvironmentName specifies the Exchange Online environment and elimin Type: ExchangeEnvironment Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 2 @@ -183,6 +189,9 @@ 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. @@ -193,7 +202,6 @@ 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 @@ -203,6 +211,9 @@ 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. @@ -213,7 +224,6 @@ 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 @@ -223,6 +233,9 @@ 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. @@ -233,7 +246,6 @@ 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 @@ -243,13 +255,15 @@ 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 @@ -259,13 +273,15 @@ 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 @@ -275,6 +291,9 @@ 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. @@ -285,7 +304,6 @@ 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 @@ -295,6 +313,9 @@ 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). @@ -303,7 +324,6 @@ 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 @@ -313,13 +333,15 @@ 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 @@ -329,6 +351,9 @@ 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. @@ -339,7 +364,6 @@ 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 @@ -349,6 +373,9 @@ 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. @@ -359,7 +386,6 @@ 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 @@ -369,6 +395,9 @@ 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: @@ -385,7 +414,6 @@ 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 @@ -395,6 +423,9 @@ 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. @@ -407,7 +438,6 @@ 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 @@ -417,6 +447,9 @@ 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. @@ -429,7 +462,6 @@ 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 @@ -439,6 +471,9 @@ 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. @@ -451,7 +486,6 @@ If your login was successful, the PowerShell connection continues. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -461,6 +495,9 @@ 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. @@ -471,7 +508,6 @@ 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 @@ -481,13 +517,15 @@ 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 @@ -497,6 +535,9 @@ 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. @@ -509,7 +550,6 @@ This switch does not work with accounts that use MFA. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -519,6 +559,9 @@ 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. @@ -531,7 +574,6 @@ 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 @@ -541,6 +583,9 @@ 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 ("). @@ -549,7 +594,6 @@ 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 @@ -559,13 +603,15 @@ 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 @@ -575,6 +621,9 @@ 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: @@ -594,7 +643,6 @@ 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 @@ -604,6 +652,9 @@ 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. @@ -614,7 +665,6 @@ 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 @@ -624,6 +674,9 @@ 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). @@ -634,7 +687,6 @@ 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 @@ -644,13 +696,15 @@ 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 @@ -660,6 +714,9 @@ 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). @@ -669,7 +726,6 @@ 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 @@ -679,6 +735,9 @@ 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. @@ -688,7 +747,6 @@ 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 @@ -698,6 +756,9 @@ 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. @@ -710,7 +771,6 @@ 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 @@ -720,6 +780,9 @@ 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. @@ -734,7 +797,6 @@ This switch doesn't work with the UseRPSSession switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -744,6 +806,9 @@ 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. @@ -756,7 +821,6 @@ This switch doesn't work with the UseRPSSession switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -766,6 +830,9 @@ 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. @@ -777,7 +844,6 @@ This parameter works only when logging is enabled. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -787,6 +853,9 @@ 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. @@ -796,7 +865,6 @@ The UseMultithreading parameter specifies whether to disable or enable multi-thr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -806,6 +874,9 @@ 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). @@ -814,7 +885,6 @@ 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 @@ -824,6 +894,9 @@ 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. @@ -836,7 +909,6 @@ 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/exchange/Connect-IPPSSession.md b/exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md similarity index 96% rename from exchange/exchange-ps/exchange/Connect-IPPSSession.md rename to exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md index a260cad194..1e45e6ebcc 100644 --- a/exchange/exchange-ps/exchange/Connect-IPPSSession.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/connect-ippssession +schema: 2.0.0 +title: Connect-IPPSSession --- # Connect-IPPSSession @@ -82,6 +82,9 @@ 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. @@ -93,7 +96,6 @@ The ConnectionUri parameter specifies the connection endpoint for the PowerShell Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -103,6 +105,9 @@ 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. @@ -115,7 +120,6 @@ 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 @@ -125,6 +129,9 @@ 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. @@ -138,7 +145,6 @@ 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 @@ -148,6 +154,9 @@ 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. @@ -158,7 +167,6 @@ 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 @@ -168,6 +176,9 @@ 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. @@ -178,7 +189,6 @@ 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 @@ -188,13 +198,15 @@ 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 @@ -204,13 +216,15 @@ 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 @@ -220,6 +234,9 @@ 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. @@ -230,7 +247,6 @@ 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 @@ -240,6 +256,9 @@ 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). @@ -248,7 +267,6 @@ 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 @@ -258,13 +276,15 @@ 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 @@ -274,6 +294,9 @@ 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. @@ -284,7 +307,6 @@ 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 @@ -294,6 +316,9 @@ 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. @@ -304,7 +329,6 @@ 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 @@ -314,6 +338,9 @@ 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: @@ -330,7 +357,6 @@ 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 @@ -340,6 +366,9 @@ 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. @@ -352,7 +381,6 @@ 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 @@ -362,6 +390,9 @@ 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. @@ -372,7 +403,6 @@ 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 @@ -382,6 +412,9 @@ 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). @@ -390,7 +423,6 @@ 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 @@ -400,6 +432,9 @@ 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). @@ -408,7 +443,6 @@ 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 @@ -418,6 +452,9 @@ 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). @@ -432,7 +469,6 @@ 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/exchange/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/Connect-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md index 87bea6279a..2f33e9ae11 100644 --- a/exchange/exchange-ps/exchange/Connect-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/connect-mailbox +schema: 2.0.0 +title: Connect-Mailbox --- # Connect-Mailbox @@ -166,6 +167,9 @@ 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 @@ -178,7 +182,6 @@ 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 @@ -188,6 +191,9 @@ 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 @@ -200,7 +206,6 @@ 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 @@ -210,6 +215,9 @@ 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). @@ -218,7 +226,6 @@ 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 @@ -228,6 +235,9 @@ 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. @@ -236,7 +246,6 @@ 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 @@ -246,6 +255,9 @@ 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 @@ -259,7 +271,6 @@ 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 @@ -269,6 +280,9 @@ 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). @@ -277,7 +291,6 @@ 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 @@ -287,6 +300,9 @@ 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. @@ -295,7 +311,6 @@ 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 @@ -305,6 +320,9 @@ 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. @@ -313,7 +331,6 @@ 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 @@ -323,6 +340,9 @@ 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 @@ -335,7 +355,6 @@ 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 @@ -345,6 +364,9 @@ 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 @@ -357,7 +379,6 @@ 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 @@ -367,6 +388,9 @@ 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: @@ -391,7 +415,6 @@ 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 @@ -401,13 +424,15 @@ 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 @@ -417,13 +442,15 @@ 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 @@ -433,6 +460,9 @@ 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`. @@ -442,7 +472,6 @@ 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 @@ -452,13 +481,15 @@ 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 @@ -468,6 +499,9 @@ 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. @@ -476,7 +510,6 @@ 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 @@ -486,6 +519,9 @@ 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). @@ -494,7 +530,6 @@ 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 @@ -504,13 +539,15 @@ 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 @@ -520,13 +557,15 @@ 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 @@ -536,6 +575,9 @@ 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 @@ -548,7 +590,6 @@ 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 @@ -558,6 +599,9 @@ 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: @@ -578,7 +622,6 @@ 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 @@ -588,13 +631,15 @@ 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/exchange/Delete-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md similarity index 88% rename from exchange/exchange-ps/exchange/Delete-QuarantineMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md index 3dc21e421f..61dec38a97 100644 --- a/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/delete-quarantinemessage +schema: 2.0.0 +title: Delete-QuarantineMessage --- # Delete-QuarantineMessage @@ -76,6 +77,9 @@ 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. @@ -86,7 +90,6 @@ 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 @@ -96,15 +99,17 @@ 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 +Parameter Sets: Identities, IdentityOnly Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -113,20 +118,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: IdentityOnly -Aliases: -Applicable: Exchange Online, Exchange Online Protection +### -Confirm -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -### -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`. @@ -136,7 +131,6 @@ 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 @@ -146,6 +140,9 @@ 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 @@ -157,7 +154,6 @@ 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 @@ -167,6 +163,9 @@ 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. @@ -175,7 +174,6 @@ 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 @@ -185,13 +183,15 @@ 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,13 +201,15 @@ 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/exchange/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md index fe87141f2e..cf6aa68bb1 100644 --- a/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-atpprotectionpolicyrule +schema: 2.0.0 +title: Disable-ATPProtectionPolicyRule --- # Disable-ATPProtectionPolicyRule @@ -46,6 +47,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-AddressListPaging.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md index 45471267d2..7afd170dd3 100644 --- a/exchange/exchange-ps/exchange/Disable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-addresslistpaging +schema: 2.0.0 +title: Disable-AddressListPaging --- # Disable-AddressListPaging @@ -42,6 +43,9 @@ 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`. @@ -53,7 +57,6 @@ 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 @@ -63,13 +66,15 @@ 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,13 +84,15 @@ 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/exchange/Disable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Disable-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md index df08fecd4f..ed2171d9d5 100644 --- a/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-antiphishrule +schema: 2.0.0 +title: Disable-AntiPhishRule --- # Disable-AntiPhishRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-App.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-App.md index 881f7f9195..e2b6811c5f 100644 --- a/exchange/exchange-ps/exchange/Disable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-app +schema: 2.0.0 +title: Disable-App --- # Disable-App @@ -62,13 +63,15 @@ 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 @@ -78,6 +81,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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. @@ -107,7 +115,6 @@ 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 @@ -117,6 +124,9 @@ 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 @@ -136,7 +146,6 @@ 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 @@ -146,13 +155,15 @@ 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/exchange/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md index fa38ef00f2..c07d7a3f38 100644 --- a/exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-cmdletextensionagent +schema: 2.0.0 +title: Disable-CmdletExtensionAgent --- # Disable-CmdletExtensionAgent @@ -47,6 +48,9 @@ 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 @@ -57,7 +61,6 @@ 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 @@ -67,6 +70,9 @@ 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`. @@ -78,7 +84,6 @@ 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,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md index e773646d76..3fa2c221fe 100644 --- a/exchange/exchange-ps/exchange/Disable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-distributiongroup +schema: 2.0.0 +title: Disable-DistributionGroup --- # Disable-DistributionGroup @@ -46,6 +47,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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,6 +113,9 @@ 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: @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md index 9b1751508e..367a39f99f 100644 --- a/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-dnssecforverifieddomain +schema: 2.0.0 +title: Disable-DnssecForVerifiedDomain --- # Disable-DnssecForVerifiedDomain @@ -44,13 +45,15 @@ 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 @@ -60,13 +63,15 @@ 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 @@ -76,13 +81,15 @@ 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/exchange/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md index b611fc63b1..205744f3ca 100644 --- a/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-eopprotectionpolicyrule +schema: 2.0.0 +title: Disable-EOPProtectionPolicyRule --- # Disable-EOPProtectionPolicyRule @@ -53,6 +54,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -86,7 +92,6 @@ 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 @@ -96,13 +101,15 @@ 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/exchange/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md index 7adfa0cbae..39094c071f 100644 --- a/exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-hostedcontentfilterrule +schema: 2.0.0 +title: Disable-HostedContentFilterRule --- # Disable-HostedContentFilterRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md index 442273d3c0..6305162b46 100644 --- a/exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-hostedoutboundspamfilterrule +schema: 2.0.0 +title: Disable-HostedOutboundSpamFilterRule --- # Disable-HostedOutboundSpamFilterRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md index 59ff3a79b1..7b5c4ee2dd 100644 --- a/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain +schema: 2.0.0 +title: Disable-IPv6ForAcceptedDomain --- # Disable-IPv6ForAcceptedDomain @@ -46,13 +46,15 @@ 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 @@ -62,13 +64,15 @@ 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 @@ -78,13 +82,15 @@ 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/exchange/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Disable-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md index 7bc6e6bce3..bb1c9bf5e1 100644 --- a/exchange/exchange-ps/exchange/Disable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-inboxrule +schema: 2.0.0 +title: Disable-InboxRule --- # Disable-InboxRule @@ -48,6 +49,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,6 +90,9 @@ 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`. @@ -96,7 +104,6 @@ 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 @@ -106,6 +113,9 @@ 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. @@ -114,7 +124,6 @@ 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 @@ -124,6 +133,9 @@ 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. @@ -134,7 +146,6 @@ 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 @@ -144,6 +155,9 @@ 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 @@ -161,7 +175,6 @@ 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 @@ -171,13 +184,15 @@ 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/exchange/Disable-JournalArchiving.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-JournalArchiving.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md index a1bf697510..25dd98b31a 100644 --- a/exchange/exchange-ps/exchange/Disable-JournalArchiving.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-journalarchiving +schema: 2.0.0 +title: Disable-JournalArchiving --- # Disable-JournalArchiving @@ -49,6 +50,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Disable-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md index f36f1eaaaa..62968d00d4 100644 --- a/exchange/exchange-ps/exchange/Disable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-journalrule +schema: 2.0.0 +title: Disable-JournalRule --- # Disable-JournalRule @@ -52,13 +53,15 @@ 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 @@ -68,6 +71,9 @@ 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,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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. @@ -97,7 +105,6 @@ 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,13 +114,15 @@ 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/exchange/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md index 97902c5fd6..26af1dd189 100644 --- a/exchange/exchange-ps/exchange/Disable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailcontact +schema: 2.0.0 +title: Disable-MailContact --- # Disable-MailContact @@ -46,6 +47,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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,6 +113,9 @@ 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: @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/Disable-MailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md index a4aadbbe70..f43ca6d3f0 100644 --- a/exchange/exchange-ps/exchange/Disable-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailpublicfolder +schema: 2.0.0 +title: Disable-MailPublicFolder --- # Disable-MailPublicFolder @@ -44,6 +45,9 @@ 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. @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ 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: @@ -116,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ 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/exchange/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md index c0728ff91a..7a011fc18e 100644 --- a/exchange/exchange-ps/exchange/Disable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailuser +schema: 2.0.0 +title: Disable-MailUser --- # Disable-MailUser @@ -47,6 +48,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,13 +96,15 @@ 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,6 +114,9 @@ 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: @@ -118,7 +128,6 @@ 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 @@ -128,6 +137,9 @@ 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. @@ -138,7 +150,6 @@ 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 @@ -148,13 +159,15 @@ 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/exchange/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Disable-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md index 8997b03b35..b97c065d16 100644 --- a/exchange/exchange-ps/exchange/Disable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailbox +schema: 2.0.0 +title: Disable-Mailbox --- # Disable-Mailbox @@ -99,6 +100,9 @@ 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 @@ -116,7 +120,6 @@ 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 @@ -126,6 +129,9 @@ 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. @@ -136,7 +142,6 @@ 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 @@ -146,6 +151,9 @@ 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. @@ -154,7 +162,6 @@ 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 @@ -164,6 +171,9 @@ 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`. @@ -175,7 +185,6 @@ 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 @@ -185,6 +194,9 @@ 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. @@ -193,7 +205,6 @@ 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 @@ -203,6 +214,9 @@ 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. @@ -211,7 +225,6 @@ 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 @@ -221,6 +234,9 @@ 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. @@ -229,7 +245,6 @@ 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 @@ -239,6 +254,9 @@ 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. @@ -252,7 +270,6 @@ 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 @@ -262,6 +279,9 @@ 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. @@ -274,7 +294,6 @@ 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 @@ -284,6 +303,9 @@ 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. @@ -297,7 +319,6 @@ The PermanentlyDisable switch specifies whether to permanently disable the mailb Type: SwitchParameter Parameter Sets: Archive Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -307,6 +328,9 @@ 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. @@ -317,7 +341,6 @@ 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 @@ -327,6 +350,9 @@ 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. @@ -337,7 +363,6 @@ 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 @@ -347,13 +372,15 @@ 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/exchange/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md index 98aaf73776..9fbf9a605e 100644 --- a/exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailboxquarantine +schema: 2.0.0 +title: Disable-MailboxQuarantine --- # Disable-MailboxQuarantine @@ -83,6 +84,9 @@ 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 @@ -100,9 +104,8 @@ You can't use this parameter with the Database or Server parameters. ```yaml Type: GeneralMailboxIdParameter -Parameter Sets: MailboxIdentity +Parameter Sets: MailboxIdentity, MailboxOrMailUserIdentity Aliases: -Applicable: Exchange Server 2013 Required: True Position: 1 @@ -111,20 +114,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: MailboxOrMailUserIdentity -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -Database -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019 -### -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 @@ -139,7 +132,6 @@ 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 @@ -149,6 +141,9 @@ 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. @@ -157,7 +152,6 @@ 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 @@ -167,6 +161,9 @@ 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. @@ -175,7 +172,6 @@ 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 @@ -185,6 +181,9 @@ 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 @@ -198,7 +197,6 @@ 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 @@ -208,6 +206,9 @@ 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. @@ -218,7 +219,6 @@ 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,6 +228,9 @@ 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`. @@ -239,7 +242,6 @@ 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 @@ -249,13 +251,15 @@ 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 @@ -265,13 +269,15 @@ 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/exchange/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md index 127a8f0542..f6880fba29 100644 --- a/exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-malwarefilterrule +schema: 2.0.0 +title: Disable-MalwareFilterRule --- # Disable-MalwareFilterRule @@ -43,13 +44,15 @@ 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 @@ -59,6 +62,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md index 87451f2763..38b864b820 100644 --- a/exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-metacachedatabase +schema: 2.0.0 +title: Disable-MetaCacheDatabase --- # Disable-MetaCacheDatabase @@ -42,6 +43,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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/exchange/Disable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md index 30685164f7..9fdddae8ce 100644 --- a/exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-outlookanywhere +schema: 2.0.0 +title: Disable-OutlookAnywhere --- # Disable-OutlookAnywhere @@ -66,6 +67,9 @@ 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 @@ -80,7 +84,6 @@ 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 @@ -90,6 +93,9 @@ 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`. @@ -99,7 +105,6 @@ 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 @@ -109,13 +114,15 @@ 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 @@ -125,6 +132,9 @@ 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 @@ -136,7 +146,6 @@ 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 @@ -146,13 +155,15 @@ 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/exchange/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md index 6032b60587..78166a3af3 100644 --- a/exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-outlookprotectionrule +schema: 2.0.0 +title: Disable-OutlookProtectionRule --- # Disable-OutlookProtectionRule @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md index ade8f3935d..595ba99370 100644 --- a/exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-pushnotificationproxy +schema: 2.0.0 +title: Disable-PushNotificationProxy --- # Disable-PushNotificationProxy @@ -43,6 +44,9 @@ 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`. @@ -54,7 +58,6 @@ 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 @@ -64,13 +67,15 @@ 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/exchange/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md index 8039e5d1fd..8998626307 100644 --- a/exchange/exchange-ps/exchange/Disable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-remotemailbox +schema: 2.0.0 +title: Disable-RemoteMailbox --- # Disable-RemoteMailbox @@ -67,6 +68,9 @@ 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 @@ -82,7 +86,6 @@ 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 @@ -92,6 +95,9 @@ 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. @@ -100,7 +106,6 @@ 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 @@ -110,6 +115,9 @@ 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,7 +129,6 @@ 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 @@ -131,13 +138,15 @@ 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,6 +156,9 @@ 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: @@ -158,7 +170,6 @@ 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 @@ -168,6 +179,9 @@ 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. @@ -176,7 +190,6 @@ 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 @@ -186,13 +199,15 @@ 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/exchange/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md index 8e8073a184..717d8a2f1a 100644 --- a/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-reportsubmissionrule +schema: 2.0.0 +title: Disable-ReportSubmissionRule --- # Disable-ReportSubmissionRule @@ -42,13 +43,15 @@ 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 @@ -58,6 +61,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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/exchange/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md index 35ef4b854d..453895a698 100644 --- a/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-safeattachmentrule +schema: 2.0.0 +title: Disable-SafeAttachmentRule --- # Disable-SafeAttachmentRule @@ -44,6 +45,9 @@ 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: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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`. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Disable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md index fa714bf72f..b5be6955dc 100644 --- a/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-safelinksrule +schema: 2.0.0 +title: Disable-SafeLinksRule --- # Disable-SafeLinksRule @@ -44,6 +45,9 @@ 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: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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`. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md index 13a29e56ed..ff7f7ab381 100644 --- a/exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-serviceemailchannel +schema: 2.0.0 +title: Disable-ServiceEmailChannel --- # Disable-ServiceEmailChannel @@ -59,6 +60,9 @@ 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: @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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,7 +105,6 @@ 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 @@ -109,13 +114,15 @@ 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,13 +132,15 @@ 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/exchange/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md index 927fd4cd53..bda077e999 100644 --- a/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-smtpdaneinbound +schema: 2.0.0 +title: Disable-SmtpDaneInbound --- # Disable-SmtpDaneInbound @@ -44,13 +45,15 @@ 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 @@ -60,13 +63,15 @@ 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 @@ -76,13 +81,15 @@ 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/exchange/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md index 225c628693..8ff70f7f4e 100644 --- a/exchange/exchange-ps/exchange/Disable-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-sweeprule +schema: 2.0.0 +title: Disable-SweepRule --- # Disable-SweepRule @@ -51,6 +52,9 @@ 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==). @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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 @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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/exchange/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md similarity index 91% rename from exchange/exchange-ps/exchange/Disable-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md index 5ccd3fab73..5535020d62 100644 --- a/exchange/exchange-ps/exchange/Disable-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-transportagent +schema: 2.0.0 +title: Disable-TransportAgent --- # Disable-TransportAgent @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,6 +86,9 @@ 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. @@ -89,7 +97,6 @@ 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,6 +106,9 @@ 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. @@ -111,7 +121,6 @@ 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 @@ -121,13 +130,15 @@ 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/exchange/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/Disable-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md index 03d4189525..042c89d5e0 100644 --- a/exchange/exchange-ps/exchange/Disable-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-transportrule +schema: 2.0.0 +title: Disable-TransportRule --- # Disable-TransportRule @@ -45,6 +46,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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/exchange/Disable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md index 9a332903c9..c285b9c36e 100644 --- a/exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umautoattendant +schema: 2.0.0 +title: Disable-UMAutoAttendant --- # Disable-UMAutoAttendant @@ -47,13 +48,15 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md index d9f8154eaf..0d730155e6 100644 --- a/exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umcallansweringrule +schema: 2.0.0 +title: Disable-UMCallAnsweringRule --- # Disable-UMCallAnsweringRule @@ -62,13 +63,15 @@ 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 @@ -78,6 +81,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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 @@ -134,7 +144,6 @@ 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 @@ -144,13 +153,15 @@ 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/exchange/Disable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md index f0738b7185..0fe6f76a1f 100644 --- a/exchange/exchange-ps/exchange/Disable-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umipgateway +schema: 2.0.0 +title: Disable-UMIPGateway --- # Disable-UMIPGateway @@ -53,13 +54,15 @@ 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 @@ -69,6 +72,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,13 +131,15 @@ 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/exchange/Disable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md similarity index 92% rename from exchange/exchange-ps/exchange/Disable-UMMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md index f9ea3dd8ba..18b6f117ad 100644 --- a/exchange/exchange-ps/exchange/Disable-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-ummailbox +schema: 2.0.0 +title: Disable-UMMailbox --- # Disable-UMMailbox @@ -47,6 +48,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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: @@ -120,7 +130,6 @@ 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 @@ -130,6 +139,9 @@ 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. @@ -139,7 +151,6 @@ 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 @@ -149,13 +160,15 @@ 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/exchange/Disable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md similarity index 96% rename from exchange/exchange-ps/exchange/Disable-UMServer.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md index 2b34bd0f25..be20e81f10 100644 --- a/exchange/exchange-ps/exchange/Disable-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umserver +schema: 2.0.0 +title: Disable-UMServer --- # Disable-UMServer @@ -60,13 +61,15 @@ 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 @@ -76,6 +79,9 @@ 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`. @@ -85,7 +91,6 @@ 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 @@ -95,13 +100,15 @@ 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 @@ -111,13 +118,15 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Disable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md similarity index 94% rename from exchange/exchange-ps/exchange/Disable-UMService.md rename to exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md index 48cc82a85b..dc92334e3d 100644 --- a/exchange/exchange-ps/exchange/Disable-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disable-umservice +schema: 2.0.0 +title: Disable-UMService --- # Disable-UMService @@ -62,6 +63,9 @@ 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 @@ -73,7 +77,6 @@ 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 @@ -83,6 +86,9 @@ 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`. @@ -92,7 +98,6 @@ 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,13 +107,15 @@ 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 @@ -118,13 +125,15 @@ 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 @@ -134,13 +143,15 @@ 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/exchange/Disconnect-ExchangeOnline.md b/exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md similarity index 97% rename from exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md rename to exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md index c2a6bb1153..f7a9b13321 100644 --- a/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/disconnect-exchangeonline +schema: 2.0.0 +title: Disconnect-ExchangeOnline --- # Disconnect-ExchangeOnline @@ -85,6 +85,9 @@ 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`. @@ -94,7 +97,6 @@ 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 @@ -104,6 +106,9 @@ 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. @@ -114,7 +119,6 @@ Don't use this parameter with the ModulePrefix parameter. Type: String[] Parameter Sets: ConnectionId Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -124,6 +128,9 @@ 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. @@ -134,7 +141,6 @@ Don't use this parameter with the ConnectionId parameter. Type: String[] Parameter Sets: ModulePrefix Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -144,13 +150,15 @@ 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/exchange/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md similarity index 90% rename from exchange/exchange-ps/exchange/Dismount-Database.md rename to exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md index 7159912a4e..337f656c60 100644 --- a/exchange/exchange-ps/exchange/Dismount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/dismount-database +schema: 2.0.0 +title: Dismount-Database --- # Dismount-Database @@ -45,6 +46,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md similarity index 90% rename from exchange/exchange-ps/exchange/Dump-ProvisioningCache.md rename to exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md index b16e9a249e..4497e1de90 100644 --- a/exchange/exchange-ps/exchange/Dump-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/dump-provisioningcache +schema: 2.0.0 +title: Dump-ProvisioningCache --- # Dump-ProvisioningCache @@ -60,13 +61,15 @@ 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 @@ -76,6 +79,9 @@ 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 @@ -89,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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. @@ -123,7 +133,6 @@ 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 @@ -133,6 +142,9 @@ 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`. @@ -142,7 +154,6 @@ 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 @@ -152,13 +163,15 @@ 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 @@ -168,13 +181,15 @@ 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 @@ -184,13 +199,15 @@ 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/exchange/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md index af887e025f..b1ada7c605 100644 --- a/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-atpprotectionpolicyrule +schema: 2.0.0 +title: Enable-ATPProtectionPolicyRule --- # Enable-ATPProtectionPolicyRule @@ -46,6 +47,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-AddressListPaging.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md index 7bdc8deb33..5d0565af6f 100644 --- a/exchange/exchange-ps/exchange/Enable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-addresslistpaging +schema: 2.0.0 +title: Enable-AddressListPaging --- # Enable-AddressListPaging @@ -44,6 +45,9 @@ 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`. @@ -53,7 +57,6 @@ 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 @@ -63,13 +66,15 @@ 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,13 +84,15 @@ 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/exchange/Enable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Enable-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md index 55bc463ac2..85ec99410b 100644 --- a/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-antiphishrule +schema: 2.0.0 +title: Enable-AntiPhishRule --- # Enable-AntiPhishRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Enable-AntispamUpdates.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md similarity index 86% rename from exchange/exchange-ps/exchange/Enable-AntispamUpdates.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md index 40a8ec1a57..8185ecbda6 100644 --- a/exchange/exchange-ps/exchange/Enable-AntispamUpdates.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-antispamupdates +schema: 2.0.0 +title: Enable-AntispamUpdates --- # Enable-AntispamUpdates @@ -41,13 +42,15 @@ 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 @@ -57,13 +60,15 @@ 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 @@ -73,13 +78,15 @@ 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 @@ -89,13 +96,15 @@ 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/exchange/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md similarity index 91% rename from exchange/exchange-ps/exchange/Enable-App.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-App.md index 788dc99c86..681e5392f9 100644 --- a/exchange/exchange-ps/exchange/Enable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-app +schema: 2.0.0 +title: Enable-App --- # Enable-App @@ -62,13 +63,15 @@ 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 @@ -78,6 +81,9 @@ 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`. @@ -87,7 +93,6 @@ 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 @@ -97,6 +102,9 @@ 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. @@ -105,7 +113,6 @@ 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 @@ -115,6 +122,9 @@ 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 @@ -132,7 +142,6 @@ 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 @@ -142,13 +151,15 @@ 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/exchange/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md index 926da3eb88..fc6e53e70e 100644 --- a/exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-cmdletextensionagent +schema: 2.0.0 +title: Enable-CmdletExtensionAgent --- # Enable-CmdletExtensionAgent @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md index c2a69f5215..75deb6ffd0 100644 --- a/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-compliancetagstorage +schema: 2.0.0 +title: Enable-ComplianceTagStorage --- # Enable-ComplianceTagStorage @@ -45,6 +46,9 @@ 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`. @@ -54,7 +58,6 @@ 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 @@ -64,13 +67,15 @@ 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 @@ -80,13 +85,15 @@ 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/exchange/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/Enable-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md index cda305dfb4..1cf8244a98 100644 --- a/exchange/exchange-ps/exchange/Enable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-distributiongroup +schema: 2.0.0 +title: Enable-DistributionGroup --- # Enable-DistributionGroup @@ -50,6 +51,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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: @@ -95,7 +101,6 @@ 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 @@ -105,6 +110,9 @@ 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`. @@ -114,7 +122,6 @@ 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,13 +131,15 @@ 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 @@ -140,13 +149,15 @@ 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,6 +167,9 @@ 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. @@ -164,7 +178,6 @@ 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 @@ -174,13 +187,15 @@ 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/exchange/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md similarity index 95% rename from exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md index 785b0029ab..867f4bc3f8 100644 --- a/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-dnssecforverifieddomain +schema: 2.0.0 +title: Enable-DnssecForVerifiedDomain --- # Enable-DnssecForVerifiedDomain @@ -46,13 +47,15 @@ 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 @@ -62,13 +65,15 @@ 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 @@ -78,13 +83,15 @@ 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/exchange/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md index a73b54c47d..4a46ec22a4 100644 --- a/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-eopprotectionpolicyrule +schema: 2.0.0 +title: Enable-EOPProtectionPolicyRule --- # Enable-EOPProtectionPolicyRule @@ -53,6 +54,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -84,7 +90,6 @@ 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 @@ -94,13 +99,15 @@ 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/exchange/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md index 29cc1af6d3..4fc81568ed 100644 --- a/exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-exchangecertificate +schema: 2.0.0 +title: Enable-ExchangeCertificate --- # Enable-ExchangeCertificate @@ -70,6 +71,9 @@ 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. @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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` @@ -103,7 +109,6 @@ 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 @@ -113,6 +118,9 @@ 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. @@ -133,7 +141,6 @@ 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 @@ -143,6 +150,9 @@ 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`. @@ -152,7 +162,6 @@ 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 @@ -162,6 +171,9 @@ 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. @@ -170,7 +182,6 @@ 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 @@ -180,6 +191,9 @@ 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. @@ -188,7 +202,6 @@ 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 @@ -198,6 +211,9 @@ 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. @@ -208,7 +224,6 @@ 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 @@ -218,13 +233,15 @@ 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 @@ -234,6 +251,9 @@ 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 @@ -249,7 +269,6 @@ 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 @@ -259,13 +278,15 @@ 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/exchange/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md index 8b49e06134..cfe29c42ea 100644 --- a/exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-hostedcontentfilterrule +schema: 2.0.0 +title: Enable-HostedContentFilterRule --- # Enable-HostedContentFilterRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md index b0b6d2ea45..361b21de2a 100644 --- a/exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-hostedoutboundspamfilterrule +schema: 2.0.0 +title: Enable-HostedOutboundSpamFilterRule --- # Enable-HostedOutboundSpamFilterRule @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md similarity index 95% rename from exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md index 1ce4f5db89..88cef3367a 100644 --- a/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-ipv6foraccepteddomain +schema: 2.0.0 +title: Enable-IPv6ForAcceptedDomain --- # Enable-IPv6ForAcceptedDomain @@ -46,13 +46,15 @@ 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 @@ -62,13 +64,15 @@ 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 @@ -78,13 +82,15 @@ 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/exchange/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Enable-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md index a4e38bdcbb..bd64dd9d64 100644 --- a/exchange/exchange-ps/exchange/Enable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-inboxrule +schema: 2.0.0 +title: Enable-InboxRule --- # Enable-InboxRule @@ -48,6 +49,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,6 +90,9 @@ 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`. @@ -94,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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,7 +122,6 @@ 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,6 +131,9 @@ 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. @@ -132,7 +144,6 @@ 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 @@ -142,6 +153,9 @@ 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 @@ -159,7 +173,6 @@ 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 @@ -169,13 +182,15 @@ 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/exchange/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md index a642ee6b6f..0bffbaf999 100644 --- a/exchange/exchange-ps/exchange/Enable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-journalrule +schema: 2.0.0 +title: Enable-JournalRule --- # Enable-JournalRule @@ -45,13 +46,15 @@ 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 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md index 32afb576cd..23504775a3 100644 --- a/exchange/exchange-ps/exchange/Enable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailcontact +schema: 2.0.0 +title: Enable-MailContact --- # Enable-MailContact @@ -52,6 +53,9 @@ 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 @@ -63,7 +67,6 @@ 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 @@ -73,6 +76,9 @@ 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. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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: @@ -115,7 +123,6 @@ 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 @@ -125,6 +132,9 @@ 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,7 +144,6 @@ 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,13 +153,15 @@ 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 @@ -160,13 +171,15 @@ 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 @@ -176,6 +189,9 @@ 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) @@ -192,7 +208,6 @@ 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 @@ -202,6 +217,9 @@ 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 @@ -217,7 +235,6 @@ 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 @@ -227,6 +244,9 @@ 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 @@ -243,7 +263,6 @@ 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 @@ -253,6 +272,9 @@ 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. @@ -263,7 +285,6 @@ 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 @@ -273,6 +294,9 @@ 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. @@ -282,7 +306,6 @@ 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 @@ -292,13 +315,15 @@ 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/exchange/Enable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md similarity index 89% rename from exchange/exchange-ps/exchange/Enable-MailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md index a029579014..35c5207004 100644 --- a/exchange/exchange-ps/exchange/Enable-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailpublicfolder +schema: 2.0.0 +title: Enable-MailPublicFolder --- # Enable-MailPublicFolder @@ -53,6 +54,9 @@ 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. @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,13 +115,15 @@ 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 @@ -124,6 +133,9 @@ 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. @@ -132,7 +144,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -142,6 +153,9 @@ 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: @@ -157,7 +171,6 @@ 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 @@ -167,13 +180,15 @@ 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/exchange/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md similarity index 89% rename from exchange/exchange-ps/exchange/Enable-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md index 0a00e13f2c..390a667b82 100644 --- a/exchange/exchange-ps/exchange/Enable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailuser +schema: 2.0.0 +title: Enable-MailUser --- # Enable-MailUser @@ -68,6 +69,9 @@ 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 @@ -79,7 +83,6 @@ 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 @@ -89,13 +92,15 @@ 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 +Parameter Sets: EnabledUser, EnableGuestUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -104,20 +109,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: ProxyAddress -Parameter Sets: EnableGuestUser -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Alias -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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: @@ -142,7 +137,6 @@ 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 @@ -152,6 +146,9 @@ 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`. @@ -161,7 +158,6 @@ 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,13 +167,15 @@ 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 @@ -187,13 +185,15 @@ 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,6 +203,9 @@ 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) @@ -219,7 +222,6 @@ 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 @@ -229,6 +231,9 @@ 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 @@ -244,7 +249,6 @@ 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 @@ -254,6 +258,9 @@ 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 @@ -270,7 +277,6 @@ 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 @@ -280,6 +286,9 @@ 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. @@ -290,7 +299,6 @@ 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 @@ -300,6 +308,9 @@ 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. @@ -309,7 +320,6 @@ 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 @@ -319,13 +329,15 @@ 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/exchange/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md index 3a49c7ac0c..5655159064 100644 --- a/exchange/exchange-ps/exchange/Enable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailbox +schema: 2.0.0 +title: Enable-Mailbox --- # Enable-Mailbox @@ -302,6 +303,9 @@ 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 @@ -313,7 +317,6 @@ 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 @@ -323,6 +326,9 @@ 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. @@ -333,7 +339,6 @@ 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 @@ -343,6 +348,9 @@ 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. @@ -353,7 +361,6 @@ 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 @@ -363,6 +370,9 @@ 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. @@ -373,7 +383,6 @@ 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 @@ -383,6 +392,9 @@ 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. @@ -393,7 +405,6 @@ 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 @@ -403,6 +414,9 @@ 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. @@ -413,7 +427,6 @@ 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 @@ -423,6 +436,9 @@ 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: @@ -438,7 +454,6 @@ 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 @@ -448,6 +463,9 @@ 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. @@ -458,7 +476,6 @@ 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 @@ -468,6 +485,9 @@ 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. @@ -478,7 +498,6 @@ 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 @@ -488,6 +507,9 @@ 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. @@ -498,7 +520,6 @@ 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 @@ -508,6 +529,9 @@ 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. @@ -518,7 +542,6 @@ 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 @@ -528,6 +551,9 @@ 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:. @@ -542,7 +568,6 @@ 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 @@ -552,6 +577,9 @@ 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: @@ -566,7 +594,6 @@ 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 @@ -576,6 +603,9 @@ 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. @@ -602,7 +632,6 @@ 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 @@ -612,13 +641,15 @@ 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 @@ -628,6 +659,9 @@ 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: @@ -640,7 +674,6 @@ 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 @@ -650,6 +683,9 @@ 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. @@ -658,7 +694,6 @@ 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 @@ -668,6 +703,9 @@ 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: @@ -684,7 +722,6 @@ 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 @@ -694,6 +731,9 @@ 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. @@ -702,7 +742,6 @@ 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 @@ -712,6 +751,9 @@ 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. @@ -727,7 +769,6 @@ 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 @@ -737,6 +778,9 @@ 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`. @@ -746,7 +790,6 @@ 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 @@ -756,6 +799,9 @@ 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: @@ -768,7 +814,6 @@ 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 @@ -778,6 +823,9 @@ 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 ("). @@ -788,7 +836,6 @@ 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 @@ -798,6 +845,9 @@ 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. @@ -806,7 +856,6 @@ 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 @@ -816,6 +865,9 @@ 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. @@ -824,7 +876,6 @@ 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 @@ -834,6 +885,9 @@ 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. @@ -846,7 +900,6 @@ 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 @@ -856,6 +909,9 @@ 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. @@ -866,7 +922,6 @@ 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 @@ -876,6 +931,9 @@ 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. @@ -884,7 +942,6 @@ 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 @@ -894,6 +951,9 @@ 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. @@ -906,7 +966,6 @@ 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 @@ -916,6 +975,9 @@ 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. @@ -926,7 +988,6 @@ 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 @@ -936,6 +997,9 @@ 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. @@ -946,7 +1010,6 @@ 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 @@ -956,6 +1019,9 @@ 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: @@ -970,7 +1036,6 @@ 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 @@ -980,6 +1045,9 @@ 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 @@ -992,7 +1060,6 @@ 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 @@ -1002,13 +1069,15 @@ 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/exchange/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md similarity index 89% rename from exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md index 94f1b1b2d7..cffdc9a758 100644 --- a/exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailboxquarantine +schema: 2.0.0 +title: Enable-MailboxQuarantine --- # Enable-MailboxQuarantine @@ -67,6 +68,9 @@ 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 @@ -84,9 +88,8 @@ You can't use this parameter with the Database parameter. ```yaml Type: GeneralMailboxIdParameter -Parameter Sets: MailboxIdentity +Parameter Sets: MailboxIdentity, MailboxOrMailUserIdentity Aliases: -Applicable: Exchange Server 2013 Required: True Position: 1 @@ -95,20 +98,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: MailboxOrMailUserIdentity -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -Database -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019 -### -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 @@ -123,7 +116,6 @@ 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 @@ -133,6 +125,9 @@ 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. @@ -143,7 +138,6 @@ 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 @@ -153,6 +147,9 @@ 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. @@ -161,7 +158,6 @@ 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 @@ -171,6 +167,9 @@ 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`. @@ -182,7 +181,6 @@ 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 @@ -192,6 +190,9 @@ 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. @@ -200,7 +201,6 @@ 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,13 +210,15 @@ 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 @@ -226,13 +228,15 @@ 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/exchange/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md index d671effeae..3bd0040492 100644 --- a/exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-malwarefilterrule +schema: 2.0.0 +title: Enable-MalwareFilterRule --- # Enable-MalwareFilterRule @@ -43,13 +44,15 @@ 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 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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. @@ -86,7 +94,6 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md index 642a0ec9b8..3fc59b7873 100644 --- a/exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-metacachedatabase +schema: 2.0.0 +title: Enable-MetaCacheDatabase --- # Enable-MetaCacheDatabase @@ -42,6 +43,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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/exchange/Enable-OrganizationCustomization.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md index 23f178be9e..f7fbf56438 100644 --- a/exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-organizationcustomization +schema: 2.0.0 +title: Enable-OrganizationCustomization --- # Enable-OrganizationCustomization @@ -56,6 +57,9 @@ 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`. @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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/exchange/Enable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md index f2706fde72..6dfd0ca928 100644 --- a/exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-outlookanywhere +schema: 2.0.0 +title: Enable-OutlookAnywhere --- # Enable-OutlookAnywhere @@ -84,6 +85,9 @@ 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 @@ -97,7 +101,6 @@ 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 @@ -107,6 +110,9 @@ 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: @@ -120,7 +126,6 @@ If the DefaultAuthenticationMethod parameter is specified, neither the ClientAut Type: AuthenticationMethod Parameter Sets: DefaultIdentity Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -130,13 +135,15 @@ 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 @@ -146,13 +153,15 @@ 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 @@ -162,6 +171,9 @@ 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`. @@ -171,7 +183,6 @@ 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 @@ -181,13 +192,15 @@ 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 @@ -197,6 +210,9 @@ 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. @@ -209,7 +225,6 @@ 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 @@ -219,6 +234,9 @@ 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: @@ -230,7 +248,6 @@ The possible values are: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -240,6 +257,9 @@ 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. @@ -257,7 +277,6 @@ 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 @@ -267,6 +286,9 @@ 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. @@ -279,7 +301,6 @@ 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 @@ -289,6 +310,9 @@ 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 @@ -300,7 +324,6 @@ 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 @@ -310,13 +333,15 @@ 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/exchange/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md index 63e2c39801..c8cbec66da 100644 --- a/exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-outlookprotectionrule +schema: 2.0.0 +title: Enable-OutlookProtectionRule --- # Enable-OutlookProtectionRule @@ -47,13 +48,15 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md similarity index 93% rename from exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md index e23369448c..7abe225095 100644 --- a/exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-pushnotificationproxy +schema: 2.0.0 +title: Enable-PushNotificationProxy --- # Enable-PushNotificationProxy @@ -54,6 +55,9 @@ 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`. @@ -63,7 +67,6 @@ 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 @@ -73,13 +76,15 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md index e2ca574784..452efa0cf5 100644 --- a/exchange/exchange-ps/exchange/Enable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-remotemailbox +schema: 2.0.0 +title: Enable-RemoteMailbox --- # Enable-RemoteMailbox @@ -134,6 +135,9 @@ 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 @@ -148,7 +152,6 @@ 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 @@ -158,6 +161,9 @@ 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). @@ -168,7 +174,6 @@ 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 @@ -178,6 +183,9 @@ 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. @@ -186,7 +194,6 @@ 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 @@ -196,6 +203,9 @@ 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. @@ -206,7 +216,6 @@ 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 @@ -216,13 +225,15 @@ 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 @@ -232,6 +243,9 @@ 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: @@ -256,7 +270,6 @@ 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 @@ -266,13 +279,15 @@ 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 @@ -282,6 +297,9 @@ 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: @@ -296,7 +314,6 @@ 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 @@ -306,6 +323,9 @@ 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`. @@ -315,7 +335,6 @@ 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 @@ -325,13 +344,15 @@ 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 @@ -341,13 +362,15 @@ 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 @@ -357,13 +380,15 @@ 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 @@ -373,13 +398,15 @@ 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 @@ -389,13 +416,15 @@ 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/exchange/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md index 9bf1aa79ac..ca6a6518c3 100644 --- a/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-reportsubmissionrule +schema: 2.0.0 +title: Enable-ReportSubmissionRule --- # Enable-ReportSubmissionRule @@ -42,13 +43,15 @@ 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 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md index 2642212149..4d6284d776 100644 --- a/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-safeattachmentrule +schema: 2.0.0 +title: Enable-SafeAttachmentRule --- # Enable-SafeAttachmentRule @@ -44,6 +45,9 @@ 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: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Enable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md index 1314b22664..0f3c3bdc63 100644 --- a/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-safelinksrule +schema: 2.0.0 +title: Enable-SafeLinksRule --- # Enable-SafeLinksRule @@ -44,6 +45,9 @@ 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: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md index 206921ec6f..24c197fdb0 100644 --- a/exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-serviceemailchannel +schema: 2.0.0 +title: Enable-ServiceEmailChannel --- # Enable-ServiceEmailChannel @@ -59,6 +60,9 @@ 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: @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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,7 +103,6 @@ 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,13 +112,15 @@ 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 @@ -123,13 +130,15 @@ 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/exchange/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md similarity index 95% rename from exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md index 84502bb3b4..19904d6409 100644 --- a/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-smtpdaneinbound +schema: 2.0.0 +title: Enable-SmtpDaneInbound --- # Enable-SmtpDaneInbound @@ -44,13 +45,15 @@ 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 @@ -60,13 +63,15 @@ 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 @@ -76,13 +81,15 @@ 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/exchange/Enable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md index a5d16d3d5f..4bedc3d1b9 100644 --- a/exchange/exchange-ps/exchange/Enable-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-sweeprule +schema: 2.0.0 +title: Enable-SweepRule --- # Enable-SweepRule @@ -51,6 +52,9 @@ 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==). @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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 @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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/exchange/Enable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md similarity index 90% rename from exchange/exchange-ps/exchange/Enable-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md index 1985292cfa..4d0fdebebb 100644 --- a/exchange/exchange-ps/exchange/Enable-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-transportagent +schema: 2.0.0 +title: Enable-TransportAgent --- # Enable-TransportAgent @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,6 +84,9 @@ 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. @@ -87,7 +95,6 @@ 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 @@ -97,6 +104,9 @@ 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. @@ -109,7 +119,6 @@ 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 @@ -119,13 +128,15 @@ 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/exchange/Enable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/Enable-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md index 4f9a620693..cbae459a87 100644 --- a/exchange/exchange-ps/exchange/Enable-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-transportrule +schema: 2.0.0 +title: Enable-TransportRule --- # Enable-TransportRule @@ -53,6 +54,9 @@ 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 @@ -63,7 +67,6 @@ 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 @@ -73,6 +76,9 @@ 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,7 +88,6 @@ 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 @@ -92,6 +97,9 @@ 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,7 +110,6 @@ 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 @@ -112,6 +119,9 @@ 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. @@ -124,7 +134,6 @@ 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 @@ -134,13 +143,15 @@ 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/exchange/Enable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md index b5a6029718..6afce3ea8c 100644 --- a/exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umautoattendant +schema: 2.0.0 +title: Enable-UMAutoAttendant --- # Enable-UMAutoAttendant @@ -45,13 +46,15 @@ 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 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md index 871ebf54fd..19f7806276 100644 --- a/exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umcallansweringrule +schema: 2.0.0 +title: Enable-UMCallAnsweringRule --- # Enable-UMCallAnsweringRule @@ -62,13 +63,15 @@ 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 @@ -78,6 +81,9 @@ 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`. @@ -87,7 +93,6 @@ 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 @@ -97,13 +102,15 @@ 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 @@ -113,6 +120,9 @@ 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 @@ -132,7 +142,6 @@ 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 @@ -142,13 +151,15 @@ 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/exchange/Enable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md similarity index 92% rename from exchange/exchange-ps/exchange/Enable-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md index 2b49427750..9c66aeb570 100644 --- a/exchange/exchange-ps/exchange/Enable-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umipgateway +schema: 2.0.0 +title: Enable-UMIPGateway --- # Enable-UMIPGateway @@ -47,13 +48,15 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Enable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Enable-UMMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md index 64d7a8d5d7..5086d0b209 100644 --- a/exchange/exchange-ps/exchange/Enable-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-ummailbox +schema: 2.0.0 +title: Enable-UMMailbox --- # Enable-UMMailbox @@ -83,6 +84,9 @@ 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 @@ -100,7 +104,6 @@ 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 @@ -110,6 +113,9 @@ 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 @@ -118,9 +124,8 @@ The UMMailboxPolicy parameter specifies the UM mailbox policy that you want to a ```yaml Type: MailboxPolicyIdParameter -Parameter Sets: Identity +Parameter Sets: Identity, CloudVoiceMail Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -129,20 +134,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxPolicyIdParameter -Parameter Sets: CloudVoiceMail -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 +### -AutomaticSpeechRecognitionEnabled -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -### -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. @@ -152,7 +147,6 @@ 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 @@ -162,6 +156,9 @@ 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`. @@ -171,7 +168,6 @@ 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 @@ -181,13 +177,15 @@ 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 @@ -197,13 +195,15 @@ 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,6 +213,9 @@ 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. @@ -221,7 +224,6 @@ 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 @@ -231,6 +233,9 @@ 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: @@ -242,7 +247,6 @@ 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 @@ -252,13 +256,15 @@ 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 @@ -268,13 +274,15 @@ 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 @@ -284,6 +292,9 @@ 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. @@ -292,7 +303,6 @@ 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 @@ -302,6 +312,9 @@ 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. @@ -311,7 +324,6 @@ 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 @@ -321,6 +333,9 @@ 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. @@ -330,7 +345,6 @@ 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 @@ -340,13 +354,15 @@ 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 @@ -356,6 +372,9 @@ 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. @@ -364,7 +383,6 @@ 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 @@ -374,13 +392,15 @@ 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/exchange/Enable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md similarity index 96% rename from exchange/exchange-ps/exchange/Enable-UMServer.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md index 01417d0e76..135aa70dc9 100644 --- a/exchange/exchange-ps/exchange/Enable-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umserver +schema: 2.0.0 +title: Enable-UMServer --- # Enable-UMServer @@ -47,13 +48,15 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Enable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md similarity index 94% rename from exchange/exchange-ps/exchange/Enable-UMService.md rename to exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md index d0441b4357..0d1e2998c8 100644 --- a/exchange/exchange-ps/exchange/Enable-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/enable-umservice +schema: 2.0.0 +title: Enable-UMService --- # Enable-UMService @@ -49,6 +50,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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`. @@ -79,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/exchange.md b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md similarity index 99% rename from exchange/exchange-ps/exchange/exchange.md rename to exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md index 7aab792266..01c57aaaee 100644 --- a/exchange/exchange-ps/exchange/exchange.md +++ b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md @@ -1,6 +1,7 @@ --- -Module Name: Exchange PowerShell -Module Guid: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX +Locale: en-US +Module Guid: 00000000-0000-0000-0000-000000000000 +Module Name: ExchangePowerShell title: exchange --- @@ -398,7 +399,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Set-ExoPhishSimOverrideRule](Set-ExoPhishSimOverrideRule.md) -### [Set-ExoSecOpsOverrideRule](Remove-ExoSecOpsOverrideRule.md) +### [Set-ExoSecOpsOverrideRule](Set-ExoSecOpsOverrideRule.md) ### [Set-HostedConnectionFilterPolicy](Set-HostedConnectionFilterPolicy.md) @@ -940,6 +941,8 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Test-IRMConfiguration](Test-IRMConfiguration.md) +### [Test-M365DataAtRestEncryptionPolicy](Test-M365DataAtRestEncryptionPolicy.md) + ## federation-and-hybrid Cmdlets ### [Add-FederatedDomain](Add-FederatedDomain.md) @@ -1344,8 +1347,12 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Get-MessageTrace](Get-MessageTrace.md) +### [Get-MessageTraceV2](Get-MessageTraceV2.md) + ### [Get-MessageTraceDetail](Get-MessageTraceDetail.md) +### [Get-MessageTraceDetailV2](Get-MessageTraceDetailV2.md) + ### [Get-MessageTrackingLog](Get-MessageTrackingLog.md) ### [Get-MessageTrackingReport](Get-MessageTrackingReport.md) @@ -2156,7 +2163,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Get-FilePlanPropertyReferenceId](Get-FilePlanPropertyReferenceId.md) -### [Get-FilePlanPropertyStructure](Get-FilePlanPropertyStructur.md) +### [Get-FilePlanPropertyStructure](Get-FilePlanPropertyStructure.md) ### [Get-FilePlanPropertySubCategory](Get-FilePlanPropertySubCategory.md) @@ -2250,7 +2257,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Remove-FilePlanPropertyReferenceId](Remove-FilePlanPropertyReferenceId.md) -### [Remove-FilePlanPropertySubCategory](Remove-FilePlanPropertySubCategor.md) +### [Remove-FilePlanPropertySubCategory](Remove-FilePlanPropertySubCategory.md) ### [Remove-HoldCompliancePolicy](Remove-HoldCompliancePolicy.md) @@ -2280,7 +2287,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Set-ComplianceTag](Set-ComplianceTag.md) -### [Set-FilePlanPropertyAuthority](Set-FilePlanPropertyAuthorit.md) +### [Set-FilePlanPropertyAuthority](Set-FilePlanPropertyAuthority.md) ### [Set-FilePlanPropertyCategory](Set-FilePlanPropertyCategory.md) @@ -2434,7 +2441,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Get-SupervisoryReviewTopCasesReport](Get-SupervisoryReviewTopCasesReport.md) -### [Test-Message](Test-Message.md] +### [Test-Message](Test-Message.md) ## role-based-access-control Cmdlets ### [Add-ManagementRoleEntry](Add-ManagementRoleEntry.md) diff --git a/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md similarity index 97% rename from exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md rename to exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md index 8da13825b6..65f7724aae 100644 --- a/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md +++ b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/execute-azureadlabelsync +schema: 2.0.0 +title: Execute-AzureADLabelSync --- # Execute-AzureADLabelSync diff --git a/exchange/exchange-ps/exchange/Expedite-Delicensing.md b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md similarity index 97% rename from exchange/exchange-ps/exchange/Expedite-Delicensing.md rename to exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md index f5c2af5041..845bd8f3c7 100644 --- a/exchange/exchange-ps/exchange/Expedite-Delicensing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/expedite-delicensing +schema: 2.0.0 +title: Expedite-Delicensing --- # Expedite-Delicensing @@ -40,6 +41,9 @@ 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: @@ -56,7 +60,6 @@ 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/exchange/Export-ActiveSyncLog.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md similarity index 88% rename from exchange/exchange-ps/exchange/Export-ActiveSyncLog.md rename to exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md index 2af091f5e0..e898d2c434 100644 --- a/exchange/exchange-ps/exchange/Export-ActiveSyncLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-activesynclog +schema: 2.0.0 +title: Export-ActiveSyncLog --- # Export-ActiveSyncLog @@ -64,13 +65,15 @@ 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 @@ -80,6 +83,9 @@ 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,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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. @@ -123,7 +133,6 @@ 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 @@ -133,13 +142,15 @@ 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 @@ -149,13 +160,15 @@ 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 @@ -165,13 +178,15 @@ 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 @@ -181,6 +196,9 @@ 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. @@ -189,7 +207,6 @@ 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 @@ -199,13 +216,15 @@ 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/exchange/Export-ActivityExplorerData.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md similarity index 97% rename from exchange/exchange-ps/exchange/Export-ActivityExplorerData.md rename to exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md index 78b9dd23dd..bbd80ee5d6 100644 --- a/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata +schema: 2.0.0 +title: Export-ActivityExplorerData --- # Export-ActivityExplorerData @@ -219,6 +220,9 @@ 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". @@ -227,7 +231,6 @@ 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 @@ -237,6 +240,9 @@ Accept wildcard characters: False ``` ### -OutputFormat + +> Applicable: Security & Compliance + The OutputFormat parameter specifies the output format. Valid values are: - Csv @@ -247,7 +253,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: csv, json -Applicable: Security & Compliance Required: True Position: Named @@ -257,6 +262,9 @@ 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". @@ -265,7 +273,6 @@ 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 @@ -275,6 +282,9 @@ 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`. @@ -287,7 +297,6 @@ 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 @@ -297,6 +306,9 @@ 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. @@ -305,7 +317,6 @@ 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 @@ -315,6 +326,9 @@ 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. @@ -323,7 +337,6 @@ 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 @@ -333,6 +346,9 @@ 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. @@ -341,7 +357,6 @@ 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 @@ -351,6 +366,9 @@ 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. @@ -359,7 +377,6 @@ 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 @@ -369,13 +386,15 @@ 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 @@ -385,13 +404,15 @@ 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/exchange/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md index 01b6148ebe..7af9efffe4 100644 --- a/exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-autodiscoverconfig +schema: 2.0.0 +title: Export-AutoDiscoverConfig --- # Export-AutoDiscoverConfig @@ -56,6 +57,9 @@ 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. @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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,13 +98,15 @@ 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 @@ -109,13 +116,15 @@ 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,6 +134,9 @@ 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. @@ -134,7 +146,6 @@ 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 @@ -144,13 +155,15 @@ 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 @@ -160,6 +173,9 @@ 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). @@ -168,7 +184,6 @@ 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 @@ -178,6 +193,9 @@ 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). @@ -186,7 +204,6 @@ 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 @@ -196,13 +213,15 @@ 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/exchange/Export-ContentExplorerData.md b/exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md similarity index 95% rename from exchange/exchange-ps/exchange/Export-ContentExplorerData.md rename to exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md index 547c01be2a..2671504285 100644 --- a/exchange/exchange-ps/exchange/Export-ContentExplorerData.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-contentexplorerdata +schema: 2.0.0 +title: Export-ContentExplorerData --- # Export-ContentExplorerData @@ -80,6 +81,9 @@ 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 @@ -91,7 +95,6 @@ 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 @@ -101,6 +104,9 @@ 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. @@ -117,7 +123,6 @@ 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 @@ -127,6 +132,9 @@ 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 @@ -138,7 +146,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: high, medium, low -Applicable: Security & Compliance Required: False Position: 0 @@ -148,13 +155,15 @@ 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 @@ -164,6 +173,9 @@ 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. @@ -172,7 +184,6 @@ 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 @@ -182,6 +193,9 @@ 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. @@ -190,7 +204,6 @@ You use this parameter for SharePoint and OneDrive workloads. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 3 @@ -200,13 +213,15 @@ 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 @@ -216,6 +231,9 @@ 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. @@ -224,7 +242,6 @@ You use this parameter for Exchange and Microsoft Teams workloads. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 6 @@ -234,6 +251,9 @@ 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 @@ -245,7 +265,6 @@ 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/exchange/Export-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md similarity index 92% rename from exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md index 0c2de21c86..e39be48923 100644 --- a/exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-dlppolicycollection +schema: 2.0.0 +title: Export-DlpPolicyCollection --- # Export-DlpPolicyCollection @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Export-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md similarity index 93% rename from exchange/exchange-ps/exchange/Export-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md index ec431d5516..12bcee3d77 100644 --- a/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-exchangecertificate +schema: 2.0.0 +title: Export-ExchangeCertificate --- # Export-ExchangeCertificate @@ -108,6 +109,9 @@ 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. @@ -116,7 +120,6 @@ 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 @@ -126,6 +129,9 @@ 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` @@ -141,7 +147,6 @@ 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 @@ -151,6 +156,9 @@ 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. @@ -159,7 +167,6 @@ 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 @@ -169,6 +176,9 @@ 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`. @@ -178,7 +188,6 @@ 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 @@ -188,6 +197,9 @@ 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. @@ -196,7 +208,6 @@ 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 @@ -206,6 +217,9 @@ 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. @@ -216,7 +230,6 @@ 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 @@ -226,6 +239,9 @@ 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: @@ -238,7 +254,6 @@ 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 @@ -248,6 +263,9 @@ 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 @@ -263,7 +281,6 @@ 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 @@ -273,13 +290,15 @@ 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/exchange/Export-FilePlanProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md similarity index 94% rename from exchange/exchange-ps/exchange/Export-FilePlanProperty.md rename to exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md index 91b4a41f26..5fbe3166bc 100644 --- a/exchange/exchange-ps/exchange/Export-FilePlanProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md @@ -1,9 +1,11 @@ --- +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/exchange/export-fileplanproperty -applicable: Security & Compliance -title: Export-FilePlanProperty schema: 2.0.0 +title: Export-FilePlanProperty --- # Export-FilePlanProperty @@ -36,6 +38,9 @@ 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. @@ -45,7 +50,6 @@ 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 @@ -55,13 +59,15 @@ 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 @@ -71,13 +77,15 @@ 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/exchange/Export-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md similarity index 92% rename from exchange/exchange-ps/exchange/Export-JournalRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md index 0b68ce68f7..55444c921c 100644 --- a/exchange/exchange-ps/exchange/Export-JournalRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-journalrulecollection +schema: 2.0.0 +title: Export-JournalRuleCollection --- # Export-JournalRuleCollection @@ -57,13 +58,15 @@ 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 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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. @@ -116,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ 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/exchange/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md similarity index 89% rename from exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md rename to exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md index dada5fa300..d7d0cd688f 100644 --- a/exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-mailboxdiagnosticlogs +schema: 2.0.0 +title: Export-MailboxDiagnosticLogs --- # Export-MailboxDiagnosticLogs @@ -71,6 +72,9 @@ 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 @@ -88,7 +92,6 @@ 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 @@ -98,6 +101,9 @@ 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 @@ -127,7 +133,6 @@ 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 @@ -137,13 +142,15 @@ 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 @@ -153,6 +160,9 @@ 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. @@ -161,7 +171,6 @@ 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 @@ -171,6 +180,9 @@ 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`. @@ -180,7 +192,6 @@ 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 @@ -190,6 +201,9 @@ 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. @@ -200,7 +214,6 @@ 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 @@ -210,6 +223,9 @@ 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. @@ -218,7 +234,6 @@ 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 @@ -228,6 +243,9 @@ 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. @@ -238,7 +256,6 @@ 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 @@ -248,6 +265,9 @@ 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. @@ -260,7 +280,6 @@ 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 @@ -270,13 +289,15 @@ 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 @@ -286,13 +307,15 @@ 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/exchange/Export-Message.md b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md similarity index 94% rename from exchange/exchange-ps/exchange/Export-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Export-Message.md index 28b6f435c6..a05035f60a 100644 --- a/exchange/exchange-ps/exchange/Export-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-message +schema: 2.0.0 +title: Export-Message --- # Export-Message @@ -63,13 +64,15 @@ 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 @@ -79,6 +82,9 @@ 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,7 +94,6 @@ 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,13 +103,15 @@ 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/exchange/Export-MigrationReport.md b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md similarity index 89% rename from exchange/exchange-ps/exchange/Export-MigrationReport.md rename to exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md index 4610a82482..896ca6b666 100644 --- a/exchange/exchange-ps/exchange/Export-MigrationReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-migrationreport +schema: 2.0.0 +title: Export-MigrationReport --- # Export-MigrationReport @@ -55,13 +56,15 @@ 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 @@ -71,13 +74,15 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,13 +110,15 @@ 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 @@ -119,6 +128,9 @@ 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`. @@ -128,7 +140,6 @@ 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 @@ -138,6 +149,9 @@ 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. @@ -146,7 +160,6 @@ 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 @@ -156,6 +169,9 @@ 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. @@ -164,7 +180,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -174,13 +189,15 @@ 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/exchange/Export-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md similarity index 89% rename from exchange/exchange-ps/exchange/Export-QuarantineMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md index f20bb9e7c2..060bade789 100644 --- a/exchange/exchange-ps/exchange/Export-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-quarantinemessage +schema: 2.0.0 +title: Export-QuarantineMessage --- # Export-QuarantineMessage @@ -88,6 +89,9 @@ 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. @@ -98,7 +102,6 @@ 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 @@ -108,15 +111,17 @@ 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 +Parameter Sets: Identities, IdentityOnly Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -125,20 +130,10 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: IdentityOnly -Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection +### -CompressOutput -Required: True -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` +> Applicable: Security & Compliance, Exchange Online Protection -### -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. @@ -147,7 +142,6 @@ 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 @@ -157,6 +151,9 @@ 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 @@ -168,7 +165,6 @@ 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 @@ -178,6 +174,9 @@ 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. @@ -186,7 +185,6 @@ 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 @@ -196,6 +194,9 @@ 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: @@ -210,7 +211,6 @@ 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,13 +220,15 @@ 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 @@ -236,13 +238,15 @@ 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 @@ -252,13 +256,15 @@ 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/exchange/Export-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md similarity index 90% rename from exchange/exchange-ps/exchange/Export-RecipientDataProperty.md rename to exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md index 79ca27c8bb..74957df426 100644 --- a/exchange/exchange-ps/exchange/Export-RecipientDataProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-recipientdataproperty +schema: 2.0.0 +title: Export-RecipientDataProperty --- # Export-RecipientDataProperty @@ -66,6 +67,9 @@ 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 @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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,6 +131,9 @@ 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. @@ -134,7 +144,6 @@ 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 @@ -144,6 +153,9 @@ 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. @@ -154,7 +166,6 @@ 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 @@ -164,13 +175,15 @@ 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/exchange/Export-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md similarity index 91% rename from exchange/exchange-ps/exchange/Export-TransportRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md index 1996ade66b..72227663ad 100644 --- a/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-transportrulecollection +schema: 2.0.0 +title: Export-TransportRuleCollection --- # Export-TransportRuleCollection @@ -64,6 +65,9 @@ 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: @@ -76,7 +80,6 @@ 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 @@ -86,6 +89,9 @@ 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`. @@ -95,7 +101,6 @@ 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 @@ -105,6 +110,9 @@ 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. @@ -115,7 +123,6 @@ 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,6 +132,9 @@ 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. @@ -133,7 +143,6 @@ 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 @@ -143,6 +152,9 @@ 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: @@ -155,7 +167,6 @@ 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 @@ -165,13 +176,15 @@ 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/exchange/Export-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md similarity index 91% rename from exchange/exchange-ps/exchange/Export-UMCallDataRecord.md rename to exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md index 29e7f3790d..dc3f6fb87b 100644 --- a/exchange/exchange-ps/exchange/Export-UMCallDataRecord.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-umcalldatarecord +schema: 2.0.0 +title: Export-UMCallDataRecord --- # Export-UMCallDataRecord @@ -56,13 +57,15 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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 @@ -123,13 +132,15 @@ 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 @@ -139,13 +150,15 @@ 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 @@ -155,13 +168,15 @@ 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/exchange/Export-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md similarity index 92% rename from exchange/exchange-ps/exchange/Export-UMPrompt.md rename to exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md index 02e8841d44..50c812990d 100644 --- a/exchange/exchange-ps/exchange/Export-UMPrompt.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/export-umprompt +schema: 2.0.0 +title: Export-UMPrompt --- # Export-UMPrompt @@ -68,13 +69,15 @@ 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 @@ -84,13 +87,15 @@ 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 @@ -100,13 +105,15 @@ 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 @@ -116,6 +123,9 @@ 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`. @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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 @@ -151,13 +162,15 @@ 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/exchange/Get-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ADPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md index 773f0467b4..5e29767da2 100644 --- a/exchange/exchange-ps/exchange/Get-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adpermission +schema: 2.0.0 +title: Get-ADPermission --- # Get-ADPermission @@ -60,13 +61,15 @@ 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 @@ -76,6 +79,9 @@ 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. @@ -84,7 +90,6 @@ 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,6 +99,9 @@ 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. @@ -102,7 +110,6 @@ 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 @@ -112,6 +119,9 @@ 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 @@ -142,7 +152,6 @@ 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/exchange/Get-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-ADServerSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md index e44f8bd977..fd4afe6bf8 100644 --- a/exchange/exchange-ps/exchange/Get-ADServerSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adserversettings +schema: 2.0.0 +title: Get-ADServerSettings --- # Get-AdServerSettings diff --git a/exchange/exchange-ps/exchange/Get-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ADSite.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md index 507afd4a61..7cc1fb5d25 100644 --- a/exchange/exchange-ps/exchange/Get-ADSite.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adsite +schema: 2.0.0 +title: Get-ADSite --- # Get-AdSite @@ -43,13 +44,15 @@ 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 @@ -59,6 +62,9 @@ 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. @@ -67,7 +73,6 @@ 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/exchange/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md index 714d4981eb..b9808576e5 100644 --- a/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-atpbuiltinprotectionrule +schema: 2.0.0 +title: Get-ATPBuiltInProtectionRule --- # Get-ATPBuiltInProtectionRule @@ -41,6 +42,9 @@ 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 @@ -53,7 +57,6 @@ 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 @@ -63,6 +66,9 @@ Accept wildcard characters: False ``` ### -State + +> Applicable: Exchange Online + The State parameter filters the results by the state of the rule. Valid values are: - Disabled @@ -75,7 +81,6 @@ Type: RuleState Parameter Sets: (All) Aliases: Accepted values: Enabled, Disabled -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md index f0a24d140f..9960270959 100644 --- a/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-atpprotectionpolicyrule +schema: 2.0.0 +title: Get-ATPProtectionPolicyRule --- # Get-ATPProtectionPolicyRule @@ -50,6 +51,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ Accept wildcard characters: False ``` ### -State + +> Applicable: Exchange Online + The State parameter filters the results by the state of the rule. Valid values are: - Enabled @@ -82,7 +88,6 @@ Type: RuleState Parameter Sets: (All) Aliases: Accepted values: Enabled, Disabled -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md index 754759eea3..87e3ea15d8 100644 --- a/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-atptotaltrafficreport +schema: 2.0.0 +title: Get-ATPTotalTrafficReport --- # Get-ATPTotalTrafficReport @@ -69,6 +70,9 @@ 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. @@ -77,7 +81,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -87,13 +90,15 @@ 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 @@ -103,6 +108,9 @@ 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 @@ -114,7 +122,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -124,13 +131,15 @@ 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 @@ -140,6 +149,9 @@ 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". @@ -148,7 +160,6 @@ 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 @@ -158,13 +169,15 @@ 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 @@ -174,13 +187,15 @@ 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 @@ -190,13 +205,15 @@ 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 @@ -206,6 +223,9 @@ 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". @@ -214,7 +234,6 @@ 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 @@ -224,6 +243,9 @@ 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: @@ -239,7 +261,6 @@ 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/exchange/Get-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-AcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md index 7a46a55884..717b71c364 100644 --- a/exchange/exchange-ps/exchange/Get-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-accepteddomain +schema: 2.0.0 +title: Get-AcceptedDomain --- # Get-AcceptedDomain @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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. @@ -75,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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/exchange/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md index c42017f450..daa8f90c02 100644 --- a/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-accesstocustomerdatarequest +schema: 2.0.0 +title: Get-AccessToCustomerDataRequest --- # Get-AccessToCustomerDataRequest @@ -58,6 +59,9 @@ 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 @@ -69,7 +73,6 @@ 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 @@ -79,6 +82,9 @@ 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: @@ -90,7 +96,6 @@ 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 @@ -100,13 +105,15 @@ 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/exchange/Get-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md index 76afb95c32..488efec211 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdevice +schema: 2.0.0 +title: Get-ActiveSyncDevice --- # Get-ActiveSyncDevice @@ -77,6 +78,9 @@ 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 @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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 @@ -114,7 +120,6 @@ 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 @@ -124,6 +129,9 @@ 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. @@ -132,7 +140,6 @@ 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 @@ -142,6 +149,9 @@ 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. @@ -178,7 +188,6 @@ 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 @@ -188,6 +197,9 @@ 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. @@ -198,7 +210,6 @@ 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 @@ -208,6 +219,9 @@ 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 @@ -219,7 +233,6 @@ 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 @@ -229,13 +242,15 @@ 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 @@ -245,6 +260,9 @@ 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. @@ -271,7 +289,6 @@ 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/exchange/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md index d3a5a05c35..1b097bb38c 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceaccessrule +schema: 2.0.0 +title: Get-ActiveSyncDeviceAccessRule --- # Get-ActiveSyncDeviceAccessRule @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md index 0bb8724eba..6c252b8fa8 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceautoblockthreshold +schema: 2.0.0 +title: Get-ActiveSyncDeviceAutoblockThreshold --- # Get-ActiveSyncDeviceAutoblockThreshold @@ -43,13 +44,15 @@ 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 @@ -59,13 +62,15 @@ 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/exchange/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md index 56664b5b8c..837dcdd22c 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceclass +schema: 2.0.0 +title: Get-ActiveSyncDeviceClass --- # Get-ActiveSyncDeviceClass @@ -52,6 +53,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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,7 +86,6 @@ 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,6 +95,9 @@ 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. @@ -111,7 +119,6 @@ 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 @@ -121,6 +128,9 @@ 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. @@ -135,7 +145,6 @@ 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/exchange/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md index df60827dd4..68ae398f1b 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdevicestatistics +schema: 2.0.0 +title: Get-ActiveSyncDeviceStatistics --- # Get-ActiveSyncDeviceStatistics @@ -77,13 +78,15 @@ 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 @@ -93,6 +96,9 @@ 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 @@ -110,7 +116,6 @@ 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 @@ -120,6 +125,9 @@ 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. @@ -128,7 +136,6 @@ 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,13 +145,15 @@ 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 @@ -154,6 +163,9 @@ 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. @@ -162,7 +174,6 @@ 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 @@ -172,13 +183,15 @@ 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/exchange/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md index c43f7a04a7..0b42866613 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncmailboxpolicy +schema: 2.0.0 +title: Get-ActiveSyncMailboxPolicy --- # Get-ActiveSyncMailboxPolicy @@ -59,13 +60,15 @@ 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 @@ -75,6 +78,9 @@ 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,7 +89,6 @@ 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/exchange/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md index 554ac124b7..e91b742b5e 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncorganizationsettings +schema: 2.0.0 +title: Get-ActiveSyncOrganizationSettings --- # Get-ActiveSyncOrganizationSettings @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md index 84a7bede86..7406f1c82a 100644 --- a/exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncvirtualdirectory +schema: 2.0.0 +title: Get-ActiveSyncVirtualDirectory --- # Get-ActiveSyncVirtualDirectory @@ -69,6 +70,9 @@ 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 @@ -83,7 +87,6 @@ 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 @@ -93,6 +96,9 @@ 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 @@ -106,7 +112,6 @@ 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 @@ -116,6 +121,9 @@ 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. @@ -124,7 +132,6 @@ 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 @@ -134,13 +141,15 @@ 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,6 +159,9 @@ 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. @@ -160,7 +172,6 @@ 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/exchange/Get-AdSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AdSiteLink.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md index 11565da45f..1aa30e7887 100644 --- a/exchange/exchange-ps/exchange/Get-AdSiteLink.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adsitelink +schema: 2.0.0 +title: Get-AdSiteLink --- # Get-AdSiteLink @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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. @@ -72,7 +78,6 @@ 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/exchange/Get-AdaptiveScope.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AdaptiveScope.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md index 1444986464..e82ef6c13c 100644 --- a/exchange/exchange-ps/exchange/Get-AdaptiveScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adaptivescope +schema: 2.0.0 +title: Get-AdaptiveScope --- # Get-AdaptiveScope @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,13 +71,15 @@ 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 @@ -84,13 +89,15 @@ 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/exchange/Get-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AddressBookPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md index 83e1de7f90..d7177e3bf1 100644 --- a/exchange/exchange-ps/exchange/Get-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-addressbookpolicy +schema: 2.0.0 +title: Get-AddressBookPolicy --- # Get-AddressBookPolicy @@ -57,13 +58,15 @@ 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 @@ -73,6 +76,9 @@ 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,7 +87,6 @@ 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/exchange/Get-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md index cf62cd285e..1b417d56e4 100644 --- a/exchange/exchange-ps/exchange/Get-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-addresslist +schema: 2.0.0 +title: Get-AddressList --- # Get-AddressList @@ -67,6 +68,9 @@ 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 @@ -80,7 +84,6 @@ 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 @@ -90,6 +93,9 @@ 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 @@ -103,7 +109,6 @@ 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 @@ -113,6 +118,9 @@ 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,7 +129,6 @@ 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,6 +138,9 @@ 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. @@ -139,7 +149,6 @@ 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/exchange/Get-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md index 7faa2b133d..71c53b48d4 100644 --- a/exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-addressrewriteentry +schema: 2.0.0 +title: Get-AddressRewriteEntry --- # Get-AddressRewriteEntry @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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. @@ -72,7 +78,6 @@ 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/exchange/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md index e9159a5432..cb89773a4e 100644 --- a/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-adminauditlogconfig +schema: 2.0.0 +title: Get-AdminAuditLogConfig --- # Get-AdminAuditLogConfig @@ -45,6 +46,9 @@ 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. @@ -53,7 +57,6 @@ 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/exchange/Get-AdministrativeUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-AdministrativeUnit.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md index 6a2753ab2d..b386d978d4 100644 --- a/exchange/exchange-ps/exchange/Get-AdministrativeUnit.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-administrativeunit +schema: 2.0.0 +title: Get-AdministrativeUnit --- # Get-AdministrativeUnit @@ -52,6 +53,9 @@ 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) @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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. @@ -101,7 +109,6 @@ 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 @@ -111,13 +118,15 @@ 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/exchange/Get-AgentLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-AgentLog.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md index 90b89266d4..93cfda98fe 100644 --- a/exchange/exchange-ps/exchange/Get-AgentLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-agentlog +schema: 2.0.0 +title: Get-AgentLog --- # Get-AgentLog @@ -43,6 +44,9 @@ 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". @@ -51,7 +55,6 @@ 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 @@ -61,13 +64,15 @@ 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 @@ -77,6 +82,9 @@ 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". @@ -85,7 +93,6 @@ 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 @@ -95,6 +102,9 @@ 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. @@ -107,7 +117,6 @@ 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/exchange/Get-AggregateZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-AggregateZapReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md index fd62052590..6c281a1769 100644 --- a/exchange/exchange-ps/exchange/Get-AggregateZapReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-aggregatezapreport +schema: 2.0.0 +title: Get-AggregateZapReport --- # Get-AggregateZapReport @@ -57,6 +58,9 @@ 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". @@ -67,7 +71,6 @@ 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 @@ -77,13 +80,15 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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". @@ -119,7 +129,6 @@ 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/exchange/Get-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md index 332d193a34..25d1eb6835 100644 --- a/exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-antiphishpolicy +schema: 2.0.0 +title: Get-AntiPhishPolicy --- # Get-AntiPhishPolicy @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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 @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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 @@ -123,7 +131,6 @@ Impersonation settings are available only in anti-phishing policies in Microsoft Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -133,6 +140,9 @@ 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 @@ -144,7 +154,6 @@ 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/exchange/Get-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md index 9593dd004c..12bd1bcb49 100644 --- a/exchange/exchange-ps/exchange/Get-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-antiphishrule +schema: 2.0.0 +title: Get-AntiPhishRule --- # Get-AntiPhishRule @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,13 +71,15 @@ 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/exchange/Get-App.md b/exchange/exchange-ps/ExchangePowerShell/Get-App.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-App.md rename to exchange/exchange-ps/ExchangePowerShell/Get-App.md index 4d63102688..71250e79d7 100644 --- a/exchange/exchange-ps/exchange/Get-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-App.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-app +schema: 2.0.0 +title: Get-App --- # Get-App @@ -60,13 +61,15 @@ 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 @@ -76,6 +79,9 @@ 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,7 +90,6 @@ 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 @@ -94,6 +99,9 @@ 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 @@ -115,7 +123,6 @@ 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 @@ -125,13 +132,15 @@ 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 @@ -141,6 +150,9 @@ 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. @@ -149,7 +161,6 @@ 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/exchange/Get-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md index 1feb6b2100..b8f8ced196 100644 --- a/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-appretentioncompliancepolicy +schema: 2.0.0 +title: Get-AppRetentionCompliancePolicy --- # Get-AppRetentionCompliancePolicy @@ -52,6 +53,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,6 +111,9 @@ 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. @@ -112,7 +122,6 @@ 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/exchange/Get-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md index b61fb71ac0..e80c26014d 100644 --- a/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-appretentioncompliancerule +schema: 2.0.0 +title: Get-AppRetentionComplianceRule --- # Get-AppRetentionComplianceRule @@ -46,6 +47,9 @@ 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 @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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 @@ -76,7 +82,6 @@ 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/exchange/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md index 60e3070aa4..5722f4420d 100644 --- a/exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-applicationaccesspolicy +schema: 2.0.0 +title: Get-ApplicationAccessPolicy --- # Get-ApplicationAccessPolicy @@ -49,13 +50,15 @@ 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/exchange/Get-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-ArcConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md index 84df4c911e..91b600cf5d 100644 --- a/exchange/exchange-ps/exchange/Get-ArcConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-arcconfig +schema: 2.0.0 +title: Get-ArcConfig --- # Get-ArcConfig diff --git a/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md index 31818f3779..eeb370b2c8 100644 --- a/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-atppolicyforo365 +schema: 2.0.0 +title: Get-AtpPolicyForO365 --- # Get-AtpPolicyForO365 @@ -50,13 +51,15 @@ 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/exchange/Get-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md index f9144d58cd..4d81a5493b 100644 --- a/exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-attachmentfilterentry +schema: 2.0.0 +title: Get-AttachmentFilterEntry --- # Get-AttachmentFilterEntry @@ -57,6 +58,9 @@ 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. @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ 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. @@ -84,7 +90,6 @@ 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/exchange/Get-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md index f05c82c01c..14dbc956e6 100644 --- a/exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-attachmentfilterlistconfig +schema: 2.0.0 +title: Get-AttachmentFilterListConfig --- # Get-AttachmentFilterListConfig @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-AuditConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AuditConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md index 65476171dc..224bc25924 100644 --- a/exchange/exchange-ps/exchange/Get-AuditConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-auditconfig +schema: 2.0.0 +title: Get-AuditConfig --- # Get-AuditConfig @@ -40,13 +41,15 @@ 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/exchange/Get-AuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-AuditLogSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md index a77201fca0..6ed3f110ff 100644 --- a/exchange/exchange-ps/exchange/Get-AuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-auditlogsearch +schema: 2.0.0 +title: Get-AuditLogSearch --- # Get-AuditLogSearch @@ -53,13 +54,15 @@ 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 @@ -69,6 +72,9 @@ 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". @@ -77,7 +83,6 @@ 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 @@ -87,6 +92,9 @@ 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". @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ 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 @@ -121,13 +130,15 @@ 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/exchange/Get-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AuthConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md index 7acbfbce8c..521572970c 100644 --- a/exchange/exchange-ps/exchange/Get-AuthConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-authconfig +schema: 2.0.0 +title: Get-AuthConfig --- # Get-AuthConfig @@ -40,13 +41,15 @@ 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/exchange/Get-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AuthRedirect.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md index a1e538e22c..e4e094965c 100644 --- a/exchange/exchange-ps/exchange/Get-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-authredirect +schema: 2.0.0 +title: Get-AuthRedirect --- # Get-AuthRedirect @@ -50,13 +51,15 @@ 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 @@ -66,13 +69,15 @@ 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/exchange/Get-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-AuthServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md index ecf577d5a2..6461f7e4b5 100644 --- a/exchange/exchange-ps/exchange/Get-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-authserver +schema: 2.0.0 +title: Get-AuthServer --- # Get-AuthServer @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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. @@ -78,7 +84,6 @@ 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/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index b79c7d9b3c..bd25769376 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-authenticationpolicy +schema: 2.0.0 +title: Get-AuthenticationPolicy --- # Get-AuthenticationPolicy @@ -55,6 +56,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -90,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ Accept wildcard characters: False ``` ### -TenantId + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill TenantId Description }} @@ -108,7 +116,6 @@ 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/exchange/Get-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md index b60b6db4da..7e02484620 100644 --- a/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-autosensitivitylabelpolicy +schema: 2.0.0 +title: Get-AutoSensitivityLabelPolicy --- # Get-AutoSensitivityLabelPolicy @@ -44,6 +45,9 @@ 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 @@ -54,7 +58,6 @@ 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 @@ -64,13 +67,15 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -89,7 +97,6 @@ The ForceValidate parameter specifies whether to include details related to the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -99,6 +106,9 @@ 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. @@ -107,7 +117,6 @@ 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 @@ -117,6 +126,9 @@ 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. @@ -126,7 +138,6 @@ 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/exchange/Get-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md index ebaea6d9d6..b432e17d95 100644 --- a/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-autosensitivitylabelrule +schema: 2.0.0 +title: Get-AutoSensitivityLabelRule --- # Get-AutoSensitivityLabelRule @@ -46,6 +47,9 @@ 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 @@ -56,7 +60,6 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,6 +105,9 @@ 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. @@ -107,7 +117,6 @@ The IncludeExecutionRuleGuids parameter specifies whether to include the executi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -117,6 +126,9 @@ 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. @@ -126,7 +138,6 @@ The IncludeExecutionRuleInformation parameter specifies whether to include the e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -136,6 +147,9 @@ 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 @@ -146,7 +160,6 @@ 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 @@ -156,13 +169,15 @@ 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/exchange/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md index e8c693c9bf..63acf04b72 100644 --- a/exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-autodiscovervirtualdirectory +schema: 2.0.0 +title: Get-AutodiscoverVirtualDirectory --- # Get-AutodiscoverVirtualDirectory @@ -67,6 +68,9 @@ 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 @@ -81,7 +85,6 @@ 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 @@ -91,6 +94,9 @@ 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 @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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. @@ -122,7 +130,6 @@ 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,13 +139,15 @@ 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,6 +157,9 @@ 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. @@ -158,7 +170,6 @@ 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/exchange/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md index bfde6fcc4c..975ed0d155 100644 --- a/exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityaddressspace +schema: 2.0.0 +title: Get-AvailabilityAddressSpace --- # Get-AvailabilityAddressSpace @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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,7 +84,6 @@ 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/exchange/Get-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-AvailabilityConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md index 7932aaed30..95a01b36a9 100644 --- a/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityconfig +schema: 2.0.0 +title: Get-AvailabilityConfig --- # Get-AvailabilityConfig @@ -46,13 +47,15 @@ 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 @@ -62,6 +65,9 @@ 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. @@ -70,7 +76,6 @@ 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/exchange/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md rename to exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md index b73d3f29f3..04dd371ed0 100644 --- a/exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityreportoutage +schema: 2.0.0 +title: Get-AvailabilityReportOutage --- # Get-AvailabilityReportOutage @@ -50,13 +51,15 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Get-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-BlockedConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md index c6701d3230..2fd76469bf 100644 --- a/exchange/exchange-ps/exchange/Get-BlockedConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-blockedconnector +schema: 2.0.0 +title: Get-BlockedConnector --- # Get-BlockedConnector @@ -46,13 +47,15 @@ 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/exchange/Get-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md rename to exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md index 4a14ad443b..2108e2aa05 100644 --- a/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-blockedsenderaddress +schema: 2.0.0 +title: Get-BlockedSenderAddress --- # Get-BlockedSenderAddress @@ -47,13 +48,15 @@ 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/exchange/Get-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-CASMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md index 00439ed122..44f12cfa6a 100644 --- a/exchange/exchange-ps/exchange/Get-CASMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-casmailbox +schema: 2.0.0 +title: Get-CASMailbox --- # Get-CASMailbox @@ -106,6 +107,9 @@ 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 @@ -123,7 +127,6 @@ 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 @@ -133,6 +136,9 @@ 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. @@ -143,7 +149,6 @@ 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 @@ -153,13 +158,15 @@ 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 @@ -169,6 +176,9 @@ 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) @@ -181,7 +191,6 @@ 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 @@ -191,6 +200,9 @@ 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). @@ -199,7 +211,6 @@ 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 @@ -209,6 +220,9 @@ 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. @@ -217,7 +231,6 @@ 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 @@ -227,6 +240,9 @@ 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. @@ -242,7 +258,6 @@ 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 @@ -252,6 +267,9 @@ 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: @@ -263,7 +281,6 @@ 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 @@ -273,6 +290,9 @@ 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. @@ -283,7 +303,6 @@ 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 @@ -293,6 +312,9 @@ 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 @@ -304,7 +326,6 @@ 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 @@ -314,6 +335,9 @@ 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 @@ -331,7 +355,6 @@ 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 @@ -341,6 +364,9 @@ 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. @@ -353,7 +379,6 @@ 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 @@ -363,13 +388,15 @@ 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 @@ -379,6 +406,9 @@ 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. @@ -387,7 +417,6 @@ 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 @@ -397,6 +426,9 @@ 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: @@ -418,7 +450,6 @@ You can specify multiple values separated by commas. Type: RecipientTypeDetails[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -428,13 +459,15 @@ 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 @@ -444,6 +477,9 @@ 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. @@ -458,7 +494,6 @@ 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/exchange/Get-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-CASMailboxPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md index c825898743..fa030a377f 100644 --- a/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-casmailboxplan +schema: 2.0.0 +title: Get-CASMailboxPlan --- # Get-CASMailboxPlan @@ -55,6 +56,9 @@ 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 @@ -67,7 +71,6 @@ 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 @@ -77,6 +80,9 @@ 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). @@ -85,7 +91,6 @@ 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 @@ -95,13 +100,15 @@ 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 @@ -111,6 +118,9 @@ 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. @@ -126,7 +136,6 @@ 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 @@ -136,6 +145,9 @@ 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. @@ -144,7 +156,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -154,13 +165,15 @@ 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 @@ -170,6 +183,9 @@ 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. @@ -185,7 +201,6 @@ 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/exchange/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md index 497c465e12..d75b946359 100644 --- a/exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticanalysis +schema: 2.0.0 +title: Get-CalendarDiagnosticAnalysis --- # Get-CalendarDiagnosticAnalysis @@ -99,6 +100,9 @@ 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. @@ -111,7 +115,6 @@ 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 @@ -121,6 +124,9 @@ 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. @@ -135,7 +141,6 @@ 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 @@ -145,6 +150,9 @@ 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. @@ -154,7 +162,6 @@ 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 @@ -164,6 +171,9 @@ 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). @@ -172,7 +182,6 @@ 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 @@ -182,6 +191,9 @@ 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) @@ -192,7 +204,6 @@ 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/exchange/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md similarity index 87% rename from exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md index 38b63df96c..f020ba6a7d 100644 --- a/exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticlog +schema: 2.0.0 +title: Get-CalendarDiagnosticLog --- # Get-CalendarDiagnosticLog @@ -113,6 +114,9 @@ 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 @@ -130,7 +134,6 @@ 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 @@ -140,6 +143,9 @@ 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. @@ -154,9 +160,8 @@ In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAna ```yaml Type: String -Parameter Sets: ExportToMsg +Parameter Sets: ExportToMsg, MeetingId, MeetingSubject Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online Required: True Position: Named @@ -165,20 +170,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: MeetingId, MeetingSubject -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online +### -MeetingID -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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. @@ -187,9 +182,8 @@ Don't use this parameter with the Subject parameter, because the value of the Me ```yaml Type: String -Parameter Sets: MeetingId +Parameter Sets: MeetingId, ExportToMsg Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -198,29 +192,18 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: ExportToMsg -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Subject -Required: False -Position: Named -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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 +Parameter Sets: MeetingSubject, ExportToMsg Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -229,20 +212,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: ExportToMsg -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Credential -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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. @@ -253,7 +226,6 @@ 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 @@ -263,6 +235,9 @@ 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. @@ -271,7 +246,6 @@ 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,6 +255,9 @@ 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". @@ -289,7 +266,6 @@ 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 @@ -299,13 +275,15 @@ 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 @@ -315,6 +293,9 @@ 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". @@ -330,7 +311,6 @@ 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 @@ -340,6 +320,9 @@ 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. @@ -348,7 +331,6 @@ 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 @@ -358,13 +340,15 @@ 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 @@ -374,13 +358,15 @@ 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 @@ -390,6 +376,9 @@ 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. @@ -402,7 +391,6 @@ 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 @@ -412,13 +400,15 @@ 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 @@ -428,6 +418,9 @@ 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". @@ -436,7 +429,6 @@ 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/exchange/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md index e01ded63d5..37b5eeb8e2 100644 --- a/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticobjects +schema: 2.0.0 +title: Get-CalendarDiagnosticObjects --- # Get-CalendarDiagnosticObjects @@ -93,6 +94,9 @@ 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 @@ -110,7 +114,6 @@ 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 @@ -120,13 +123,15 @@ 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 @@ -136,13 +141,15 @@ 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 @@ -152,13 +159,15 @@ 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 @@ -168,6 +177,9 @@ 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. @@ -176,7 +188,6 @@ You can specify multiple values separated by commas. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -186,6 +197,9 @@ 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". @@ -194,7 +208,6 @@ 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 @@ -204,13 +217,15 @@ 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 @@ -220,13 +235,15 @@ 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 @@ -236,6 +253,9 @@ 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". @@ -251,7 +271,6 @@ 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 @@ -261,13 +280,15 @@ 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 @@ -277,13 +298,15 @@ 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 @@ -293,13 +316,15 @@ 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 @@ -309,13 +334,15 @@ 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 @@ -325,13 +352,15 @@ 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 @@ -341,13 +370,15 @@ 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 @@ -357,6 +388,9 @@ 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. @@ -366,7 +400,6 @@ The ShouldBindToItem parameter specifies whether to truncate large streamable pr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -376,13 +409,15 @@ 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 @@ -392,13 +427,15 @@ 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 @@ -408,6 +445,9 @@ 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. @@ -417,7 +457,6 @@ The ShouldFetchRecurrenceExceptions parameter specifies whether to include excep Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -427,6 +466,9 @@ 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". @@ -435,7 +477,6 @@ 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 @@ -445,13 +486,15 @@ 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/exchange/Get-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-CalendarNotification.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md index 014d7e719e..3ca8ce73de 100644 --- a/exchange/exchange-ps/exchange/Get-CalendarNotification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-calendarnotification +schema: 2.0.0 +title: Get-CalendarNotification --- # Get-CalendarNotification @@ -48,6 +49,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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). @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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. @@ -119,7 +129,6 @@ 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 @@ -129,13 +138,15 @@ 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/exchange/Get-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-CalendarProcessing.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md index a38f7b7958..74027e8e74 100644 --- a/exchange/exchange-ps/exchange/Get-CalendarProcessing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-calendarprocessing +schema: 2.0.0 +title: Get-CalendarProcessing --- # Get-CalendarProcessing @@ -45,6 +46,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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,7 +86,6 @@ 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,6 +95,9 @@ 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. @@ -102,7 +110,6 @@ 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 @@ -112,13 +119,15 @@ 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/exchange/Get-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md index 54654c842b..d2850979de 100644 --- a/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy +schema: 2.0.0 +title: Get-CaseHoldPolicy --- # Get-CaseHoldPolicy @@ -51,6 +52,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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 @@ -82,7 +88,6 @@ 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 @@ -92,6 +97,9 @@ 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". @@ -109,7 +117,6 @@ The following properties are affected by this switch: Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -119,13 +126,15 @@ Accept wildcard characters: False ``` ### -IncludeBindings + +> Applicable: Security & Compliance + PARAMVALUE: SwitchParameter ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -135,13 +144,15 @@ 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/exchange/Get-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-CaseHoldRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md index 632e20fe65..48f594563b 100644 --- a/exchange/exchange-ps/exchange/Get-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-caseholdrule +schema: 2.0.0 +title: Get-CaseHoldRule --- # Get-CaseHoldRule @@ -45,6 +46,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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 @@ -77,7 +83,6 @@ 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/exchange/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md index b246435ac5..a54d314ecf 100644 --- a/exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-classificationrulecollection +schema: 2.0.0 +title: Get-ClassificationRuleCollection --- # Get-ClassificationRuleCollection @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ClientAccessArray.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md index c879bde532..161a986521 100644 --- a/exchange/exchange-ps/exchange/Get-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessarray +schema: 2.0.0 +title: Get-ClientAccessArray --- # Get-ClientAccessArray @@ -56,6 +57,9 @@ 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) @@ -68,7 +72,6 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,6 +99,9 @@ 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 @@ -105,7 +113,6 @@ 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/exchange/Get-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-ClientAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md index 0e40aa0d98..489a684717 100644 --- a/exchange/exchange-ps/exchange/Get-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessrule +schema: 2.0.0 +title: Get-ClientAccessRule --- # Get-ClientAccessRule @@ -55,6 +56,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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`. @@ -84,7 +90,6 @@ 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 @@ -94,6 +99,9 @@ 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. @@ -102,7 +110,6 @@ 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 @@ -112,13 +119,15 @@ 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/exchange/Get-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ClientAccessServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md index c3cb98eccc..1f47d159d5 100644 --- a/exchange/exchange-ps/exchange/Get-ClientAccessServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessserver +schema: 2.0.0 +title: Get-ClientAccessServer --- # Get-ClientAccessServer @@ -52,6 +53,9 @@ 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: @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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 @@ -91,6 +96,9 @@ 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`. @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ 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`. @@ -117,7 +127,6 @@ 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/exchange/Get-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ClientAccessService.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md index 1f3d8c72e4..dcd5b55a08 100644 --- a/exchange/exchange-ps/exchange/Get-ClientAccessService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessservice +schema: 2.0.0 +title: Get-ClientAccessService --- # Get-ClientAccessService @@ -50,6 +51,9 @@ 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: @@ -63,7 +67,6 @@ 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 @@ -73,13 +76,15 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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`. @@ -115,7 +125,6 @@ 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/exchange/Get-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-Clutter.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md index abd9f70458..8ebd24606b 100644 --- a/exchange/exchange-ps/exchange/Get-Clutter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-clutter +schema: 2.0.0 +title: Get-Clutter --- # Get-Clutter @@ -41,6 +42,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,13 +71,15 @@ 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/exchange/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md index b863d66f12..dd5aba596e 100644 --- a/exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-cmdletextensionagent +schema: 2.0.0 +title: Get-CmdletExtensionAgent --- # Get-CmdletExtensionAgent @@ -59,6 +60,9 @@ 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 @@ -69,7 +73,6 @@ 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 @@ -79,13 +82,15 @@ 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 @@ -95,13 +100,15 @@ 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,6 +118,9 @@ 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. @@ -122,7 +132,6 @@ 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/exchange/Get-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ComplianceCase.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md index 74d35075bf..86d872f344 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancecase +schema: 2.0.0 +title: Get-ComplianceCase --- # Get-ComplianceCase @@ -65,6 +66,9 @@ 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 @@ -74,7 +78,6 @@ 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 @@ -84,6 +87,9 @@ 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**. @@ -100,7 +106,6 @@ 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 @@ -110,13 +115,15 @@ 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 @@ -126,6 +133,9 @@ 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. @@ -134,7 +144,6 @@ 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 @@ -144,13 +153,15 @@ 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/exchange/Get-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md index 5588971c20..2d2e1c0896 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancecasemember +schema: 2.0.0 +title: Get-ComplianceCaseMember --- # Get-ComplianceCaseMember @@ -52,13 +53,15 @@ 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 @@ -68,13 +71,15 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Get-ComplianceRetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md index 4688db4274..1ce9266d5a 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-complianceretentionevent +schema: 2.0.0 +title: Get-ComplianceRetentionEvent --- # Get-ComplianceRetentionEvent @@ -51,6 +52,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,13 +74,15 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,13 +110,15 @@ 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 @@ -119,13 +128,15 @@ 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/exchange/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md index 413b3c7aa3..7d5ded8910 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-complianceretentioneventtype +schema: 2.0.0 +title: Get-ComplianceRetentionEventType --- # Get-ComplianceRetentionEventType @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -76,7 +82,6 @@ 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/exchange/Get-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md index 95ca1983f2..f700c36ca5 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesearch +schema: 2.0.0 +title: Get-ComplianceSearch --- # Get-ComplianceSearch @@ -54,6 +55,9 @@ 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: @@ -81,7 +85,6 @@ 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 @@ -91,6 +94,9 @@ 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. @@ -101,7 +107,6 @@ 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 @@ -111,6 +116,9 @@ 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. @@ -119,7 +127,6 @@ 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 @@ -129,13 +136,15 @@ 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/exchange/Get-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md index a0ca0a62b5..543eedbc13 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesearchaction +schema: 2.0.0 +title: Get-ComplianceSearchAction --- # Get-ComplianceSearchAction @@ -96,6 +97,9 @@ 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"`. @@ -115,7 +119,6 @@ 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 @@ -125,6 +128,9 @@ 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. @@ -133,7 +139,6 @@ 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 @@ -143,13 +148,15 @@ 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 @@ -159,6 +166,9 @@ 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. @@ -167,7 +177,6 @@ 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 @@ -177,6 +186,9 @@ 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. @@ -187,7 +199,6 @@ 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 @@ -197,13 +208,15 @@ 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 @@ -213,6 +226,9 @@ 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. @@ -221,7 +237,6 @@ This parameter is reserved for internal Microsoft use. Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -231,6 +246,9 @@ 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. @@ -239,7 +257,6 @@ 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 @@ -249,6 +266,9 @@ 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. @@ -259,7 +279,6 @@ 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 @@ -269,13 +288,15 @@ 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/exchange/Get-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md index 0c3ff1f88a..4989134761 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesecurityfilter +schema: 2.0.0 +title: Get-ComplianceSecurityFilter --- # Get-ComplianceSecurityFilter @@ -53,6 +54,9 @@ 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. @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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`. @@ -84,7 +90,6 @@ 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 @@ -94,13 +99,15 @@ 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 @@ -110,6 +117,9 @@ 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. @@ -120,7 +130,6 @@ 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 @@ -130,13 +139,15 @@ 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/exchange/Get-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ComplianceTag.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md index 2c704b8488..dd8b525fd9 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancetag +schema: 2.0.0 +title: Get-ComplianceTag --- # Get-ComplianceTag @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Get-ComplianceTagStorage.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md index c3aa8eaca3..c9b91fc8df 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancetagstorage +schema: 2.0.0 +title: Get-ComplianceTagStorage --- # Get-ComplianceTagStorage @@ -41,6 +42,9 @@ 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) @@ -53,7 +57,6 @@ 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 @@ -63,13 +66,15 @@ 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/exchange/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md index d26e9e5e0d..4c0e91e2a9 100644 --- a/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compromiseduseraggregatereport +schema: 2.0.0 +title: Get-CompromisedUserAggregateReport --- # Get-CompromisedUserAggregateReport @@ -51,6 +52,9 @@ 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 @@ -62,7 +66,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -72,6 +75,9 @@ 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. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,6 +131,9 @@ 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. @@ -130,7 +142,6 @@ 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/exchange/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md index 07d5d63148..cc47aea53f 100644 --- a/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-compromiseduserdetailreport +schema: 2.0.0 +title: Get-CompromisedUserDetailReport --- # Get-CompromisedUserDetailReport @@ -51,6 +52,9 @@ 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 @@ -62,7 +66,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -72,6 +75,9 @@ 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. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,6 +131,9 @@ 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. @@ -132,7 +144,6 @@ 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/exchange/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md index ff118bc38d..ce1571a8c2 100644 --- a/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-configanalyzerpolicyrecommendation +schema: 2.0.0 +title: Get-ConfigAnalyzerPolicyRecommendation --- # Get-ConfigAnalyzerPolicyRecommendation @@ -62,13 +63,15 @@ 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 @@ -78,6 +81,9 @@ 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 @@ -87,7 +93,6 @@ The RecommendedPolicyType parameter specifies the preset security policy that yo Type: RecommendedPolicyType Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -97,6 +102,9 @@ 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. @@ -105,7 +113,6 @@ 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/exchange/Get-ConnectionInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-ConnectionInformation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md index 97f9d3efd2..1073280013 100644 --- a/exchange/exchange-ps/exchange/Get-ConnectionInformation.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-connectioninformation +schema: 2.0.0 +title: Get-ConnectionInformation --- # Get-ConnectionInformation @@ -87,6 +87,9 @@ 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. @@ -97,7 +100,6 @@ Don't use this parameter with the ModulePrefix parameter. Type: String[] Parameter Sets: ConnectionId Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -107,6 +109,9 @@ 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. @@ -119,7 +124,6 @@ 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/exchange/Get-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-Contact.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Contact.md index 389fa44712..09a4a511f5 100644 --- a/exchange/exchange-ps/exchange/Get-Contact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-contact +schema: 2.0.0 +title: Get-Contact --- # Get-Contact @@ -79,6 +80,9 @@ 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 @@ -90,7 +94,6 @@ 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 @@ -100,6 +103,9 @@ 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) @@ -112,7 +118,6 @@ 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 @@ -122,6 +127,9 @@ 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. @@ -132,7 +140,6 @@ 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 @@ -142,6 +149,9 @@ 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. @@ -150,7 +160,6 @@ 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 @@ -160,6 +169,9 @@ 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. @@ -175,7 +187,6 @@ 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 @@ -185,6 +196,9 @@ 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. @@ -198,7 +212,6 @@ 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 @@ -208,6 +221,9 @@ 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 @@ -219,7 +235,6 @@ 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 @@ -229,6 +244,9 @@ 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. @@ -241,7 +259,6 @@ 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 @@ -251,6 +268,9 @@ 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 @@ -263,7 +283,6 @@ 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 @@ -273,13 +292,15 @@ 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 @@ -289,6 +310,9 @@ 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. @@ -306,7 +330,6 @@ 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/exchange/Get-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ContentFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md index 8de0cb720d..aad53cb6c8 100644 --- a/exchange/exchange-ps/exchange/Get-ContentFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-contentfilterconfig +schema: 2.0.0 +title: Get-ContentFilterConfig --- # Get-ContentFilterConfig @@ -40,6 +41,9 @@ 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. @@ -48,7 +52,6 @@ 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/exchange/Get-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md index 1b1f47b29b..47fcc0b8b5 100644 --- a/exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-contentfilterphrase +schema: 2.0.0 +title: Get-ContentFilterPhrase --- # Get-ContentFilterPhrase @@ -63,6 +64,9 @@ 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. @@ -71,7 +75,6 @@ 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 @@ -81,6 +84,9 @@ 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. @@ -89,7 +95,6 @@ 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,6 +104,9 @@ 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. @@ -107,7 +115,6 @@ 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/exchange/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md index 2c884d0e2f..5a0e007fcb 100644 --- a/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-contentmalwaremdoaggregatereport +schema: 2.0.0 +title: Get-ContentMalwareMdoAggregateReport --- # Get-ContentMalwareMdoAggregateReport @@ -55,6 +56,9 @@ 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 @@ -67,7 +71,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -77,6 +80,9 @@ 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. @@ -85,7 +91,6 @@ 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 @@ -95,13 +100,15 @@ 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 @@ -111,13 +118,15 @@ 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 @@ -127,6 +136,9 @@ 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. @@ -135,7 +147,6 @@ 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 @@ -145,6 +156,9 @@ 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 @@ -157,7 +171,6 @@ 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/exchange/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md index eb99b53c05..ca8cfe777b 100644 --- a/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-contentmalwaremdodetailreport +schema: 2.0.0 +title: Get-ContentMalwareMdoDetailReport --- # Get-ContentMalwareMdoDetailReport @@ -57,6 +58,9 @@ 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 @@ -69,7 +73,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -79,6 +82,9 @@ 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. @@ -87,7 +93,6 @@ 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 @@ -97,13 +102,15 @@ 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 @@ -113,13 +120,15 @@ 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 @@ -129,6 +138,9 @@ 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. @@ -137,7 +149,6 @@ 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 @@ -147,6 +158,9 @@ 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 @@ -159,7 +173,6 @@ 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/exchange/Get-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DataClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md index 9bfe9cc832..ed5b57d5ea 100644 --- a/exchange/exchange-ps/exchange/Get-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dataclassification +schema: 2.0.0 +title: Get-DataClassification --- # Get-DataClassification @@ -67,13 +68,15 @@ 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 @@ -83,6 +86,9 @@ 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 @@ -93,7 +99,6 @@ 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 @@ -103,13 +108,15 @@ 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/exchange/Get-DataClassificationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-DataClassificationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md index 03342c3e31..5e57c531b9 100644 --- a/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dataclassificationconfig +schema: 2.0.0 +title: Get-DataClassificationConfig --- # Get-DataClassificationConfig diff --git a/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md index b58632caa0..557dbea62f 100644 --- a/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dataencryptionpolicy +schema: 2.0.0 +title: Get-DataEncryptionPolicy --- # Get-DataEncryptionPolicy @@ -54,6 +55,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,13 +116,15 @@ 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/exchange/Get-DataRetentionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DataRetentionReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md index 1f38d8c687..64313203d8 100644 --- a/exchange/exchange-ps/exchange/Get-DataRetentionReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dataretentionreport +schema: 2.0.0 +title: Get-DataRetentionReport --- # Get-DataRetentionReport @@ -52,6 +53,9 @@ 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". @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,6 +109,9 @@ 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". @@ -112,7 +122,6 @@ 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/exchange/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md index 6f519626b5..d54bf1139b 100644 --- a/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-databaseavailabilitygroup +schema: 2.0.0 +title: Get-DatabaseAvailabilityGroup --- # Get-DatabaseAvailabilityGroup @@ -59,13 +60,15 @@ 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 @@ -75,13 +78,15 @@ 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 @@ -91,13 +96,15 @@ 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/exchange/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md index deb02d5a8e..78a3f92fc4 100644 --- a/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-databaseavailabilitygroupnetwork +schema: 2.0.0 +title: Get-DatabaseAvailabilityGroupNetwork --- # Get-DatabaseAvailabilityGroupNetwork @@ -75,13 +76,15 @@ 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 @@ -91,13 +94,15 @@ 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,6 +112,9 @@ 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 @@ -118,7 +126,6 @@ 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/exchange/Get-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantBriefingConfig.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantBriefingConfig.md index 13ed2a7226..50986bd862 100644 --- a/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-defaulttenantbriefingconfig +schema: 2.0.0 +title: Get-DefaultTenantBriefingConfig --- # Get-DefaultTenantBriefingConfig @@ -55,13 +55,15 @@ 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/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantMyAnalyticsFeatureConfig.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantMyAnalyticsFeatureConfig.md index 76bb40fd28..8ca8852a10 100644 --- a/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-defaulttenantmyanalyticsfeatureconfig +schema: 2.0.0 +title: Get-DefaultTenantMyAnalyticsFeatureConfig --- # Get-DefaultTenantMyAnalyticsFeatureConfig @@ -51,13 +51,15 @@ 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/exchange/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md index 363d35c76f..f1b07834c8 100644 --- a/exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-deliveryagentconnector +schema: 2.0.0 +title: Get-DeliveryAgentConnector --- # Get-DeliveryAgentConnector @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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. @@ -74,7 +80,6 @@ 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/exchange/Get-DetailZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DetailZapReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md index e2332bf377..87846c60e9 100644 --- a/exchange/exchange-ps/exchange/Get-DetailZapReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-detailzapreport +schema: 2.0.0 +title: Get-DetailZapReport --- # Get-DetailZapReport @@ -68,6 +69,9 @@ 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". @@ -78,7 +82,6 @@ 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 @@ -88,13 +91,15 @@ 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 @@ -104,13 +109,15 @@ 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 @@ -120,6 +127,9 @@ 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". @@ -130,7 +140,6 @@ 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/exchange/Get-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-DetailsTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md index 71900617a9..8a8cc5ccbb 100644 --- a/exchange/exchange-ps/exchange/Get-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-detailstemplate +schema: 2.0.0 +title: Get-DetailsTemplate --- # Get-DetailsTemplate @@ -59,6 +60,9 @@ 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 @@ -72,7 +76,6 @@ 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 @@ -82,6 +85,9 @@ 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`. @@ -91,7 +97,6 @@ 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 @@ -101,13 +106,15 @@ 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 @@ -117,13 +124,15 @@ 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/exchange/Get-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md index a79926c166..aa4f3433ad 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconditionalaccesspolicy +schema: 2.0.0 +title: Get-DeviceConditionalAccessPolicy --- # Get-DeviceConditionalAccessPolicy @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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/exchange/Get-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md index 65fe845674..dbe653dc37 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconditionalaccessrule +schema: 2.0.0 +title: Get-DeviceConditionalAccessRule --- # Get-DeviceConditionalAccessRule @@ -58,13 +59,15 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,13 +95,15 @@ 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/exchange/Get-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md index 34e6dc1ae0..da59041650 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconfigurationpolicy +schema: 2.0.0 +title: Get-DeviceConfigurationPolicy --- # Get-DeviceConfigurationPolicy @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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/exchange/Get-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md index 84afa08d75..48f70c420c 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconfigurationrule +schema: 2.0.0 +title: Get-DeviceConfigurationRule --- # Get-DeviceConfigurationRule @@ -58,13 +59,15 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,13 +95,15 @@ 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/exchange/Get-DevicePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DevicePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md index f7cb5c1dce..0aa282b8c7 100644 --- a/exchange/exchange-ps/exchange/Get-DevicePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-devicepolicy +schema: 2.0.0 +title: Get-DevicePolicy --- # Get-DevicePolicy @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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/exchange/Get-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md index ce5c1c516e..68c8ae08a2 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-devicetenantpolicy +schema: 2.0.0 +title: Get-DeviceTenantPolicy --- # Get-DeviceTenantPolicy @@ -49,13 +50,15 @@ 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/exchange/Get-DeviceTenantRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DeviceTenantRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md index 3d61488bdc..6533fad408 100644 --- a/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-devicetenantrule +schema: 2.0.0 +title: Get-DeviceTenantRule --- # Get-DeviceTenantRule @@ -50,13 +51,15 @@ 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 @@ -66,13 +69,15 @@ 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/exchange/Get-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md index d91f0fd648..4cf9b86ef5 100644 --- a/exchange/exchange-ps/exchange/Get-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-distributiongroup +schema: 2.0.0 +title: Get-DistributionGroup --- # Get-DistributionGroup @@ -112,6 +113,9 @@ 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 @@ -125,7 +129,6 @@ 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 @@ -135,6 +138,9 @@ 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) @@ -147,7 +153,6 @@ 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 @@ -157,6 +162,9 @@ 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). @@ -165,7 +173,6 @@ 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 @@ -175,6 +182,9 @@ 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,7 +193,6 @@ 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,6 +202,9 @@ 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. @@ -208,7 +220,6 @@ 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,6 +229,9 @@ 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. @@ -231,7 +245,6 @@ 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 @@ -241,6 +254,9 @@ 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. @@ -251,7 +267,6 @@ 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 @@ -261,6 +276,9 @@ 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. @@ -271,7 +289,6 @@ 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 @@ -281,6 +298,9 @@ 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. @@ -291,7 +311,6 @@ 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 @@ -301,6 +320,9 @@ 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. @@ -311,7 +333,6 @@ 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 @@ -321,6 +342,9 @@ 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. @@ -331,7 +355,6 @@ 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 @@ -341,6 +364,9 @@ 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. @@ -351,7 +377,6 @@ 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 @@ -361,6 +386,9 @@ 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. @@ -371,7 +399,6 @@ 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 @@ -381,6 +408,9 @@ 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 @@ -394,7 +424,6 @@ 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 @@ -404,6 +433,9 @@ 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 @@ -415,7 +447,6 @@ 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 @@ -425,6 +456,9 @@ 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. @@ -437,7 +471,6 @@ 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 @@ -447,6 +480,9 @@ 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 @@ -460,7 +496,6 @@ 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 @@ -470,13 +505,15 @@ 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 @@ -486,6 +523,9 @@ 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. @@ -505,7 +545,6 @@ 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/exchange/Get-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-DistributionGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md index 3113e769e2..833ee2e77f 100644 --- a/exchange/exchange-ps/exchange/Get-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-distributiongroupmember +schema: 2.0.0 +title: Get-DistributionGroupMember --- # Get-DistributionGroupMember @@ -74,6 +75,9 @@ 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 @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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). @@ -105,7 +111,6 @@ 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 @@ -115,6 +120,9 @@ 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,7 +131,6 @@ 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,6 +140,9 @@ 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. @@ -146,7 +156,6 @@ 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 @@ -156,6 +165,9 @@ 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. @@ -166,7 +178,6 @@ 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 @@ -176,6 +187,9 @@ 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. @@ -188,7 +202,6 @@ 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 @@ -198,13 +211,15 @@ 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/exchange/Get-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DkimSigningConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md index 9fe8d4bfd8..4349b810fb 100644 --- a/exchange/exchange-ps/exchange/Get-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dkimsigningconfig +schema: 2.0.0 +title: Get-DkimSigningConfig --- # Get-DkimSigningConfig @@ -49,6 +50,9 @@ 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). @@ -59,7 +63,6 @@ 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/exchange/Get-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md index f5a379ed1b..d223a211ff 100644 --- a/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpcompliancepolicy +schema: 2.0.0 +title: Get-DlpCompliancePolicy --- # Get-DlpCompliancePolicy @@ -69,6 +70,9 @@ 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 @@ -80,7 +84,6 @@ 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 @@ -90,13 +93,15 @@ 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 @@ -106,6 +111,9 @@ 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. @@ -114,7 +122,6 @@ The DistributionDetail switch returns detailed policy distribution information i Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -124,13 +131,15 @@ 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 @@ -140,13 +149,15 @@ 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 @@ -156,13 +167,15 @@ 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 @@ -172,13 +185,15 @@ 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 @@ -188,13 +203,15 @@ 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 @@ -204,13 +221,15 @@ 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/exchange/Get-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DlpComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md index 3ec06ed550..1d5ea9f45b 100644 --- a/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpcompliancerule +schema: 2.0.0 +title: Get-DlpComplianceRule --- # Get-DlpComplianceRule @@ -57,6 +58,9 @@ 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 @@ -68,7 +72,6 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,13 +99,15 @@ 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 @@ -110,6 +117,9 @@ 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 @@ -121,7 +131,6 @@ 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/exchange/Get-DlpDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DlpDetailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md index ec4460246a..fd19dfd9e3 100644 --- a/exchange/exchange-ps/exchange/Get-DlpDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpdetailreport +schema: 2.0.0 +title: Get-DlpDetailReport --- # Get-DlpDetailReport @@ -74,6 +75,9 @@ 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 @@ -86,7 +90,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -96,6 +99,9 @@ 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"`. @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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"`. @@ -122,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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,7 +150,6 @@ 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 @@ -150,6 +159,9 @@ 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". @@ -158,7 +170,6 @@ 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 @@ -168,6 +179,9 @@ Accept wildcard characters: False ``` ### -EventType + +> Applicable: Exchange Online, Security & Compliance + The EventType parameter filters the report by the event type. Valid values are: - DLPActionHits @@ -186,7 +200,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -196,13 +209,15 @@ 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 @@ -212,13 +227,15 @@ 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 @@ -228,6 +245,9 @@ Accept wildcard characters: False ``` ### -Source + +> Applicable: Exchange Online, Security & Compliance + The Source parameter filters the report by workload. Valid values are: - EXCH: Exchange Online @@ -240,7 +260,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -250,6 +269,9 @@ 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". @@ -258,7 +280,6 @@ 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/exchange/Get-DlpDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md index be1c5ba605..efb47d2988 100644 --- a/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpdetectionsreport +schema: 2.0.0 +title: Get-DlpDetectionsReport --- # Get-DlpDetectionsReport @@ -66,6 +67,9 @@ 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 @@ -78,7 +82,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -88,13 +91,15 @@ 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 @@ -104,6 +109,9 @@ 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"`. @@ -112,7 +120,6 @@ 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 @@ -122,6 +129,9 @@ 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"`. @@ -130,7 +140,6 @@ 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 @@ -140,6 +149,9 @@ 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". @@ -148,7 +160,6 @@ 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 @@ -158,6 +169,9 @@ Accept wildcard characters: False ``` ### -EventType + +> Applicable: Exchange Online, Security & Compliance + The EventType parameter filters the report by the event type. Valid values are: - DataRetentions @@ -183,7 +197,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -193,6 +206,9 @@ 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. @@ -201,7 +217,6 @@ This parameter is reserved for internal Microsoft use. Type: Expression Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -211,13 +226,15 @@ 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,13 +244,15 @@ 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 @@ -243,6 +262,9 @@ Accept wildcard characters: False ``` ### -Source + +> Applicable: Exchange Online, Security & Compliance + The Source parameter filters the report by workload. Valid values are: - EXCH: Exchange Online @@ -255,7 +277,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -265,6 +286,9 @@ 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". @@ -273,7 +297,6 @@ 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 @@ -283,6 +306,9 @@ 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: @@ -297,7 +323,6 @@ 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/exchange/Get-DlpEdmSchema.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DlpEdmSchema.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md index d9052762b8..5bc2f63ecf 100644 --- a/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpedmschema +schema: 2.0.0 +title: Get-DlpEdmSchema --- # Get-DlpEdmSchema @@ -47,6 +48,9 @@ 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 @@ -56,7 +60,6 @@ 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/exchange/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md index 59707c5464..b7049611e7 100644 --- a/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpincidentdetailsreport +schema: 2.0.0 +title: Get-DlpIncidentDetailReport --- # Get-DlpIncidentDetailReport @@ -79,6 +80,9 @@ 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 @@ -91,7 +95,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -101,6 +104,9 @@ 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"`. @@ -109,7 +115,6 @@ 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,6 +124,9 @@ 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"`. @@ -127,7 +135,6 @@ 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 @@ -137,6 +144,9 @@ 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"`. @@ -145,7 +155,6 @@ 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 @@ -155,6 +164,9 @@ 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". @@ -163,7 +175,6 @@ 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 @@ -173,6 +184,9 @@ Accept wildcard characters: False ``` ### -EventType + +> Applicable: Exchange Online, Security & Compliance + The EventType parameter filters the report by the event type. Valid values are: - DLPByIncidentIdActionHits @@ -190,7 +204,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -200,13 +213,15 @@ 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 @@ -216,13 +231,15 @@ 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 @@ -232,6 +249,9 @@ Accept wildcard characters: False ``` ### -Source + +> Applicable: Exchange Online, Security & Compliance + The Source parameter filters the report by workload. Valid values are: - EXCH: Exchange Online @@ -245,7 +265,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -255,6 +274,9 @@ 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". @@ -263,7 +285,6 @@ 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/exchange/Get-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md index cf21bb85d5..7f2af1ae8c 100644 --- a/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpkeyworddictionary +schema: 2.0.0 +title: Get-DlpKeywordDictionary --- # Get-DlpKeywordDictionary @@ -47,13 +48,15 @@ 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/exchange/Get-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DlpPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md index ef75ad1628..5ef738f7b8 100644 --- a/exchange/exchange-ps/exchange/Get-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlppolicy +schema: 2.0.0 +title: Get-DlpPolicy --- # Get-DlpPolicy @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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/exchange/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md index bafb90d765..9d8ad175ee 100644 --- a/exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlppolicytemplate +schema: 2.0.0 +title: Get-DlpPolicyTemplate --- # Get-DlpPolicyTemplate @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md index 99d0a14db7..ad7334abc6 100644 --- a/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtype +schema: 2.0.0 +title: Get-DlpSensitiveInformationType --- # Get-DlpSensitiveInformationType @@ -53,6 +54,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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 @@ -120,13 +129,15 @@ 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/exchange/Get-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md index 322925e01f..8aebbfb9ea 100644 --- a/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtyperulepackage +schema: 2.0.0 +title: Get-DlpSensitiveInformationTypeRulePackage --- # Get-DlpSensitiveInformationTypeRulePackage @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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/exchange/Get-DlpSiDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md index b89d2416f2..ee462abac4 100644 --- a/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsidetectionsreport +schema: 2.0.0 +title: Get-DlpSiDetectionsReport --- # Get-DlpSiDetectionsReport @@ -59,6 +60,9 @@ 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". @@ -67,7 +71,6 @@ 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 @@ -77,6 +80,9 @@ 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"`. @@ -85,7 +91,6 @@ 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/exchange/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md index 05ddacb11c..da5051303d 100644 --- a/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dnssecstatusforverifieddomain +schema: 2.0.0 +title: Get-DnssecStatusForVerifiedDomain --- # Get-DnssecStatusForVerifiedDomain @@ -97,13 +98,15 @@ 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 @@ -113,13 +116,15 @@ 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 @@ -129,13 +134,15 @@ 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 @@ -145,13 +152,15 @@ 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 @@ -161,13 +170,15 @@ 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 @@ -177,13 +188,15 @@ 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/exchange/Get-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-DomainController.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md index b36194819e..6797a610bf 100644 --- a/exchange/exchange-ps/exchange/Get-DomainController.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-domaincontroller +schema: 2.0.0 +title: Get-DomainController --- # Get-DomainController @@ -59,13 +60,15 @@ 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 @@ -75,6 +78,9 @@ 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). @@ -85,7 +91,6 @@ 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 @@ -95,13 +100,15 @@ 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 @@ -111,13 +118,15 @@ 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/exchange/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md index 4dfc211e99..a7a57a9d05 100644 --- a/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dynamicdistributiongroup +schema: 2.0.0 +title: Get-DynamicDistributionGroup --- # Get-DynamicDistributionGroup @@ -126,6 +127,9 @@ 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 @@ -139,7 +143,6 @@ 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 @@ -149,6 +152,9 @@ 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) @@ -161,7 +167,6 @@ 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 @@ -171,6 +176,9 @@ 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). @@ -179,7 +187,6 @@ 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 @@ -189,6 +196,9 @@ 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. @@ -197,7 +207,6 @@ 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 @@ -207,6 +216,9 @@ 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. @@ -222,7 +234,6 @@ 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 @@ -232,6 +243,9 @@ 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,7 +259,6 @@ 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 @@ -255,6 +268,9 @@ 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. @@ -265,7 +281,6 @@ 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 @@ -275,6 +290,9 @@ 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. @@ -285,7 +303,6 @@ 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 @@ -295,6 +312,9 @@ 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. @@ -305,7 +325,6 @@ 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 @@ -315,6 +334,9 @@ 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. @@ -325,7 +347,6 @@ 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 @@ -335,6 +356,9 @@ 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. @@ -345,7 +369,6 @@ 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 @@ -355,6 +378,9 @@ 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. @@ -365,7 +391,6 @@ 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 @@ -375,6 +400,9 @@ 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. @@ -385,7 +413,6 @@ 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 @@ -395,6 +422,9 @@ 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. @@ -403,7 +433,6 @@ 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 @@ -413,6 +442,9 @@ 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 @@ -426,7 +458,6 @@ 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 @@ -436,6 +467,9 @@ 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,7 +481,6 @@ 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 @@ -457,6 +490,9 @@ 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. @@ -469,7 +505,6 @@ 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 @@ -479,13 +514,15 @@ 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 @@ -495,6 +532,9 @@ 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. @@ -509,7 +549,6 @@ 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/exchange/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md index d93483e17c..062faad168 100644 --- a/exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-dynamicdistributiongroupmember +schema: 2.0.0 +title: Get-DynamicDistributionGroupMember --- # Get-DynamicDistributionGroupMember @@ -45,6 +46,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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). @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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. @@ -94,7 +102,6 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Get-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md index b10e5bcf46..25d4394c2a 100644 --- a/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-eopprotectionpolicyrule +schema: 2.0.0 +title: Get-EOPProtectionPolicyRule --- # Get-EOPProtectionPolicyRule @@ -50,6 +51,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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 @@ -82,7 +88,6 @@ 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/exchange/Get-EXOCasMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOCasMailbox.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EXOCasMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOCasMailbox.md index 72e7aca6f2..576d17dd9a 100644 --- a/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exocasmailbox +schema: 2.0.0 +title: Get-EXOCasMailbox --- # Get-EXOCasMailbox @@ -83,6 +83,9 @@ 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) @@ -104,7 +107,6 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -114,6 +116,9 @@ 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) @@ -128,7 +133,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima Type: String Parameter Sets: Anr Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -138,13 +142,15 @@ 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 @@ -154,6 +160,9 @@ 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. @@ -162,7 +171,6 @@ 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 @@ -172,6 +180,9 @@ 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. @@ -187,7 +198,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -197,13 +207,15 @@ 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 @@ -213,13 +225,15 @@ 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 @@ -229,13 +243,15 @@ 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 @@ -245,6 +261,9 @@ 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 @@ -256,7 +275,6 @@ 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 @@ -266,6 +284,9 @@ 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. @@ -274,7 +295,6 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity, Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -284,6 +304,9 @@ 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). @@ -292,7 +315,6 @@ For more information about the available properties, see [Get-EXOCasMailbox prop Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -302,6 +324,9 @@ 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) @@ -321,7 +346,6 @@ 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 @@ -331,6 +355,9 @@ 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 @@ -348,7 +375,6 @@ 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 @@ -358,13 +384,15 @@ 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 @@ -374,13 +402,15 @@ 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 @@ -390,13 +420,15 @@ 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 @@ -406,6 +438,9 @@ 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. @@ -414,7 +449,6 @@ 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/exchange/Get-EXOMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailbox.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EXOMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMailbox.md index 29b21ed26e..683b314e60 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailbox +schema: 2.0.0 +title: Get-EXOMailbox --- # Get-EXOMailbox @@ -105,6 +105,9 @@ 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) @@ -126,7 +129,6 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -136,6 +138,9 @@ 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) @@ -150,7 +155,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima Type: String Parameter Sets: Anr Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -160,13 +164,15 @@ 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 @@ -176,13 +182,15 @@ 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 @@ -192,6 +200,9 @@ 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. @@ -200,7 +211,6 @@ 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 @@ -210,6 +220,9 @@ 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. @@ -225,7 +238,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -235,13 +247,15 @@ 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 @@ -251,6 +265,9 @@ 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. @@ -261,7 +278,6 @@ 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 @@ -271,6 +287,9 @@ 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. @@ -281,7 +300,6 @@ 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 @@ -291,6 +309,9 @@ 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 @@ -305,7 +326,6 @@ 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 @@ -315,13 +335,15 @@ 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 @@ -331,6 +353,9 @@ 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 @@ -342,7 +367,6 @@ 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 @@ -352,6 +376,9 @@ 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. @@ -360,7 +387,6 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity, Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -370,6 +396,9 @@ 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). @@ -378,7 +407,6 @@ For more information about the available properties, see [Get-EXOMailbox propert Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -388,6 +416,9 @@ 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 @@ -417,7 +448,6 @@ 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 @@ -427,13 +457,15 @@ 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 @@ -443,6 +475,9 @@ Accept wildcard characters: False ``` ### -RecipientTypeDetails + +> Applicable: Exchange Online + The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are: - DiscoveryMailbox @@ -462,7 +497,6 @@ You can specify multiple values separated by commas. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -472,13 +506,15 @@ 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 @@ -488,6 +524,9 @@ 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. @@ -496,7 +535,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -506,6 +544,9 @@ 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. @@ -514,7 +555,6 @@ 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/exchange/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md index d15ff5ab3c..b5499a0771 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission +schema: 2.0.0 +title: Get-EXOMailboxFolderPermission --- # Get-EXOMailboxFolderPermission @@ -53,6 +53,9 @@ 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: @@ -70,7 +73,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -80,6 +82,9 @@ 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. @@ -88,7 +93,6 @@ 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 @@ -98,13 +102,15 @@ 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 @@ -114,6 +120,9 @@ 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. @@ -122,7 +131,6 @@ 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 @@ -132,6 +140,9 @@ 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 @@ -147,7 +158,6 @@ 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 @@ -157,6 +167,9 @@ 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. @@ -165,7 +178,6 @@ 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/exchange/Get-EXOMailboxFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderStatistics.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderStatistics.md index b6d21cf8d8..e25dcbd38e 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderstatistics +schema: 2.0.0 +title: Get-EXOMailboxFolderStatistics --- # Get-EXOMailboxFolderStatistics @@ -67,6 +67,9 @@ 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. @@ -75,7 +78,6 @@ 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 @@ -85,13 +87,15 @@ 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 @@ -101,6 +105,9 @@ 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. @@ -109,7 +116,6 @@ 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 @@ -119,6 +125,9 @@ Accept wildcard characters: False ``` ### -Folderscope + +> Applicable: Exchange Online + The FolderScope parameter specifies the scope of the search by folder type. Valid values include: - All @@ -148,7 +157,6 @@ 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 @@ -158,6 +166,9 @@ 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: @@ -174,7 +185,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -184,13 +194,15 @@ 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 @@ -200,13 +212,15 @@ 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 @@ -216,6 +230,9 @@ 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. @@ -224,7 +241,6 @@ 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 @@ -234,6 +250,9 @@ 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. @@ -242,7 +261,6 @@ 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 @@ -252,6 +270,9 @@ 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. @@ -260,7 +281,6 @@ 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/exchange/Get-EXOMailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md index d008aa8f24..1bce64b15f 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxpermission +schema: 2.0.0 +title: Get-EXOMailboxPermission --- # Get-EXOMailboxPermission @@ -72,6 +72,9 @@ 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. @@ -80,7 +83,6 @@ 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 @@ -90,6 +92,9 @@ 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: @@ -106,7 +111,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -116,13 +120,15 @@ 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 @@ -132,6 +138,9 @@ 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. @@ -140,7 +149,6 @@ 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 @@ -150,13 +158,15 @@ 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 @@ -166,6 +176,9 @@ 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. @@ -174,7 +187,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -184,6 +196,9 @@ 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: @@ -199,7 +214,6 @@ 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 @@ -209,6 +223,9 @@ 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. @@ -217,7 +234,6 @@ 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/exchange/Get-EXOMailboxStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxStatistics.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxStatistics.md index cbe03cc816..43c5cfeacc 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxstatistics +schema: 2.0.0 +title: Get-EXOMailboxStatistics --- # Get-EXOMailboxStatistics @@ -61,13 +61,15 @@ 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 @@ -77,13 +79,15 @@ 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 @@ -93,13 +97,15 @@ 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 @@ -109,6 +115,9 @@ 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: @@ -127,7 +136,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -137,13 +145,15 @@ 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 @@ -153,13 +163,15 @@ 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 @@ -169,6 +181,9 @@ 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. @@ -177,7 +192,6 @@ Soft-deleted recipients are deleted recipients that are still recoverable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -187,6 +201,9 @@ 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. @@ -195,7 +212,6 @@ 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 @@ -205,6 +221,9 @@ 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). @@ -213,7 +232,6 @@ For more information about the available properties, see [Get-EXOMailboxStatisti Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -223,6 +241,9 @@ 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) @@ -236,7 +257,6 @@ 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 @@ -246,6 +266,9 @@ 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. @@ -254,7 +277,6 @@ 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/exchange/Get-EXOMobileDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMobileDeviceStatistics.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXOMobileDeviceStatistics.md index 91b5ebab64..6bbd3574f8 100644 --- a/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exomobiledevicestatistics +schema: 2.0.0 +title: Get-EXOMobileDeviceStatistics --- # Get-EXOMobileDeviceStatistics @@ -72,6 +72,9 @@ 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 @@ -83,7 +86,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, Mailbox, Primar Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -93,6 +95,9 @@ 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 @@ -104,7 +109,6 @@ 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 @@ -114,13 +118,15 @@ 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 @@ -130,6 +136,9 @@ 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. @@ -138,7 +147,6 @@ 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 @@ -148,13 +156,15 @@ 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 @@ -164,13 +174,15 @@ 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 @@ -180,13 +192,15 @@ 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 @@ -196,6 +210,9 @@ 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. @@ -204,7 +221,6 @@ 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 @@ -214,13 +230,15 @@ 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 @@ -230,13 +248,15 @@ 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 @@ -246,13 +266,15 @@ 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 @@ -262,6 +284,9 @@ 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. @@ -270,7 +295,6 @@ 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/exchange/Get-EXORecipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-EXORecipient.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md index fd34b10f9d..1c217a1839 100644 --- a/exchange/exchange-ps/exchange/Get-EXORecipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exorecipient +schema: 2.0.0 +title: Get-EXORecipient --- # Get-EXORecipient @@ -76,6 +76,9 @@ 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) @@ -97,7 +100,6 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -107,6 +109,9 @@ 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) @@ -121,7 +126,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima Type: String Parameter Sets: Anr Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -131,6 +135,9 @@ 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. @@ -139,7 +146,6 @@ 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 @@ -149,6 +155,9 @@ 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. @@ -164,7 +173,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -174,6 +182,9 @@ 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. @@ -182,7 +193,6 @@ Soft-deleted recipients are deleted recipients that are still recoverable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -192,6 +202,9 @@ 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 @@ -203,7 +216,6 @@ 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 @@ -213,6 +225,9 @@ 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. @@ -221,7 +236,6 @@ 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 @@ -231,6 +245,9 @@ 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). @@ -239,7 +256,6 @@ For more information about the available properties, see [Get-EXORecipient prope Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -249,6 +265,9 @@ 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) @@ -263,7 +282,6 @@ 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 @@ -273,13 +291,15 @@ 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 @@ -289,6 +309,9 @@ Accept wildcard characters: False ``` ### -RecipientType + +> Applicable: Exchange Online + The RecipientType parameter filters the results by the specified recipient type. Valid values are: - DynamicDistributionGroup @@ -306,7 +329,6 @@ You can specify multiple values separated by commas. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -316,6 +338,9 @@ Accept wildcard characters: False ``` ### -RecipientTypeDetails + +> Applicable: Exchange Online + The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are: - DiscoveryMailbox @@ -355,7 +380,6 @@ 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 @@ -365,13 +389,15 @@ 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 @@ -381,6 +407,9 @@ 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. @@ -389,7 +418,6 @@ 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/exchange/Get-EXORecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-EXORecipientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md index 3ec37b7a9d..6aaa5a1267 100644 --- a/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exorecipientpermission +schema: 2.0.0 +title: Get-EXORecipientPermission --- # Get-EXORecipientPermission @@ -56,6 +56,9 @@ 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 @@ -85,7 +88,6 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -95,13 +97,15 @@ 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 @@ -111,6 +115,9 @@ 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. @@ -119,7 +126,6 @@ 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 @@ -129,6 +135,9 @@ 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. @@ -137,7 +146,6 @@ 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 @@ -147,13 +155,15 @@ 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 @@ -163,6 +173,9 @@ 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 @@ -185,7 +198,6 @@ You need to use this parameter with the Identity, PrimarySmtpAddress, UserPrinci Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -195,6 +207,9 @@ 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. @@ -203,7 +218,6 @@ 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/exchange/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md index 1235c14ba1..32414e1610 100644 --- a/exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ecpvirtualdirectory +schema: 2.0.0 +title: Get-EcpVirtualDirectory --- # Get-EcpVirtualDirectory @@ -69,6 +70,9 @@ 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 @@ -83,7 +87,6 @@ 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 @@ -93,6 +96,9 @@ 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 @@ -106,7 +112,6 @@ 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 @@ -116,6 +121,9 @@ 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. @@ -124,7 +132,6 @@ 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 @@ -134,13 +141,15 @@ 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,6 +159,9 @@ 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. @@ -160,7 +172,6 @@ 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/exchange/Get-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-EdgeSubscription.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md index 4e288d9293..6da98aaa66 100644 --- a/exchange/exchange-ps/exchange/Get-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-edgesubscription +schema: 2.0.0 +title: Get-EdgeSubscription --- # Get-EdgeSubscription @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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. @@ -74,7 +80,6 @@ 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/exchange/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md index fa33987f4c..46e9d51488 100644 --- a/exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-edgesyncserviceconfig +schema: 2.0.0 +title: Get-EdgeSyncServiceConfig --- # Get-EdgeSyncServiceConfig @@ -42,13 +43,15 @@ 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 @@ -58,13 +61,15 @@ 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 @@ -74,13 +79,15 @@ 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/exchange/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md index fe9c386e7f..98bc73afd1 100644 --- a/exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-eligibledistributiongroupformigration +schema: 2.0.0 +title: Get-EligibleDistributionGroupForMigration --- # Get-EligibleDistributionGroupForMigration @@ -51,6 +52,9 @@ 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. @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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 @@ -84,7 +90,6 @@ 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 @@ -94,6 +99,9 @@ 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 @@ -105,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ 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/exchange/Get-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md index 1cb8b5a7a3..64591b8f89 100644 --- a/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-emailaddresspolicy +schema: 2.0.0 +title: Get-EmailAddressPolicy --- # Get-EmailAddressPolicy @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,6 +92,9 @@ 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. @@ -99,7 +107,6 @@ 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/exchange/Get-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-EmailTenantSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md index 025fdca73a..e09806855a 100644 --- a/exchange/exchange-ps/exchange/Get-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-emailtenantsettings +schema: 2.0.0 +title: Get-EmailTenantSettings --- # Get-EmailTenantSettings @@ -39,13 +40,15 @@ 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/exchange/Get-EtrLimits.md b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-EtrLimits.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md index 759a8d045c..e6cd41a79e 100644 --- a/exchange/exchange-ps/exchange/Get-EtrLimits.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-etrlimits +schema: 2.0.0 +title: Get-EtrLimits --- # Get-EtrLimits diff --git a/exchange/exchange-ps/exchange/Get-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-EventLogLevel.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md index cc925f4f3d..9479411847 100644 --- a/exchange/exchange-ps/exchange/Get-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-eventloglevel +schema: 2.0.0 +title: Get-EventLogLevel --- # Get-EventLogLevel @@ -49,6 +50,9 @@ 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. @@ -57,7 +61,6 @@ 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 @@ -67,6 +70,9 @@ 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 @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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/exchange/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md index 30df67b8a5..42182577a2 100644 --- a/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-eventsfromemailconfiguration +schema: 2.0.0 +title: Get-EventsFromEmailConfiguration --- # Get-EventsFromEmailConfiguration @@ -42,13 +43,15 @@ 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/exchange/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md index d2853de47a..576eb90674 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeassistanceconfig +schema: 2.0.0 +title: Get-ExchangeAssistanceConfig --- # Get-ExchangeAssistanceConfig @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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. @@ -72,7 +78,6 @@ 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/exchange/Get-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md index eec9e123ff..59679b843e 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangecertificate +schema: 2.0.0 +title: Get-ExchangeCertificate --- # Get-ExchangeCertificate @@ -126,6 +127,9 @@ 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. @@ -134,7 +138,6 @@ 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 @@ -144,6 +147,9 @@ 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` @@ -157,7 +163,6 @@ 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 @@ -167,6 +172,9 @@ 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. @@ -175,7 +183,6 @@ 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 @@ -185,13 +192,15 @@ 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 @@ -201,13 +210,15 @@ 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 @@ -217,6 +228,9 @@ 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 @@ -232,7 +246,6 @@ 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/exchange/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md index ca36c14478..24ead9955e 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangediagnosticinfo +schema: 2.0.0 +title: Get-ExchangeDiagnosticInfo --- # Get-ExchangeDiagnosticInfo @@ -53,6 +54,9 @@ 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. @@ -63,7 +67,6 @@ 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 @@ -73,6 +76,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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. @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ 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,7 +132,6 @@ 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 @@ -132,13 +141,15 @@ 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/exchange/Get-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ExchangeFeature.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md index 6bf6bb29bf..3b7339badc 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md @@ -1,12 +1,14 @@ --- -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/exchange/get-exchangefeature +schema: 2.0.0 +title: Get-ExchangeFeature --- # Get-ExchangeFeature @@ -50,6 +52,9 @@ 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 @@ -63,7 +68,6 @@ 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 @@ -73,13 +77,15 @@ 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 @@ -89,13 +95,15 @@ 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 @@ -105,13 +113,15 @@ 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/exchange/Get-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ExchangeServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md index 4331ccbb63..fef174995b 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserver +schema: 2.0.0 +title: Get-ExchangeServer --- # Get-ExchangeServer @@ -62,6 +63,9 @@ 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 @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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. @@ -93,7 +99,6 @@ 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 @@ -103,6 +108,9 @@ 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. @@ -111,7 +119,6 @@ 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 @@ -121,6 +128,9 @@ 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. @@ -129,7 +139,6 @@ 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/exchange/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md index 4d95f68bfd..e168b1b1ea 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserveraccesslicense +schema: 2.0.0 +title: Get-ExchangeServerAccessLicense --- # Get-ExchangeServerAccessLicense diff --git a/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md index 4c62c163e4..12c6bf5538 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserveraccesslicenseuser +schema: 2.0.0 +title: Get-ExchangeServerAccessLicenseUser --- # Get-ExchangeServerAccessLicenseUser @@ -42,6 +43,9 @@ 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` @@ -55,7 +59,6 @@ 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/exchange/Get-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-ExchangeSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md index 9088353301..214308b369 100644 --- a/exchange/exchange-ps/exchange/Get-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangesettings +schema: 2.0.0 +title: Get-ExchangeSettings --- # Get-ExchangeSettings @@ -60,6 +61,9 @@ 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 @@ -70,7 +74,6 @@ 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 @@ -80,6 +83,9 @@ 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. @@ -88,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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 @@ -109,7 +117,6 @@ 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 @@ -119,6 +126,9 @@ 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. @@ -129,7 +139,6 @@ 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 @@ -139,13 +148,15 @@ 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 @@ -155,13 +166,15 @@ 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 @@ -171,6 +184,9 @@ 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. @@ -179,7 +195,6 @@ 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 @@ -189,13 +204,15 @@ 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 @@ -205,13 +222,15 @@ 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 @@ -221,13 +240,15 @@ 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 @@ -237,13 +258,15 @@ 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 @@ -253,13 +276,15 @@ 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 @@ -269,6 +294,9 @@ 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 @@ -280,7 +308,6 @@ 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 @@ -290,13 +317,15 @@ 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/exchange/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md index 08f6210738..7cee6c9b41 100644 --- a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarrierpolicy +schema: 2.0.0 +title: Get-ExoInformationBarrierPolicy --- # Get-ExoInformationBarrierPolicy @@ -46,6 +47,9 @@ 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 @@ -57,7 +61,6 @@ The Identity parameter specifies the Exchange Online information barrier policy Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -67,6 +70,9 @@ 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: @@ -78,7 +84,6 @@ 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/exchange/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md index 8e1ddb9d25..a8b3978043 100644 --- a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarrierrelationship +schema: 2.0.0 +title: Get-ExoInformationBarrierRelationship --- # Get-ExoInformationBarrierRelationship @@ -40,6 +41,9 @@ 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 @@ -53,7 +57,6 @@ The RecipientId1 parameter specifies the first recipient in the Exchange Online Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -63,6 +66,9 @@ 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 @@ -76,7 +82,6 @@ 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/exchange/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md index b0caf1efcb..f335c81c4e 100644 --- a/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarriersegment +schema: 2.0.0 +title: Get-ExoInformationBarrierSegment --- # Get-ExoInformationBarrierSegment @@ -46,6 +47,9 @@ 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 @@ -57,7 +61,6 @@ The Identity parameter specifies the Exchange Online information barrier segment Type: InformationBarrierSegmentIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -67,6 +70,9 @@ 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. @@ -75,7 +81,6 @@ 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/exchange/Get-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md index f909f50138..a49fb0a664 100644 --- a/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exophishsimoverriderule +schema: 2.0.0 +title: Get-ExoPhishSimOverrideRule --- # Get-ExoPhishSimOverrideRule @@ -53,6 +54,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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 @@ -119,7 +129,6 @@ The Policy parameter filters the results by phishing simulator override policy. Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -129,13 +138,15 @@ 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/exchange/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md index 8fd400e919..730a3f8044 100644 --- a/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exosecopsoverriderule +schema: 2.0.0 +title: Get-ExoSecOpsOverrideRule --- # Get-ExoSecOpsOverrideRule @@ -53,6 +54,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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 @@ -119,7 +129,6 @@ 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 @@ -129,13 +138,15 @@ 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/exchange/Get-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ExternalInOutlook.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md index 451de0b213..5c279f8f9f 100644 --- a/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-externalinoutlook +schema: 2.0.0 +title: Get-ExternalInOutlook --- # Get-ExternalInOutlook @@ -44,13 +45,15 @@ 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/exchange/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md index 14df25198f..3e1df3bfb9 100644 --- a/exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-failedcontentindexdocuments +schema: 2.0.0 +title: Get-FailedContentIndexDocuments --- # Get-FailedContentIndexDocuments @@ -91,6 +92,9 @@ 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 @@ -108,7 +112,6 @@ 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 @@ -118,6 +121,9 @@ 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 @@ -128,7 +134,6 @@ 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 @@ -138,6 +143,9 @@ 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 @@ -148,7 +156,6 @@ 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 @@ -158,6 +165,9 @@ 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`. @@ -167,7 +177,6 @@ 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 @@ -177,13 +186,15 @@ 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,6 +204,9 @@ 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. @@ -201,7 +215,6 @@ 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 @@ -211,6 +224,9 @@ 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". @@ -219,7 +235,6 @@ 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 @@ -229,13 +244,15 @@ 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 @@ -245,6 +262,9 @@ 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. @@ -255,7 +275,6 @@ 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 @@ -265,13 +284,15 @@ 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 @@ -281,6 +302,9 @@ 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". @@ -289,7 +313,6 @@ 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 @@ -299,13 +322,15 @@ 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/exchange/Get-FeatureConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-FeatureConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md index 87063ff596..075d7fe06a 100644 --- a/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md @@ -1,9 +1,11 @@ --- +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/exchange/get-featureconfiguration -applicable: Security & Compliance -title: Get-FeatureConfiguration schema: 2.0.0 +title: Get-FeatureConfiguration --- # Get-FeatureConfiguration @@ -52,6 +54,9 @@ 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 @@ -62,7 +67,6 @@ 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 @@ -72,6 +76,9 @@ 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 @@ -80,7 +87,6 @@ The FeatureScenario parameter specifies the scenario for the feature configurati Type: PolicyScenario Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -90,13 +96,15 @@ 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 @@ -106,13 +114,15 @@ 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/exchange/Get-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-FederatedDomainProof.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md index 498c943b79..3b8fe0dbb5 100644 --- a/exchange/exchange-ps/exchange/Get-FederatedDomainProof.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-federateddomainproof +schema: 2.0.0 +title: Get-FederatedDomainProof --- # Get-FederatedDomainProof @@ -51,13 +52,15 @@ 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 @@ -67,13 +70,15 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md index 141f7f644a..dfa35fee03 100644 --- a/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-federatedorganizationidentifier +schema: 2.0.0 +title: Get-FederatedOrganizationIdentifier --- # Get-FederatedOrganizationIdentifier @@ -51,13 +52,15 @@ 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 @@ -67,6 +70,9 @@ 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. @@ -75,7 +81,6 @@ 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,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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/exchange/Get-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-FederationInformation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md index bcd6a357a3..ec3ea4b4b8 100644 --- a/exchange/exchange-ps/exchange/Get-FederationInformation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-federationinformation +schema: 2.0.0 +title: Get-FederationInformation --- # Get-FederationInformation @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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. @@ -90,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Get-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-FederationTrust.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md index 98175c1a29..3be4cc8f62 100644 --- a/exchange/exchange-ps/exchange/Get-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-federationtrust +schema: 2.0.0 +title: Get-FederationTrust --- # Get-FederationTrust @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-FilePlanPropertyAuthority.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md index 023b70021a..e747148fd0 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md @@ -1,9 +1,11 @@ --- +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/exchange/get-fileplanpropertyauthority -applicable: Security & Compliance -title: Get-FilePlanPropertyAuthority schema: 2.0.0 +title: Get-FilePlanPropertyAuthority --- # Get-FilePlanPropertyAuthority @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FilePlanPropertyCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md index c7b0bab4ef..913b1ab139 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md @@ -1,9 +1,11 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertycategory applicable: Security & Compliance -title: Get-FilePlanPropertyCategory +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +https: //learn.microsoft.com/powershell/module/exchange/get-fileplanpropertycategory +Locale: en-US +Module Name: ExchangePowerShell schema: 2.0.0 +title: Get-FilePlanPropertyCategory --- # Get-FilePlanPropertyCategory @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FilePlanPropertyCitation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md index 9080e6137a..9c3212311d 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertycitation -applicable: Security & Compliance -title: Get-FilePlanPropertyCitation schema: 2.0.0 +title: Get-FilePlanPropertyCitation --- # Get-FilePlanPropertyCitation @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FilePlanPropertyDepartment.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md index 58fc2c7f5e..6495c29add 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md @@ -1,9 +1,11 @@ --- +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/exchange/get-fileplanpropertydepartment -applicable: Security & Compliance -title: Get-FilePlanPropertyDepartment schema: 2.0.0 +title: Get-FilePlanPropertyDepartment --- # Get-FilePlanPropertyDepartment @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md index c1ec2f310a..8154e93f11 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md @@ -1,9 +1,11 @@ --- +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/exchange/get-fileplanpropertyreferenceid -applicable: Security & Compliance -title: Get-FilePlanPropertyReferenceId schema: 2.0.0 +title: Get-FilePlanPropertyReferenceId --- # Get-FilePlanPropertyReferenceId @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FilePlanPropertyStructure.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md index f2e64f89a2..f6e4a6e2da 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md @@ -1,9 +1,11 @@ --- +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/exchange/get-fileplanpropertystructure -applicable: Security & Compliance -title: Get-FilePlanPropertyStructure schema: 2.0.0 +title: Get-FilePlanPropertyStructure --- # Get-FilePlanPropertyStructure @@ -36,13 +38,15 @@ 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/exchange/Get-FilePlanPropertySubCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md index ed2bc3113e..da2d7d08c4 100644 --- a/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/get-fileplanpropertysubcategory -applicable: Security & Compliance -title: Get-FilePlanPropertySubCategory schema: 2.0.0 +title: Get-FilePlanPropertySubCategory --- # Get-FilePlanPropertySubCategory @@ -43,6 +45,9 @@ 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 @@ -53,7 +58,6 @@ 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/exchange/Get-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-FocusedInbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md index c7b5967c67..a48532abcf 100644 --- a/exchange/exchange-ps/exchange/Get-FocusedInbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-focusedinbox +schema: 2.0.0 +title: Get-FocusedInbox --- # Get-FocusedInbox @@ -43,6 +44,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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/exchange/Get-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ForeignConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md index 1d19d0d26f..c6792f2d66 100644 --- a/exchange/exchange-ps/exchange/Get-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-foreignconnector +schema: 2.0.0 +title: Get-ForeignConnector --- # Get-ForeignConnector @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -76,7 +82,6 @@ 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/exchange/Get-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-FrontendTransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md index e768cd1838..c0225e5ac8 100644 --- a/exchange/exchange-ps/exchange/Get-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-frontendtransportservice +schema: 2.0.0 +title: Get-FrontendTransportService --- # Get-FrontendTransportService @@ -50,6 +51,9 @@ 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: @@ -63,7 +67,6 @@ 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 @@ -73,13 +76,15 @@ 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/exchange/Get-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-GlobalAddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md index 0a3a6daa60..b7f93922b4 100644 --- a/exchange/exchange-ps/exchange/Get-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-globaladdresslist +schema: 2.0.0 +title: Get-GlobalAddressList --- # Get-GlobalAddressList @@ -60,6 +61,9 @@ 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 @@ -70,7 +74,6 @@ 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 @@ -80,13 +83,15 @@ 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 @@ -96,6 +101,9 @@ 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,7 +112,6 @@ 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/exchange/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md index 24e4681b00..2d26c614c3 100644 --- a/exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-globalmonitoringoverride +schema: 2.0.0 +title: Get-GlobalMonitoringOverride --- # Get-GlobalMonitoringOverride @@ -47,6 +48,9 @@ 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. @@ -55,7 +59,6 @@ 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/exchange/Get-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-Group.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Group.md index b940181519..b7a7f728c6 100644 --- a/exchange/exchange-ps/exchange/Get-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-group +schema: 2.0.0 +title: Get-Group --- # Get-Group @@ -81,6 +82,9 @@ 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 @@ -92,7 +96,6 @@ 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 @@ -102,6 +105,9 @@ 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) @@ -114,7 +120,6 @@ 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,6 +129,9 @@ 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. @@ -134,7 +142,6 @@ 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 @@ -144,6 +151,9 @@ 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. @@ -154,7 +164,6 @@ 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,6 +173,9 @@ 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. @@ -179,7 +191,6 @@ 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 @@ -189,6 +200,9 @@ 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. @@ -202,7 +216,6 @@ 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 @@ -212,6 +225,9 @@ 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 @@ -223,7 +239,6 @@ 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 @@ -233,6 +248,9 @@ 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. @@ -245,7 +263,6 @@ 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 @@ -255,6 +272,9 @@ 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 @@ -271,7 +291,6 @@ 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 @@ -281,13 +300,15 @@ 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 @@ -297,6 +318,9 @@ 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. @@ -310,7 +334,6 @@ 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/exchange/Get-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-HealthReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md index fb4ff840c9..2186bc5eae 100644 --- a/exchange/exchange-ps/exchange/Get-HealthReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-healthreport +schema: 2.0.0 +title: Get-HealthReport --- # Get-HealthReport @@ -54,6 +55,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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 @@ -91,13 +96,15 @@ 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 @@ -107,13 +114,15 @@ 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 @@ -123,13 +132,15 @@ 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 @@ -139,13 +150,15 @@ 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/exchange/Get-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-HistoricalSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md index 9aa5b5f171..9db9ffa015 100644 --- a/exchange/exchange-ps/exchange/Get-HistoricalSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-historicalsearch +schema: 2.0.0 +title: Get-HistoricalSearch --- # Get-HistoricalSearch @@ -49,13 +50,15 @@ 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/exchange/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md index ec353acb7a..3a3b2242b7 100644 --- a/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-holdcompliancepolicy +schema: 2.0.0 +title: Get-HoldCompliancePolicy --- # Get-HoldCompliancePolicy @@ -57,6 +58,9 @@ 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 @@ -67,7 +71,6 @@ 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 @@ -77,13 +80,15 @@ 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/exchange/Get-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-HoldComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md index 898c6c476a..03b27915ce 100644 --- a/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-holdcompliancerule +schema: 2.0.0 +title: Get-HoldComplianceRule --- # Get-HoldComplianceRule @@ -57,6 +58,9 @@ 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 @@ -67,7 +71,6 @@ 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 @@ -77,6 +80,9 @@ 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 @@ -89,7 +95,6 @@ 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/exchange/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md index 5c3c8cd5f4..a8a424bedf 100644 --- a/exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedconnectionfilterpolicy +schema: 2.0.0 +title: Get-HostedConnectionFilterPolicy --- # Get-HostedConnectionFilterPolicy @@ -47,6 +48,9 @@ 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 @@ -59,7 +63,6 @@ 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/exchange/Get-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md index 855377d33a..c1ea954d10 100644 --- a/exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedcontentfilterpolicy +schema: 2.0.0 +title: Get-HostedContentFilterPolicy --- # Get-HostedContentFilterPolicy @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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/exchange/Get-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md index 0531374eab..903bf3876e 100644 --- a/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedcontentfilterrule +schema: 2.0.0 +title: Get-HostedContentFilterRule --- # Get-HostedContentFilterRule @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -94,7 +102,6 @@ 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/exchange/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md index 1e40b52a4d..b5dad8289e 100644 --- a/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedoutboundspamfilterpolicy +schema: 2.0.0 +title: Get-HostedOutboundSpamFilterPolicy --- # Get-HostedOutboundSpamFilterPolicy @@ -47,6 +48,9 @@ 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 @@ -57,7 +61,6 @@ 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/exchange/Get-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md index 0a620cec54..5f6d06dfd3 100644 --- a/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedoutboundspamfilterrule +schema: 2.0.0 +title: Get-HostedOutboundSpamFilterRule --- # Get-HostedOutboundSpamFilterRule @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -77,7 +83,6 @@ 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/exchange/Get-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-HybridConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md index 426766c54c..e0b2205366 100644 --- a/exchange/exchange-ps/exchange/Get-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hybridconfiguration +schema: 2.0.0 +title: Get-HybridConfiguration --- # Get-HybridConfiguration @@ -40,13 +41,15 @@ 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/exchange/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md rename to exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md index 4f793be1a3..2fb253abfc 100644 --- a/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-hybridmailflowdatacenterips +schema: 2.0.0 +title: Get-HybridMailflowDatacenterIPs --- # Get-HybridMailflowDatacenterIPs diff --git a/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-IPAllowListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md index 0da96065e8..bb72894762 100644 --- a/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistconfig +schema: 2.0.0 +title: Get-IPAllowListConfig --- # Get-IPAllowListConfig @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-IPAllowListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md index 7221b9e90b..64ba528def 100644 --- a/exchange/exchange-ps/exchange/Get-IPAllowListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistentry +schema: 2.0.0 +title: Get-IPAllowListEntry --- # Get-IPAllowListEntry @@ -58,13 +59,15 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ 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 @@ -121,7 +131,6 @@ 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/exchange/Get-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-IPAllowListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md index 1d17905936..b680d53b75 100644 --- a/exchange/exchange-ps/exchange/Get-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistprovider +schema: 2.0.0 +title: Get-IPAllowListProvider --- # Get-IPAllowListProvider @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -76,7 +82,6 @@ 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/exchange/Get-IPAllowListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md index b56f559df4..a547a17c42 100644 --- a/exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistprovidersconfig +schema: 2.0.0 +title: Get-IPAllowListProvidersConfig --- # Get-IPAllowListProvidersConfig @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-IPBlockListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-IPBlockListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md index 517988a7ae..2248425fd0 100644 --- a/exchange/exchange-ps/exchange/Get-IPBlockListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistconfig +schema: 2.0.0 +title: Get-IPBlockListConfig --- # Get-IPBlockListConfig @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-IPBlockListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md index d6a1d41ce8..d7548aba42 100644 --- a/exchange/exchange-ps/exchange/Get-IPBlockListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistentry +schema: 2.0.0 +title: Get-IPBlockListEntry --- # Get-IPBlockListEntry @@ -58,13 +59,15 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ 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 @@ -121,7 +131,6 @@ 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/exchange/Get-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-IPBlockListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md index f8849f592d..e825ab77fe 100644 --- a/exchange/exchange-ps/exchange/Get-IPBlockListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistprovider +schema: 2.0.0 +title: Get-IPBlockListProvider --- # Get-IPBlockListProvider @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -76,7 +82,6 @@ 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/exchange/Get-IPBlockListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md index f7bcc606fa..f5d8c9de39 100644 --- a/exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistprovidersconfig +schema: 2.0.0 +title: Get-IPBlockListProvidersConfig --- # Get-IPBlockListProvidersConfig @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md index e8d7109c9a..b67f5fe7ac 100644 --- a/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ipv6statusforaccepteddomain +schema: 2.0.0 +title: Get-IPv6StatusForAcceptedDomain --- # Get-IPv6StatusForAcceptedDomain @@ -58,13 +58,15 @@ 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 @@ -74,13 +76,15 @@ 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 @@ -90,13 +94,15 @@ 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/exchange/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-IRMConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md index 377c44454f..9b72328df8 100644 --- a/exchange/exchange-ps/exchange/Get-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-irmconfiguration +schema: 2.0.0 +title: Get-IRMConfiguration --- # Get-IRMConfiguration @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ImapSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md index 78a0faa6d4..3090028710 100644 --- a/exchange/exchange-ps/exchange/Get-ImapSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-imapsettings +schema: 2.0.0 +title: Get-ImapSettings --- # Get-ImapSettings @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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 @@ -70,7 +76,6 @@ 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/exchange/Get-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-InboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md index 2447b733ef..3345a0c7d6 100644 --- a/exchange/exchange-ps/exchange/Get-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-inboundconnector +schema: 2.0.0 +title: Get-InboundConnector --- # Get-InboundConnector @@ -50,13 +51,15 @@ 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 @@ -66,13 +69,15 @@ 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/exchange/Get-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md index 5ed6b13784..65d65140b9 100644 --- a/exchange/exchange-ps/exchange/Get-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-inboxrule +schema: 2.0.0 +title: Get-InboxRule --- # Get-InboxRule @@ -59,6 +60,9 @@ 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 @@ -70,7 +74,6 @@ 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 @@ -80,13 +83,15 @@ 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 @@ -96,6 +101,9 @@ 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. @@ -104,7 +112,6 @@ 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 @@ -114,6 +121,9 @@ 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"). @@ -126,7 +136,6 @@ 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 @@ -136,6 +145,9 @@ 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. @@ -144,7 +156,6 @@ 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 @@ -154,13 +165,15 @@ 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 @@ -170,6 +183,9 @@ 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 @@ -187,7 +203,6 @@ 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 @@ -197,6 +212,9 @@ 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. @@ -205,7 +223,6 @@ 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 @@ -215,6 +232,9 @@ Accept wildcard characters: False ``` ### -SkipCount + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipCount Description }} @@ -223,7 +243,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -233,6 +252,9 @@ 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. @@ -243,7 +265,6 @@ 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 @@ -253,6 +274,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -261,7 +285,6 @@ 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/exchange/Get-InformationBarrierPoliciesApplicationStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md rename to exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md index 4ba383b667..1bde95b233 100644 --- a/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierpoliciesapplicationstatus +schema: 2.0.0 +title: Get-InformationBarrierPoliciesApplicationStatus --- # Get-InformationBarrierPoliciesApplicationStatus @@ -57,13 +58,15 @@ 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 @@ -73,6 +76,9 @@ 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. @@ -81,7 +87,6 @@ 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/exchange/Get-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md index 32c2276297..6f7f815ab3 100644 --- a/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierpolicy +schema: 2.0.0 +title: Get-InformationBarrierPolicy --- # Get-InformationBarrierPolicy @@ -57,6 +58,9 @@ 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 @@ -69,7 +73,6 @@ You can't use this parameter with the ExOPolicyId parameter. Type: PolicyIdParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: 0 @@ -79,6 +82,9 @@ 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. @@ -87,7 +93,6 @@ You can't use this parameter with the Identity parameter. Type: Guid Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md rename to exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md index 862519808e..3aa794ee0e 100644 --- a/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierrecipientstatus +schema: 2.0.0 +title: Get-InformationBarrierRecipientStatus --- # Get-InformationBarrierRecipientStatus @@ -56,6 +57,9 @@ 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 @@ -69,7 +73,6 @@ 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 @@ -79,6 +82,9 @@ 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 @@ -96,7 +102,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md index 3178fd949a..53dec8d02f 100644 --- a/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-intraorganizationconfiguration +schema: 2.0.0 +title: Get-IntraOrganizationConfiguration --- # Get-IntraOrganizationConfiguration @@ -44,6 +45,9 @@ 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. @@ -52,7 +56,6 @@ 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/exchange/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md index d07a069726..3baba3824c 100644 --- a/exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-intraorganizationconnector +schema: 2.0.0 +title: Get-IntraOrganizationConnector --- # Get-IntraOrganizationConnector @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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. @@ -78,7 +84,6 @@ 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/exchange/Get-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md index 68b259f8f9..3a6795f62e 100644 --- a/exchange/exchange-ps/exchange/Get-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-journalrule +schema: 2.0.0 +title: Get-JournalRule --- # Get-JournalRule @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-Label.md b/exchange/exchange-ps/ExchangePowerShell/Get-Label.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-Label.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Label.md index b2cf3b4226..1bbc94d94d 100644 --- a/exchange/exchange-ps/exchange/Get-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Label.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-label +schema: 2.0.0 +title: Get-Label --- # Get-Label @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Get-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-LabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md index 7a90fbaa71..d2889a707f 100644 --- a/exchange/exchange-ps/exchange/Get-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-labelpolicy +schema: 2.0.0 +title: Get-LabelPolicy --- # Get-LabelPolicy @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,13 +71,15 @@ 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/exchange/Get-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-LinkedUser.md rename to exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md index 7407a5f12b..03e867984b 100644 --- a/exchange/exchange-ps/exchange/Get-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-linkeduser +schema: 2.0.0 +title: Get-LinkedUser --- # Get-LinkedUser @@ -62,6 +63,9 @@ 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 @@ -73,7 +77,6 @@ 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 @@ -83,6 +86,9 @@ 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) @@ -95,7 +101,6 @@ 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 @@ -105,6 +110,9 @@ 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. @@ -120,7 +128,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -130,13 +137,15 @@ 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 @@ -146,13 +155,15 @@ 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 @@ -162,6 +173,9 @@ 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. @@ -179,7 +193,6 @@ 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/exchange/Get-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-LogonStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md index bfdee00794..52ad83798a 100644 --- a/exchange/exchange-ps/exchange/Get-LogonStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-logonstatistics +schema: 2.0.0 +title: Get-LogonStatistics --- # Get-LogonStatistics @@ -60,6 +61,9 @@ 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 @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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 @@ -102,7 +108,6 @@ 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 @@ -112,6 +117,9 @@ 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) @@ -125,7 +133,6 @@ 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 @@ -135,13 +142,15 @@ 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/exchange/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md index c7992e4955..5abdd8ff81 100644 --- a/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-m365dataatrestencryptionpolicy +schema: 2.0.0 +title: Get-M365DataAtRestEncryptionPolicy --- # Get-M365DataAtRestEncryptionPolicy @@ -54,6 +55,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,13 +116,15 @@ 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/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md index 486e093215..8d61b9ce56 100644 --- a/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-m365dataatrestencryptionpolicyassignment +schema: 2.0.0 +title: Get-M365DataAtRestEncryptionPolicyAssignment --- # Get-M365DataAtRestEncryptionPolicyAssignment @@ -45,6 +46,8 @@ 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/exchange/Get-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md index aa00b27a06..94103bb2f5 100644 --- a/exchange/exchange-ps/exchange/Get-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailcontact +schema: 2.0.0 +title: Get-MailContact --- # Get-MailContact @@ -74,6 +75,9 @@ 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 @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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) @@ -109,7 +115,6 @@ 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 @@ -119,6 +124,9 @@ 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. @@ -129,7 +137,6 @@ 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 @@ -139,6 +146,9 @@ 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,7 +157,6 @@ 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 @@ -157,6 +166,9 @@ 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. @@ -172,7 +184,6 @@ 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 @@ -182,6 +193,9 @@ 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. @@ -195,7 +209,6 @@ 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 @@ -205,6 +218,9 @@ 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 @@ -216,7 +232,6 @@ 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 @@ -226,6 +241,9 @@ 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. @@ -238,7 +256,6 @@ 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 @@ -248,6 +265,9 @@ 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 @@ -259,7 +279,6 @@ 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 @@ -269,13 +288,15 @@ 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 @@ -285,6 +306,9 @@ 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. @@ -299,7 +323,6 @@ 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/exchange/Get-MailDetailATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailDetailATPReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md index 2894c21ea7..db8e4c6086 100644 --- a/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailatpreport +schema: 2.0.0 +title: Get-MailDetailATPReport --- # Get-MailDetailATPReport @@ -78,13 +79,15 @@ 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 @@ -94,6 +97,9 @@ 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 @@ -106,7 +112,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -116,13 +121,15 @@ 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 @@ -132,6 +139,9 @@ 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". @@ -140,7 +150,6 @@ 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 @@ -150,6 +159,9 @@ 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 @@ -181,7 +193,6 @@ 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 @@ -191,6 +202,9 @@ Accept wildcard characters: False ``` ### -MalwareName + +> Applicable: Exchange Online, Exchange Online Protection + The MalwareName parameter filters the results by malware payload. Valid values are: - Excel @@ -207,7 +221,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -217,13 +230,15 @@ 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 @@ -233,6 +248,9 @@ 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. @@ -249,7 +267,6 @@ 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 @@ -259,13 +276,15 @@ 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 @@ -275,13 +294,15 @@ 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 @@ -291,13 +312,15 @@ 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 @@ -307,13 +330,15 @@ 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 @@ -323,13 +348,15 @@ 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 @@ -339,6 +366,9 @@ 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". @@ -347,7 +377,6 @@ 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/exchange/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md index 213354eae3..bd86eca096 100644 --- a/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetaildlppolicyreport +schema: 2.0.0 +title: Get-MailDetailDlpPolicyReport --- # Get-MailDetailDlpPolicyReport @@ -54,6 +55,9 @@ 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. @@ -62,7 +66,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -72,6 +75,9 @@ Accept wildcard characters: False ``` ### -Direction + +> Applicable: Exchange Online + The Direction parameter filters the results by incoming or outgoing messages. Valid values are: - Inbound @@ -83,7 +89,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -93,13 +98,15 @@ 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 @@ -109,13 +116,15 @@ 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 @@ -125,6 +134,9 @@ 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". @@ -133,7 +145,6 @@ 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 @@ -143,6 +154,9 @@ Accept wildcard characters: False ``` ### -EventType + +> Applicable: Exchange Online + The EventType parameter filters the report by the event type. Valid values are: - DLPActionHits @@ -159,7 +173,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -169,13 +182,15 @@ 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 @@ -185,6 +200,9 @@ 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. @@ -201,7 +219,6 @@ 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 @@ -211,13 +228,15 @@ 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 @@ -227,13 +246,15 @@ 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 @@ -243,13 +264,15 @@ 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 @@ -259,13 +282,15 @@ 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 @@ -275,13 +300,15 @@ 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 @@ -291,6 +318,9 @@ 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". @@ -299,7 +329,6 @@ 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 @@ -309,13 +338,15 @@ 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/exchange/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md index 62ff5f0f00..938086752d 100644 --- a/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailencryptionreport +schema: 2.0.0 +title: Get-MailDetailEncryptionReport --- # Get-MailDetailEncryptionReport @@ -67,13 +68,15 @@ 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 @@ -83,13 +86,15 @@ 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,6 +104,9 @@ 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 @@ -110,7 +118,6 @@ 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 @@ -120,13 +127,15 @@ 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 @@ -136,6 +145,9 @@ 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". @@ -144,7 +156,6 @@ 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 @@ -154,6 +165,9 @@ 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 @@ -167,7 +181,6 @@ 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 @@ -177,6 +190,9 @@ 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. @@ -185,7 +201,6 @@ 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 @@ -195,6 +210,9 @@ 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. @@ -211,7 +229,6 @@ 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 @@ -221,13 +238,15 @@ 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 @@ -237,13 +256,15 @@ 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 @@ -253,13 +274,15 @@ 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 @@ -269,6 +292,9 @@ 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". @@ -277,7 +303,6 @@ 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/exchange/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md index ca463e1112..ee22637110 100644 --- a/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailtransportrulereport +schema: 2.0.0 +title: Get-MailDetailTransportRuleReport --- # Get-MailDetailTransportRuleReport @@ -53,6 +54,9 @@ 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. @@ -61,7 +65,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -71,6 +74,9 @@ 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 @@ -82,7 +88,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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". @@ -116,7 +126,6 @@ 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,6 +135,9 @@ 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 @@ -141,7 +153,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -151,13 +162,15 @@ 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 @@ -167,6 +180,9 @@ 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. @@ -183,7 +199,6 @@ 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 @@ -193,13 +208,15 @@ 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 @@ -209,13 +226,15 @@ 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 @@ -225,13 +244,15 @@ 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 @@ -241,13 +262,15 @@ 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 @@ -257,13 +280,15 @@ 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 @@ -273,6 +298,9 @@ 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". @@ -283,7 +311,6 @@ 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 @@ -293,13 +320,15 @@ 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/exchange/Get-MailFilterListReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailFilterListReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md index 4fe3fbe363..7ad09152f9 100644 --- a/exchange/exchange-ps/exchange/Get-MailFilterListReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailfilterlistreport +schema: 2.0.0 +title: Get-MailFilterListReport --- # Get-MailFilterListReport @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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. @@ -68,7 +74,6 @@ This parameter is reserved for internal Microsoft use. Type: Expression Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -78,13 +83,15 @@ 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 @@ -94,6 +101,9 @@ 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 @@ -108,7 +118,6 @@ 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/exchange/Get-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md index eea8f2f7e7..ae5885855e 100644 --- a/exchange/exchange-ps/exchange/Get-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailpublicfolder +schema: 2.0.0 +title: Get-MailPublicFolder --- # Get-MailPublicFolder @@ -77,6 +78,9 @@ 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. @@ -85,7 +89,6 @@ 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 @@ -95,6 +98,9 @@ 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) @@ -107,7 +113,6 @@ 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 @@ -117,6 +122,9 @@ 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). @@ -125,7 +133,6 @@ 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 @@ -135,6 +142,9 @@ 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. @@ -143,7 +153,6 @@ 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 @@ -153,6 +162,9 @@ 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. @@ -168,7 +180,6 @@ 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 @@ -178,6 +189,9 @@ 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: @@ -189,7 +203,6 @@ 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 @@ -199,6 +212,9 @@ Accept wildcard characters: False ``` ### -IncludeGrantSendOnBehalfToWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }} @@ -207,7 +223,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -217,6 +232,9 @@ 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. @@ -229,7 +247,6 @@ 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 @@ -239,13 +256,15 @@ 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 @@ -255,6 +274,9 @@ 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: @@ -268,7 +290,6 @@ 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 @@ -278,6 +299,9 @@ 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. @@ -293,7 +317,6 @@ 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/exchange/Get-MailTrafficATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md index f846e08198..4353db420e 100644 --- a/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficatpreport +schema: 2.0.0 +title: Get-MailTrafficATPReport --- # Get-MailTrafficATPReport @@ -73,6 +74,9 @@ 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. @@ -81,7 +85,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -91,13 +94,15 @@ 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 @@ -107,6 +112,9 @@ 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 @@ -119,7 +127,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -129,13 +136,15 @@ 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 @@ -145,6 +154,9 @@ 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: @@ -158,7 +170,6 @@ 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 @@ -168,6 +179,9 @@ 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 @@ -199,7 +213,6 @@ 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 @@ -209,13 +222,15 @@ 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 @@ -225,13 +240,15 @@ 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 @@ -241,13 +258,15 @@ 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 @@ -257,13 +276,15 @@ 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 @@ -273,13 +294,15 @@ 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 @@ -289,6 +312,9 @@ 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: @@ -302,7 +328,6 @@ 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 @@ -312,6 +337,9 @@ 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: @@ -327,7 +355,6 @@ 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 @@ -337,13 +364,15 @@ 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/exchange/Get-MailTrafficEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md index 8fe274f754..97a28b41b6 100644 --- a/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficencryptionreport +schema: 2.0.0 +title: Get-MailTrafficEncryptionReport --- # Get-MailTrafficEncryptionReport @@ -60,6 +61,9 @@ 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. @@ -68,7 +72,6 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,6 +99,9 @@ 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 @@ -105,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ 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 @@ -131,6 +140,9 @@ 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". @@ -139,7 +151,6 @@ 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 @@ -149,6 +160,9 @@ 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 @@ -162,7 +176,6 @@ 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 @@ -172,13 +185,15 @@ 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 @@ -188,13 +203,15 @@ 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 @@ -204,13 +221,15 @@ 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 @@ -220,6 +239,9 @@ 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". @@ -228,7 +250,6 @@ 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 @@ -238,6 +259,9 @@ 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: @@ -252,7 +276,6 @@ 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/exchange/Get-MailTrafficPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md index f1ab603a7f..325dda9f30 100644 --- a/exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficpolicyreport +schema: 2.0.0 +title: Get-MailTrafficPolicyReport --- # Get-MailTrafficPolicyReport @@ -76,6 +77,9 @@ 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. @@ -84,7 +88,6 @@ 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,13 +97,15 @@ 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 @@ -110,6 +115,9 @@ 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 @@ -121,7 +129,6 @@ 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,13 +138,15 @@ 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 @@ -147,13 +156,15 @@ 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 @@ -163,6 +174,9 @@ 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". @@ -171,7 +185,6 @@ 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 @@ -181,6 +194,9 @@ 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 @@ -199,7 +215,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -209,13 +224,15 @@ 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 @@ -225,13 +242,15 @@ 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 @@ -241,13 +260,15 @@ 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 @@ -257,6 +278,9 @@ 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". @@ -265,7 +289,6 @@ 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 @@ -275,6 +298,9 @@ 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: @@ -292,7 +318,6 @@ 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 @@ -302,13 +327,15 @@ 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/exchange/Get-MailTrafficSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md index 5ef4d9692a..b5b3bf6788 100644 --- a/exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficsummaryreport +schema: 2.0.0 +title: Get-MailTrafficSummaryReport --- # Get-MailTrafficSummaryReport @@ -54,6 +55,9 @@ 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 @@ -84,7 +88,6 @@ 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 @@ -94,13 +97,15 @@ 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 @@ -110,13 +115,15 @@ 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 @@ -126,6 +133,9 @@ 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". @@ -134,7 +144,6 @@ 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 @@ -144,13 +153,15 @@ 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 @@ -160,13 +171,15 @@ 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 @@ -176,13 +189,15 @@ 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 @@ -192,6 +207,9 @@ 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". @@ -200,7 +218,6 @@ 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 @@ -210,13 +227,15 @@ 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/exchange/Get-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md index 82f050e5ea..6d521f6c68 100644 --- a/exchange/exchange-ps/exchange/Get-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailuser +schema: 2.0.0 +title: Get-MailUser --- # Get-MailUser @@ -99,6 +100,9 @@ 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 @@ -112,7 +116,6 @@ 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 @@ -122,6 +125,9 @@ 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) @@ -134,7 +140,6 @@ 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 @@ -144,6 +149,9 @@ 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. @@ -154,7 +162,6 @@ 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 @@ -164,6 +171,9 @@ 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,7 +182,6 @@ 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 @@ -182,6 +191,9 @@ 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. @@ -197,7 +209,6 @@ 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 @@ -207,6 +218,9 @@ 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. @@ -215,7 +229,6 @@ 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 @@ -225,6 +238,9 @@ 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. @@ -238,7 +254,6 @@ 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 @@ -248,6 +263,9 @@ 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. @@ -256,7 +274,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: LOBAppAccount Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -266,6 +283,9 @@ 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 @@ -277,7 +297,6 @@ 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 @@ -287,6 +306,9 @@ 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. @@ -299,7 +321,6 @@ 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 @@ -309,13 +330,15 @@ 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 @@ -325,6 +348,9 @@ Accept wildcard characters: False ``` ### -SharedWithMailUser + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill SharedWithMailUser Description }} @@ -333,7 +359,6 @@ 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 @@ -343,6 +368,9 @@ 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. @@ -358,7 +386,6 @@ 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 @@ -368,6 +395,9 @@ 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. @@ -378,7 +408,6 @@ 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/exchange/Get-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md index cae3773fe1..29e01a819c 100644 --- a/exchange/exchange-ps/exchange/Get-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailbox +schema: 2.0.0 +title: Get-Mailbox --- # Get-Mailbox @@ -209,6 +210,9 @@ 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 @@ -228,7 +232,6 @@ 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 @@ -238,6 +241,9 @@ 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) @@ -250,7 +256,6 @@ 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 @@ -260,6 +265,9 @@ 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. @@ -272,7 +280,6 @@ 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 @@ -282,13 +289,15 @@ 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 @@ -298,6 +307,9 @@ 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. @@ -310,7 +322,6 @@ 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 @@ -320,6 +331,9 @@ 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. @@ -332,7 +346,6 @@ 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 @@ -342,6 +355,9 @@ 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. @@ -352,7 +368,6 @@ 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 @@ -362,6 +377,9 @@ 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: @@ -376,7 +394,6 @@ 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 @@ -386,6 +403,9 @@ 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. @@ -394,7 +414,6 @@ 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 @@ -404,6 +423,9 @@ 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. @@ -419,7 +441,6 @@ 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 @@ -429,13 +450,15 @@ 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 @@ -445,6 +468,9 @@ 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. @@ -458,7 +484,6 @@ 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 @@ -468,6 +493,9 @@ 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. @@ -480,7 +508,6 @@ 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 @@ -490,6 +517,9 @@ Accept wildcard characters: False ``` ### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames Description }} @@ -498,7 +528,6 @@ 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 @@ -508,6 +537,9 @@ Accept wildcard characters: False ``` ### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames Description }} @@ -516,7 +548,6 @@ 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 @@ -526,6 +557,9 @@ Accept wildcard characters: False ``` ### -IncludeAcceptMessagesOnlyFromWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeAcceptMessagesOnlyFromWithDisplayNames Description }} @@ -534,7 +568,6 @@ 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 @@ -544,6 +577,9 @@ Accept wildcard characters: False ``` ### -IncludeEmailAddressDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeEmailAddressDisplayNames Description }} @@ -552,7 +588,6 @@ 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 @@ -562,6 +597,9 @@ Accept wildcard characters: False ``` ### -IncludeForwardingAddressWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeForwardingAddressWithDisplayNames Description }} @@ -570,7 +608,6 @@ 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 @@ -580,6 +617,9 @@ Accept wildcard characters: False ``` ### -IncludeGrantSendOnBehalfToWithDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }} @@ -588,7 +628,6 @@ 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 @@ -598,6 +637,9 @@ 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. @@ -610,7 +652,6 @@ 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 @@ -620,6 +661,9 @@ 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: @@ -638,7 +682,6 @@ 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 @@ -648,13 +691,15 @@ 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 @@ -664,6 +709,9 @@ 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. @@ -674,7 +722,6 @@ 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 @@ -684,6 +731,9 @@ 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 @@ -695,7 +745,6 @@ 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 @@ -705,6 +754,9 @@ 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. @@ -713,7 +765,6 @@ 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 @@ -723,6 +774,9 @@ 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. @@ -735,7 +789,6 @@ 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 @@ -745,6 +798,9 @@ 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 @@ -765,7 +821,6 @@ 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 @@ -775,6 +830,9 @@ 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. @@ -785,7 +843,6 @@ 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 @@ -795,13 +852,15 @@ 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 @@ -811,6 +870,9 @@ 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. @@ -832,7 +894,6 @@ 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 @@ -842,6 +903,9 @@ 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. @@ -852,7 +916,6 @@ 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 @@ -862,6 +925,9 @@ 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. @@ -878,7 +944,6 @@ 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 @@ -888,6 +953,9 @@ 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. @@ -896,7 +964,6 @@ 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/exchange/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md index 52e699b66f..f4d876777f 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxauditbypassassociation +schema: 2.0.0 +title: Get-MailboxAuditBypassAssociation --- # Get-MailboxAuditBypassAssociation @@ -60,13 +61,15 @@ 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 @@ -76,6 +79,9 @@ 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,7 +90,6 @@ 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 @@ -94,13 +99,15 @@ 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/exchange/Get-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md index 2eaf391e3c..74fbd780a6 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxautoreplyconfiguration +schema: 2.0.0 +title: Get-MailboxAutoReplyConfiguration --- # Get-MailboxAutoReplyConfiguration @@ -60,6 +61,9 @@ 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 @@ -77,7 +81,6 @@ 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 @@ -87,6 +90,9 @@ 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). @@ -95,7 +101,6 @@ 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,6 +110,9 @@ 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,7 +121,6 @@ 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 @@ -123,6 +130,9 @@ 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. @@ -133,7 +143,6 @@ 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 @@ -143,13 +152,15 @@ 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 @@ -159,6 +170,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -167,7 +181,6 @@ 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/exchange/Get-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md index d8966ce18e..3c957ab1b9 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxcalendarconfiguration +schema: 2.0.0 +title: Get-MailboxCalendarConfiguration --- # Get-MailboxCalendarConfiguration @@ -80,6 +81,9 @@ 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 @@ -95,9 +99,8 @@ The Identity parameter specifies the mailbox that you want to view. You can use ```yaml Type: MailboxIdParameter -Parameter Sets: Default +Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -106,20 +109,10 @@ Accept pipeline input: True (ByPropertyName, ByValue) Accept wildcard characters: False ``` -```yaml -Type: MailboxIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -DomainController -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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. @@ -128,7 +121,6 @@ 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 @@ -138,6 +130,9 @@ Accept wildcard characters: False ``` ### -MailboxLocation + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MailboxLocation Description }} @@ -146,7 +141,6 @@ 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/exchange/Get-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md index 075437cc2c..850dd3be5d 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxcalendarfolder +schema: 2.0.0 +title: Get-MailboxCalendarFolder --- # Get-MailboxCalendarFolder @@ -58,6 +59,9 @@ 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: @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ 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. @@ -97,7 +103,6 @@ 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,6 +112,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -115,7 +123,6 @@ 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/exchange/Get-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md index 82286a48e4..1274c340fa 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxdatabase +schema: 2.0.0 +title: Get-MailboxDatabase --- # Get-MailboxDatabase @@ -73,6 +74,9 @@ 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 @@ -85,7 +89,6 @@ 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 @@ -95,6 +98,9 @@ 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 @@ -108,7 +114,6 @@ 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 @@ -118,13 +123,15 @@ 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,13 +141,15 @@ 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 @@ -150,13 +159,15 @@ 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 @@ -166,6 +177,9 @@ 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. @@ -174,7 +188,6 @@ The IncludePreExchange2010 switch specifies whether to return information about Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -184,13 +197,15 @@ 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 @@ -200,6 +215,9 @@ 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 @@ -214,7 +232,6 @@ 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/exchange/Get-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md index d58b4dc67d..8503d20c9a 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxdatabasecopystatus +schema: 2.0.0 +title: Get-MailboxDatabaseCopyStatus --- # Get-MailboxDatabaseCopyStatus @@ -74,13 +75,15 @@ 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 @@ -90,13 +93,15 @@ 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 @@ -106,13 +111,15 @@ 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 @@ -122,13 +129,15 @@ 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 @@ -138,13 +147,15 @@ 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 @@ -154,13 +165,15 @@ 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 @@ -170,13 +183,15 @@ 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 @@ -186,13 +201,15 @@ 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/exchange/Get-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md index 106407e8e1..2b0322fc08 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxexportrequest +schema: 2.0.0 +title: Get-MailboxExportRequest --- # Get-MailboxExportRequest @@ -98,6 +99,9 @@ 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: @@ -113,7 +117,6 @@ 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 @@ -123,6 +126,9 @@ 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. @@ -131,7 +137,6 @@ 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 @@ -141,6 +146,9 @@ 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: @@ -155,7 +163,6 @@ 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 @@ -165,13 +172,15 @@ 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 @@ -181,6 +190,9 @@ 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. @@ -192,7 +204,6 @@ 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 @@ -202,6 +213,9 @@ 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. @@ -223,9 +237,8 @@ You can't use this parameter with the Identity parameter. ```yaml Type: MailboxOrMailUserIdParameter -Parameter Sets: MailboxFiltering +Parameter Sets: MailboxFiltering, MailboxLocationFiltering Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -234,20 +247,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxLocationIdParameter -Parameter Sets: MailboxLocationFiltering -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -Name -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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. @@ -260,7 +263,6 @@ 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 @@ -270,13 +272,15 @@ 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 @@ -286,6 +290,9 @@ 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 @@ -307,7 +314,6 @@ 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 @@ -317,6 +323,9 @@ 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. @@ -325,7 +334,6 @@ 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 @@ -335,6 +343,9 @@ 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 @@ -347,7 +358,6 @@ 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/exchange/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md index 27ef9ad06f..508a60ba10 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxexportrequeststatistics +schema: 2.0.0 +title: Get-MailboxExportRequestStatistics --- # Get-MailboxExportRequestStatistics @@ -106,6 +107,9 @@ 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. @@ -114,7 +118,6 @@ 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 @@ -124,6 +127,9 @@ 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. @@ -134,7 +140,6 @@ 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 @@ -144,6 +149,9 @@ 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: @@ -158,7 +166,6 @@ 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 @@ -168,6 +175,9 @@ 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. @@ -176,7 +186,6 @@ 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 @@ -186,13 +195,15 @@ 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 @@ -202,6 +213,9 @@ 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. @@ -210,7 +224,6 @@ 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 @@ -220,13 +233,15 @@ 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 @@ -236,13 +251,15 @@ 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 @@ -252,13 +269,15 @@ 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 @@ -268,13 +287,15 @@ 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/exchange/Get-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailboxFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md index 3e9a4e5383..96938d255f 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolder +schema: 2.0.0 +title: Get-MailboxFolder --- # Get-MailboxFolder @@ -85,6 +86,9 @@ 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. @@ -110,7 +114,6 @@ 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 @@ -120,6 +123,9 @@ 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. @@ -128,7 +134,6 @@ 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 @@ -138,6 +143,9 @@ 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. @@ -146,7 +154,6 @@ 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 @@ -156,6 +163,9 @@ 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,7 +174,6 @@ 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 @@ -174,13 +183,15 @@ 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 @@ -190,13 +201,15 @@ 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/exchange/Get-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md index 1873b6abc7..d2b6604ad5 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission +schema: 2.0.0 +title: Get-MailboxFolderPermission --- # Get-MailboxFolderPermission @@ -62,6 +63,9 @@ 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: @@ -83,7 +87,6 @@ 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 @@ -93,6 +96,9 @@ 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,7 +107,6 @@ 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,13 +116,15 @@ 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 @@ -127,6 +134,9 @@ 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. @@ -135,7 +145,6 @@ 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 @@ -145,6 +154,9 @@ Accept wildcard characters: False ``` ### -SkipCount + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipCount Description }} @@ -153,7 +165,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -163,6 +174,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -171,7 +185,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -181,6 +194,9 @@ 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: @@ -201,7 +217,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md index 8b201910e4..7ad81b4119 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderstatistics +schema: 2.0.0 +title: Get-MailboxFolderStatistics --- # Get-MailboxFolderStatistics @@ -115,6 +116,9 @@ 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 @@ -130,9 +134,8 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c ```yaml Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: Identity +Parameter Sets: Identity, AuditLog Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -141,20 +144,10 @@ Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` -```yaml -Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: AuditLog -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -Database -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName) -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -Database This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -163,7 +156,6 @@ This parameter is reserved for internal Microsoft use. Type: DatabaseIdParameter Parameter Sets: Database Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -173,6 +165,9 @@ 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. @@ -181,7 +176,6 @@ This parameter is reserved for internal Microsoft use. Type: StoreMailboxIdParameter Parameter Sets: Database Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -191,13 +185,15 @@ 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 @@ -207,6 +203,9 @@ 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. @@ -215,7 +214,6 @@ 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 @@ -225,6 +223,9 @@ 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. @@ -233,7 +234,6 @@ 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,6 +243,9 @@ 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. @@ -251,7 +254,6 @@ 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 @@ -261,6 +263,9 @@ 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 @@ -289,7 +294,6 @@ 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 @@ -299,6 +303,9 @@ 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. @@ -307,7 +314,6 @@ 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 @@ -317,13 +323,15 @@ 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 @@ -333,6 +341,9 @@ 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. @@ -343,7 +354,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -353,6 +363,9 @@ 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. @@ -361,7 +374,6 @@ 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 @@ -371,6 +383,9 @@ Accept wildcard characters: False ``` ### -SkipCount + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipCount Description }} @@ -379,7 +394,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -389,6 +403,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -397,7 +414,6 @@ 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/exchange/Get-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md index ca07bcdfd7..80d95f0a85 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxirmaccess +schema: 2.0.0 +title: Get-MailboxIRMAccess --- # Get-MailboxIRMAccess @@ -56,6 +57,9 @@ 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 @@ -73,7 +77,6 @@ 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 @@ -83,6 +86,9 @@ 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 @@ -100,7 +106,6 @@ 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/exchange/Get-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md index 63f31df6ff..f2759b6726 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboximportrequest +schema: 2.0.0 +title: Get-MailboxImportRequest --- # Get-MailboxImportRequest @@ -100,6 +101,9 @@ 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: @@ -115,7 +119,6 @@ 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 @@ -125,6 +128,9 @@ 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. @@ -133,7 +139,6 @@ 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 @@ -143,6 +148,9 @@ 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: @@ -157,7 +165,6 @@ 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 @@ -167,6 +174,9 @@ 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. @@ -175,7 +185,6 @@ 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 @@ -185,6 +194,9 @@ 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: @@ -198,7 +210,6 @@ 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 @@ -208,6 +219,9 @@ 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. @@ -231,9 +245,8 @@ You can't use this parameter with the Identity parameter. ```yaml Type: MailboxOrMailUserIdParameter -Parameter Sets: MailboxFiltering +Parameter Sets: MailboxFiltering, MailboxLocationFiltering Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -242,20 +255,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxLocationIdParameter -Parameter Sets: MailboxLocationFiltering -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Name -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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). @@ -266,7 +269,6 @@ 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 @@ -276,13 +278,15 @@ 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 @@ -292,6 +296,9 @@ 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 @@ -313,7 +320,6 @@ 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 @@ -323,6 +329,9 @@ 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. @@ -331,7 +340,6 @@ 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 @@ -341,6 +349,9 @@ 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: @@ -355,7 +366,6 @@ 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/exchange/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md index 5803c36890..ae67639973 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboximportrequeststatistics +schema: 2.0.0 +title: Get-MailboxImportRequestStatistics --- # Get-MailboxImportRequestStatistics @@ -108,6 +109,9 @@ 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. @@ -116,7 +120,6 @@ 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 @@ -126,6 +129,9 @@ 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. @@ -136,7 +142,6 @@ 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 @@ -146,6 +151,9 @@ 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. @@ -162,7 +170,6 @@ 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 @@ -172,6 +179,9 @@ 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. @@ -182,7 +192,6 @@ 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 @@ -192,6 +201,9 @@ 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. @@ -200,7 +212,6 @@ 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 @@ -210,6 +221,9 @@ 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. @@ -218,7 +232,6 @@ 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 @@ -228,6 +241,9 @@ 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. @@ -236,7 +252,6 @@ 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 @@ -246,13 +261,15 @@ 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 @@ -262,6 +279,9 @@ Accept wildcard characters: False ``` ### -IncludeSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeSkippedItems Description }} @@ -270,7 +290,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: IdentityCloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -280,6 +299,9 @@ 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. @@ -290,7 +312,6 @@ 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 @@ -300,13 +321,15 @@ 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/exchange/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md index 4f8fe4884f..215e6a225c 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxjunkemailconfiguration +schema: 2.0.0 +title: Get-MailboxJunkEmailConfiguration --- # Get-MailboxJunkEmailConfiguration @@ -67,6 +68,9 @@ 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 @@ -86,7 +90,6 @@ 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 @@ -96,6 +99,9 @@ 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). @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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. @@ -142,7 +152,6 @@ 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,13 +161,15 @@ 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/exchange/Get-MailboxLocation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxLocation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md index ea42b8a024..ba564614c6 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxLocation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxlocation +schema: 2.0.0 +title: Get-MailboxLocation --- # Get-MailboxLocation @@ -73,6 +74,9 @@ 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: @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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 @@ -112,7 +118,6 @@ 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 @@ -122,6 +127,9 @@ 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: @@ -137,7 +145,6 @@ You can't use this parameter with the Identity parameter. Type: UserIdParameter Parameter Sets: User Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -147,6 +154,9 @@ 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`. @@ -156,7 +166,6 @@ 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 @@ -166,6 +175,9 @@ 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. @@ -176,7 +188,6 @@ You can only use this switch with the User parameter. Type: SwitchParameter Parameter Sets: User Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -186,6 +197,9 @@ 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 @@ -200,7 +214,6 @@ 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 @@ -210,13 +223,15 @@ 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 @@ -226,13 +241,15 @@ 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/exchange/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md index fff93d6e2a..0448b6646f 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxmessageconfiguration +schema: 2.0.0 +title: Get-MailboxMessageConfiguration --- # Get-MailboxMessageConfiguration @@ -58,6 +59,9 @@ 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 @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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). @@ -93,7 +99,6 @@ 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 @@ -103,6 +108,9 @@ 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. @@ -111,7 +119,6 @@ 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 @@ -121,6 +128,9 @@ 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. @@ -131,7 +141,6 @@ 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 @@ -141,13 +150,15 @@ 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 @@ -157,6 +168,9 @@ Accept wildcard characters: False ``` ### -SignatureName + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SignatureName Description }} @@ -165,7 +179,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -175,6 +188,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -183,7 +199,6 @@ 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/exchange/Get-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md index 80fc4e6f73..d1962fa6bb 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxpermission +schema: 2.0.0 +title: Get-MailboxPermission --- # Get-MailboxPermission @@ -97,6 +98,9 @@ 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 @@ -114,7 +118,6 @@ 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 @@ -124,6 +127,9 @@ 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). @@ -132,7 +138,6 @@ 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,6 +147,9 @@ 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. @@ -150,7 +158,6 @@ 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 @@ -160,6 +167,9 @@ 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. @@ -168,7 +178,6 @@ 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 @@ -178,6 +187,9 @@ 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. @@ -188,7 +200,6 @@ 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 @@ -198,6 +209,9 @@ 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. @@ -206,7 +220,6 @@ The IncludeUnresolvedPermissions switch returns unresolved permissions in the re Type: SwitchParameter Parameter Sets: AccessRights Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,6 +229,9 @@ Accept wildcard characters: False ``` ### -IncludeUserWithDisplayName + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeUserWithDisplayName Description }} @@ -224,7 +240,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -234,6 +249,9 @@ 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. @@ -242,7 +260,6 @@ 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 @@ -252,6 +269,9 @@ 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. @@ -262,7 +282,6 @@ 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 @@ -272,13 +291,15 @@ 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 @@ -288,6 +309,9 @@ 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. @@ -298,7 +322,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: AccessRights Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -308,6 +331,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -316,7 +342,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -326,6 +351,9 @@ 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 @@ -356,7 +384,6 @@ 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/exchange/Get-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-MailboxPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md index c1a6bb560a..0deb783a99 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxplan +schema: 2.0.0 +title: Get-MailboxPlan --- # Get-MailboxPlan @@ -55,6 +56,9 @@ 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 @@ -67,7 +71,6 @@ 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 @@ -77,6 +80,9 @@ 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. @@ -85,7 +91,6 @@ 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 @@ -95,6 +100,9 @@ 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). @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ 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,7 +138,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -138,13 +147,15 @@ 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 @@ -154,13 +165,15 @@ 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 @@ -170,6 +183,9 @@ 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. @@ -184,7 +200,6 @@ 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/exchange/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md index 0915467f52..76ea643b83 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxregionalconfiguration +schema: 2.0.0 +title: Get-MailboxRegionalConfiguration --- # Get-MailboxRegionalConfiguration @@ -72,6 +73,9 @@ 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 @@ -87,9 +91,8 @@ The Identity parameter specifies the mailbox that you want to view. You can use ```yaml Type: MailboxIdParameter -Parameter Sets: (All) +Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -98,20 +101,10 @@ Accept pipeline input: True (ByPropertyName, ByValue) Accept wildcard characters: False ``` -```yaml -Type: MailboxIdParameter -Parameter Sets: Identity -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Archive -Required: False -Position: 1 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -Archive This parameter is available only in the cloud-based service. {{ Fill Archive Description }} @@ -120,7 +113,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -130,6 +122,9 @@ 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. @@ -138,7 +133,6 @@ 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 @@ -148,6 +142,9 @@ Accept wildcard characters: False ``` ### -MailboxLocation + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MailboxLocation Description }} @@ -156,7 +153,6 @@ This parameter is available only in the cloud-based service. Type: MailboxLocationIdParameter Parameter Sets: MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -166,6 +162,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -174,7 +173,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -184,6 +182,9 @@ 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: @@ -200,7 +201,6 @@ 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/exchange/Get-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md index d247baf12a..358fe454a4 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrepairrequest +schema: 2.0.0 +title: Get-MailboxRepairRequest --- # Get-MailboxRepairRequest @@ -83,6 +84,9 @@ 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. @@ -91,7 +95,6 @@ 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 @@ -101,6 +104,9 @@ 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 @@ -113,7 +119,6 @@ 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 @@ -123,6 +128,9 @@ 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 @@ -142,7 +150,6 @@ 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 @@ -152,6 +159,9 @@ 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. @@ -160,7 +170,6 @@ 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 @@ -170,6 +179,9 @@ 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. @@ -180,7 +192,6 @@ 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 @@ -190,13 +201,15 @@ 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 @@ -206,13 +219,15 @@ 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/exchange/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md index 307c4af120..b2df442646 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrestorerequest +schema: 2.0.0 +title: Get-MailboxRestoreRequest --- # Get-MailboxRestoreRequest @@ -80,6 +81,9 @@ 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). @@ -90,7 +94,6 @@ 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 @@ -100,6 +103,9 @@ 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. @@ -108,7 +114,6 @@ 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 @@ -118,6 +123,9 @@ 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,7 +134,6 @@ 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 @@ -136,6 +143,9 @@ 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. @@ -147,7 +157,6 @@ 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 @@ -157,6 +166,9 @@ 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. @@ -169,7 +181,6 @@ 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 @@ -179,6 +190,9 @@ 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: @@ -193,7 +207,6 @@ 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 @@ -203,13 +216,15 @@ 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 @@ -219,6 +234,9 @@ 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: @@ -233,7 +251,6 @@ 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 @@ -243,6 +260,9 @@ 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 @@ -262,7 +282,6 @@ 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 @@ -272,6 +291,9 @@ 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. @@ -280,7 +302,6 @@ 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 @@ -290,6 +311,9 @@ 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: @@ -304,7 +328,6 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: Filtering Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -314,6 +337,9 @@ 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 @@ -330,7 +356,6 @@ 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/exchange/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md index 08a0693b85..64c64dc1d0 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrestorerequeststatistics +schema: 2.0.0 +title: Get-MailboxRestoreRequestStatistics --- # Get-MailboxRestoreRequestStatistics @@ -104,6 +105,9 @@ 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). @@ -114,7 +118,6 @@ 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 @@ -124,6 +127,9 @@ 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. @@ -134,7 +140,6 @@ 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 @@ -144,6 +149,9 @@ 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. @@ -160,7 +168,6 @@ 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 @@ -170,13 +177,15 @@ 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 @@ -186,6 +195,9 @@ 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. @@ -194,7 +206,6 @@ 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 @@ -204,6 +215,9 @@ 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. @@ -214,7 +228,6 @@ 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 @@ -224,6 +237,9 @@ 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. @@ -232,7 +248,6 @@ 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 @@ -242,6 +257,9 @@ 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. @@ -250,7 +268,6 @@ 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 @@ -260,6 +277,9 @@ 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. @@ -268,7 +288,6 @@ 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 @@ -278,6 +297,9 @@ Accept wildcard characters: False ``` ### -IncludeSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeSkippedItems Description }} @@ -286,7 +308,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: IdentityCloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -296,13 +317,15 @@ 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/exchange/Get-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md index 3051b480ef..d073a5c3f1 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxsearch +schema: 2.0.0 +title: Get-MailboxSearch --- # Get-MailboxSearch @@ -83,6 +84,9 @@ 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: @@ -98,9 +102,8 @@ To view these properties, you have to provide the name of a mailbox search. ```yaml Type: SearchObjectIdParameter -Parameter Sets: EwsStoreObjectIdentity +Parameter Sets: EwsStoreObjectIdentity, SearchObjectIdentity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -109,27 +112,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: SearchObjectIdParameter -Parameter Sets: SearchObjectIdentity -Aliases: -Applicable: Exchange Server 2010 +### -InPlaceHoldIdentity -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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 @@ -139,6 +131,9 @@ 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,7 +142,6 @@ 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 @@ -157,13 +151,15 @@ 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 @@ -173,13 +169,15 @@ 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/exchange/Get-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md index 0db5f4e4f3..f5adbbfe7a 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxsentitemsconfiguration +schema: 2.0.0 +title: Get-MailboxSentItemsConfiguration --- # Get-MailboxSentItemsConfiguration @@ -43,13 +44,15 @@ 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 @@ -59,6 +62,9 @@ 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 @@ -76,7 +82,6 @@ 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/exchange/Get-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md index 7b2886ee8a..d68d6be325 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxserver +schema: 2.0.0 +title: Get-MailboxServer --- # Get-MailboxServer @@ -51,6 +52,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,13 +74,15 @@ 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 @@ -87,6 +92,9 @@ 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. @@ -95,7 +103,6 @@ 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/exchange/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md index 711e199b87..d3e0508396 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxspellingconfiguration +schema: 2.0.0 +title: Get-MailboxSpellingConfiguration --- # Get-MailboxSpellingConfiguration @@ -62,6 +63,9 @@ 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 @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ 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. @@ -97,7 +103,6 @@ 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/exchange/Get-MailboxStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MailboxStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md index 364729d637..535a09c839 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxstatistics +schema: 2.0.0 +title: Get-MailboxStatistics --- # Get-MailboxStatistics @@ -148,6 +149,9 @@ 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 @@ -165,7 +169,6 @@ 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 @@ -175,6 +178,9 @@ 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: @@ -188,7 +194,6 @@ 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 @@ -198,13 +203,15 @@ 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 @@ -214,6 +221,9 @@ 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. @@ -231,7 +241,6 @@ 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 @@ -241,6 +250,9 @@ 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: @@ -255,7 +267,6 @@ 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 @@ -265,6 +276,9 @@ 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. @@ -273,7 +287,6 @@ 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 @@ -283,6 +296,9 @@ 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'"`. @@ -302,7 +318,6 @@ 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 @@ -312,13 +327,15 @@ 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 @@ -328,6 +345,9 @@ 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. @@ -336,7 +356,6 @@ 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 @@ -346,6 +365,9 @@ 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. @@ -356,7 +378,6 @@ 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 @@ -366,6 +387,9 @@ 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. @@ -376,7 +400,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -386,6 +409,9 @@ 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. @@ -396,7 +422,6 @@ 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 @@ -406,6 +431,9 @@ 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. @@ -416,7 +444,6 @@ 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 @@ -426,6 +453,9 @@ 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: @@ -439,7 +469,6 @@ 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 @@ -449,6 +478,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -457,7 +489,6 @@ 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/exchange/Get-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MailboxTransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md index 4e4beb49a3..78d334f3c3 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxtransportservice +schema: 2.0.0 +title: Get-MailboxTransportService --- # Get-MailboxTransportService @@ -50,13 +51,15 @@ 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 @@ -66,13 +69,15 @@ 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/exchange/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md index 6487e6dc0e..2a78cbee23 100644 --- a/exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxuserconfiguration +schema: 2.0.0 +title: Get-MailboxUserConfiguration --- # Get-MailboxUserConfiguration @@ -50,6 +51,9 @@ 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. @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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 @@ -86,7 +92,6 @@ 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 @@ -96,13 +101,15 @@ 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 @@ -112,6 +119,9 @@ 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. @@ -120,7 +130,6 @@ 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 @@ -130,13 +139,15 @@ 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/exchange/Get-MailflowStatusReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailflowStatusReport.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MailflowStatusReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MailflowStatusReport.md index fef6949dce..9688c98f76 100644 --- a/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailflowStatusReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mailflowstatusreport +schema: 2.0.0 +title: Get-MailFlowStatusReport --- # Get-MailFlowStatusReport @@ -55,6 +56,9 @@ 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 @@ -67,7 +71,6 @@ You can specify multiple value separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -77,13 +80,15 @@ 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 @@ -93,6 +98,9 @@ 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. @@ -101,7 +109,6 @@ 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 @@ -111,6 +118,9 @@ 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 @@ -126,7 +136,6 @@ 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,13 +145,15 @@ 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 @@ -152,13 +163,15 @@ 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 @@ -168,13 +181,15 @@ 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 @@ -184,6 +199,9 @@ 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. @@ -192,7 +210,6 @@ 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/exchange/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md index 077860de6f..151df48bcf 100644 --- a/exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilterpolicy +schema: 2.0.0 +title: Get-MalwareFilterPolicy --- # Get-MalwareFilterPolicy @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md index d8b421d6ef..87c1bca3dd 100644 --- a/exchange/exchange-ps/exchange/Get-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilterrule +schema: 2.0.0 +title: Get-MalwareFilterRule --- # Get-MalwareFilterRule @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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. @@ -73,7 +79,6 @@ 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,13 +88,15 @@ 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/exchange/Get-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md index 11a67a8298..3d65419ccf 100644 --- a/exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilteringserver +schema: 2.0.0 +title: Get-MalwareFilteringServer --- # Get-MalwareFilteringServer @@ -48,6 +49,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ 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. @@ -77,7 +83,6 @@ 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/exchange/Get-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ManagedContentSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md index 543f807e2a..0aa255748d 100644 --- a/exchange/exchange-ps/exchange/Get-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managedcontentsettings +schema: 2.0.0 +title: Get-ManagedContentSettings --- # Get-ManagedContentSettings @@ -67,6 +68,9 @@ 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. @@ -75,7 +79,6 @@ This parameter can't be used with the FolderName parameter. Type: ELCContentSettingsIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: 1 @@ -85,13 +88,15 @@ 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 @@ -101,6 +106,9 @@ 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. @@ -109,7 +117,6 @@ 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/exchange/Get-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ManagedFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md index f7a6302c2b..c4a492fc9f 100644 --- a/exchange/exchange-ps/exchange/Get-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managedfolder +schema: 2.0.0 +title: Get-ManagedFolder --- # Get-ManagedFolder @@ -57,13 +58,15 @@ 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 @@ -73,13 +76,15 @@ 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 @@ -89,6 +94,9 @@ 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 @@ -108,7 +116,6 @@ 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/exchange/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md index 773b53f264..5e9fcefdc5 100644 --- a/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managedfoldermailboxpolicy +schema: 2.0.0 +title: Get-ManagedFolderMailboxPolicy --- # Get-ManagedFolderMailboxPolicy @@ -45,13 +46,15 @@ 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 @@ -61,13 +64,15 @@ 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/exchange/Get-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md similarity index 83% rename from exchange/exchange-ps/exchange/Get-ManagementRole.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md index 72a4c467e8..5559902da0 100644 --- a/exchange/exchange-ps/exchange/Get-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managementrole +schema: 2.0.0 +title: Get-ManagementRole --- # Get-ManagementRole @@ -112,13 +113,15 @@ 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 +Parameter Sets: GetChildren, Recurse, Identity, Script 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 @@ -127,20 +130,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```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 +### -GetChildren -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -### -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. @@ -151,7 +144,6 @@ 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 @@ -161,6 +153,9 @@ 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. @@ -171,7 +166,6 @@ 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 @@ -181,13 +175,15 @@ 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 @@ -197,13 +193,15 @@ 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 @@ -213,6 +211,9 @@ 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. @@ -221,7 +222,6 @@ 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,13 +231,15 @@ 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 @@ -247,13 +249,15 @@ 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 @@ -263,13 +267,15 @@ 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/exchange/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md similarity index 86% rename from exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md index 574baae033..d030d7be35 100644 --- a/exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managementroleassignment +schema: 2.0.0 +title: Get-ManagementRoleAssignment --- # Get-ManagementRoleAssignment @@ -131,13 +132,15 @@ 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 @@ -147,6 +150,9 @@ 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 @@ -162,7 +168,6 @@ 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 @@ -172,13 +177,15 @@ 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 @@ -188,6 +195,9 @@ 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. @@ -200,7 +210,6 @@ 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 @@ -210,6 +219,9 @@ 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. @@ -220,7 +232,6 @@ 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 @@ -230,6 +241,9 @@ 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. @@ -238,7 +252,6 @@ 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 @@ -248,6 +261,9 @@ 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,7 +272,6 @@ 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 @@ -266,13 +281,15 @@ 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 @@ -282,6 +299,9 @@ 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. @@ -290,7 +310,6 @@ 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 @@ -300,6 +319,9 @@ 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. @@ -312,7 +334,6 @@ 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 @@ -322,6 +343,9 @@ 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. @@ -332,7 +356,6 @@ 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 @@ -342,6 +365,9 @@ 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. @@ -350,7 +376,6 @@ 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 @@ -360,6 +385,9 @@ 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. @@ -370,7 +398,6 @@ 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 @@ -380,6 +407,9 @@ 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. @@ -388,7 +418,6 @@ 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 @@ -398,13 +427,15 @@ 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 @@ -414,13 +445,15 @@ 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 @@ -430,13 +463,15 @@ 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 @@ -446,6 +481,9 @@ 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. @@ -456,7 +494,6 @@ 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 @@ -466,13 +503,15 @@ 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 @@ -482,6 +521,9 @@ 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: @@ -496,7 +538,6 @@ 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 @@ -506,6 +547,9 @@ 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. @@ -514,7 +558,6 @@ 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 @@ -524,6 +567,9 @@ 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. @@ -541,7 +587,6 @@ 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/exchange/Get-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md index 8ba8cccb05..42ad1d8b4d 100644 --- a/exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managementroleentry +schema: 2.0.0 +title: Get-ManagementRoleEntry --- # Get-ManagementRoleEntry @@ -63,6 +64,9 @@ 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). @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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. @@ -93,7 +99,6 @@ 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,6 +108,9 @@ 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. @@ -111,7 +119,6 @@ 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 @@ -121,13 +128,15 @@ 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 @@ -137,6 +146,9 @@ 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,7 +157,6 @@ 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 @@ -155,13 +166,15 @@ 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/exchange/Get-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-ManagementScope.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md index 38673e7eda..6af08242cc 100644 --- a/exchange/exchange-ps/exchange/Get-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-managementscope +schema: 2.0.0 +title: Get-ManagementScope --- # Get-ManagementScope @@ -68,13 +69,15 @@ 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 @@ -84,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -102,13 +107,15 @@ 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 @@ -118,13 +125,15 @@ 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/exchange/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md index 77a025f2c7..2a9e34247c 100644 --- a/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mapivirtualdirectory +schema: 2.0.0 +title: Get-MapiVirtualDirectory --- # Get-MapiVirtualDirectory @@ -71,6 +72,9 @@ 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 @@ -85,7 +89,6 @@ 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 @@ -95,6 +98,9 @@ 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 @@ -108,7 +114,6 @@ 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 @@ -118,6 +123,9 @@ 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. @@ -126,7 +134,6 @@ 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 @@ -136,13 +143,15 @@ 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 @@ -152,6 +161,9 @@ 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. @@ -164,7 +176,6 @@ 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/exchange/Get-Message.md b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Message.md index 634425d077..ad6b208ff5 100644 --- a/exchange/exchange-ps/exchange/Get-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-message +schema: 2.0.0 +title: Get-Message --- # Get-Message @@ -97,13 +98,15 @@ 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 @@ -113,13 +116,15 @@ 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 @@ -129,13 +134,15 @@ 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 @@ -145,6 +152,9 @@ 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 ("). @@ -153,7 +163,6 @@ 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 @@ -163,13 +172,15 @@ 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 @@ -179,6 +190,9 @@ 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. @@ -187,7 +201,6 @@ 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 @@ -197,6 +210,9 @@ 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. @@ -217,7 +233,6 @@ 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 @@ -227,6 +242,9 @@ 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. @@ -235,7 +253,6 @@ 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 @@ -245,13 +262,15 @@ 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 @@ -261,13 +280,15 @@ 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 @@ -277,13 +298,15 @@ 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 @@ -293,6 +316,9 @@ 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 @@ -308,7 +334,6 @@ 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 @@ -318,6 +343,9 @@ 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. @@ -326,7 +354,6 @@ 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/exchange/Get-MessageCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MessageCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md index 6cebfc35f4..68592b3f64 100644 --- a/exchange/exchange-ps/exchange/Get-MessageCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagecategory +schema: 2.0.0 +title: Get-MessageCategory --- # Get-MessageCategory @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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 @@ -95,7 +103,6 @@ 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/exchange/Get-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MessageClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md index bfb6750a16..76eb991165 100644 --- a/exchange/exchange-ps/exchange/Get-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messageclassification +schema: 2.0.0 +title: Get-MessageClassification --- # Get-MessageClassification @@ -42,6 +43,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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/exchange/Get-MessageTrace.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MessageTrace.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md index fa030fd3a1..8161c67210 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTrace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrace +schema: 2.0.0 +title: Get-MessageTrace --- # Get-MessageTrace @@ -65,6 +66,9 @@ 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". @@ -73,7 +77,6 @@ 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 @@ -83,13 +86,15 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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: @@ -129,7 +139,6 @@ 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 @@ -139,13 +148,15 @@ 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 @@ -155,13 +166,15 @@ 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 @@ -171,13 +184,15 @@ 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 @@ -187,13 +202,15 @@ 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 @@ -203,13 +220,15 @@ 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 @@ -219,6 +238,9 @@ 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". @@ -227,7 +249,6 @@ 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 @@ -237,6 +258,9 @@ 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. @@ -252,7 +276,6 @@ 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 @@ -262,13 +285,15 @@ 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/exchange/Get-MessageTraceDetail.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-MessageTraceDetail.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md index 2053d79a67..e629039d65 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetail +schema: 2.0.0 +title: Get-MessageTraceDetail --- # Get-MessageTraceDetail @@ -63,6 +64,9 @@ 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: @@ -77,7 +81,6 @@ 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 @@ -87,13 +90,15 @@ 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 @@ -103,6 +108,9 @@ 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. @@ -111,7 +119,6 @@ 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,6 +128,9 @@ 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". @@ -131,7 +141,6 @@ 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 @@ -141,6 +150,9 @@ 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. @@ -157,7 +169,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -167,13 +178,15 @@ 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 @@ -183,13 +196,15 @@ 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 @@ -199,13 +214,15 @@ 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 @@ -215,13 +232,15 @@ 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 @@ -231,13 +250,15 @@ 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 @@ -247,6 +268,9 @@ 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". @@ -257,7 +281,6 @@ 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/exchange/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md index 78e1a37969..07dcbe7702 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2 +schema: 2.0.0 +title: Get-MessageTraceDetailV2 --- # Get-MessageTraceDetailV2 @@ -52,13 +53,15 @@ 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 @@ -68,13 +71,15 @@ 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 @@ -84,6 +89,9 @@ 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. @@ -92,7 +100,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 1 @@ -102,6 +109,9 @@ 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". @@ -112,7 +122,6 @@ 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 @@ -122,6 +131,9 @@ 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. @@ -138,7 +150,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 3 @@ -148,13 +159,15 @@ 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 @@ -164,13 +177,15 @@ 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 @@ -180,6 +195,9 @@ 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". @@ -190,7 +208,6 @@ 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/exchange/Get-MessageTraceV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-MessageTraceV2.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md index f356876da6..6faecad6ce 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTraceV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracev2 +schema: 2.0.0 +title: Get-MessageTraceV2 --- # Get-MessageTraceV2 @@ -69,6 +70,9 @@ 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". @@ -77,7 +81,6 @@ 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 @@ -87,13 +90,15 @@ 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 @@ -103,13 +108,15 @@ 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 @@ -119,6 +126,9 @@ 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: @@ -133,7 +143,6 @@ 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 @@ -143,13 +152,15 @@ 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 @@ -159,6 +170,9 @@ 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. @@ -167,7 +181,6 @@ 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 @@ -177,13 +190,15 @@ 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 @@ -193,6 +208,9 @@ 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". @@ -201,7 +219,6 @@ 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 @@ -211,13 +228,15 @@ 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 @@ -227,6 +246,9 @@ 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. @@ -244,7 +266,6 @@ You can separate multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 10 @@ -254,6 +275,9 @@ 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. @@ -262,7 +286,6 @@ 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 @@ -272,6 +295,9 @@ 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 @@ -284,7 +310,6 @@ We recommend using StartsWith or EndsWith instead of Contains whenever possible. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 12 @@ -294,13 +319,15 @@ 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/exchange/Get-MessageTrackingLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-MessageTrackingLog.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md index 877d2fd0a3..8da11d8de6 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTrackingLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrackinglog +schema: 2.0.0 +title: Get-MessageTrackingLog --- # Get-MessageTrackingLog @@ -74,6 +75,9 @@ 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. @@ -82,7 +86,6 @@ 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 @@ -92,6 +95,9 @@ 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". @@ -100,7 +106,6 @@ 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 @@ -110,13 +115,15 @@ 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 @@ -126,6 +133,9 @@ 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. @@ -134,7 +144,6 @@ 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 @@ -144,13 +153,15 @@ 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 @@ -160,13 +171,15 @@ 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 @@ -176,13 +189,15 @@ 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 @@ -192,13 +207,15 @@ 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 @@ -208,13 +225,15 @@ 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 @@ -224,13 +243,15 @@ 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 @@ -240,6 +261,9 @@ 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 @@ -253,7 +277,6 @@ 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 @@ -263,6 +286,9 @@ 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". @@ -271,7 +297,6 @@ 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 @@ -281,13 +306,15 @@ 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 @@ -297,13 +324,15 @@ 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 @@ -313,13 +342,15 @@ 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/exchange/Get-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-MessageTrackingReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md index fe0eb16c93..7272487611 100644 --- a/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrackingreport +schema: 2.0.0 +title: Get-MessageTrackingReport --- # Get-MessageTrackingReport @@ -67,6 +68,9 @@ 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. @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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. @@ -93,7 +99,6 @@ 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 @@ -103,6 +108,9 @@ 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. @@ -112,7 +120,6 @@ 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 @@ -122,13 +129,15 @@ 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,6 +147,9 @@ 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. @@ -146,7 +158,6 @@ 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 @@ -156,13 +167,15 @@ 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 @@ -172,13 +185,15 @@ 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 @@ -188,6 +203,9 @@ 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. @@ -197,7 +215,6 @@ 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 @@ -207,13 +224,15 @@ 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 @@ -223,6 +242,9 @@ 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 @@ -235,7 +257,6 @@ 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 @@ -245,6 +266,9 @@ 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. @@ -257,7 +281,6 @@ 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/exchange/Get-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md index ecc0d0aa97..791df3fc9f 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationbatch +schema: 2.0.0 +title: Get-MigrationBatch --- # Get-MigrationBatch @@ -100,6 +101,9 @@ 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. @@ -108,7 +112,6 @@ 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 @@ -118,6 +121,9 @@ 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. @@ -128,7 +134,6 @@ 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 @@ -138,6 +143,9 @@ 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. @@ -146,7 +154,6 @@ 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 @@ -156,6 +163,9 @@ 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: @@ -184,7 +194,6 @@ 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 @@ -194,6 +203,9 @@ 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. @@ -202,7 +214,6 @@ 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 @@ -212,6 +223,9 @@ 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. @@ -220,7 +234,6 @@ 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 @@ -230,6 +243,9 @@ 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. @@ -238,7 +254,6 @@ 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 @@ -248,6 +263,9 @@ 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. @@ -256,7 +274,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -266,6 +283,9 @@ 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. @@ -274,7 +294,6 @@ 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 @@ -284,6 +303,9 @@ 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 @@ -306,7 +328,6 @@ 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/exchange/Get-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MigrationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md index 1d8997faf8..77b75df211 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationconfig +schema: 2.0.0 +title: Get-MigrationConfig --- # Get-MigrationConfig @@ -55,6 +56,9 @@ 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 }} @@ -63,7 +67,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: AllPartitions Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -73,6 +76,9 @@ 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. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ Accept wildcard characters: False ``` ### -IncludeSimplifiedGmailMigrationData + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeSimplifiedGmailMigrationData Description }} @@ -99,7 +107,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Partition, AllPartitions Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -109,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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/exchange/Get-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-MigrationEndpoint.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md index 8f8f5dd3c9..6da1275456 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationendpoint +schema: 2.0.0 +title: Get-MigrationEndpoint --- # Get-MigrationEndpoint @@ -80,13 +81,15 @@ 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 @@ -96,6 +99,9 @@ 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. @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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. @@ -124,7 +132,6 @@ 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 @@ -134,6 +141,9 @@ 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. @@ -142,7 +152,6 @@ 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 @@ -152,6 +161,9 @@ 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: @@ -180,7 +192,6 @@ 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 @@ -190,6 +201,9 @@ 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. @@ -198,7 +212,6 @@ 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 @@ -208,6 +221,9 @@ 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. @@ -216,7 +232,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -226,6 +241,9 @@ 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 @@ -237,7 +255,6 @@ 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/exchange/Get-MigrationStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-MigrationStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md index c397c884ee..080aed2c69 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationstatistics +schema: 2.0.0 +title: Get-MigrationStatistics --- # Get-MigrationStatistics @@ -44,6 +45,9 @@ 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. @@ -54,7 +58,6 @@ 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 @@ -64,6 +67,9 @@ 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. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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: @@ -110,7 +118,6 @@ 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 @@ -120,6 +127,9 @@ 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,7 +138,6 @@ 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 @@ -138,6 +147,9 @@ 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. @@ -146,7 +158,6 @@ 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/exchange/Get-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MigrationUser.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md index e379851050..7d99538c17 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationuser +schema: 2.0.0 +title: Get-MigrationUser --- # Get-MigrationUser @@ -96,13 +97,15 @@ 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 @@ -112,13 +115,15 @@ 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 @@ -128,13 +133,15 @@ 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 @@ -144,6 +151,9 @@ 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. @@ -152,7 +162,6 @@ 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 @@ -162,13 +171,15 @@ 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 @@ -178,6 +189,9 @@ Accept wildcard characters: False ``` ### -IncludeAssociatedUsers + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeAssociatedUsers Description }} @@ -186,7 +200,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -196,6 +209,9 @@ 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. @@ -204,7 +220,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -214,13 +229,15 @@ 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 @@ -230,6 +247,9 @@ 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 @@ -258,7 +278,6 @@ 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 @@ -268,6 +287,9 @@ 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 @@ -280,7 +302,6 @@ 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/exchange/Get-MigrationUserStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md index 5e64b3de72..5e2e7b8c50 100644 --- a/exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationuserstatistics +schema: 2.0.0 +title: Get-MigrationUserStatistics --- # Get-MigrationUserStatistics @@ -85,13 +86,15 @@ 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 @@ -101,6 +104,9 @@ 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. @@ -111,7 +117,6 @@ 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 @@ -121,6 +126,9 @@ 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. @@ -129,7 +137,6 @@ 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 @@ -139,6 +146,9 @@ 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. @@ -147,7 +157,6 @@ 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 @@ -157,6 +166,9 @@ 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. @@ -165,7 +177,6 @@ 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,6 +186,9 @@ Accept wildcard characters: False ``` ### -IncludeCopilotReport + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeCopilotReport Description }} @@ -183,7 +197,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -193,13 +206,15 @@ 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 @@ -209,13 +224,15 @@ 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 @@ -225,13 +242,15 @@ 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 @@ -241,6 +260,9 @@ 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. @@ -249,7 +271,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -259,13 +280,15 @@ 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/exchange/Get-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MobileDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md index 7da6e04fbb..1125d47174 100644 --- a/exchange/exchange-ps/exchange/Get-MobileDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevice +schema: 2.0.0 +title: Get-MobileDevice --- # Get-MobileDevice @@ -83,6 +84,9 @@ 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`) @@ -93,7 +97,6 @@ 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 @@ -103,6 +106,9 @@ 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 @@ -122,7 +128,6 @@ 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 @@ -132,13 +137,15 @@ 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 @@ -148,6 +155,9 @@ 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. @@ -156,7 +166,6 @@ 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 @@ -166,6 +175,9 @@ 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. @@ -202,7 +214,6 @@ 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 @@ -212,6 +223,9 @@ 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. @@ -222,7 +236,6 @@ 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 @@ -232,6 +245,9 @@ 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 @@ -243,7 +259,6 @@ 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 @@ -253,13 +268,15 @@ 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 @@ -269,13 +286,15 @@ 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 @@ -285,6 +304,9 @@ 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. @@ -311,7 +333,6 @@ 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 @@ -321,13 +342,15 @@ 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 @@ -337,13 +360,15 @@ 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/exchange/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md index 5a1d4c078b..ae24f3a825 100644 --- a/exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevicemailboxpolicy +schema: 2.0.0 +title: Get-MobileDeviceMailboxPolicy --- # Get-MobileDeviceMailboxPolicy @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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,7 +80,6 @@ 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/exchange/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md index d493f60367..d8630d7fa7 100644 --- a/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevicestatistics +schema: 2.0.0 +title: Get-MobileDeviceStatistics --- # Get-MobileDeviceStatistics @@ -87,6 +88,9 @@ 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`) @@ -99,7 +103,6 @@ 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 @@ -109,6 +112,9 @@ 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 @@ -128,7 +134,6 @@ 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 @@ -138,13 +143,15 @@ 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 @@ -154,6 +161,9 @@ 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,7 +172,6 @@ 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 @@ -172,13 +181,15 @@ 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 @@ -188,6 +199,9 @@ 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. @@ -196,7 +210,6 @@ 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 @@ -206,13 +219,15 @@ 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 @@ -222,13 +237,15 @@ 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 @@ -238,13 +255,15 @@ 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 @@ -254,13 +273,15 @@ 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 @@ -270,6 +291,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -278,7 +302,6 @@ 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/exchange/Get-MonitoringItemHelp.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md index b720090806..200a6f2577 100644 --- a/exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-monitoringitemhelp +schema: 2.0.0 +title: Get-MonitoringItemHelp --- # Get-MonitoringItemHelp @@ -40,13 +41,15 @@ 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 @@ -56,6 +59,9 @@ 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 @@ -67,7 +73,6 @@ 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/exchange/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md index 993413da94..b8a9a76279 100644 --- a/exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-monitoringitemidentity +schema: 2.0.0 +title: Get-MonitoringItemIdentity --- # Get-MonitoringItemIdentity @@ -40,13 +41,15 @@ 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 @@ -56,6 +59,9 @@ 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 @@ -67,7 +73,6 @@ 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/exchange/Get-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md similarity index 87% rename from exchange/exchange-ps/exchange/Get-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md index 9bd1b19333..3cc1bb15a4 100644 --- a/exchange/exchange-ps/exchange/Get-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-moverequest +schema: 2.0.0 +title: Get-MoveRequest --- # Get-MoveRequest @@ -88,6 +89,9 @@ 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 @@ -118,7 +122,6 @@ 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 @@ -128,6 +131,9 @@ 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. @@ -136,7 +142,6 @@ 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 @@ -146,6 +151,9 @@ 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. @@ -156,7 +164,6 @@ 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 @@ -166,6 +173,9 @@ 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,7 +184,6 @@ 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 @@ -184,6 +193,9 @@ 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 @@ -207,7 +219,6 @@ 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 @@ -217,6 +228,9 @@ 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. @@ -227,7 +241,6 @@ 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 @@ -237,6 +250,9 @@ 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. @@ -245,7 +261,6 @@ 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 @@ -255,6 +270,9 @@ 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 @@ -273,7 +291,6 @@ 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 @@ -283,6 +300,9 @@ 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. @@ -291,7 +311,6 @@ 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 @@ -301,6 +320,9 @@ 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 @@ -312,7 +334,6 @@ 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 @@ -322,6 +343,9 @@ 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. @@ -332,7 +356,6 @@ 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 @@ -342,6 +365,9 @@ 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: @@ -361,7 +387,6 @@ 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 @@ -371,6 +396,9 @@ 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. @@ -379,7 +407,6 @@ 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 @@ -389,13 +416,15 @@ 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 @@ -405,6 +434,9 @@ 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. @@ -419,7 +451,6 @@ 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 @@ -429,6 +460,9 @@ 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: @@ -443,7 +477,6 @@ 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 @@ -453,6 +486,9 @@ 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: @@ -473,7 +509,6 @@ 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 @@ -483,6 +518,9 @@ 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. @@ -491,7 +529,6 @@ 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 @@ -501,6 +538,9 @@ 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. @@ -509,7 +549,6 @@ 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 @@ -519,6 +558,9 @@ 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: @@ -533,7 +575,6 @@ 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/exchange/Get-MoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md index 8f312cf0ae..f2cb66a897 100644 --- a/exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-moverequeststatistics +schema: 2.0.0 +title: Get-MoveRequestStatistics --- # Get-MoveRequestStatistics @@ -115,6 +116,9 @@ 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 @@ -131,7 +135,6 @@ 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 @@ -141,6 +144,9 @@ 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. @@ -157,7 +163,6 @@ 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 @@ -167,6 +172,9 @@ 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. @@ -177,7 +185,6 @@ 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 @@ -187,6 +194,9 @@ Accept wildcard characters: False ``` ### -Analysis + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Analysis Description }} @@ -195,7 +205,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: IdentityCloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -205,6 +214,9 @@ 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. @@ -215,7 +227,6 @@ 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 @@ -225,6 +236,9 @@ 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. @@ -233,7 +247,6 @@ 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 @@ -243,6 +256,9 @@ 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: @@ -255,7 +271,6 @@ 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 @@ -265,6 +280,9 @@ Accept wildcard characters: False ``` ### -DiagnosticOnly + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DiagnosticOnly Description }} @@ -273,7 +291,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: IdentityCloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -283,6 +300,9 @@ 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. @@ -291,7 +311,6 @@ 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 @@ -301,13 +320,15 @@ 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 @@ -317,6 +338,9 @@ 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. @@ -327,7 +351,6 @@ 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 @@ -337,6 +360,9 @@ 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: @@ -356,7 +382,6 @@ 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 @@ -366,13 +391,15 @@ 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/exchange/Get-MxRecordReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-MxRecordReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md index 1600495130..146aedf9be 100644 --- a/exchange/exchange-ps/exchange/Get-MxRecordReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-mxrecordreport +schema: 2.0.0 +title: Get-MxRecordReport --- # Get-MxRecordReport @@ -41,13 +42,15 @@ 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 @@ -57,13 +60,15 @@ 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/exchange/Get-MyAnalyticsFeatureConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md index ad5461513b..b63befffff 100644 --- a/exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md @@ -1,12 +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-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/exchange/get-myanalyticsfeatureconfig +schema: 2.0.0 +title: Get-MyAnalyticsFeatureConfig --- # Get-MyAnalyticsFeatureConfig @@ -60,13 +61,15 @@ 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 @@ -76,13 +79,15 @@ 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/exchange/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md rename to exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md index 3b753febcb..0cc59d2543 100644 --- a/exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-networkconnectioninfo +schema: 2.0.0 +title: Get-NetworkConnectionInfo --- # Get-NetworkConnectionInfo @@ -49,6 +50,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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,7 +86,6 @@ 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/exchange/Get-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-Notification.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Notification.md index a354e891db..2220e54f72 100644 --- a/exchange/exchange-ps/exchange/Get-Notification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-notification +schema: 2.0.0 +title: Get-Notification --- # Get-Notification @@ -83,13 +84,15 @@ 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 @@ -99,6 +102,9 @@ 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. @@ -111,7 +117,6 @@ 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 @@ -121,6 +126,9 @@ 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. @@ -129,7 +137,6 @@ 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 @@ -139,6 +146,9 @@ 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 @@ -149,9 +159,8 @@ The ProcessType parameter filters the results by the type of notification event. ```yaml Type: AsyncOperationType -Parameter Sets: Settings +Parameter Sets: Settings, Filter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -160,27 +169,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: AsyncOperationType -Parameter Sets: Filter -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -ResultSize -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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 @@ -190,6 +188,9 @@ 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". @@ -198,7 +199,6 @@ 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,6 +208,9 @@ 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. @@ -216,7 +219,6 @@ 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/exchange/Get-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-OMEConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md index 801c20e7db..773c2b86ef 100644 --- a/exchange/exchange-ps/exchange/Get-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-omeconfiguration +schema: 2.0.0 +title: Get-OMEConfiguration --- # Get-OMEConfiguration @@ -47,13 +48,15 @@ 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/exchange/Get-OMEMessageStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-OMEMessageStatus.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md index 1162642bbb..73f20be663 100644 --- a/exchange/exchange-ps/exchange/Get-OMEMessageStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-omemessagestatus +schema: 2.0.0 +title: Get-OMEMessageStatus --- # Get-OMEMessageStatus @@ -42,6 +43,9 @@ 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. @@ -50,7 +54,6 @@ 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/exchange/Get-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md index 274bd7b330..3f35fdf87e 100644 --- a/exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-oabvirtualdirectory +schema: 2.0.0 +title: Get-OabVirtualDirectory --- # Get-OabVirtualDirectory @@ -67,6 +68,9 @@ 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 @@ -81,7 +85,6 @@ 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 @@ -91,6 +94,9 @@ 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 @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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. @@ -122,7 +130,6 @@ 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,13 +139,15 @@ 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,6 +157,9 @@ 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. @@ -158,7 +170,6 @@ 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/exchange/Get-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md index dbf02a696b..b0b644d2e9 100644 --- a/exchange/exchange-ps/exchange/Get-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-offlineaddressbook +schema: 2.0.0 +title: Get-OfflineAddressBook --- # Get-OfflineAddressBook @@ -65,6 +66,9 @@ 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 @@ -77,7 +81,6 @@ 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 @@ -87,6 +90,9 @@ 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. @@ -105,7 +111,6 @@ 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 @@ -115,6 +120,9 @@ 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,7 +131,6 @@ 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/exchange/Get-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md index 18d268514c..2fcdf3905a 100644 --- a/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-onpremisesorganization +schema: 2.0.0 +title: Get-OnPremisesOrganization --- # Get-OnPremisesOrganization @@ -51,6 +52,9 @@ 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 @@ -61,7 +65,6 @@ 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/exchange/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md index 57d2252911..09d93c0340 100644 --- a/exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-onlinemeetingconfiguration +schema: 2.0.0 +title: Get-OnlineMeetingConfiguration --- # Get-OnlineMeetingConfiguration @@ -48,6 +49,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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/exchange/Get-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-OrganizationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md index 0d00218842..60d3d7e606 100644 --- a/exchange/exchange-ps/exchange/Get-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationconfig +schema: 2.0.0 +title: Get-OrganizationConfig --- # Get-OrganizationConfig @@ -60,6 +61,9 @@ 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. @@ -70,7 +74,6 @@ 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/exchange/Get-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-OrganizationRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md index 0c2f80f334..99be8a51e3 100644 --- a/exchange/exchange-ps/exchange/Get-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationrelationship +schema: 2.0.0 +title: Get-OrganizationRelationship --- # Get-OrganizationRelationship @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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,7 +82,6 @@ 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/exchange/Get-OrganizationSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-OrganizationSegment.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md index 12687a5a45..621edd9fba 100644 --- a/exchange/exchange-ps/exchange/Get-OrganizationSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationsegment +schema: 2.0.0 +title: Get-OrganizationSegment --- # Get-OrganizationSegment @@ -55,6 +56,9 @@ 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 @@ -65,7 +69,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-OrganizationalUnit.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md index 01e951b29f..061e8de309 100644 --- a/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationalunit +schema: 2.0.0 +title: Get-OrganizationalUnit --- # Get-OrganizationalUnit @@ -67,6 +68,9 @@ 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 @@ -80,7 +84,6 @@ 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 @@ -90,6 +93,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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 @@ -124,13 +131,15 @@ 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 @@ -140,13 +149,15 @@ 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 @@ -156,6 +167,9 @@ 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. @@ -164,7 +178,6 @@ 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/exchange/Get-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-OutboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md index ef832c3069..bcb259a91b 100644 --- a/exchange/exchange-ps/exchange/Get-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-outboundconnector +schema: 2.0.0 +title: Get-OutboundConnector --- # Get-OutboundConnector @@ -45,6 +46,9 @@ 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 @@ -55,7 +59,6 @@ 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 @@ -65,6 +68,9 @@ 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. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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. @@ -97,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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/exchange/Get-OutboundConnectorReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md index a111c53994..c74b5729f5 100644 --- a/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-outboundconnectorreport +schema: 2.0.0 +title: Get-OutboundConnectorReport --- # Get-OutboundConnectorReport @@ -41,13 +42,15 @@ 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 @@ -57,13 +60,15 @@ 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/exchange/Get-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-OutlookAnywhere.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md index e2189d867d..053135824e 100644 --- a/exchange/exchange-ps/exchange/Get-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookanywhere +schema: 2.0.0 +title: Get-OutlookAnywhere --- # Get-OutlookAnywhere @@ -60,6 +61,9 @@ 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 @@ -74,7 +78,6 @@ 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 @@ -84,6 +87,9 @@ 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 @@ -97,7 +103,6 @@ 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 @@ -107,6 +112,9 @@ 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. @@ -115,7 +123,6 @@ 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 @@ -125,13 +132,15 @@ 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,6 +150,9 @@ 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. @@ -151,7 +163,6 @@ 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/exchange/Get-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md index ed2ad0aa94..fe096106c3 100644 --- a/exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookprotectionrule +schema: 2.0.0 +title: Get-OutlookProtectionRule --- # Get-OutlookProtectionRule @@ -54,13 +55,15 @@ 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 @@ -70,6 +73,9 @@ 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,7 +84,6 @@ 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/exchange/Get-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-OutlookProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md index 72b2e977b7..184c99356e 100644 --- a/exchange/exchange-ps/exchange/Get-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookprovider +schema: 2.0.0 +title: Get-OutlookProvider --- # Get-OutlookProvider @@ -50,6 +51,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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/exchange/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md index d3d81a63ed..eee7415816 100644 --- a/exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-owamailboxpolicy +schema: 2.0.0 +title: Get-OwaMailboxPolicy --- # Get-OwaMailboxPolicy @@ -55,6 +56,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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,7 +89,6 @@ 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/exchange/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md index 6087a13fe7..c943befc4f 100644 --- a/exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-owavirtualdirectory +schema: 2.0.0 +title: Get-OwaVirtualDirectory --- # Get-OwaVirtualDirectory @@ -71,6 +72,9 @@ 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 @@ -85,7 +89,6 @@ 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 @@ -95,6 +98,9 @@ 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 @@ -108,7 +114,6 @@ 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 @@ -118,6 +123,9 @@ 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. @@ -126,7 +134,6 @@ 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 @@ -136,13 +143,15 @@ 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 @@ -152,6 +161,9 @@ 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. @@ -162,7 +174,6 @@ 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/exchange/Get-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-PartnerApplication.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md index 1e1e76f5db..15f4047ec5 100644 --- a/exchange/exchange-ps/exchange/Get-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-partnerapplication +schema: 2.0.0 +title: Get-PartnerApplication --- # Get-PartnerApplication @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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. @@ -86,7 +94,6 @@ 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/exchange/Get-PendingDelicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md index ca13e8b6fa..6a8048933c 100644 --- a/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-pendingdelicenseuser +schema: 2.0.0 +title: Get-PendingDelicenseUser --- # Get-PendingDelicenseUser @@ -61,6 +62,9 @@ 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: @@ -79,7 +83,6 @@ 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 @@ -89,13 +92,15 @@ 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 @@ -105,6 +110,9 @@ 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. @@ -113,7 +121,6 @@ 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/exchange/Get-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md index e646d32251..3d192c76a6 100644 --- a/exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-pendingfederateddomain +schema: 2.0.0 +title: Get-PendingFederatedDomain --- # Get-PendingFederatedDomain diff --git a/exchange/exchange-ps/exchange/Get-PerimeterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-PerimeterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md index 0559a00b0d..2dab525079 100644 --- a/exchange/exchange-ps/exchange/Get-PerimeterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-perimeterconfig +schema: 2.0.0 +title: Get-PerimeterConfig --- # Get-PerimeterConfig @@ -40,13 +41,15 @@ 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/exchange/Get-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md index 7e1d8bcf8e..1b3de471b8 100644 --- a/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-phishsimoverridepolicy +schema: 2.0.0 +title: Get-PhishSimOverridePolicy --- # Get-PhishSimOverridePolicy @@ -39,6 +40,9 @@ 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 @@ -50,7 +54,6 @@ The Identity parameter specifies the phishing simulation override policy that yo Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -60,13 +63,15 @@ 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/exchange/Get-Place.md b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-Place.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Place.md index c13137555b..05ade6040e 100644 --- a/exchange/exchange-ps/exchange/Get-Place.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-place +schema: 2.0.0 +title: Get-Place --- # Get-Place @@ -67,6 +68,9 @@ 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 @@ -82,7 +86,6 @@ You can't use this parameter with the Type parameter. Type: RecipientIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -92,13 +95,15 @@ 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 @@ -108,13 +113,15 @@ 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 @@ -124,6 +131,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Online + The Type parameter filters the results by the type of room mailbox. Valid values are: - Room @@ -136,7 +146,6 @@ You can't use this parameter with the Identity parameter. Type: GetPlaceType Parameter Sets: AllPlaces Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -146,13 +155,15 @@ 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/exchange/Get-PolicyConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-PolicyConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md index 7b985e28c4..dc05d4e083 100644 --- a/exchange/exchange-ps/exchange/Get-PolicyConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-policyconfig +schema: 2.0.0 +title: Get-PolicyConfig --- # Get-PolicyConfig @@ -39,13 +40,15 @@ 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/exchange/Get-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-PolicyTipConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md index 0704474cc3..12407779b6 100644 --- a/exchange/exchange-ps/exchange/Get-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-policytipconfig +schema: 2.0.0 +title: Get-PolicyTipConfig --- # Get-PolicyTipConfig @@ -65,6 +66,9 @@ 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. @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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 @@ -102,7 +108,6 @@ 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 @@ -112,6 +117,9 @@ 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. @@ -120,7 +128,6 @@ 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 @@ -130,6 +137,9 @@ 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). @@ -140,7 +150,6 @@ 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 @@ -150,6 +159,9 @@ 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. @@ -158,7 +170,6 @@ 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/exchange/Get-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-PopSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md index 4223b39960..9fae98933c 100644 --- a/exchange/exchange-ps/exchange/Get-PopSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-popsettings +schema: 2.0.0 +title: Get-PopSettings --- # Get-PopSettings @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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 @@ -77,7 +83,6 @@ 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/exchange/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md index b46a6dbd1e..3ca09a170c 100644 --- a/exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-powershellvirtualdirectory +schema: 2.0.0 +title: Get-PowerShellVirtualDirectory --- # Get-PowerShellVirtualDirectory @@ -67,6 +68,9 @@ 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 @@ -81,7 +85,6 @@ 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 @@ -91,6 +94,9 @@ 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 @@ -104,7 +110,6 @@ 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 @@ -114,6 +119,9 @@ 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. @@ -122,7 +130,6 @@ 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,13 +139,15 @@ 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,6 +157,9 @@ 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. @@ -158,7 +170,6 @@ 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/exchange/Get-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ProtectionAlert.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md index 2e99bc420c..8979e49fed 100644 --- a/exchange/exchange-ps/exchange/Get-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-protectionalert +schema: 2.0.0 +title: Get-ProtectionAlert --- # Get-ProtectionAlert @@ -48,6 +49,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,13 +71,15 @@ 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/exchange/Get-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-PublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md index 6236c3d432..59615e927d 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolder +schema: 2.0.0 +title: Get-PublicFolder --- # Get-PublicFolder @@ -118,13 +119,15 @@ 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 @@ -134,6 +137,9 @@ 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. @@ -142,7 +148,6 @@ 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 @@ -152,6 +157,9 @@ 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. @@ -160,7 +168,6 @@ 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 @@ -170,6 +177,9 @@ 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. @@ -178,7 +188,6 @@ 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,6 +197,9 @@ 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. @@ -198,7 +210,6 @@ 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 @@ -208,6 +219,9 @@ 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 @@ -225,7 +239,6 @@ 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 @@ -235,6 +248,9 @@ 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. @@ -243,7 +259,6 @@ 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 @@ -253,6 +268,9 @@ 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. @@ -261,7 +279,6 @@ 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 @@ -271,13 +288,15 @@ 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 @@ -287,6 +306,9 @@ 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: @@ -300,7 +322,6 @@ 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/exchange/Get-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md index 8827234280..6670ec99f2 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderadministrativepermission +schema: 2.0.0 +title: Get-PublicFolderAdministrativePermission --- # Get-PublicFolderAdministrativePermission @@ -65,6 +66,9 @@ 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. @@ -73,7 +77,6 @@ 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 @@ -83,13 +86,15 @@ 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 @@ -99,6 +104,9 @@ 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. @@ -107,7 +115,6 @@ You can't use this switch with the User parameter. Type: SwitchParameter Parameter Sets: Owner Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -117,6 +124,9 @@ 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 @@ -128,7 +138,6 @@ 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 @@ -138,6 +147,9 @@ 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 @@ -163,7 +175,6 @@ 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/exchange/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md index a78eb99b9f..e71bda8a1d 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderclientpermission +schema: 2.0.0 +title: Get-PublicFolderClientPermission --- # Get-PublicFolderClientPermission @@ -54,6 +55,9 @@ 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. @@ -62,7 +66,6 @@ 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,6 +75,9 @@ 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,7 +86,6 @@ 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,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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: @@ -121,7 +131,6 @@ 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 @@ -131,6 +140,9 @@ 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: @@ -142,7 +154,6 @@ 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 @@ -152,6 +163,9 @@ 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 @@ -171,7 +185,6 @@ 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/exchange/Get-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md index 163d873ee4..6ea3731e3b 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderdatabase +schema: 2.0.0 +title: Get-PublicFolderDatabase --- # Get-PublicFolderDatabase @@ -73,6 +74,9 @@ 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 @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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 @@ -110,7 +116,6 @@ 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 @@ -120,13 +125,15 @@ 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 @@ -136,6 +143,9 @@ 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. @@ -146,7 +156,6 @@ 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 @@ -156,13 +165,15 @@ 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 @@ -172,13 +183,15 @@ 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/exchange/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md index 7e8d13e1d4..63347cecab 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderitemstatistics +schema: 2.0.0 +title: Get-PublicFolderItemStatistics --- # Get-PublicFolderItemStatistics @@ -64,13 +65,15 @@ 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 @@ -80,6 +83,9 @@ 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. @@ -88,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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 @@ -115,7 +123,6 @@ 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 @@ -125,6 +132,9 @@ 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. @@ -133,7 +143,6 @@ 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 @@ -143,6 +152,9 @@ 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: @@ -156,7 +168,6 @@ 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/exchange/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md index d7b0c82238..cdcb611e24 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxdiagnostics +schema: 2.0.0 +title: Get-PublicFolderMailboxDiagnostics --- # Get-PublicFolderMailboxDiagnostics @@ -52,6 +53,9 @@ 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: @@ -71,7 +75,6 @@ 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 @@ -81,6 +84,9 @@ 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`. @@ -90,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ 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. @@ -108,7 +116,6 @@ 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 @@ -118,13 +125,15 @@ 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 @@ -134,6 +143,9 @@ 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: @@ -153,7 +165,6 @@ 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 @@ -163,13 +174,15 @@ 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/exchange/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md index 4fe2797ff4..8856a8e973 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxmigrationrequest +schema: 2.0.0 +title: Get-PublicFolderMailboxMigrationRequest --- # Get-PublicFolderMailboxMigrationRequest @@ -83,6 +84,9 @@ 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: @@ -98,7 +102,6 @@ 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 @@ -108,6 +111,9 @@ 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. @@ -116,7 +122,6 @@ 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 @@ -126,6 +131,9 @@ 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. @@ -134,7 +142,6 @@ 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 @@ -144,6 +151,9 @@ 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: @@ -157,7 +167,6 @@ 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 @@ -167,6 +176,9 @@ 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. @@ -175,7 +187,6 @@ 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 @@ -185,6 +196,9 @@ 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: @@ -199,7 +213,6 @@ 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 @@ -209,13 +222,15 @@ 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 @@ -225,6 +240,9 @@ 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 @@ -244,7 +262,6 @@ 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 @@ -254,6 +271,9 @@ 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. @@ -262,7 +282,6 @@ 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/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md index cb164285ad..1bf524de7e 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxmigrationrequeststatistics +schema: 2.0.0 +title: Get-PublicFolderMailboxMigrationRequestStatistics --- # Get-PublicFolderMailboxMigrationRequestStatistics @@ -75,6 +76,9 @@ 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. @@ -83,7 +87,6 @@ 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 @@ -93,6 +96,9 @@ 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. @@ -109,7 +115,6 @@ 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 @@ -119,6 +124,9 @@ 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. @@ -129,7 +137,6 @@ 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 @@ -139,6 +146,9 @@ 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. @@ -147,7 +157,6 @@ 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 @@ -157,6 +166,9 @@ 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. @@ -165,7 +177,6 @@ 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 @@ -175,6 +186,9 @@ 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. @@ -183,7 +197,6 @@ 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 @@ -193,13 +206,15 @@ 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 @@ -209,6 +224,9 @@ Accept wildcard characters: False ``` ### -IncludeSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeSkippedItems Description }} @@ -217,7 +235,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: IdentityCloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -227,13 +244,15 @@ 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 @@ -243,6 +262,9 @@ 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. @@ -253,7 +275,6 @@ 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/exchange/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md index c001744a6d..6b58dc709f 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermigrationrequest +schema: 2.0.0 +title: Get-PublicFolderMigrationRequest --- # Get-PublicFolderMigrationRequest @@ -66,6 +67,9 @@ 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 @@ -77,7 +81,6 @@ 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 @@ -87,6 +90,9 @@ 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. @@ -95,7 +101,6 @@ 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 @@ -105,13 +110,15 @@ 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 @@ -121,6 +128,9 @@ 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. @@ -132,7 +142,6 @@ 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 @@ -142,6 +151,9 @@ 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. @@ -150,7 +162,6 @@ 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 @@ -160,6 +171,9 @@ 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 @@ -172,7 +186,6 @@ 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 @@ -182,13 +195,15 @@ 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 @@ -198,6 +213,9 @@ 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 @@ -217,7 +235,6 @@ 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 @@ -227,6 +244,9 @@ 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. @@ -235,7 +255,6 @@ 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/exchange/Get-PublicFolderMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md index 2ef492d5cb..44e33561bb 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermigrationrequeststatistics +schema: 2.0.0 +title: Get-PublicFolderMigrationRequestStatistics --- # Get-PublicFolderMigrationRequestStatistics @@ -68,6 +69,9 @@ 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 @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ 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: @@ -103,7 +109,6 @@ 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 @@ -113,6 +118,9 @@ 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. @@ -121,7 +129,6 @@ 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 @@ -131,13 +138,15 @@ 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 @@ -147,13 +156,15 @@ 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 @@ -163,13 +174,15 @@ 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 @@ -179,13 +192,15 @@ 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 @@ -195,6 +210,9 @@ 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. @@ -203,7 +221,6 @@ 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/exchange/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md index 5d234a047b..0a13b7e42e 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermoverequest +schema: 2.0.0 +title: Get-PublicFolderMoveRequest --- # Get-PublicFolderMoveRequest @@ -64,6 +65,9 @@ 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: @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ Accept wildcard characters: False ``` ### -AccountPartition + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AccountPartition Description }} @@ -97,7 +103,6 @@ This parameter is available only in the cloud-based service. Type: AccountPartitionIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -107,6 +112,9 @@ 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. @@ -115,7 +123,6 @@ 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 @@ -125,6 +132,9 @@ 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. @@ -133,7 +143,6 @@ 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 @@ -143,6 +152,9 @@ 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. @@ -154,7 +166,6 @@ 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 @@ -164,6 +175,9 @@ 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. @@ -172,7 +186,6 @@ 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 @@ -182,6 +195,9 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Organization Description }} @@ -190,7 +206,6 @@ This parameter is available only in the cloud-based service. Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -200,6 +215,9 @@ 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 @@ -212,7 +230,6 @@ 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 @@ -222,13 +239,15 @@ 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 @@ -238,6 +257,9 @@ 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 @@ -257,7 +279,6 @@ 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 @@ -267,6 +288,9 @@ 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. @@ -275,7 +299,6 @@ 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/exchange/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md index 475fc29578..23c061b708 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermoverequeststatistics +schema: 2.0.0 +title: Get-PublicFolderMoveRequestStatistics --- # Get-PublicFolderMoveRequestStatistics @@ -68,6 +69,9 @@ 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. @@ -76,7 +80,6 @@ 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 @@ -86,6 +89,9 @@ 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: @@ -100,7 +106,6 @@ 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 @@ -110,6 +115,9 @@ 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. @@ -118,7 +126,6 @@ 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 @@ -128,13 +135,15 @@ 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 @@ -144,6 +153,9 @@ Accept wildcard characters: False ``` ### -DiagnosticInfo + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DiagnosticInfo Description }} @@ -152,7 +164,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -162,6 +173,9 @@ 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. @@ -170,7 +184,6 @@ 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 @@ -180,13 +193,15 @@ 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 @@ -196,6 +211,9 @@ Accept wildcard characters: False ``` ### -IncludeSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeSkippedItems Description }} @@ -204,7 +222,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -214,13 +231,15 @@ 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 @@ -230,6 +249,9 @@ 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. @@ -238,7 +260,6 @@ 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/exchange/Get-PublicFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md index 023a6d31c0..f97b9cbb66 100644 --- a/exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderstatistics +schema: 2.0.0 +title: Get-PublicFolderStatistics --- # Get-PublicFolderStatistics @@ -44,6 +45,9 @@ 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. @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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 @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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. @@ -115,7 +125,6 @@ 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 @@ -125,6 +134,9 @@ 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: @@ -138,7 +150,6 @@ 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/exchange/Get-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-QuarantineMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md index afa39b7a2e..2defa40d8a 100644 --- a/exchange/exchange-ps/exchange/Get-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinemessage +schema: 2.0.0 +title: Get-QuarantineMessage --- # Get-QuarantineMessage @@ -102,6 +103,9 @@ 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`. @@ -110,7 +114,6 @@ 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 @@ -120,6 +123,9 @@ 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 @@ -131,7 +137,6 @@ 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 @@ -141,13 +146,15 @@ 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 @@ -157,6 +164,9 @@ 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". @@ -167,7 +177,6 @@ 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 @@ -177,6 +186,9 @@ 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". @@ -185,7 +197,6 @@ 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 @@ -195,6 +206,9 @@ 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 @@ -206,7 +220,6 @@ 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 @@ -216,13 +229,15 @@ 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 @@ -232,13 +247,15 @@ 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 @@ -248,13 +265,15 @@ 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 @@ -264,13 +283,15 @@ 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 @@ -280,13 +301,15 @@ 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 @@ -296,6 +319,9 @@ 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 @@ -306,7 +332,6 @@ 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 @@ -316,6 +341,9 @@ 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 @@ -331,7 +359,6 @@ 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 @@ -341,6 +368,9 @@ 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 @@ -363,7 +393,6 @@ 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 @@ -373,13 +402,15 @@ 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 @@ -389,6 +420,9 @@ 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. @@ -397,7 +431,6 @@ 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 @@ -407,6 +440,9 @@ 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 @@ -425,7 +461,6 @@ 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 @@ -435,6 +470,9 @@ 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. @@ -444,7 +482,6 @@ 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 @@ -454,13 +491,15 @@ 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 @@ -470,6 +509,9 @@ 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". @@ -480,7 +522,6 @@ 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 @@ -490,6 +531,9 @@ 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". @@ -500,7 +544,6 @@ 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 @@ -510,13 +553,15 @@ 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 @@ -526,6 +571,9 @@ 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: @@ -539,7 +587,6 @@ 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 @@ -549,6 +596,9 @@ 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 @@ -568,7 +618,6 @@ 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/exchange/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md rename to exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md index 9dac21f945..7a971ac4b8 100644 --- a/exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinemessageheader +schema: 2.0.0 +title: Get-QuarantineMessageHeader --- # Get-QuarantineMessageHeader @@ -53,6 +54,9 @@ 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. @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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 @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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/exchange/Get-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-QuarantinePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md index 93177a8f2a..f137e4ae34 100644 --- a/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinepolicy +schema: 2.0.0 +title: Get-QuarantinePolicy --- # Get-QuarantinePolicy @@ -57,6 +58,9 @@ 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 @@ -67,7 +71,6 @@ 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 @@ -77,6 +80,9 @@ 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. @@ -87,7 +93,6 @@ 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/exchange/Get-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-Queue.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Queue.md index 1b83dcd4a3..6ea72114de 100644 --- a/exchange/exchange-ps/exchange/Get-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-queue +schema: 2.0.0 +title: Get-Queue --- # Get-Queue @@ -87,13 +88,15 @@ 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 @@ -103,13 +106,15 @@ 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 @@ -119,13 +124,15 @@ 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 @@ -135,6 +142,9 @@ 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 @@ -145,7 +155,6 @@ 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 @@ -155,6 +164,9 @@ 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 ("). @@ -163,7 +175,6 @@ 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 @@ -173,6 +184,9 @@ 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 @@ -183,7 +197,6 @@ 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 @@ -193,13 +206,15 @@ 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 @@ -209,13 +224,15 @@ 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 @@ -225,13 +242,15 @@ 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 @@ -241,13 +260,15 @@ 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 @@ -257,6 +278,9 @@ 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 @@ -272,7 +296,6 @@ 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 @@ -282,6 +305,9 @@ 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. @@ -290,7 +316,6 @@ 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/exchange/Get-QueueDigest.md b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-QueueDigest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md index a45a074bd3..806b884679 100644 --- a/exchange/exchange-ps/exchange/Get-QueueDigest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-queuedigest +schema: 2.0.0 +title: Get-QueueDigest --- # Get-QueueDigest @@ -88,6 +89,9 @@ 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. @@ -96,7 +100,6 @@ 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 @@ -106,6 +109,9 @@ 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. @@ -114,7 +120,6 @@ 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 @@ -124,6 +129,9 @@ 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. @@ -132,7 +140,6 @@ 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 @@ -142,6 +149,9 @@ 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. @@ -150,7 +160,6 @@ 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 @@ -160,13 +169,15 @@ 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 @@ -176,6 +187,9 @@ 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 ("). @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ 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 @@ -210,7 +226,6 @@ 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 @@ -220,13 +235,15 @@ 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 @@ -236,6 +253,9 @@ 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. @@ -244,7 +264,6 @@ 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/exchange/Get-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-RMSTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md index e495368203..310ceadb9a 100644 --- a/exchange/exchange-ps/exchange/Get-RMSTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-rmstemplate +schema: 2.0.0 +title: Get-RMSTemplate --- # Get-RMSTemplate @@ -53,13 +54,15 @@ 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 @@ -69,6 +72,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,6 +110,9 @@ 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: @@ -115,7 +125,6 @@ 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 @@ -125,6 +134,9 @@ 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: @@ -137,7 +149,6 @@ 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/exchange/Get-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-ReceiveConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md index f34ec98584..073dd1c324 100644 --- a/exchange/exchange-ps/exchange/Get-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-receiveconnector +schema: 2.0.0 +title: Get-ReceiveConnector --- # Get-ReceiveConnector @@ -58,6 +59,9 @@ 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 @@ -71,7 +75,6 @@ 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 @@ -81,6 +84,9 @@ 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. @@ -89,7 +95,6 @@ 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,6 +104,9 @@ 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 @@ -112,7 +120,6 @@ 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/exchange/Get-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md similarity index 86% rename from exchange/exchange-ps/exchange/Get-Recipient.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md index 4b5a71f8b1..f5782d0bb3 100644 --- a/exchange/exchange-ps/exchange/Get-Recipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recipient +schema: 2.0.0 +title: Get-Recipient --- # Get-Recipient @@ -144,6 +145,9 @@ 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 @@ -157,7 +161,6 @@ 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 @@ -167,6 +170,9 @@ 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) @@ -179,7 +185,6 @@ 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 @@ -189,6 +194,9 @@ 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: @@ -200,7 +208,6 @@ 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 @@ -210,13 +217,15 @@ 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 @@ -226,6 +235,9 @@ 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. @@ -234,7 +246,6 @@ 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 @@ -244,6 +255,9 @@ 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. @@ -254,7 +268,6 @@ 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 @@ -264,6 +277,9 @@ 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: @@ -276,7 +292,6 @@ 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 @@ -286,6 +301,9 @@ 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. @@ -294,7 +312,6 @@ 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 @@ -304,6 +321,9 @@ 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. @@ -319,7 +339,6 @@ 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 @@ -329,6 +348,9 @@ 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. @@ -342,7 +364,6 @@ 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 @@ -352,13 +373,15 @@ 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 @@ -368,6 +391,9 @@ Accept wildcard characters: False ``` ### -IncludeManagerWithDisplayName + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill IncludeManagerWithDisplayName Description }} @@ -376,7 +402,6 @@ 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 @@ -386,6 +411,9 @@ 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. @@ -396,7 +424,6 @@ 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 @@ -406,6 +433,9 @@ 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 @@ -417,7 +447,6 @@ 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 @@ -427,13 +456,15 @@ 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 @@ -443,13 +474,15 @@ 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 @@ -459,6 +492,9 @@ 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,7 +507,6 @@ 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 @@ -481,13 +516,15 @@ 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 @@ -497,6 +534,9 @@ 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 @@ -514,7 +554,6 @@ 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 @@ -524,6 +563,9 @@ 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 @@ -563,7 +605,6 @@ 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 @@ -573,13 +614,15 @@ 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 @@ -589,6 +632,9 @@ 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. @@ -608,7 +654,6 @@ 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/exchange/Get-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md index 76a02ece24..f2fee7f891 100644 --- a/exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientfilterconfig +schema: 2.0.0 +title: Get-RecipientFilterConfig --- # Get-RecipientFilterConfig @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-RecipientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md index 985fc7ff66..3fffbada07 100644 --- a/exchange/exchange-ps/exchange/Get-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientpermission +schema: 2.0.0 +title: Get-RecipientPermission --- # Get-RecipientPermission @@ -58,6 +59,9 @@ 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 @@ -79,7 +83,6 @@ 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 @@ -89,13 +92,15 @@ 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 @@ -105,13 +110,15 @@ 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 @@ -121,13 +128,15 @@ 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 @@ -137,6 +146,9 @@ 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 @@ -160,7 +172,6 @@ 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/exchange/Get-RecipientStatisticsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md index 8f2d888cba..8e8a3d466a 100644 --- a/exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientstatisticsreport +schema: 2.0.0 +title: Get-RecipientStatisticsReport --- # Get-RecipientStatisticsReport diff --git a/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md index 4f413a8bf3..a8327ce267 100644 --- a/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recordreviewnotificationtemplateconfig +schema: 2.0.0 +title: Get-RecordReviewNotificationTemplateConfig --- # Get-RecordReviewNotificationTemplateConfig diff --git a/exchange/exchange-ps/exchange/Get-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-RecoverableItems.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md index aebb11746e..e04ed7fc8e 100644 --- a/exchange/exchange-ps/exchange/Get-RecoverableItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-recoverableitems +schema: 2.0.0 +title: Get-RecoverableItems --- # Get-RecoverableItems @@ -74,6 +75,9 @@ 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 @@ -91,9 +95,8 @@ In Exchange Online, you can specify multiple mailboxes separated by commas. If t ```yaml Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: OnPremises +Parameter Sets: OnPremises, Cloud Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -102,20 +105,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: GeneralMailboxOrMailUserIdParameter[] -Parameter Sets: Cloud -Aliases: -Applicable: Exchange Online +### -EntryID -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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.). @@ -124,7 +117,6 @@ 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 @@ -134,6 +126,9 @@ 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". @@ -142,7 +137,6 @@ 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 @@ -152,6 +146,9 @@ 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) @@ -164,7 +161,6 @@ 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 @@ -174,6 +170,9 @@ 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". @@ -182,7 +181,6 @@ 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 @@ -192,13 +190,15 @@ 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,6 +208,9 @@ 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. @@ -218,7 +221,6 @@ 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 @@ -228,6 +230,9 @@ Accept wildcard characters: False ``` ### -PolicyTag + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill PolicyTag Description }} @@ -236,7 +241,6 @@ This parameter is available only in the cloud-based service. Type: String[] Parameter Sets: Cloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -246,13 +250,15 @@ 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 @@ -262,6 +268,9 @@ Accept wildcard characters: False ``` ### -SkipCount + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipCount Description }} @@ -270,7 +279,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -280,6 +288,9 @@ 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. @@ -294,7 +305,6 @@ 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 @@ -304,13 +314,15 @@ 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/exchange/Get-RegulatoryComplianceUI.md b/exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md index 69ceb96099..55a6f318c1 100644 --- a/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md @@ -1,9 +1,11 @@ --- +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/exchange/get-regulatorycomplianceui -applicable: Security & Compliance -title: Get-RegulatoryComplianceUI schema: 2.0.0 +title: Get-RegulatoryComplianceUI --- # Get-RegulatoryComplianceUI diff --git a/exchange/exchange-ps/exchange/Get-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-RemoteDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md index ea01811a75..71234026a9 100644 --- a/exchange/exchange-ps/exchange/Get-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-remotedomain +schema: 2.0.0 +title: Get-RemoteDomain --- # Get-RemoteDomain @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ 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,7 +92,6 @@ 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 @@ -96,6 +101,9 @@ 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. @@ -104,7 +112,6 @@ 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/exchange/Get-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md index f40415ec08..3a6e18f1f1 100644 --- a/exchange/exchange-ps/exchange/Get-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-remotemailbox +schema: 2.0.0 +title: Get-RemoteMailbox --- # Get-RemoteMailbox @@ -83,6 +84,9 @@ 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 @@ -100,7 +104,6 @@ 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 @@ -110,6 +113,9 @@ 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) @@ -122,7 +128,6 @@ 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 @@ -132,13 +137,15 @@ 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 @@ -148,6 +155,9 @@ 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). @@ -156,7 +166,6 @@ 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 @@ -166,13 +175,15 @@ 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 @@ -182,6 +193,9 @@ 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. @@ -197,7 +211,6 @@ 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 @@ -207,6 +220,9 @@ 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: @@ -218,7 +234,6 @@ 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 @@ -228,6 +243,9 @@ 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: @@ -241,7 +259,6 @@ 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 @@ -251,6 +268,9 @@ 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. @@ -261,7 +281,6 @@ 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 @@ -271,6 +290,9 @@ 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). @@ -279,7 +301,6 @@ 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 @@ -289,6 +310,9 @@ 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. @@ -303,7 +327,6 @@ 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/exchange/Get-ReportExecutionInstance.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md index 134a709559..9c2614278a 100644 --- a/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-reportexecutioninstance +schema: 2.0.0 +title: Get-ReportExecutionInstance --- # Get-ReportExecutionInstance @@ -48,13 +49,15 @@ 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 @@ -64,13 +67,15 @@ 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/exchange/Get-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md index 483f073460..4d75553929 100644 --- a/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-reportsubmissionpolicy +schema: 2.0.0 +title: Get-ReportSubmissionPolicy --- # Get-ReportSubmissionPolicy @@ -43,13 +44,15 @@ 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/exchange/Get-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md index f64f8d899b..3e88572b98 100644 --- a/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-reportsubmissionrule +schema: 2.0.0 +title: Get-ReportSubmissionRule --- # Get-ReportSubmissionRule @@ -39,13 +40,15 @@ 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 @@ -55,6 +58,9 @@ 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 @@ -67,7 +73,6 @@ Type: RuleState Parameter Sets: (All) Aliases: Accepted values: Enabled, Disabled -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Get-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ResourceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md index e5087116d5..aad7943c20 100644 --- a/exchange/exchange-ps/exchange/Get-ResourceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-resourceconfig +schema: 2.0.0 +title: Get-ResourceConfig --- # Get-ResourceConfig @@ -41,6 +42,9 @@ 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. @@ -49,7 +53,6 @@ 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 @@ -59,6 +62,9 @@ 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. @@ -67,7 +73,6 @@ 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/exchange/Get-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ResubmitRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md index e6837d4223..c0b3a0b24c 100644 --- a/exchange/exchange-ps/exchange/Get-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-resubmitrequest +schema: 2.0.0 +title: Get-ResubmitRequest --- # Get-ResubmitRequest @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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 @@ -77,7 +83,6 @@ 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/exchange/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md index fbb20052f5..c24c5f9623 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-retentioncompliancepolicy +schema: 2.0.0 +title: Get-RetentionCompliancePolicy --- # Get-RetentionCompliancePolicy @@ -61,6 +62,9 @@ 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 @@ -71,7 +75,6 @@ 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 @@ -81,6 +84,9 @@ 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. @@ -89,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,13 +122,15 @@ 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 @@ -131,6 +140,9 @@ 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). @@ -139,7 +151,6 @@ 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 @@ -149,13 +160,15 @@ 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 @@ -165,6 +178,9 @@ 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. @@ -173,7 +189,6 @@ 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 @@ -183,13 +198,15 @@ 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/exchange/Get-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md index 9c1279ce96..1ebe884318 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-retentioncompliancerule +schema: 2.0.0 +title: Get-RetentionComplianceRule --- # Get-RetentionComplianceRule @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ 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 @@ -88,7 +94,6 @@ 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 @@ -98,13 +103,15 @@ 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/exchange/Get-RetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-RetentionEvent.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md index c650acf830..4ebabac162 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionevent +schema: 2.0.0 +title: Get-RetentionEvent --- # Get-RetentionEvent @@ -49,13 +50,15 @@ 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 @@ -65,13 +68,15 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Get-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-RetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md index 231c381cff..9e3bf97e36 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionpolicy +schema: 2.0.0 +title: Get-RetentionPolicy --- # Get-RetentionPolicy @@ -43,13 +44,15 @@ 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 @@ -59,6 +62,9 @@ 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. @@ -67,7 +73,6 @@ 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/exchange/Get-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md index 53ece7d08e..fe029082c5 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionpolicytag +schema: 2.0.0 +title: Get-RetentionPolicyTag --- # Get-RetentionPolicyTag @@ -83,13 +84,15 @@ 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 @@ -99,6 +102,9 @@ 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,7 +113,6 @@ 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,13 +122,15 @@ 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 @@ -133,6 +140,9 @@ 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 @@ -152,7 +162,6 @@ 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 @@ -162,6 +171,9 @@ 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. @@ -170,7 +182,6 @@ 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 @@ -180,6 +191,9 @@ 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 @@ -204,7 +218,6 @@ 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/exchange/Get-ReviewItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-ReviewItems.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md index b9fa1c3b40..cbad24d97a 100644 --- a/exchange/exchange-ps/exchange/Get-ReviewItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-reviewitems +schema: 2.0.0 +title: Get-ReviewItems --- # Get-ReviewItems @@ -84,6 +85,9 @@ 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`. @@ -92,7 +96,6 @@ 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 @@ -102,6 +105,9 @@ 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. @@ -111,7 +117,6 @@ 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 @@ -121,6 +126,9 @@ 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. @@ -130,7 +138,6 @@ The IncludeHeaders parameter specifies whether headers are returned as a propert Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -140,6 +147,9 @@ 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. @@ -151,7 +161,6 @@ 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/exchange/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md index 20474cb2b2..5d76176ab4 100644 --- a/exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-roleassignmentpolicy +schema: 2.0.0 +title: Get-RoleAssignmentPolicy --- # Get-RoleAssignmentPolicy @@ -63,13 +64,15 @@ 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 @@ -79,6 +82,9 @@ 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,7 +95,6 @@ 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/exchange/Get-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-RoleGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md index 7e6cfdc324..a4fc9de139 100644 --- a/exchange/exchange-ps/exchange/Get-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-rolegroup +schema: 2.0.0 +title: Get-RoleGroup --- # Get-RoleGroup @@ -69,6 +70,9 @@ 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. @@ -77,7 +81,6 @@ 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 @@ -87,6 +90,9 @@ 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,7 +101,6 @@ 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,6 +110,9 @@ 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. @@ -129,7 +137,6 @@ 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 @@ -139,6 +146,9 @@ 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. @@ -151,7 +161,6 @@ 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 @@ -161,13 +170,15 @@ 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 @@ -177,6 +188,9 @@ 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. @@ -187,7 +201,6 @@ 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 @@ -197,6 +210,9 @@ 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. @@ -210,7 +226,6 @@ 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/exchange/Get-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-RoleGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md index 8416becc8f..42ef83c9f5 100644 --- a/exchange/exchange-ps/exchange/Get-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-rolegroupmember +schema: 2.0.0 +title: Get-RoleGroupMember --- # Get-RoleGroupMember @@ -52,13 +53,15 @@ 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 @@ -68,6 +71,9 @@ 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,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Get-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md index 2f0f384197..d3508105f6 100644 --- a/exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-routinggroupconnector +schema: 2.0.0 +title: Get-RoutingGroupConnector --- # Get-RoutingGroupConnector @@ -43,13 +44,15 @@ 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 @@ -59,13 +62,15 @@ 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/exchange/Get-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-RpcClientAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md index adedda699a..ecda42dfa5 100644 --- a/exchange/exchange-ps/exchange/Get-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-rpcclientaccess +schema: 2.0.0 +title: Get-RpcClientAccess --- # Get-RpcClientAccess @@ -48,13 +49,15 @@ 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 @@ -64,6 +67,9 @@ 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: @@ -77,7 +83,6 @@ 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/exchange/Get-SCInsights.md b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SCInsights.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md index 7675f4455f..7001b4d71c 100644 --- a/exchange/exchange-ps/exchange/Get-SCInsights.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-scinsights +schema: 2.0.0 +title: Get-SCInsights --- # Get-SCInsights @@ -55,6 +56,9 @@ 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: @@ -66,7 +70,6 @@ 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/exchange/Get-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md index 1330056090..d8f8b9a038 100644 --- a/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safeattachmentpolicy +schema: 2.0.0 +title: Get-SafeAttachmentPolicy --- # Get-SafeAttachmentPolicy @@ -49,6 +50,9 @@ 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: @@ -61,7 +65,6 @@ 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/exchange/Get-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md index 0dded56904..3a6663e3ee 100644 --- a/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safeattachmentrule +schema: 2.0.0 +title: Get-SafeAttachmentRule --- # Get-SafeAttachmentRule @@ -50,6 +51,9 @@ 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: @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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/exchange/Get-SafeLinksAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md index 27c72f641a..429e30cd74 100644 --- a/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksaggregatereport +schema: 2.0.0 +title: Get-SafeLinksAggregateReport --- # Get-SafeLinksAggregateReport @@ -56,6 +57,9 @@ 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 @@ -73,7 +77,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -83,6 +86,9 @@ 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 @@ -95,7 +101,6 @@ 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 @@ -105,6 +110,9 @@ 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. @@ -115,7 +123,6 @@ 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 @@ -125,6 +132,9 @@ 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. @@ -135,7 +145,6 @@ 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 @@ -145,6 +154,9 @@ 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: @@ -156,7 +168,6 @@ 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/exchange/Get-SafeLinksDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md index ef6379a4e6..907ed003a4 100644 --- a/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksdetailreport +schema: 2.0.0 +title: Get-SafeLinksDetailReport --- # Get-SafeLinksDetailReport @@ -75,6 +76,9 @@ 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. @@ -94,7 +98,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -104,6 +107,9 @@ 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 @@ -116,7 +122,6 @@ 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 @@ -126,6 +131,9 @@ 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. @@ -134,7 +142,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -144,6 +151,9 @@ 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. @@ -154,7 +164,6 @@ 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 @@ -164,13 +173,15 @@ 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 @@ -180,13 +191,15 @@ 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 @@ -196,6 +209,9 @@ 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. @@ -204,7 +220,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -214,6 +229,9 @@ 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. @@ -224,7 +242,6 @@ 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/exchange/Get-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md index 63a24625de..08acece5cb 100644 --- a/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinkspolicy +schema: 2.0.0 +title: Get-SafeLinksPolicy --- # Get-SafeLinksPolicy @@ -49,6 +50,9 @@ 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: @@ -61,7 +65,6 @@ 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/exchange/Get-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md index 279ebc68cd..988a89fb5b 100644 --- a/exchange/exchange-ps/exchange/Get-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksrule +schema: 2.0.0 +title: Get-SafeLinksRule --- # Get-SafeLinksRule @@ -50,6 +51,9 @@ 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: @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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/exchange/Get-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md index 562980e971..cc7cd0a6ad 100644 --- a/exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-searchdocumentformat +schema: 2.0.0 +title: Get-SearchDocumentFormat --- # Get-SearchDocumentFormat @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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: @@ -81,7 +87,6 @@ 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/exchange/Get-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md index a986f97d43..4fec673bf9 100644 --- a/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-secopsoverridepolicy +schema: 2.0.0 +title: Get-SecOpsOverridePolicy --- # Get-SecOpsOverridePolicy @@ -41,6 +42,9 @@ 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 @@ -52,7 +56,6 @@ 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 @@ -62,13 +65,15 @@ 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/exchange/Get-SecurityPrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md similarity index 87% rename from exchange/exchange-ps/exchange/Get-SecurityPrincipal.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md index 458dcbe1b3..60cd84e5d7 100644 --- a/exchange/exchange-ps/exchange/Get-SecurityPrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-securityprincipal +schema: 2.0.0 +title: Get-SecurityPrincipal --- # Get-SecurityPrincipal @@ -70,13 +71,15 @@ 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 @@ -86,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -104,6 +109,9 @@ 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. @@ -119,7 +127,6 @@ 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 @@ -129,6 +136,9 @@ 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. @@ -139,7 +149,6 @@ 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 @@ -149,6 +158,9 @@ 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 @@ -160,7 +172,6 @@ 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 @@ -170,13 +181,15 @@ 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 @@ -186,13 +199,15 @@ 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 @@ -202,6 +217,9 @@ 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 @@ -217,7 +235,6 @@ 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/exchange/Get-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-SendConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md index b285afa86f..cb8c2335a8 100644 --- a/exchange/exchange-ps/exchange/Get-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sendconnector +schema: 2.0.0 +title: Get-SendConnector --- # Get-SendConnector @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-SenderFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md index b89a8e9412..0f8f0a44f0 100644 --- a/exchange/exchange-ps/exchange/Get-SenderFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-senderfilterconfig +schema: 2.0.0 +title: Get-SenderFilterConfig --- # Get-SenderFilterConfig @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SenderIdConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md index 1e0dad4cd1..9857a91e83 100644 --- a/exchange/exchange-ps/exchange/Get-SenderIdConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-senderidconfig +schema: 2.0.0 +title: Get-SenderIdConfig --- # Get-SenderIdConfig @@ -40,6 +41,9 @@ 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. @@ -48,7 +52,6 @@ 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/exchange/Get-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SenderReputationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md index 83288be5e1..d3af2e2f8c 100644 --- a/exchange/exchange-ps/exchange/Get-SenderReputationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-senderreputationconfig +schema: 2.0.0 +title: Get-SenderReputationConfig --- # Get-SenderReputationConfig @@ -40,6 +41,9 @@ 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. @@ -48,7 +52,6 @@ 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/exchange/Get-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ServerComponentState.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md index 2008d37985..28ca1e828e 100644 --- a/exchange/exchange-ps/exchange/Get-ServerComponentState.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-servercomponentstate +schema: 2.0.0 +title: Get-ServerComponentState --- # Get-ServerComponentState @@ -49,6 +50,9 @@ 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 @@ -59,7 +63,6 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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/exchange/Get-ServerHealth.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-ServerHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md index 329cfe409b..5ba6c138e5 100644 --- a/exchange/exchange-ps/exchange/Get-ServerHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-serverhealth +schema: 2.0.0 +title: Get-ServerHealth --- # Get-ServerHealth @@ -53,6 +54,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,13 +95,15 @@ 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/exchange/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md index 2986dafdb9..711ef32f24 100644 --- a/exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-servermonitoringoverride +schema: 2.0.0 +title: Get-ServerMonitoringOverride --- # Get-ServerMonitoringOverride @@ -40,6 +41,9 @@ 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 @@ -53,7 +57,6 @@ 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/exchange/Get-ServiceDeliveryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md index 842dc2fa11..9f9ca7a1f2 100644 --- a/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-servicedeliveryreport +schema: 2.0.0 +title: Get-ServiceDeliveryReport --- # Get-ServiceDeliveryReport @@ -41,13 +42,15 @@ 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 @@ -57,13 +60,15 @@ 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/exchange/Get-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-ServicePrincipal.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md index ee06d9d363..f6bfd76094 100644 --- a/exchange/exchange-ps/exchange/Get-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-serviceprincipal +schema: 2.0.0 +title: Get-ServicePrincipal --- # Get-ServicePrincipal @@ -52,6 +53,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,13 +77,15 @@ 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/exchange/Get-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-SettingOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md index dec2d72019..86343595a4 100644 --- a/exchange/exchange-ps/exchange/Get-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-settingoverride +schema: 2.0.0 +title: Get-SettingOverride --- # Get-SettingOverride @@ -52,6 +53,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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/exchange/Get-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-SharingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md index a9e5d5b87f..a70897ceea 100644 --- a/exchange/exchange-ps/exchange/Get-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sharingpolicy +schema: 2.0.0 +title: Get-SharingPolicy --- # Get-SharingPolicy @@ -50,6 +51,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -79,7 +85,6 @@ 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/exchange/Get-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-SiteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md index a35a4f6e0c..128ae76aaf 100644 --- a/exchange/exchange-ps/exchange/Get-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailbox +schema: 2.0.0 +title: Get-SiteMailbox --- # Get-SiteMailbox @@ -64,6 +65,9 @@ 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 @@ -77,7 +81,6 @@ 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 @@ -87,6 +90,9 @@ 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) @@ -99,7 +105,6 @@ 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 @@ -109,6 +114,9 @@ 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. @@ -117,7 +125,6 @@ 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 @@ -127,6 +134,9 @@ 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. @@ -135,7 +145,6 @@ 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 @@ -145,13 +154,15 @@ 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,6 +172,9 @@ 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. @@ -171,7 +185,6 @@ 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 @@ -181,13 +194,15 @@ 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/exchange/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md index a79fefc2f8..a7bd9d5e25 100644 --- a/exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailboxdiagnostics +schema: 2.0.0 +title: Get-SiteMailboxDiagnostics --- # Get-SiteMailboxDiagnostics @@ -55,6 +56,9 @@ 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 @@ -68,7 +72,6 @@ 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 @@ -78,6 +81,9 @@ 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. @@ -86,7 +92,6 @@ 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 @@ -96,6 +101,9 @@ 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`. @@ -105,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ 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 @@ -131,13 +140,15 @@ 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/exchange/Get-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md index 1e107e4c93..e2b7703b6f 100644 --- a/exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailboxprovisioningpolicy +schema: 2.0.0 +title: Get-SiteMailboxProvisioningPolicy --- # Get-SiteMailboxProvisioningPolicy @@ -52,6 +53,9 @@ 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 @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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/exchange/Get-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-SmimeConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md index 94acefe7bf..e4ed84135b 100644 --- a/exchange/exchange-ps/exchange/Get-SmimeConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-smimeconfig +schema: 2.0.0 +title: Get-SmimeConfig --- # Get-SmimeConfig @@ -40,13 +41,15 @@ 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/exchange/Get-SmtpDaneInboundStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md index 2bc72a8f55..f4f5206b48 100644 --- a/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-smtpdaneinboundstatus +schema: 2.0.0 +title: Get-SmtpDaneInboundStatus --- # Get-SmtpDaneInboundStatus @@ -41,13 +42,15 @@ 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/exchange/Get-SpoofIntelligenceInsight.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md index 01335195b4..24ef8fab92 100644 --- a/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-spoofintelligenceinsight +schema: 2.0.0 +title: Get-SpoofIntelligenceInsight --- # Get-SpoofIntelligenceInsight @@ -57,13 +58,15 @@ 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/exchange/Get-SpoofMailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-SpoofMailReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md index 312ec706dc..bd1757429e 100644 --- a/exchange/exchange-ps/exchange/Get-SpoofMailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-spoofmailreport +schema: 2.0.0 +title: Get-SpoofMailReport --- # Get-SpoofMailReport @@ -65,6 +66,9 @@ 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. @@ -75,7 +79,6 @@ 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 @@ -85,13 +88,15 @@ 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 @@ -101,6 +106,9 @@ 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". @@ -109,7 +117,6 @@ 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 @@ -119,13 +126,15 @@ 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 @@ -135,13 +144,15 @@ 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 @@ -151,13 +162,15 @@ 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 @@ -167,13 +180,15 @@ 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 @@ -183,6 +198,9 @@ 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". @@ -191,7 +209,6 @@ 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/exchange/Get-StoreUsageStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md rename to exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md index 4a09b7af84..f59e6c6819 100644 --- a/exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-storeusagestatistics +schema: 2.0.0 +title: Get-StoreUsageStatistics --- # Get-StoreUsageStatistics @@ -78,6 +79,9 @@ 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 @@ -96,7 +100,6 @@ 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 @@ -106,6 +109,9 @@ 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 @@ -118,7 +124,6 @@ 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 @@ -128,6 +133,9 @@ 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) @@ -139,7 +147,6 @@ 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 @@ -149,6 +156,9 @@ 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 @@ -161,7 +171,6 @@ 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 @@ -171,13 +180,15 @@ 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 @@ -187,6 +198,9 @@ 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. @@ -202,7 +216,6 @@ 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 @@ -212,6 +225,9 @@ 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. @@ -220,7 +236,6 @@ 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/exchange/Get-SupervisoryReviewActivity.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md index 420045a251..799a5de338 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewactivity +schema: 2.0.0 +title: Get-SupervisoryReviewActivity --- # Get-SupervisoryReviewActivity @@ -47,6 +48,9 @@ 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". @@ -55,7 +59,6 @@ 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 @@ -65,13 +68,15 @@ 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 @@ -81,6 +86,9 @@ 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". @@ -89,7 +97,6 @@ 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/exchange/Get-SupervisoryReviewOverallProgressReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md index 3a432c1505..884745cecb 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewoverallprogressreport +schema: 2.0.0 +title: Get-SupervisoryReviewOverallProgressReport --- # Get-SupervisoryReviewOverallProgressReport @@ -43,6 +44,9 @@ 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". @@ -51,7 +55,6 @@ 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 @@ -61,13 +64,15 @@ 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 @@ -77,13 +82,15 @@ 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 @@ -93,6 +100,9 @@ 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". @@ -101,7 +111,6 @@ 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/exchange/Get-SupervisoryReviewPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md index d3982ce31b..7aab4b1add 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewpolicyreport +schema: 2.0.0 +title: Get-SupervisoryReviewPolicyReport --- # Get-SupervisoryReviewPolicyReport @@ -60,6 +61,9 @@ 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". @@ -68,7 +72,6 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,13 +99,15 @@ 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 @@ -110,6 +117,9 @@ 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. @@ -118,7 +128,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -128,6 +137,9 @@ 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". @@ -136,7 +148,6 @@ 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/exchange/Get-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md index cc356b57a5..286160f1da 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewpolicyv2 +schema: 2.0.0 +title: Get-SupervisoryReviewPolicyV2 --- # Get-SupervisoryReviewPolicyV2 @@ -47,6 +48,9 @@ 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 @@ -57,7 +61,6 @@ 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/exchange/Get-SupervisoryReviewReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md index 5e1a033aa5..4e16f5b9e7 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewreport +schema: 2.0.0 +title: Get-SupervisoryReviewReport --- # Get-SupervisoryReviewReport @@ -52,6 +53,9 @@ 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". @@ -60,7 +64,6 @@ 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 @@ -70,13 +73,15 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,6 +109,9 @@ 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. @@ -110,7 +120,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -120,6 +129,9 @@ 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. @@ -128,7 +140,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -138,6 +149,9 @@ 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". @@ -146,7 +160,6 @@ 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/exchange/Get-SupervisoryReviewRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md index 1a7f812f23..0e9ba2b961 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewrule +schema: 2.0.0 +title: Get-SupervisoryReviewRule --- # Get-SupervisoryReviewRule @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,6 +97,9 @@ 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 @@ -102,7 +110,6 @@ 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/exchange/Get-SupervisoryReviewTopCasesReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md index f630b5e84b..4542a24d04 100644 --- a/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewtopcasesreport +schema: 2.0.0 +title: Get-SupervisoryReviewTopCasesReport --- # Get-SupervisoryReviewTopCasesReport @@ -42,6 +43,9 @@ 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". @@ -50,7 +54,6 @@ 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 @@ -60,13 +63,15 @@ 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 @@ -76,13 +81,15 @@ 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 @@ -92,6 +99,9 @@ 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". @@ -100,7 +110,6 @@ 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/exchange/Get-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md index ceab5bc86d..6343946953 100644 --- a/exchange/exchange-ps/exchange/Get-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-sweeprule +schema: 2.0.0 +title: Get-SweepRule --- # Get-SweepRule @@ -59,6 +60,9 @@ 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==). @@ -69,7 +73,6 @@ 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 @@ -79,13 +82,15 @@ 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 @@ -95,6 +100,9 @@ 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. @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ 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 @@ -130,7 +140,6 @@ 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 @@ -140,13 +149,15 @@ 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 @@ -156,6 +167,9 @@ 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. @@ -164,7 +178,6 @@ 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 @@ -174,6 +187,9 @@ Accept wildcard characters: False ``` ### -SkipCount + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipCount Description }} @@ -182,7 +198,6 @@ 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/exchange/Get-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-SystemMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md index ba18ccc28c..53bb399562 100644 --- a/exchange/exchange-ps/exchange/Get-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-systemmessage +schema: 2.0.0 +title: Get-SystemMessage --- # Get-SystemMessage @@ -74,6 +75,9 @@ 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 @@ -131,7 +135,6 @@ 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 @@ -141,6 +144,9 @@ 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. @@ -149,7 +155,6 @@ 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 @@ -159,6 +164,9 @@ 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. @@ -167,7 +175,6 @@ 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/exchange/Get-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md index 4f520c8a57..b22284d537 100644 --- a/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-teamsprotectionpolicy +schema: 2.0.0 +title: Get-TeamsProtectionPolicy --- # Get-TeamsProtectionPolicy @@ -40,13 +41,15 @@ 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/exchange/Get-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md index 5aba335ec7..003f937867 100644 --- a/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-teamsprotectionpolicyrule +schema: 2.0.0 +title: Get-TeamsProtectionPolicyRule --- # Get-TeamsProtectionPolicyRule @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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 @@ -66,7 +72,6 @@ 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/exchange/Get-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md similarity index 89% rename from exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md index e011044ffb..d42545799e 100644 --- a/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-tenantallowblocklistitems +schema: 2.0.0 +title: Get-TenantAllowBlockListItems --- # Get-TenantAllowBlockListItems @@ -71,6 +72,9 @@ 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 @@ -82,7 +86,6 @@ 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 @@ -92,6 +95,9 @@ 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. @@ -105,7 +111,6 @@ 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 @@ -115,13 +120,15 @@ 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 @@ -131,13 +138,15 @@ 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 @@ -147,13 +156,15 @@ 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 @@ -163,6 +174,9 @@ 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: @@ -174,7 +188,6 @@ 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 @@ -184,6 +197,9 @@ 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 @@ -193,7 +209,6 @@ 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 @@ -203,6 +218,9 @@ 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. @@ -211,7 +229,6 @@ 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/exchange/Get-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md index a77fd3036a..68d7437896 100644 --- a/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-tenantallowblocklistspoofitems +schema: 2.0.0 +title: Get-TenantAllowBlockListSpoofItems --- # Get-TenantAllowBlockListSpoofItems @@ -71,13 +72,15 @@ 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 @@ -87,6 +90,9 @@ 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 @@ -96,7 +102,6 @@ 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 @@ -106,6 +111,9 @@ 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 @@ -115,7 +123,6 @@ 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/exchange/Get-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-TextMessagingAccount.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md index 11e102c7e7..e76da2b379 100644 --- a/exchange/exchange-ps/exchange/Get-TextMessagingAccount.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-textmessagingaccount +schema: 2.0.0 +title: Get-TextMessagingAccount --- # Get-TextMessagingAccount @@ -55,6 +56,9 @@ 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 @@ -72,7 +76,6 @@ 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 @@ -82,6 +85,9 @@ 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). @@ -90,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ 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,7 +116,6 @@ 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 @@ -118,6 +125,9 @@ 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. @@ -128,7 +138,6 @@ 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 @@ -138,13 +147,15 @@ 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/exchange/Get-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md index 5299f4079b..c5761e613b 100644 --- a/exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-throttlingpolicy +schema: 2.0.0 +title: Get-ThrottlingPolicy --- # Get-ThrottlingPolicy @@ -55,13 +56,15 @@ 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 @@ -71,6 +74,9 @@ 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,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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 @@ -121,6 +130,9 @@ 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 @@ -133,7 +145,6 @@ 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/exchange/Get-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md similarity index 91% rename from exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md rename to exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md index 6850db5cc9..eafb2991ef 100644 --- a/exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-throttlingpolicyassociation +schema: 2.0.0 +title: Get-ThrottlingPolicyAssociation --- # Get-ThrottlingPolicyAssociation @@ -71,6 +72,9 @@ 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 @@ -91,7 +95,6 @@ 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 @@ -101,6 +104,9 @@ 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) @@ -113,7 +119,6 @@ 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 @@ -123,6 +128,9 @@ 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. @@ -131,7 +139,6 @@ 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 @@ -141,13 +148,15 @@ 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 @@ -157,13 +166,15 @@ 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 @@ -173,6 +184,9 @@ 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 @@ -183,7 +197,6 @@ 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/exchange/Get-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md index 8efaaf32bc..95a393c3a7 100644 --- a/exchange/exchange-ps/exchange/Get-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportagent +schema: 2.0.0 +title: Get-TransportAgent --- # Get-TransportAgent @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -95,7 +103,6 @@ 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/exchange/Get-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-TransportConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md index 3357a4be56..5335305ebf 100644 --- a/exchange/exchange-ps/exchange/Get-TransportConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportconfig +schema: 2.0.0 +title: Get-TransportConfig --- # Get-TransportConfig @@ -50,6 +51,9 @@ 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. @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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,7 +84,6 @@ 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/exchange/Get-TransportPipeline.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-TransportPipeline.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md index 8366b7fc1a..4bd52cc56b 100644 --- a/exchange/exchange-ps/exchange/Get-TransportPipeline.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportpipeline +schema: 2.0.0 +title: Get-TransportPipeline --- # Get-TransportPipeline @@ -55,6 +56,9 @@ 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. @@ -63,7 +67,6 @@ 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/exchange/Get-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Get-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md index d55f8756f4..c2e020ff86 100644 --- a/exchange/exchange-ps/exchange/Get-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportrule +schema: 2.0.0 +title: Get-TransportRule --- # Get-TransportRule @@ -71,6 +72,9 @@ 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 @@ -81,7 +85,6 @@ 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 @@ -91,6 +94,9 @@ 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,7 +107,6 @@ 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 @@ -111,6 +116,9 @@ 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. @@ -122,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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 ("). @@ -142,7 +152,6 @@ 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 @@ -152,6 +161,9 @@ 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: @@ -163,7 +175,6 @@ 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 @@ -173,6 +184,9 @@ 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*'"`. @@ -183,7 +197,6 @@ 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 @@ -193,13 +206,15 @@ 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/exchange/Get-TransportRuleAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-TransportRuleAction.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md index a7052dc127..7b23775e27 100644 --- a/exchange/exchange-ps/exchange/Get-TransportRuleAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportruleaction +schema: 2.0.0 +title: Get-TransportRuleAction --- # Get-TransportRuleAction @@ -51,13 +52,15 @@ 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/exchange/Get-TransportRulePredicate.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-TransportRulePredicate.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md index 1781b502e3..d27a87e49d 100644 --- a/exchange/exchange-ps/exchange/Get-TransportRulePredicate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportrulepredicate +schema: 2.0.0 +title: Get-TransportRulePredicate --- # Get-TransportRulePredicate @@ -62,13 +63,15 @@ 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/exchange/Get-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-TransportServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md index 9e6bfd34f4..77dce3fe42 100644 --- a/exchange/exchange-ps/exchange/Get-TransportServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportserver +schema: 2.0.0 +title: Get-TransportServer --- # Get-TransportServer @@ -50,6 +51,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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,7 +85,6 @@ 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/exchange/Get-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-TransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md index de2c585879..fb7e10ed5a 100644 --- a/exchange/exchange-ps/exchange/Get-TransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-transportservice +schema: 2.0.0 +title: Get-TransportService --- # Get-TransportService @@ -48,6 +49,9 @@ 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 @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -79,7 +85,6 @@ 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/exchange/Get-Trust.md b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-Trust.md rename to exchange/exchange-ps/ExchangePowerShell/Get-Trust.md index 06c4e8a053..0f1f62089e 100644 --- a/exchange/exchange-ps/exchange/Get-Trust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-trust +schema: 2.0.0 +title: Get-Trust --- # Get-Trust @@ -42,13 +43,15 @@ 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/exchange/Get-UMActiveCalls.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-UMActiveCalls.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md index ad6d739107..d99aaa63dd 100644 --- a/exchange/exchange-ps/exchange/Get-UMActiveCalls.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umactivecalls +schema: 2.0.0 +title: Get-UMActiveCalls --- # Get-UMActiveCalls @@ -90,6 +91,9 @@ 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. @@ -98,7 +102,6 @@ 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 @@ -108,6 +111,9 @@ 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. @@ -116,7 +122,6 @@ 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 @@ -126,6 +131,9 @@ 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. @@ -134,7 +142,6 @@ 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 @@ -144,13 +151,15 @@ 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 @@ -160,6 +169,9 @@ 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 @@ -173,7 +185,6 @@ 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/exchange/Get-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md index 4ae3dced8b..2a7276553c 100644 --- a/exchange/exchange-ps/exchange/Get-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umautoattendant +schema: 2.0.0 +title: Get-UMAutoAttendant --- # Get-UMAutoAttendant @@ -60,13 +61,15 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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/exchange/Get-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md index e469e77136..cfdde92193 100644 --- a/exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallansweringrule +schema: 2.0.0 +title: Get-UMCallAnsweringRule --- # Get-UMCallAnsweringRule @@ -53,13 +54,15 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,6 +90,9 @@ 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 @@ -104,7 +112,6 @@ 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/exchange/Get-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-UMCallDataRecord.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md index 868677c8f0..2f42a5eecf 100644 --- a/exchange/exchange-ps/exchange/Get-UMCallDataRecord.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umcalldatarecord +schema: 2.0.0 +title: Get-UMCallDataRecord --- # Get-UMCallDataRecord @@ -58,6 +59,9 @@ 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 @@ -75,7 +79,6 @@ 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 @@ -85,13 +88,15 @@ 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/exchange/Get-UMCallRouterSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md index 44123198a3..bb0bfba1f5 100644 --- a/exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallroutersettings +schema: 2.0.0 +title: Get-UMCallRouterSettings --- # Get-UMCallRouterSettings @@ -50,6 +51,9 @@ 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 @@ -63,7 +67,6 @@ 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 @@ -73,13 +76,15 @@ 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/exchange/Get-UMCallSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md index 87b5ea88f8..cd1486614b 100644 --- a/exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallsummaryreport +schema: 2.0.0 +title: Get-UMCallSummaryReport --- # Get-UMCallSummaryReport @@ -86,6 +87,9 @@ 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. @@ -96,7 +100,6 @@ 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 @@ -106,13 +109,15 @@ 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 @@ -122,13 +127,15 @@ 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 @@ -138,13 +145,15 @@ 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/exchange/Get-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-UMDialPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md index fe86e9ee42..284b7eee15 100644 --- a/exchange/exchange-ps/exchange/Get-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umdialplan +schema: 2.0.0 +title: Get-UMDialPlan --- # Get-UMDialPlan @@ -52,13 +53,15 @@ 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 @@ -68,13 +71,15 @@ 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/exchange/Get-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-UMHuntGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md index d1a7328d41..6c05f9ce7b 100644 --- a/exchange/exchange-ps/exchange/Get-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umhuntgroup +schema: 2.0.0 +title: Get-UMHuntGroup --- # Get-UMHuntGroup @@ -60,13 +61,15 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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/exchange/Get-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md index f027b0d0a4..7bec396682 100644 --- a/exchange/exchange-ps/exchange/Get-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umipgateway +schema: 2.0.0 +title: Get-UMIPGateway --- # Get-UMIPGateway @@ -62,13 +63,15 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,6 +99,9 @@ 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. @@ -102,7 +110,6 @@ 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/exchange/Get-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-UMMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md index 215a6b501d..16b09954a8 100644 --- a/exchange/exchange-ps/exchange/Get-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailbox +schema: 2.0.0 +title: Get-UMMailbox --- # Get-UMMailbox @@ -70,6 +71,9 @@ 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 @@ -87,7 +91,6 @@ 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 @@ -97,6 +100,9 @@ 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) @@ -109,7 +115,6 @@ 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 @@ -119,6 +124,9 @@ 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). @@ -127,7 +135,6 @@ 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 @@ -137,13 +144,15 @@ 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 @@ -153,6 +162,9 @@ 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. @@ -168,7 +180,6 @@ 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 @@ -178,6 +189,9 @@ 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: @@ -189,7 +203,6 @@ 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 @@ -199,6 +212,9 @@ 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 @@ -210,7 +226,6 @@ 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 @@ -220,6 +235,9 @@ 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. @@ -230,7 +248,6 @@ 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 @@ -240,13 +257,15 @@ 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 @@ -256,6 +275,9 @@ 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. @@ -270,7 +292,6 @@ 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/exchange/Get-UMMailboxPIN.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPIN.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-UMMailboxPIN.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPIN.md index c3eb5e4cc0..291d4d790f 100644 --- a/exchange/exchange-ps/exchange/Get-UMMailboxPIN.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPIN.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailboxpin +schema: 2.0.0 +title: Get-UMMailboxPIN --- # Get-UMMailboxPin @@ -57,6 +58,9 @@ 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 @@ -74,7 +78,6 @@ 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 @@ -84,6 +87,9 @@ 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). @@ -92,7 +98,6 @@ 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 @@ -102,13 +107,15 @@ 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 @@ -118,6 +125,9 @@ 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: @@ -129,7 +139,6 @@ 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,6 +148,9 @@ 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. @@ -147,7 +159,6 @@ 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 @@ -157,6 +168,9 @@ 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. @@ -167,7 +181,6 @@ 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 @@ -177,13 +190,15 @@ 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/exchange/Get-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md index d3e95a0446..f58587ba09 100644 --- a/exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailboxpolicy +schema: 2.0.0 +title: Get-UMMailboxPolicy --- # Get-UMMailboxPolicy @@ -60,13 +61,15 @@ 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 @@ -76,13 +79,15 @@ 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 @@ -92,13 +97,15 @@ 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/exchange/Get-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-UMService.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UMService.md index 6551e952a2..73c1fc8206 100644 --- a/exchange/exchange-ps/exchange/Get-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umservice +schema: 2.0.0 +title: Get-UMService --- # Get-UMService @@ -52,6 +53,9 @@ 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 @@ -63,7 +67,6 @@ 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 @@ -73,13 +76,15 @@ 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/exchange/Get-UmServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-UmServer.md similarity index 97% rename from exchange/exchange-ps/exchange/Get-UmServer.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UmServer.md index 0ba48166ad..bc66d7ebb3 100644 --- a/exchange/exchange-ps/exchange/Get-UmServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UmServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-umserver +schema: 2.0.0 +title: Get-UmServer --- # Get-UMServer @@ -54,6 +55,9 @@ 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 @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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/exchange/Get-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md index 07a961fcf8..e94780639d 100644 --- a/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedauditlogretentionpolicy +schema: 2.0.0 +title: Get-UnifiedAuditLogRetentionPolicy --- # Get-UnifiedAuditLogRetentionPolicy @@ -53,6 +54,9 @@ 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"`. @@ -61,7 +65,6 @@ 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 @@ -71,13 +74,15 @@ 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 @@ -87,6 +92,9 @@ 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 @@ -100,7 +108,6 @@ Type: UnifiedAuditLogRetentionDuration Parameter Sets: (All) Aliases: Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears -Applicable: Security & Compliance Required: False Position: Named @@ -110,6 +117,9 @@ 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"`. @@ -118,7 +128,6 @@ 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/exchange/Get-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-UnifiedGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md index 0d661079bb..37c8d8887b 100644 --- a/exchange/exchange-ps/exchange/Get-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedgroup +schema: 2.0.0 +title: Get-UnifiedGroup --- # Get-UnifiedGroup @@ -103,6 +104,9 @@ 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 @@ -118,7 +122,6 @@ 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 @@ -128,13 +131,15 @@ 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 @@ -144,6 +149,9 @@ 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. @@ -159,7 +167,6 @@ 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 @@ -169,6 +176,9 @@ 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. @@ -177,7 +187,6 @@ 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 @@ -187,6 +196,9 @@ 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. @@ -195,7 +207,6 @@ 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 @@ -205,6 +216,9 @@ 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. @@ -213,7 +227,6 @@ 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 @@ -223,6 +236,9 @@ 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. @@ -231,7 +247,6 @@ 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 @@ -241,6 +256,9 @@ 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. @@ -249,7 +267,6 @@ 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 @@ -259,6 +276,9 @@ 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. @@ -267,7 +287,6 @@ 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 @@ -277,6 +296,9 @@ 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. @@ -285,7 +307,6 @@ 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 @@ -295,13 +316,15 @@ 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 @@ -311,6 +334,9 @@ 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. @@ -325,7 +351,6 @@ 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/exchange/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md similarity index 94% rename from exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md index e47851e9e1..e6b884366a 100644 --- a/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedgrouplinks +schema: 2.0.0 +title: Get-UnifiedGroupLinks --- # Get-UnifiedGroupLinks @@ -43,6 +44,9 @@ 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 @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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/exchange/Get-User.md b/exchange/exchange-ps/ExchangePowerShell/Get-User.md similarity index 88% rename from exchange/exchange-ps/exchange/Get-User.md rename to exchange/exchange-ps/ExchangePowerShell/Get-User.md index 3cafe8aba0..9bb42e662a 100644 --- a/exchange/exchange-ps/exchange/Get-User.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-User.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-user +schema: 2.0.0 +title: Get-User --- # Get-User @@ -102,6 +103,9 @@ 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 @@ -114,7 +118,6 @@ 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 @@ -124,6 +127,9 @@ 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) @@ -136,7 +142,6 @@ 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 @@ -146,6 +151,9 @@ 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. @@ -158,7 +166,6 @@ 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 @@ -168,6 +175,9 @@ 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. @@ -180,7 +190,6 @@ 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 @@ -190,6 +199,9 @@ 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. @@ -202,7 +214,6 @@ 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 @@ -212,6 +223,9 @@ 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. @@ -222,7 +236,6 @@ 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 @@ -232,6 +245,9 @@ 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. @@ -240,7 +256,6 @@ 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 @@ -250,6 +265,9 @@ 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. @@ -265,7 +283,6 @@ 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 @@ -275,6 +292,9 @@ 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. @@ -288,7 +308,6 @@ 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 @@ -298,6 +317,9 @@ Accept wildcard characters: False ``` ### -IncludeDirectReportsWithDisplayNames + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill IncludeDirectReportsWithDisplayNames Description }} @@ -306,7 +328,6 @@ 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 @@ -316,6 +337,9 @@ 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. @@ -326,7 +350,6 @@ 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 @@ -336,6 +359,9 @@ 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 @@ -347,7 +373,6 @@ 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 @@ -357,6 +382,9 @@ 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. @@ -365,7 +393,6 @@ 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 @@ -375,6 +402,9 @@ 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. @@ -387,7 +417,6 @@ 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 @@ -397,6 +426,9 @@ 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 @@ -429,7 +461,6 @@ 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 @@ -439,13 +470,15 @@ 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 @@ -455,6 +488,9 @@ 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. @@ -472,7 +508,6 @@ 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 @@ -482,6 +517,9 @@ 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. @@ -490,7 +528,6 @@ 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/exchange/Get-UserBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-UserBriefingConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md index 6c04f88148..a0bb17bca3 100644 --- a/exchange/exchange-ps/exchange/Get-UserBriefingConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md @@ -1,12 +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-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/exchange/get-userbriefingconfig +schema: 2.0.0 +title: Get-UserBriefingConfig --- # Get-UserBriefingConfig @@ -51,13 +52,15 @@ 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 @@ -67,13 +70,15 @@ 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/exchange/Get-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-UserPhoto.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md index 5314df112d..49b8e631a7 100644 --- a/exchange/exchange-ps/exchange/Get-UserPhoto.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-userphoto +schema: 2.0.0 +title: Get-UserPhoto --- # Get-UserPhoto @@ -80,6 +81,9 @@ 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 @@ -97,7 +101,6 @@ 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 @@ -107,6 +110,9 @@ 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) @@ -119,7 +125,6 @@ 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 @@ -129,6 +134,9 @@ 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). @@ -137,7 +145,6 @@ 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 @@ -147,13 +154,15 @@ 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 @@ -163,6 +172,9 @@ 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. @@ -178,7 +190,6 @@ 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 @@ -188,13 +199,15 @@ 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 @@ -204,6 +217,9 @@ 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: @@ -215,7 +231,6 @@ 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 @@ -225,6 +240,9 @@ 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 @@ -236,7 +254,6 @@ 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 @@ -246,13 +263,15 @@ 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 @@ -262,6 +281,9 @@ 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. @@ -270,7 +292,6 @@ 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 @@ -280,6 +301,9 @@ 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. @@ -290,7 +314,6 @@ 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 @@ -300,13 +323,15 @@ 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 @@ -316,6 +341,9 @@ 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. @@ -326,7 +354,6 @@ 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/exchange/Get-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md rename to exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md index b9afdf3095..054c0e1a47 100644 --- a/exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-userprincipalnamessuffix +schema: 2.0.0 +title: Get-UserPrincipalNamesSuffix --- # Get-UserPrincipalNamesSuffix @@ -46,6 +47,9 @@ 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 @@ -57,7 +61,6 @@ 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/exchange/Get-VivaInsightsSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md index bbfd395ab1..e75b2748c1 100644 --- a/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md @@ -1,12 +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-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/exchange/get-vivainsightssettings +schema: 2.0.0 +title: Get-VivaInsightsSettings --- # Get-VivaInsightsSettings @@ -58,13 +59,15 @@ 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 @@ -74,6 +77,9 @@ 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. @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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/exchange/Get-VivaModuleFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeature.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-VivaModuleFeature.md rename to exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeature.md index b2787501f8..2e975fbbdb 100644 --- a/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature +schema: 2.0.0 +title: Get-VivaModuleFeature --- # Get-VivaModuleFeature @@ -56,13 +56,15 @@ 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 @@ -72,6 +74,9 @@ 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. @@ -80,7 +85,6 @@ 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 @@ -90,13 +94,15 @@ 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/exchange/Get-VivaModuleFeatureEnablement.md b/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeatureEnablement.md similarity index 98% rename from exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md rename to exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeatureEnablement.md index 8fed8e655e..903eec59f7 100644 --- a/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeatureenablement +schema: 2.0.0 +title: Get-VivaModuleFeatureEnablement --- # Get-VivaModuleFeatureEnablement diff --git a/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeaturePolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeaturePolicy.md index 1e4a57e8a1..7ccdb94d97 100644 --- a/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeaturepolicy +schema: 2.0.0 +title: Get-VivaModuleFeaturePolicy --- # Get-VivaModuleFeaturePolicy @@ -88,15 +88,17 @@ 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 +Parameter Sets: FeaturePolicy, FeaturePolicyWithMembers Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -105,27 +107,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: FeaturePolicyWithMembers -Aliases: -Applicable: Exchange Online +### -ModuleId -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: True -``` +> Applicable: Exchange Online -### -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 @@ -135,6 +126,9 @@ 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. @@ -143,7 +137,6 @@ 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 @@ -153,7 +146,10 @@ Accept wildcard characters: False ``` ### -MemberIds -The MemberIds parameter specifies the specific users or groups for which you want to view the policies for the feature in the Viva module. + +> 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. You can provide up to three member IDs. Use the \* character to specify all modules or features. @@ -161,7 +157,6 @@ 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 @@ -171,13 +166,15 @@ 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/exchange/Get-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md similarity index 96% rename from exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md rename to exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md index 22defddf64..2e0cdf3c6d 100644 --- a/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md @@ -1,12 +1,12 @@ --- +author: chrisda external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement +Locale: en-US +Module Name: ExchangePowerShell +ms.author: chrisda 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: +title: Get-VivaOrgInsightsDelegatedRole --- # Get-VivaOrgInsightsDelegatedRole @@ -49,6 +49,9 @@ 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. @@ -57,7 +60,6 @@ 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 @@ -67,13 +69,15 @@ 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/exchange/Get-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md index 1345ae232f..0b7ca6d7e1 100644 --- a/exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-webservicesvirtualdirectory +schema: 2.0.0 +title: Get-WebServicesVirtualDirectory --- # Get-WebServicesVirtualDirectory @@ -71,6 +72,9 @@ 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 @@ -85,7 +89,6 @@ 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 @@ -95,6 +98,9 @@ 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 @@ -108,7 +114,6 @@ 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 @@ -118,6 +123,9 @@ 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. @@ -126,7 +134,6 @@ 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 @@ -136,13 +143,15 @@ 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 @@ -152,6 +161,9 @@ 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. @@ -162,7 +174,6 @@ 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/exchange/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md similarity index 93% rename from exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md index 3be7ea0728..0403baeb2f 100644 --- a/exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-x400authoritativedomain +schema: 2.0.0 +title: Get-X400AuthoritativeDomain --- # Get-X400AuthoritativeDomain @@ -41,13 +42,15 @@ 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 @@ -57,6 +60,9 @@ 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. @@ -65,7 +71,6 @@ 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/exchange/Get-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md similarity index 95% rename from exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md rename to exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md index 2af5f1721a..066759be35 100644 --- a/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-ediscoverycaseadmin +schema: 2.0.0 +title: Get-eDiscoveryCaseAdmin --- # Get-eDiscoveryCaseAdmin @@ -43,13 +44,15 @@ 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 @@ -59,13 +62,15 @@ 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/exchange/Import-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md similarity index 91% rename from exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md index bdec677fd8..57dee53d83 100644 --- a/exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-dlppolicycollection +schema: 2.0.0 +title: Import-DlpPolicyCollection --- # Import-DlpPolicyCollection @@ -50,13 +51,15 @@ 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 @@ -66,6 +69,9 @@ 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`). @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +101,6 @@ 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 @@ -103,13 +110,15 @@ 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 @@ -119,6 +128,9 @@ 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. @@ -127,7 +139,6 @@ 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 @@ -137,13 +148,15 @@ 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/exchange/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md similarity index 93% rename from exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md index 41752441f8..770cfa85e7 100644 --- a/exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-dlppolicytemplate +schema: 2.0.0 +title: Import-DlpPolicyTemplate --- # Import-DlpPolicyTemplate @@ -42,6 +43,9 @@ 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`). @@ -50,7 +54,6 @@ 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 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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/exchange/Import-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md similarity index 93% rename from exchange/exchange-ps/exchange/Import-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md index f9175f98ff..687612edba 100644 --- a/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-exchangecertificate +schema: 2.0.0 +title: Import-ExchangeCertificate --- # Import-ExchangeCertificate @@ -101,6 +102,9 @@ 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`). @@ -115,7 +119,6 @@ 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 @@ -125,6 +128,9 @@ 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. @@ -139,7 +145,6 @@ 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 @@ -149,13 +154,15 @@ 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 @@ -165,6 +172,9 @@ 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`. @@ -174,7 +184,6 @@ 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 @@ -184,6 +193,9 @@ 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. @@ -192,7 +204,6 @@ 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 @@ -202,6 +213,9 @@ 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. @@ -210,7 +224,6 @@ 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 @@ -220,6 +233,9 @@ 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: @@ -232,7 +248,6 @@ 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 @@ -242,6 +257,9 @@ 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. @@ -251,7 +269,6 @@ 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 @@ -261,6 +278,9 @@ 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 @@ -274,7 +294,6 @@ 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 @@ -284,13 +303,15 @@ 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/exchange/Import-FilePlanProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md similarity index 93% rename from exchange/exchange-ps/exchange/Import-FilePlanProperty.md rename to exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md index 0a64f7f630..4ea26f7595 100644 --- a/exchange/exchange-ps/exchange/Import-FilePlanProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md @@ -1,9 +1,11 @@ --- +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/exchange/import-fileplanproperty -applicable: Security & Compliance -title: Import-FilePlanProperty schema: 2.0.0 +title: Import-FilePlanProperty --- # Import-FilePlanProperty @@ -42,13 +44,15 @@ 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 @@ -58,6 +62,9 @@ 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. @@ -67,7 +74,6 @@ 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 @@ -77,13 +83,15 @@ 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 @@ -93,6 +101,9 @@ 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. @@ -101,7 +112,6 @@ 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 @@ -111,13 +121,15 @@ 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 @@ -127,13 +139,15 @@ 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/exchange/Import-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md similarity index 91% rename from exchange/exchange-ps/exchange/Import-JournalRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md index 535e6e67f0..1db84c3ed3 100644 --- a/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-journalrulecollection +schema: 2.0.0 +title: Import-JournalRuleCollection --- # Import-JournalRuleCollection @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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`). @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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`. @@ -92,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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,13 +127,15 @@ 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/exchange/Import-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md similarity index 88% rename from exchange/exchange-ps/exchange/Import-RecipientDataProperty.md rename to exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md index 3c8ed062fd..8c99cc49ed 100644 --- a/exchange/exchange-ps/exchange/Import-RecipientDataProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-recipientdataproperty +schema: 2.0.0 +title: Import-RecipientDataProperty --- # Import-RecipientDataProperty @@ -62,6 +63,9 @@ 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 @@ -73,7 +77,6 @@ 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 @@ -83,6 +86,9 @@ 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`). @@ -95,7 +101,6 @@ 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 @@ -105,6 +110,9 @@ 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`. @@ -114,7 +122,6 @@ 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 @@ -124,6 +131,9 @@ 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. @@ -132,7 +142,6 @@ 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 @@ -142,6 +151,9 @@ 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. @@ -150,7 +162,6 @@ 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 @@ -160,6 +171,9 @@ 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. @@ -168,7 +182,6 @@ 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 @@ -178,13 +191,15 @@ 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/exchange/Import-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md similarity index 89% rename from exchange/exchange-ps/exchange/Import-TransportRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md index 30fae12016..c1ebc2ef2c 100644 --- a/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-transportrulecollection +schema: 2.0.0 +title: Import-TransportRuleCollection --- # Import-TransportRuleCollection @@ -50,6 +51,9 @@ This example imports a transport rule collection from the XML file named Exporte ## 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 import. You can use any value that uniquely identifies the rule. For example: @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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`). @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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`. @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ 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,7 +129,6 @@ 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 @@ -129,6 +138,9 @@ 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. @@ -137,7 +149,6 @@ 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 @@ -147,13 +158,15 @@ 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/exchange/Import-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md similarity index 92% rename from exchange/exchange-ps/exchange/Import-UMPrompt.md rename to exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md index 5f34ab73ab..abdb60b635 100644 --- a/exchange/exchange-ps/exchange/Import-UMPrompt.md +++ b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/import-umprompt +schema: 2.0.0 +title: Import-UMPrompt --- # Import-UMPrompt @@ -89,6 +90,9 @@ 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`). @@ -97,7 +101,6 @@ 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 @@ -107,13 +110,15 @@ 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 @@ -123,13 +128,15 @@ 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 @@ -139,13 +146,15 @@ 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 @@ -155,13 +164,15 @@ 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 @@ -171,6 +182,9 @@ 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`. @@ -180,7 +194,6 @@ 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 @@ -190,13 +203,15 @@ 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 @@ -206,13 +221,15 @@ 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/exchange/Install-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md similarity index 90% rename from exchange/exchange-ps/exchange/Install-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md index 9e51b2aaa8..0c96196a1b 100644 --- a/exchange/exchange-ps/exchange/Install-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/install-transportagent +schema: 2.0.0 +title: Install-TransportAgent --- # Install-TransportAgent @@ -46,13 +47,15 @@ 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 @@ -62,13 +65,15 @@ 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 @@ -78,13 +83,15 @@ 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 @@ -94,6 +101,9 @@ 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,7 +113,6 @@ 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,6 +122,9 @@ 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. @@ -121,7 +133,6 @@ 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 @@ -131,6 +142,9 @@ 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. @@ -143,7 +157,6 @@ 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 @@ -153,13 +166,15 @@ 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/exchange/Install-UnifiedCompliancePrerequisite.md b/exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md similarity index 96% rename from exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md rename to exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md index dfc3b902a4..0620ed8517 100644 --- a/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md +++ b/exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/install-unifiedcomplianceprerequisite +schema: 2.0.0 +title: Install-UnifiedCompliancePrerequisite --- # Install-UnifiedCompliancePrerequisite @@ -71,6 +72,9 @@ 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. @@ -79,7 +83,6 @@ You can't use this switch with the LoadOnly switch. Type: SwitchParameter Parameter Sets: Initialize Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -89,6 +92,9 @@ 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. @@ -97,7 +103,6 @@ You can't use this switch with the ForceInitialize switch. Type: SwitchParameter Parameter Sets: LoadOnly Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -107,13 +112,15 @@ 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/exchange/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md similarity index 87% rename from exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md rename to exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md index d208ed10b8..32fd4984d6 100644 --- a/exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/invoke-compliancesearchactionstep +schema: 2.0.0 +title: Invoke-ComplianceSearchActionStep --- # Invoke-ComplianceSearchActionStep @@ -40,13 +41,15 @@ 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 @@ -56,13 +59,15 @@ 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 @@ -72,13 +77,15 @@ 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/exchange/Invoke-ComplianceSecurityFilterAction.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md similarity index 96% rename from exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md rename to exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md index af2ca95201..eec7d5c0d6 100644 --- a/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/invoke-compliancesecurityfilteraction +schema: 2.0.0 +title: Invoke-ComplianceSecurityFilterAction --- # Invoke-ComplianceSecurityFilterAction @@ -108,6 +109,9 @@ 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 @@ -117,7 +121,6 @@ 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 @@ -127,6 +130,9 @@ 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 @@ -140,7 +146,6 @@ If the value contains spaces, enclose the value in quotation marks. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 2 @@ -150,6 +155,9 @@ 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 @@ -160,7 +168,6 @@ Use the PropertyValue parameter to set the compliance boundary. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 3 @@ -170,13 +177,15 @@ 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 @@ -186,13 +195,15 @@ 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 @@ -202,6 +213,9 @@ 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`. @@ -211,7 +225,6 @@ 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 @@ -221,13 +234,15 @@ 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/exchange/Invoke-HoldRemovalAction.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md similarity index 95% rename from exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md rename to exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md index 3579f174b8..8499b730c9 100644 --- a/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/invoke-holdremovalaction +schema: 2.0.0 +title: Invoke-HoldRemovalAction --- # Invoke-HoldRemovalAction @@ -60,6 +61,9 @@ 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. @@ -70,7 +74,6 @@ 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 @@ -80,6 +83,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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. @@ -107,7 +115,6 @@ 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 @@ -117,6 +124,9 @@ 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. @@ -125,7 +135,6 @@ 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 @@ -135,6 +144,9 @@ 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. @@ -143,7 +155,6 @@ 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 @@ -153,6 +164,9 @@ 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. @@ -161,7 +175,6 @@ 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 @@ -171,13 +184,15 @@ 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/exchange/Invoke-MonitoringProbe.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md similarity index 87% rename from exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md rename to exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md index 858171d8c8..479bf18779 100644 --- a/exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md +++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/invoke-monitoringprobe +schema: 2.0.0 +title: Invoke-MonitoringProbe --- # Invoke-MonitoringProbe @@ -51,13 +52,15 @@ 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 @@ -67,6 +70,9 @@ 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 @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,13 +131,15 @@ 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 @@ -138,13 +149,15 @@ 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 @@ -154,13 +167,15 @@ 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 @@ -170,13 +185,15 @@ 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 @@ -186,13 +203,15 @@ 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 @@ -202,13 +221,15 @@ 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 @@ -218,13 +239,15 @@ 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/exchange/Mount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md similarity index 89% rename from exchange/exchange-ps/exchange/Mount-Database.md rename to exchange/exchange-ps/ExchangePowerShell/Mount-Database.md index 8d6dc5909a..a011ece3ed 100644 --- a/exchange/exchange-ps/exchange/Mount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/mount-database +schema: 2.0.0 +title: Mount-Database --- # Mount-Database @@ -46,6 +47,9 @@ 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 @@ -56,7 +60,6 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,13 +108,15 @@ 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 @@ -117,6 +126,9 @@ 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. @@ -125,7 +137,6 @@ 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 @@ -135,13 +146,15 @@ 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 @@ -151,13 +164,15 @@ 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/exchange/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md similarity index 90% rename from exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md index c59b2bf565..49ed2c1409 100644 --- a/exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/move-activemailboxdatabase +schema: 2.0.0 +title: Move-ActiveMailboxDatabase --- # Move-ActiveMailboxDatabase @@ -134,6 +135,9 @@ 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 @@ -146,7 +150,6 @@ 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 @@ -156,6 +159,9 @@ 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 @@ -169,7 +175,6 @@ 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 @@ -179,6 +184,9 @@ 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 @@ -192,7 +200,6 @@ 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 @@ -202,13 +209,15 @@ 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 @@ -218,6 +227,9 @@ 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. @@ -228,7 +240,6 @@ 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 @@ -238,6 +249,9 @@ 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`. @@ -247,7 +261,6 @@ 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 @@ -257,13 +270,15 @@ 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 @@ -273,6 +288,9 @@ 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. @@ -285,7 +303,6 @@ 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 @@ -295,13 +312,15 @@ 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 @@ -311,13 +330,15 @@ 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 @@ -327,6 +348,9 @@ 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. @@ -335,7 +359,6 @@ 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 @@ -345,6 +368,9 @@ 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. @@ -353,7 +379,6 @@ 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 @@ -363,13 +388,15 @@ 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 @@ -379,6 +406,9 @@ 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. @@ -387,7 +417,6 @@ 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 @@ -397,13 +426,15 @@ 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 @@ -413,6 +444,9 @@ 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. @@ -421,7 +455,6 @@ 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 @@ -431,13 +464,15 @@ 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 @@ -447,13 +482,15 @@ 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 @@ -463,13 +500,15 @@ 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/exchange/Move-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Move-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md index d2c70381c6..3a8b290abb 100644 --- a/exchange/exchange-ps/exchange/Move-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/move-addresslist +schema: 2.0.0 +title: Move-AddressList --- # Move-AddressList @@ -43,6 +44,9 @@ 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 @@ -54,7 +58,6 @@ 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 @@ -64,6 +67,9 @@ 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 @@ -75,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,13 +131,15 @@ 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/exchange/Move-DatabasePath.md b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md similarity index 89% rename from exchange/exchange-ps/exchange/Move-DatabasePath.md rename to exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md index 88ab1bea84..63878c92d1 100644 --- a/exchange/exchange-ps/exchange/Move-DatabasePath.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/move-databasepath +schema: 2.0.0 +title: Move-DatabasePath --- # Move-DatabasePath @@ -54,6 +55,9 @@ 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 @@ -64,7 +68,6 @@ 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 @@ -74,6 +77,9 @@ 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. @@ -82,7 +88,6 @@ 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 @@ -92,6 +97,9 @@ 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,7 +111,6 @@ 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,13 +120,15 @@ 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 @@ -129,13 +138,15 @@ 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 @@ -145,6 +156,9 @@ 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. @@ -153,7 +167,6 @@ 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 @@ -163,13 +176,15 @@ 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 @@ -179,13 +194,15 @@ 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 @@ -195,13 +212,15 @@ 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/exchange/Move-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md similarity index 90% rename from exchange/exchange-ps/exchange/Move-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md index 52e6b27ad3..9b141d5c69 100644 --- a/exchange/exchange-ps/exchange/Move-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/move-offlineaddressbook +schema: 2.0.0 +title: Move-OfflineAddressBook --- # Move-OfflineAddressBook @@ -44,6 +45,9 @@ 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. @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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,6 +106,9 @@ 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 @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ 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/exchange/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md index 85953675d6..557a4abc43 100644 --- a/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-atpbuiltinprotectionrule +schema: 2.0.0 +title: New-ATPBuiltInProtectionRule --- # New-ATPBuiltInProtectionRule @@ -54,6 +55,9 @@ 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. @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ 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. @@ -115,7 +125,6 @@ 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 @@ -125,13 +134,15 @@ 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 @@ -141,6 +152,9 @@ 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 @@ -156,7 +170,6 @@ 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 @@ -166,6 +179,9 @@ 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 @@ -183,7 +199,6 @@ 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 @@ -193,6 +208,9 @@ 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. @@ -201,7 +219,6 @@ 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 @@ -211,13 +228,15 @@ 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/exchange/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md index 9397716f14..ea8a44d956 100644 --- a/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-atpprotectionpolicyrule +schema: 2.0.0 +title: New-ATPProtectionPolicyRule --- # New-ATPProtectionPolicyRule @@ -58,6 +59,9 @@ 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. @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ 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: @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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: @@ -112,7 +120,6 @@ 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 @@ -122,13 +129,15 @@ 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 @@ -138,6 +147,9 @@ 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,7 +159,6 @@ 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 @@ -157,6 +168,9 @@ 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. @@ -171,7 +185,6 @@ 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 @@ -181,13 +194,15 @@ 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 @@ -197,6 +212,9 @@ 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 @@ -212,7 +230,6 @@ 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 @@ -222,6 +239,9 @@ 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 @@ -239,7 +259,6 @@ 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 @@ -249,6 +268,9 @@ 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. @@ -259,7 +281,6 @@ When you create the policy, you must use the default value. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -269,13 +290,15 @@ 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 @@ -285,6 +308,9 @@ 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 @@ -300,7 +326,6 @@ 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 @@ -310,6 +335,9 @@ 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 @@ -327,7 +355,6 @@ 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 @@ -337,13 +364,15 @@ 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/exchange/New-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/New-AcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md index 157ffaec81..ce2ce00cf4 100644 --- a/exchange/exchange-ps/exchange/New-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-accepteddomain +schema: 2.0.0 +title: New-AcceptedDomain --- # New-AcceptedDomain @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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,7 +95,6 @@ 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,6 +104,9 @@ 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. @@ -105,7 +115,6 @@ 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 @@ -115,6 +124,9 @@ 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. @@ -125,7 +137,6 @@ 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 @@ -135,13 +146,15 @@ 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/exchange/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md similarity index 89% rename from exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md index 136f962987..4fd49600d4 100644 --- a/exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncdeviceaccessrule +schema: 2.0.0 +title: New-ActiveSyncDeviceAccessRule --- # New-ActiveSyncDeviceAccessRule @@ -52,13 +53,15 @@ 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 @@ -68,6 +71,9 @@ 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 @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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`. @@ -117,7 +127,6 @@ 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 @@ -127,6 +136,9 @@ 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. @@ -135,7 +147,6 @@ 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,13 +156,15 @@ 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/exchange/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md similarity index 81% rename from exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md index 2480ceb160..8e0c8eaa74 100644 --- a/exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncmailboxpolicy +schema: 2.0.0 +title: New-ActiveSyncMailboxPolicy --- # New-ActiveSyncMailboxPolicy @@ -116,13 +117,15 @@ 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 @@ -132,6 +135,9 @@ 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. @@ -140,7 +146,6 @@ The AllowApplePushNotifications parameter specifies whether push notifications a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -150,13 +155,15 @@ 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 @@ -166,13 +173,15 @@ 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 @@ -182,13 +191,15 @@ 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 @@ -198,13 +209,15 @@ 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 @@ -214,13 +227,15 @@ 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 @@ -230,13 +245,15 @@ 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 @@ -246,13 +263,15 @@ 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 @@ -262,13 +281,15 @@ 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 @@ -278,13 +299,15 @@ 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 @@ -294,13 +317,15 @@ 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 @@ -310,13 +335,15 @@ 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 @@ -326,13 +353,15 @@ 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 @@ -342,13 +371,15 @@ 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 @@ -358,13 +389,15 @@ 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 @@ -374,13 +407,15 @@ 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 @@ -390,13 +425,15 @@ 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 @@ -406,13 +443,15 @@ 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 @@ -422,13 +461,15 @@ 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 @@ -438,13 +479,15 @@ 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 @@ -454,13 +497,15 @@ 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 @@ -470,13 +515,15 @@ 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 @@ -486,13 +533,15 @@ 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 @@ -502,13 +551,15 @@ 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 @@ -518,13 +569,15 @@ 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 @@ -534,6 +587,9 @@ 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`. @@ -543,7 +599,6 @@ 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 @@ -553,13 +608,15 @@ 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 @@ -569,13 +626,15 @@ 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 @@ -585,13 +644,15 @@ 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 @@ -601,13 +662,15 @@ 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 @@ -617,13 +680,15 @@ 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 @@ -633,6 +698,9 @@ 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. @@ -641,7 +709,6 @@ 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 @@ -651,13 +718,15 @@ 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 @@ -667,13 +736,15 @@ 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 @@ -683,13 +754,15 @@ 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 @@ -699,13 +772,15 @@ 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 @@ -715,6 +790,9 @@ 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 @@ -727,7 +805,6 @@ 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 @@ -737,13 +814,15 @@ 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 @@ -753,6 +832,9 @@ 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: @@ -770,7 +852,6 @@ 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 @@ -780,13 +861,15 @@ 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 @@ -796,13 +879,15 @@ 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 @@ -812,13 +897,15 @@ 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 @@ -828,13 +915,15 @@ 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 @@ -844,13 +933,15 @@ 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 @@ -860,13 +951,15 @@ 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 @@ -876,13 +969,15 @@ 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 @@ -892,13 +987,15 @@ 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 @@ -908,13 +1005,15 @@ 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 @@ -924,13 +1023,15 @@ 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 @@ -940,13 +1041,15 @@ 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 @@ -956,13 +1059,15 @@ 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 @@ -972,13 +1077,15 @@ 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 @@ -988,13 +1095,15 @@ 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 @@ -1004,13 +1113,15 @@ 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 @@ -1020,13 +1131,15 @@ 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 @@ -1036,13 +1149,15 @@ 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/exchange/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md index 03c846da01..16f353d1e6 100644 --- a/exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncvirtualdirectory +schema: 2.0.0 +title: New-ActiveSyncVirtualDirectory --- # New-ActiveSyncVirtualDirectory @@ -72,13 +73,15 @@ 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 @@ -88,13 +91,15 @@ 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 @@ -104,6 +109,9 @@ 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,7 +121,6 @@ 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 @@ -123,13 +130,15 @@ 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 @@ -139,6 +148,9 @@ 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. @@ -151,7 +163,6 @@ 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 @@ -161,6 +172,9 @@ 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. @@ -170,7 +184,6 @@ 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 @@ -180,6 +193,9 @@ 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. @@ -192,7 +208,6 @@ 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 @@ -202,6 +217,9 @@ 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 @@ -233,7 +251,6 @@ 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 @@ -243,13 +260,15 @@ 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 @@ -259,13 +278,15 @@ 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 @@ -275,6 +296,9 @@ 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 @@ -306,7 +330,6 @@ 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 @@ -316,13 +339,15 @@ 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 @@ -332,13 +357,15 @@ 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 @@ -348,6 +375,9 @@ 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. @@ -359,7 +389,6 @@ 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 @@ -369,6 +398,9 @@ 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 @@ -380,7 +412,6 @@ 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 @@ -390,13 +421,15 @@ 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 @@ -406,13 +439,15 @@ 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/exchange/New-AdaptiveScope.md b/exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md similarity index 95% rename from exchange/exchange-ps/exchange/New-AdaptiveScope.md rename to exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md index 88433a9deb..3ae01e7553 100644 --- a/exchange/exchange-ps/exchange/New-AdaptiveScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-adaptivescope +schema: 2.0.0 +title: New-AdaptiveScope --- # New-AdaptiveScope @@ -56,13 +57,15 @@ 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 @@ -72,6 +75,9 @@ 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"}` @@ -83,7 +89,6 @@ You can't use this parameter with the RawQuery parameter. Type: PswsHashtable Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -93,6 +98,9 @@ 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 @@ -104,7 +112,6 @@ Type: DynamicBoundaryLocationType Parameter Sets: (All) Aliases: Accepted values: Unknown, User, Group, Site -Applicable: Security & Compliance Required: True Position: Named @@ -114,6 +121,9 @@ 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. @@ -122,7 +132,6 @@ You can't use this parameter with the FilterConditions parameter. Type: String Parameter Sets: AdaptiveScopeRawQuery Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -132,13 +141,15 @@ 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 @@ -148,13 +159,15 @@ 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/exchange/New-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/New-AddressBookPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md index 4bade089b4..a288700811 100644 --- a/exchange/exchange-ps/exchange/New-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-addressbookpolicy +schema: 2.0.0 +title: New-AddressBookPolicy --- # New-AddressBookPolicy @@ -51,13 +52,15 @@ 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 @@ -67,13 +70,15 @@ 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 @@ -83,13 +88,15 @@ 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 @@ -99,13 +106,15 @@ 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 @@ -115,6 +124,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/exchange/new-addresslist#-recipientfilter) results from the address list that's specified by this parameter. @@ -133,7 +145,6 @@ 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 @@ -143,6 +154,9 @@ 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,7 +166,6 @@ 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 @@ -162,6 +175,9 @@ 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. @@ -170,7 +186,6 @@ 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 @@ -180,13 +195,15 @@ 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/exchange/New-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md similarity index 89% rename from exchange/exchange-ps/exchange/New-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/New-AddressList.md index 540855b553..018e18ba1a 100644 --- a/exchange/exchange-ps/exchange/New-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-addresslist +schema: 2.0.0 +title: New-AddressList --- # New-AddressList @@ -101,13 +102,15 @@ 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 @@ -117,6 +120,9 @@ 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. @@ -134,7 +140,6 @@ 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 @@ -144,6 +149,9 @@ 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. @@ -161,7 +169,6 @@ 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 @@ -171,6 +178,9 @@ 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. @@ -181,7 +191,6 @@ 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 @@ -191,6 +200,9 @@ 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. @@ -201,7 +213,6 @@ 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,6 +222,9 @@ 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. @@ -221,7 +235,6 @@ 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 @@ -231,6 +244,9 @@ 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. @@ -241,7 +257,6 @@ 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 @@ -251,6 +266,9 @@ 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. @@ -261,7 +279,6 @@ 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 @@ -271,6 +288,9 @@ 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. @@ -281,7 +301,6 @@ 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 @@ -291,6 +310,9 @@ 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. @@ -301,7 +323,6 @@ 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 @@ -311,6 +332,9 @@ 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. @@ -321,7 +345,6 @@ 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 @@ -331,6 +354,9 @@ 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. @@ -341,7 +367,6 @@ 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 @@ -351,6 +376,9 @@ 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. @@ -361,7 +389,6 @@ 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 @@ -371,6 +398,9 @@ 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. @@ -381,7 +411,6 @@ 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 @@ -391,6 +420,9 @@ 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. @@ -401,7 +433,6 @@ 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 @@ -411,6 +442,9 @@ 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. @@ -421,7 +455,6 @@ 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,6 +464,9 @@ 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. @@ -441,7 +477,6 @@ 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 @@ -451,6 +486,9 @@ 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. @@ -461,7 +499,6 @@ 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 @@ -471,6 +508,9 @@ 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. @@ -481,7 +521,6 @@ 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 @@ -491,6 +530,9 @@ 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. @@ -501,7 +543,6 @@ 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 @@ -511,6 +552,9 @@ 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. @@ -521,7 +565,6 @@ 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 @@ -531,6 +574,9 @@ 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`. @@ -540,7 +586,6 @@ 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 @@ -550,6 +595,9 @@ 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 @@ -563,7 +611,6 @@ 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 @@ -573,6 +620,9 @@ 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. @@ -581,7 +631,6 @@ 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 @@ -591,6 +640,9 @@ 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. @@ -599,7 +651,6 @@ 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 @@ -609,6 +660,9 @@ 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: @@ -624,7 +678,6 @@ 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 @@ -634,13 +687,15 @@ 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/exchange/New-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/New-AddressRewriteEntry.md rename to exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md index 1c5c9541bd..2b804e5b83 100644 --- a/exchange/exchange-ps/exchange/New-AddressRewriteEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-addressrewriteentry +schema: 2.0.0 +title: New-AddressRewriteEntry --- # New-AddressRewriteEntry @@ -59,13 +60,15 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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 @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ 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,7 +132,6 @@ 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 @@ -132,6 +141,9 @@ 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. @@ -140,7 +152,6 @@ 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 @@ -150,13 +161,15 @@ 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 @@ -166,6 +179,9 @@ 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). @@ -176,7 +192,6 @@ 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 @@ -186,13 +201,15 @@ 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/exchange/New-AdminAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md similarity index 84% rename from exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md rename to exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md index 1059619e55..0560a25fef 100644 --- a/exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-adminauditlogsearch +schema: 2.0.0 +title: New-AdminAuditLogSearch --- # New-AdminAuditLogSearch @@ -66,6 +67,9 @@ 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". @@ -74,7 +78,6 @@ 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 @@ -83,6 +86,9 @@ 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". @@ -91,7 +97,6 @@ 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 @@ -100,6 +105,9 @@ 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. @@ -108,7 +116,6 @@ 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 @@ -117,6 +124,9 @@ 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. @@ -125,7 +135,6 @@ 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 @@ -134,6 +143,9 @@ 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`. @@ -143,7 +155,6 @@ 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 @@ -152,6 +163,9 @@ 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,7 +174,6 @@ 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 @@ -170,13 +183,15 @@ 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 @@ -185,6 +200,9 @@ 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 ("). @@ -193,7 +211,6 @@ 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 @@ -202,6 +219,9 @@ 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. @@ -210,7 +230,6 @@ 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 @@ -219,6 +238,9 @@ 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. @@ -227,7 +249,6 @@ 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 @@ -236,6 +257,9 @@ 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. @@ -244,7 +268,6 @@ 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 @@ -253,6 +276,9 @@ 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. @@ -261,7 +287,6 @@ 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/exchange/New-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-AntiPhishPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md index 412a2a5340..4082d25c33 100644 --- a/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-antiphishpolicy +schema: 2.0.0 +title: New-AntiPhishPolicy --- # New-AntiPhishPolicy @@ -91,13 +92,15 @@ 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 @@ -107,13 +110,15 @@ 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 @@ -123,6 +128,9 @@ 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: @@ -134,7 +142,6 @@ 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 @@ -144,6 +151,9 @@ 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`. @@ -153,7 +163,6 @@ 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 @@ -163,6 +172,9 @@ 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: @@ -176,7 +188,6 @@ 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 @@ -186,6 +197,9 @@ 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: @@ -199,7 +213,6 @@ 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 @@ -209,6 +222,9 @@ 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. @@ -221,7 +237,6 @@ 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 @@ -231,6 +246,9 @@ 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. @@ -240,7 +258,6 @@ 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 @@ -250,6 +267,9 @@ 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: @@ -261,7 +281,6 @@ The EnableMailboxIntelligence parameter specifies whether to enable or disable m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -271,6 +290,9 @@ 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: @@ -286,7 +308,6 @@ 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 @@ -296,6 +317,9 @@ 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: @@ -307,7 +331,6 @@ The EnableOrganizationDomainsProtection parameter specifies whether to enable do Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -317,6 +340,9 @@ 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: @@ -328,7 +354,6 @@ The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the saf Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -338,6 +363,9 @@ 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: @@ -349,7 +377,6 @@ The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -359,6 +386,9 @@ 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: @@ -370,7 +400,6 @@ 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 @@ -380,6 +409,9 @@ 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: @@ -391,7 +423,6 @@ The EnableTargetedDomainsProtection parameter specifies whether to enable domain Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -401,6 +432,9 @@ 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: @@ -412,7 +446,6 @@ The EnableTargetedUserProtection parameter specifies whether to enable user impe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -422,6 +455,9 @@ 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: @@ -438,7 +474,6 @@ 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 @@ -448,6 +483,9 @@ 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: @@ -459,7 +497,6 @@ The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -469,6 +506,9 @@ 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: @@ -485,7 +525,6 @@ 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 @@ -495,6 +534,9 @@ 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. @@ -507,7 +549,6 @@ The maximum number of entries is approximately 1000. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -517,6 +558,9 @@ 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. @@ -527,7 +571,6 @@ The maximum number of entries is approximately 1000. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -537,6 +580,9 @@ 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: @@ -548,7 +594,6 @@ 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 @@ -558,6 +603,9 @@ 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: @@ -570,7 +618,6 @@ The ImpersonationProtectionState parameter specifies the configuration of impers Type: ImpersonationProtectionState Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -580,6 +627,9 @@ 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: @@ -597,7 +647,6 @@ This parameter is meaningful only if the EnableMailboxIntelligence and EnableMai Type: ImpersonationAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -607,6 +656,9 @@ 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. @@ -617,7 +669,6 @@ 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 @@ -627,6 +678,9 @@ 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: @@ -645,7 +699,6 @@ 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 @@ -655,6 +708,9 @@ 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). @@ -663,7 +719,6 @@ 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 @@ -673,6 +728,9 @@ 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: @@ -686,7 +744,6 @@ 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 @@ -696,13 +753,15 @@ 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 @@ -712,13 +771,15 @@ 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 @@ -728,13 +789,15 @@ 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 @@ -744,6 +807,9 @@ 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 @@ -760,7 +826,6 @@ 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 @@ -770,6 +835,9 @@ 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. @@ -780,7 +848,6 @@ 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 @@ -790,6 +857,9 @@ 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: @@ -805,7 +875,6 @@ The TargetedDomainProtectionAction parameter specifies the action to take on det Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -815,6 +884,9 @@ 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: @@ -833,7 +905,6 @@ 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 @@ -843,6 +914,9 @@ 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. @@ -853,7 +927,6 @@ You can specify multiple domains separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -863,6 +936,9 @@ 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. @@ -873,7 +949,6 @@ 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 @@ -883,6 +958,9 @@ 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: @@ -898,7 +976,6 @@ The TargetedUserProtectionAction parameter specifies the action to take on detec Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -908,6 +985,9 @@ 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: @@ -926,7 +1006,6 @@ 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 @@ -936,6 +1015,9 @@ 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. @@ -950,7 +1032,6 @@ This parameter uses the syntax: "DisplayName;EmailAddress". Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -960,13 +1041,15 @@ 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 @@ -976,13 +1059,15 @@ 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/exchange/New-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md similarity index 92% rename from exchange/exchange-ps/exchange/New-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md index 79afcd0346..3823a8a342 100644 --- a/exchange/exchange-ps/exchange/New-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-antiphishrule +schema: 2.0.0 +title: New-AntiPhishRule --- # New-AntiPhishRule @@ -59,13 +60,15 @@ 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 @@ -75,6 +78,9 @@ 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: @@ -89,7 +95,6 @@ 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 @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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`. @@ -124,7 +134,6 @@ 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 @@ -134,6 +143,9 @@ 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. @@ -145,7 +157,6 @@ 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 @@ -155,13 +166,15 @@ 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 @@ -171,6 +184,9 @@ 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 @@ -186,7 +202,6 @@ 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 @@ -196,6 +211,9 @@ 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 @@ -213,7 +231,6 @@ 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 @@ -223,6 +240,9 @@ 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: @@ -237,7 +257,6 @@ 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 @@ -247,13 +266,15 @@ 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 @@ -263,6 +284,9 @@ 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 @@ -278,7 +302,6 @@ 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 @@ -288,6 +311,9 @@ 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 @@ -305,7 +331,6 @@ 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 @@ -315,13 +340,15 @@ 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/exchange/New-App.md b/exchange/exchange-ps/ExchangePowerShell/New-App.md similarity index 88% rename from exchange/exchange-ps/exchange/New-App.md rename to exchange/exchange-ps/ExchangePowerShell/New-App.md index 12f88e9b57..138f10ad8a 100644 --- a/exchange/exchange-ps/exchange/New-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-App.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-app +schema: 2.0.0 +title: New-App --- # New-App @@ -146,6 +147,9 @@ 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 }} @@ -154,7 +158,6 @@ This parameter is available only in the cloud-based service. Type: AddInOverrides Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -164,13 +167,15 @@ 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 @@ -180,6 +185,9 @@ Accept wildcard characters: False ``` ### -AllowSetting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AllowSetting Description }} @@ -188,7 +196,6 @@ This parameter is available only in the cloud-based service. Type: AllowSetting Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -198,6 +205,9 @@ Accept wildcard characters: False ``` ### -AppState + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AppState Description }} @@ -206,7 +216,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,6 +225,9 @@ Accept wildcard characters: False ``` ### -AppType + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AppType Description }} @@ -224,7 +236,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -234,6 +245,9 @@ 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`. @@ -243,7 +257,6 @@ 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 @@ -253,6 +266,9 @@ 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. @@ -265,7 +281,6 @@ 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 @@ -275,6 +290,9 @@ 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. @@ -283,7 +301,6 @@ 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 @@ -293,6 +310,9 @@ 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. @@ -301,7 +321,6 @@ 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 @@ -311,6 +330,9 @@ 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. @@ -322,7 +344,6 @@ 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 @@ -332,13 +353,15 @@ 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 @@ -348,6 +371,9 @@ 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`). @@ -356,7 +382,6 @@ 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 @@ -366,13 +391,15 @@ 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 @@ -382,6 +409,9 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Identity Description }} @@ -390,7 +420,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -400,6 +429,9 @@ 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 @@ -417,7 +449,6 @@ 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 @@ -427,13 +458,15 @@ 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 @@ -443,13 +476,15 @@ 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 @@ -459,13 +494,15 @@ 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 @@ -475,13 +512,15 @@ 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 @@ -491,13 +530,15 @@ 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 @@ -507,13 +548,15 @@ 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 @@ -523,13 +566,15 @@ 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 @@ -539,6 +584,9 @@ 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. @@ -550,7 +598,6 @@ 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 @@ -560,6 +607,9 @@ Accept wildcard characters: False ``` ### -UpdateAppState + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UpdateAppState Description }} @@ -568,7 +618,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -578,6 +627,9 @@ 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. @@ -586,7 +638,6 @@ 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 @@ -596,6 +647,9 @@ 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: @@ -619,7 +673,6 @@ 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 @@ -629,6 +682,9 @@ Accept wildcard characters: False ``` ### -Version + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Version Description }} @@ -637,7 +693,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -647,13 +702,15 @@ 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/exchange/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md index 669e94235e..1aa72a70b2 100644 --- a/exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-appretentioncompliancepolicy +schema: 2.0.0 +title: New-AppRetentionCompliancePolicy --- # New-AppRetentionCompliancePolicy @@ -70,13 +71,15 @@ 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 @@ -86,6 +89,9 @@ 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 @@ -96,7 +102,6 @@ The AdaptiveScopeLocation parameter specifies the adaptive scope location to inc Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -106,6 +111,9 @@ 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`: @@ -136,7 +144,6 @@ This parameter uses the following syntax: `"LocationType:App1,LocationType:App2, Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -146,13 +153,15 @@ 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 @@ -162,6 +171,9 @@ 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`. @@ -171,7 +183,6 @@ 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 @@ -181,6 +192,9 @@ 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. @@ -190,7 +204,6 @@ The Enabled parameter enables or disables the policy. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -200,6 +213,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocation + +> Applicable: Security & Compliance + The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - A mailbox @@ -219,7 +235,6 @@ 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 @@ -229,6 +244,9 @@ 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 @@ -247,7 +265,6 @@ 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 @@ -257,6 +274,9 @@ 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. @@ -265,7 +285,6 @@ 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 @@ -275,6 +294,9 @@ 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 @@ -293,7 +315,6 @@ 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 @@ -303,6 +324,9 @@ 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: @@ -318,7 +342,6 @@ 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 @@ -328,6 +351,9 @@ 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. @@ -338,7 +364,6 @@ 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 @@ -348,6 +373,9 @@ 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. @@ -361,7 +389,6 @@ 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 @@ -371,13 +398,15 @@ 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/exchange/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md index 3d8602cf9a..4393263c06 100644 --- a/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-appretentioncompliancerule +schema: 2.0.0 +title: New-AppRetentionComplianceRule --- # New-AppRetentionComplianceRule @@ -63,13 +64,15 @@ 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 @@ -79,6 +82,9 @@ 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 @@ -89,7 +95,6 @@ The Policy parameter specifies the app retention compliance policy that contains Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -99,13 +104,15 @@ 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 @@ -115,6 +122,9 @@ 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`. @@ -124,7 +134,6 @@ 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,6 +143,9 @@ 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"})`. @@ -144,7 +156,6 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information Type: PswsHashtable[] Parameter Sets: ComplianceTag Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -154,6 +165,9 @@ 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). @@ -162,7 +176,6 @@ 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 @@ -172,6 +185,9 @@ 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 @@ -191,7 +207,6 @@ 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 @@ -201,6 +216,9 @@ 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 @@ -210,7 +228,6 @@ The ExpirationDateOption parameter specifies whether the expiration date is calc Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -220,13 +237,15 @@ 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 @@ -236,6 +255,9 @@ Accept wildcard characters: False ``` ### -RetentionComplianceAction + +> Applicable: Security & Compliance + The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - Delete @@ -246,7 +268,6 @@ The RetentionComplianceAction parameter specifies the retention action for the r Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -256,6 +277,9 @@ 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. @@ -265,7 +289,6 @@ The RetentionDuration parameter specifies the hold duration for the retention ru Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -275,6 +298,9 @@ 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 @@ -288,7 +314,6 @@ Type: HoldDurationHint Parameter Sets: Default Aliases: Accepted values: Days, Months, Years -Applicable: Security & Compliance Required: False Position: Named @@ -298,13 +323,15 @@ 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/exchange/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md index 3a8139e536..07407ee4ca 100644 --- a/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-applicationaccesspolicy +schema: 2.0.0 +title: New-ApplicationAccessPolicy --- # New-ApplicationAccessPolicy @@ -86,6 +87,9 @@ 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. @@ -95,7 +99,6 @@ 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 @@ -105,6 +108,9 @@ 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. @@ -113,7 +119,6 @@ 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 @@ -123,6 +128,9 @@ 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) @@ -156,7 +164,6 @@ 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 @@ -166,6 +173,9 @@ 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`. @@ -175,7 +185,6 @@ 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 @@ -185,13 +194,15 @@ 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 @@ -201,13 +212,15 @@ 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/exchange/New-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md similarity index 90% rename from exchange/exchange-ps/exchange/New-AuthRedirect.md rename to exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md index d885bf6957..4263fef384 100644 --- a/exchange/exchange-ps/exchange/New-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-authredirect +schema: 2.0.0 +title: New-AuthRedirect --- # New-AuthRedirect @@ -48,13 +49,15 @@ 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 @@ -64,13 +67,15 @@ 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 @@ -80,6 +85,9 @@ 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,7 +97,6 @@ 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 @@ -99,13 +106,15 @@ 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,13 +124,15 @@ 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/exchange/New-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md similarity index 90% rename from exchange/exchange-ps/exchange/New-AuthServer.md rename to exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md index 5837e8cdb9..2ab68344e6 100644 --- a/exchange/exchange-ps/exchange/New-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-authserver +schema: 2.0.0 +title: New-AuthServer --- # New-AuthServer @@ -73,13 +74,15 @@ 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 @@ -89,13 +92,15 @@ 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 @@ -105,6 +110,9 @@ 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 @@ -117,7 +125,6 @@ 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 @@ -127,6 +134,9 @@ 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 }} @@ -135,7 +145,6 @@ 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 @@ -145,6 +154,9 @@ 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,7 +166,6 @@ 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 @@ -164,13 +175,15 @@ 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 @@ -180,13 +193,15 @@ 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 @@ -196,6 +211,9 @@ 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 @@ -205,7 +223,6 @@ 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 @@ -215,6 +232,9 @@ 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. @@ -223,7 +243,6 @@ 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 @@ -233,13 +252,15 @@ 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/exchange/New-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/New-AuthenticationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md index 4c06f72d1a..beb96b10fc 100644 --- a/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-authenticationpolicy +schema: 2.0.0 +title: New-AuthenticationPolicy --- # New-AuthenticationPolicy @@ -77,13 +78,15 @@ 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 @@ -93,6 +96,9 @@ 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. @@ -103,7 +109,6 @@ 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 @@ -113,6 +118,9 @@ 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. @@ -123,7 +131,6 @@ 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 @@ -133,6 +140,9 @@ 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. @@ -143,7 +153,6 @@ 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 @@ -153,6 +162,9 @@ 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. @@ -163,7 +175,6 @@ 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 @@ -173,6 +184,9 @@ 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. @@ -183,7 +197,6 @@ 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 @@ -193,6 +206,9 @@ 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. @@ -203,7 +219,6 @@ 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 @@ -213,6 +228,9 @@ 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. @@ -223,7 +241,6 @@ 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 @@ -233,6 +250,9 @@ 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. @@ -243,7 +263,6 @@ 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 @@ -253,6 +272,9 @@ 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. @@ -263,7 +285,6 @@ 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 @@ -273,6 +294,9 @@ 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. @@ -283,7 +307,6 @@ 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 @@ -293,6 +316,9 @@ 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. @@ -303,7 +329,6 @@ 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 @@ -313,6 +338,9 @@ 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. @@ -323,7 +351,6 @@ 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 @@ -333,6 +360,9 @@ 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. @@ -349,7 +379,6 @@ 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 @@ -359,6 +388,9 @@ 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. @@ -375,7 +407,6 @@ 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 @@ -385,6 +416,9 @@ 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. @@ -401,7 +435,6 @@ 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 @@ -411,6 +444,9 @@ 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. @@ -427,7 +463,6 @@ 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 @@ -437,6 +472,9 @@ 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. @@ -453,7 +491,6 @@ 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 @@ -463,6 +500,9 @@ 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. @@ -479,7 +519,6 @@ 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 @@ -489,6 +528,9 @@ 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. @@ -505,7 +547,6 @@ 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 @@ -515,6 +556,9 @@ 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. @@ -531,7 +575,6 @@ 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 @@ -541,6 +584,9 @@ 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. @@ -549,7 +595,6 @@ The BlockModernAuthActiveSync switch specifies whether to block modern authentic Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -559,6 +604,9 @@ 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. @@ -567,7 +615,6 @@ The BlockModernAuthAutodiscover switch specifies whether to block modern authent Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -577,6 +624,9 @@ 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. @@ -585,7 +635,6 @@ The BlockModernAuthImap switch specifies whether to block modern authentication Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -595,6 +644,9 @@ 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. @@ -603,7 +655,6 @@ The BlockModernAuthMapi switch specifies whether to block modern authentication Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -613,6 +664,9 @@ 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. @@ -621,7 +675,6 @@ The BlockModernAuthOfflineAddressBook switch specifies whether to block modern a Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -631,6 +684,9 @@ 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. @@ -639,7 +695,6 @@ The BlockModernAuthPop switch specifies whether to block modern authentication w Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -649,6 +704,9 @@ 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. @@ -657,7 +715,6 @@ The BlockModernAuthRpc switch specifies whether to block modern authentication w Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -667,6 +724,9 @@ 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. @@ -675,7 +735,6 @@ The BlockModernAuthWebServices switch specifies whether to block modern authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -685,6 +744,9 @@ 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`. @@ -694,7 +756,6 @@ 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 @@ -704,13 +765,15 @@ 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/exchange/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md index 41c5654713..451acc9fdc 100644 --- a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-autosensitivitylabelpolicy +schema: 2.0.0 +title: New-AutoSensitivityLabelPolicy --- # New-AutoSensitivityLabelPolicy @@ -71,13 +72,15 @@ 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 @@ -87,13 +90,15 @@ 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 @@ -103,13 +108,15 @@ 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 @@ -119,6 +126,9 @@ 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`. @@ -128,7 +138,6 @@ 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 @@ -138,6 +147,9 @@ 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). @@ -150,7 +162,6 @@ You can't use this parameter with the OneDriveSharedBy parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -160,13 +171,15 @@ 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 @@ -176,13 +189,15 @@ 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 @@ -192,13 +207,15 @@ 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 @@ -208,6 +225,9 @@ 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: @@ -228,7 +248,6 @@ You can't specify inclusions and exclusions in the same policy. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -238,6 +257,9 @@ 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: `"","",...""`. @@ -250,7 +272,6 @@ You can't use this parameter with the ExchangeSenderException or ExchangeSenderM Type: SmtpAddress[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -260,6 +281,9 @@ 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: `"","",...""`. @@ -272,7 +296,6 @@ 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 @@ -282,6 +305,9 @@ 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: `"","",...""`. @@ -296,7 +322,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: SmtpAddress[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -306,6 +331,9 @@ 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: `"","",...""`. @@ -320,7 +348,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: SmtpAddress[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -330,6 +357,9 @@ 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. @@ -338,7 +368,6 @@ 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 @@ -348,6 +377,9 @@ 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. @@ -356,7 +388,6 @@ 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 @@ -366,13 +397,15 @@ 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 @@ -382,6 +415,9 @@ 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. @@ -394,7 +430,6 @@ Type: PolicyMode Parameter Sets: (All) Aliases: Accepted values: Enable, TestWithNotifications, TestWithoutNotifications, Disable, PendingDeletion -Applicable: Security & Compliance Required: False Position: Named @@ -404,13 +439,15 @@ 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 @@ -420,13 +457,15 @@ 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 @@ -436,6 +475,9 @@ 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"`. @@ -444,7 +486,6 @@ 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 @@ -454,6 +495,9 @@ 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"`. @@ -462,7 +506,6 @@ 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 @@ -472,6 +515,9 @@ 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). @@ -484,7 +530,6 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -494,13 +539,15 @@ 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 @@ -510,6 +557,9 @@ 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. @@ -521,7 +571,6 @@ This parameter works only on Exchange locations. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -531,6 +580,9 @@ 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. @@ -539,7 +591,6 @@ 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 @@ -549,13 +600,15 @@ 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 @@ -565,13 +618,15 @@ 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 @@ -581,13 +636,15 @@ 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 @@ -597,13 +654,15 @@ 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 @@ -613,6 +672,9 @@ 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. @@ -621,7 +683,6 @@ 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 @@ -631,6 +692,9 @@ 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"`. @@ -639,7 +703,6 @@ 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 @@ -649,13 +712,15 @@ 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 @@ -665,13 +730,15 @@ 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/exchange/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md index 43a5384ec8..1cfc515f96 100644 --- a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-autosensitivitylabelrule +schema: 2.0.0 +title: New-AutoSensitivityLabelRule --- # New-AutoSensitivityLabelRule @@ -97,13 +98,15 @@ 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 @@ -113,6 +116,9 @@ Accept wildcard characters: False ``` ### -Workload + +> Applicable: Security & Compliance + The Workload parameter specifies the workload. Valid values are: - Exchange @@ -124,7 +130,6 @@ Type: Workload Parameter Sets: (All) Aliases: Accepted values: Exchange, SharePoint, OneDriveForBusiness -Applicable: Security & Compliance Required: True Position: Named @@ -134,6 +139,9 @@ 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. @@ -145,7 +153,6 @@ Type: AccessScope Parameter Sets: (All) Aliases: Accepted values: InOrganization, NotInOrganization, None -Applicable: Security & Compliance Required: False Position: Named @@ -155,13 +162,15 @@ 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 @@ -171,6 +180,9 @@ 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"` @@ -185,7 +197,6 @@ 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 @@ -195,6 +206,9 @@ 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. @@ -205,7 +219,6 @@ 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 @@ -215,13 +228,15 @@ 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 @@ -231,6 +246,9 @@ 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`. @@ -240,7 +258,6 @@ 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 @@ -250,6 +267,9 @@ 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"})`. @@ -262,7 +282,6 @@ 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 @@ -272,13 +291,15 @@ 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 @@ -288,6 +309,9 @@ 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"`. @@ -296,7 +320,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -306,6 +329,9 @@ 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. @@ -315,7 +341,6 @@ 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 @@ -325,13 +350,15 @@ 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 @@ -341,6 +368,9 @@ 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. @@ -350,7 +380,6 @@ The DocumentIsPasswordProtected parameter specifies a condition for the auto-lab Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -360,6 +389,9 @@ 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. @@ -369,7 +401,6 @@ The DocumentIsUnsupported parameter specifies a condition for the auto-labeling Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -379,6 +410,9 @@ 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"` @@ -391,7 +425,6 @@ 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 @@ -401,6 +434,9 @@ 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: @@ -419,7 +455,6 @@ 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 @@ -429,6 +464,9 @@ 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. @@ -440,7 +478,6 @@ Type: AccessScope Parameter Sets: (All) Aliases: Accepted values: InOrganization, NotInOrganization, None -Applicable: Security & Compliance Required: False Position: Named @@ -450,6 +487,9 @@ 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"` @@ -464,7 +504,6 @@ 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 @@ -474,6 +513,9 @@ 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. @@ -484,7 +526,6 @@ 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 @@ -494,6 +535,9 @@ 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"})`. @@ -502,7 +546,6 @@ This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minC Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -512,13 +555,15 @@ 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 @@ -528,6 +573,9 @@ 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"`. @@ -536,7 +584,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -546,13 +593,15 @@ 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 @@ -562,6 +611,9 @@ 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. @@ -571,7 +623,6 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -581,6 +632,9 @@ 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. @@ -590,7 +644,6 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the auto- Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -600,6 +653,9 @@ 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"` @@ -612,7 +668,6 @@ 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 @@ -622,6 +677,9 @@ 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: @@ -640,7 +698,6 @@ 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 @@ -650,6 +707,9 @@ 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 @@ -663,7 +723,6 @@ 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 @@ -673,6 +732,9 @@ 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"` @@ -687,7 +749,6 @@ 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 @@ -697,6 +758,9 @@ 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. @@ -707,7 +771,6 @@ 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 @@ -717,6 +780,9 @@ 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"`. @@ -725,7 +791,6 @@ 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 @@ -735,6 +800,9 @@ 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. @@ -743,7 +811,6 @@ 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 @@ -753,6 +820,9 @@ 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. @@ -762,7 +832,6 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the aut Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -772,13 +841,15 @@ 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 @@ -788,6 +859,9 @@ 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. @@ -796,7 +870,6 @@ 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 @@ -806,6 +879,9 @@ 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. @@ -818,7 +894,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -828,6 +903,9 @@ 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 @@ -845,7 +923,6 @@ 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 @@ -855,6 +932,9 @@ 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. @@ -863,7 +943,6 @@ 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 @@ -873,6 +952,9 @@ 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. @@ -883,7 +965,6 @@ 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 @@ -893,13 +974,15 @@ 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 @@ -909,13 +992,15 @@ 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 @@ -925,6 +1010,9 @@ 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"` @@ -939,7 +1027,6 @@ 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 @@ -949,6 +1036,9 @@ 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. @@ -959,7 +1049,6 @@ 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 @@ -969,13 +1058,15 @@ 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 @@ -985,6 +1076,9 @@ 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. @@ -993,7 +1087,6 @@ 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 @@ -1003,13 +1096,15 @@ 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 @@ -1019,6 +1114,9 @@ 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 @@ -1029,7 +1127,6 @@ 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 @@ -1039,13 +1136,15 @@ 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 @@ -1055,6 +1154,9 @@ 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. @@ -1064,7 +1166,6 @@ The ProcessingLimitExceeded parameter specifies a condition for the auto-labelin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1074,13 +1175,15 @@ 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 @@ -1090,6 +1193,9 @@ 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. @@ -1102,7 +1208,6 @@ Type: RuleSeverity Parameter Sets: (All) Aliases: Accepted values: Low, Medium, High, None, Informational, Information -Applicable: Security & Compliance Required: False Position: Named @@ -1112,6 +1217,9 @@ 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 @@ -1123,7 +1231,6 @@ Type: PolicyRuleErrorAction Parameter Sets: (All) Aliases: Accepted values: Ignore, RetryThenBlock -Applicable: Security & Compliance Required: False Position: Named @@ -1133,6 +1240,9 @@ 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. @@ -1141,7 +1251,6 @@ 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 @@ -1151,6 +1260,9 @@ 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. @@ -1163,7 +1275,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1173,6 +1284,9 @@ 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 @@ -1190,7 +1304,6 @@ 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 @@ -1200,6 +1313,9 @@ 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. @@ -1208,7 +1324,6 @@ 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 @@ -1218,13 +1333,15 @@ 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 @@ -1234,6 +1351,9 @@ 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. @@ -1244,7 +1364,6 @@ 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 @@ -1254,13 +1373,15 @@ 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/exchange/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md index d79e23f643..e2d5b8f5ae 100644 --- a/exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-autodiscovervirtualdirectory +schema: 2.0.0 +title: New-AutodiscoverVirtualDirectory --- # New-AutodiscoverVirtualDirectory @@ -62,13 +63,15 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,6 +99,9 @@ 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. @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ 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,7 +132,6 @@ 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 @@ -132,6 +141,9 @@ 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. @@ -141,7 +153,6 @@ 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 @@ -151,13 +162,15 @@ 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,6 +180,9 @@ 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. @@ -179,7 +195,6 @@ 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 @@ -189,6 +204,9 @@ 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. @@ -198,7 +216,6 @@ 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 @@ -208,6 +225,9 @@ 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. @@ -220,7 +240,6 @@ 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 @@ -230,6 +249,9 @@ 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. @@ -238,7 +260,6 @@ 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 @@ -248,6 +269,9 @@ 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. @@ -256,7 +280,6 @@ 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 @@ -266,6 +289,9 @@ 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. @@ -275,7 +301,6 @@ 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 @@ -285,13 +310,15 @@ 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 @@ -301,6 +328,9 @@ 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. @@ -312,7 +342,6 @@ 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 @@ -322,6 +351,9 @@ 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 @@ -333,7 +365,6 @@ 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 @@ -343,13 +374,15 @@ 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 @@ -359,13 +392,15 @@ 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 @@ -375,6 +410,9 @@ 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. @@ -384,7 +422,6 @@ 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 @@ -394,6 +431,9 @@ 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. @@ -403,7 +443,6 @@ 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/exchange/New-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/New-AvailabilityConfig.md rename to exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md index 7019d149b7..838837f4d8 100644 --- a/exchange/exchange-ps/exchange/New-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-availabilityconfig +schema: 2.0.0 +title: New-AvailabilityConfig --- # New-AvailabilityConfig @@ -44,13 +45,15 @@ 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 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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 @@ -95,13 +102,15 @@ 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/exchange/New-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md similarity index 94% rename from exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md rename to exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md index 4c31737bf7..576921f588 100644 --- a/exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-availabilityreportoutage +schema: 2.0.0 +title: New-AvailabilityReportOutage --- # New-AvailabilityReportOutage @@ -45,13 +46,15 @@ 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 @@ -61,13 +64,15 @@ 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 @@ -77,13 +82,15 @@ 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 @@ -93,13 +100,15 @@ 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 @@ -109,6 +118,9 @@ 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`. @@ -118,7 +130,6 @@ 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 @@ -128,6 +139,9 @@ 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. @@ -136,7 +150,6 @@ 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 @@ -146,13 +159,15 @@ 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 @@ -162,13 +177,15 @@ 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 @@ -178,13 +195,15 @@ 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/exchange/New-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-CaseHoldPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md index 87605314fc..44105f5c35 100644 --- a/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-caseholdpolicy +schema: 2.0.0 +title: New-CaseHoldPolicy --- # New-CaseHoldPolicy @@ -55,13 +56,15 @@ 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 @@ -71,6 +74,9 @@ 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 @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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,6 +115,9 @@ 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`. @@ -117,7 +127,6 @@ 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 @@ -127,6 +136,9 @@ 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. @@ -136,7 +148,6 @@ 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 @@ -146,6 +157,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocation + +> Applicable: Security & Compliance + The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - A mailbox @@ -165,7 +179,6 @@ 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 @@ -175,6 +188,9 @@ 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. @@ -183,7 +199,6 @@ 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 @@ -193,13 +208,15 @@ 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 @@ -209,6 +226,9 @@ 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"`. @@ -219,7 +239,6 @@ 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 @@ -229,13 +248,15 @@ 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/exchange/New-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md similarity index 95% rename from exchange/exchange-ps/exchange/New-CaseHoldRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md index c169c5dfff..aa20ee085b 100644 --- a/exchange/exchange-ps/exchange/New-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-caseholdrule +schema: 2.0.0 +title: New-CaseHoldRule --- # New-CaseHoldRule @@ -54,13 +55,15 @@ 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 @@ -70,6 +73,9 @@ 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 @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ 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`. @@ -115,7 +125,6 @@ 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 @@ -125,6 +134,9 @@ 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). @@ -133,7 +145,6 @@ 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 @@ -143,6 +154,9 @@ 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. @@ -152,7 +166,6 @@ 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 @@ -162,13 +175,15 @@ 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/exchange/New-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md similarity index 92% rename from exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md index 2f589a0ceb..aa5f7175ba 100644 --- a/exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-classificationrulecollection +schema: 2.0.0 +title: New-ClassificationRuleCollection --- # New-ClassificationRuleCollection @@ -45,6 +46,9 @@ 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`). @@ -53,7 +57,6 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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. @@ -92,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/New-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ClientAccessArray.md rename to exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md index 93bc940c38..4f93a239bf 100644 --- a/exchange/exchange-ps/exchange/New-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-clientaccessarray +schema: 2.0.0 +title: New-ClientAccessArray --- # New-ClientAccessArray @@ -54,6 +55,9 @@ 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. @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,6 +93,9 @@ 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 @@ -100,7 +108,6 @@ 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 @@ -110,6 +117,9 @@ 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`. @@ -119,7 +129,6 @@ 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 @@ -129,13 +138,15 @@ 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 @@ -145,13 +156,15 @@ 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/exchange/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md similarity index 90% rename from exchange/exchange-ps/exchange/New-ClientAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md index af5e934438..25e103ec1c 100644 --- a/exchange/exchange-ps/exchange/New-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-clientaccessrule +schema: 2.0.0 +title: New-ClientAccessRule --- # New-ClientAccessRule @@ -91,13 +92,15 @@ 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 @@ -107,13 +110,15 @@ 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 @@ -123,6 +128,9 @@ 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. @@ -143,7 +151,6 @@ 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 @@ -153,6 +160,9 @@ 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. @@ -167,7 +177,6 @@ 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 @@ -177,6 +186,9 @@ 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: @@ -202,7 +214,6 @@ 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 @@ -212,13 +223,15 @@ 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 @@ -228,6 +241,9 @@ 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`. @@ -239,7 +255,6 @@ 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 @@ -249,6 +264,9 @@ 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. @@ -257,7 +275,6 @@ 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 @@ -267,13 +284,15 @@ 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 @@ -283,6 +302,9 @@ 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. @@ -303,7 +325,6 @@ 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 @@ -313,6 +334,9 @@ 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. @@ -327,7 +351,6 @@ 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 @@ -337,6 +360,9 @@ 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. @@ -362,7 +388,6 @@ 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 @@ -372,13 +397,15 @@ 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 @@ -388,13 +415,15 @@ 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 @@ -404,6 +433,9 @@ 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. @@ -414,7 +446,6 @@ 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 @@ -424,6 +455,9 @@ 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: @@ -438,7 +472,6 @@ 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 @@ -448,6 +481,9 @@ 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. @@ -457,7 +493,6 @@ 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 @@ -467,13 +502,15 @@ 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 @@ -483,6 +520,9 @@ 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. @@ -493,7 +533,6 @@ 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 @@ -503,6 +542,9 @@ 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. @@ -542,7 +584,6 @@ 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 @@ -552,13 +593,15 @@ 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/exchange/New-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ComplianceCase.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md index 6366bff3d0..50cd294d5e 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancecase +schema: 2.0.0 +title: New-ComplianceCase --- # New-ComplianceCase @@ -55,13 +56,15 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -87,7 +93,6 @@ 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 @@ -97,6 +102,9 @@ 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,7 +114,6 @@ 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,13 +123,15 @@ 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 @@ -132,13 +141,15 @@ 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 @@ -148,13 +159,15 @@ 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 @@ -164,13 +177,15 @@ 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 @@ -180,13 +195,15 @@ 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 @@ -196,13 +213,15 @@ 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/exchange/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md index f1f5f46411..e6cd8f1878 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-complianceretentionevent +schema: 2.0.0 +title: New-ComplianceRetentionEvent --- # New-ComplianceRetentionEvent @@ -55,13 +56,15 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -81,7 +87,6 @@ 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 @@ -91,13 +96,15 @@ 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 @@ -107,6 +114,9 @@ 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`. @@ -116,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ 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 @@ -142,6 +153,9 @@ 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". @@ -150,7 +164,6 @@ 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 @@ -160,6 +173,9 @@ 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. @@ -168,7 +184,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -178,13 +193,15 @@ 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 @@ -194,13 +211,15 @@ 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 @@ -210,13 +229,15 @@ 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 @@ -226,13 +247,15 @@ 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 @@ -242,13 +265,15 @@ 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/exchange/New-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md index f8097fbf29..7efffd5601 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-complianceretentioneventtype +schema: 2.0.0 +title: New-ComplianceRetentionEventType --- # New-ComplianceRetentionEventType @@ -43,13 +44,15 @@ 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 @@ -59,13 +62,15 @@ 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 @@ -75,6 +80,9 @@ 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,7 +92,6 @@ 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 @@ -94,13 +101,15 @@ 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/exchange/New-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md similarity index 92% rename from exchange/exchange-ps/exchange/New-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md index bb3b8def59..e432aa9e87 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesearch +schema: 2.0.0 +title: New-ComplianceSearch --- # New-ComplianceSearch @@ -81,6 +82,9 @@ 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. @@ -89,7 +93,6 @@ 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 @@ -99,6 +102,9 @@ 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. @@ -115,7 +121,6 @@ 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 @@ -125,6 +130,9 @@ 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. @@ -137,7 +145,6 @@ 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 @@ -147,6 +154,9 @@ 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`. @@ -156,7 +166,6 @@ 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 @@ -166,6 +175,9 @@ 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). @@ -174,7 +186,6 @@ 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 @@ -184,13 +195,15 @@ 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 @@ -200,6 +213,9 @@ 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. @@ -212,7 +228,6 @@ 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 @@ -222,6 +237,9 @@ 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: @@ -235,7 +253,6 @@ 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 @@ -245,6 +262,9 @@ 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. @@ -253,7 +273,6 @@ 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 @@ -263,6 +282,9 @@ 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. @@ -273,7 +295,6 @@ 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 @@ -283,13 +304,15 @@ 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 @@ -299,6 +322,9 @@ 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: @@ -310,7 +336,6 @@ The IncludeUserAppContent parameter specifies that you want to search the cloud- Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -320,6 +345,9 @@ 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). @@ -328,7 +356,6 @@ 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 @@ -338,6 +365,9 @@ 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. @@ -346,7 +376,6 @@ 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 @@ -356,6 +385,9 @@ 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. @@ -364,7 +396,6 @@ The PublicFolderLocation parameter specifies that you want to include all public Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -374,6 +405,9 @@ 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. @@ -382,7 +416,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -392,6 +425,9 @@ 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. @@ -402,7 +438,6 @@ 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 @@ -412,6 +447,9 @@ 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. @@ -420,7 +458,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -430,6 +467,9 @@ 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. @@ -438,7 +478,6 @@ 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 @@ -448,13 +487,15 @@ 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/exchange/New-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md similarity index 91% rename from exchange/exchange-ps/exchange/New-ComplianceSearchAction.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md index e2b6541d63..4dee5e4b86 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesearchaction +schema: 2.0.0 +title: New-ComplianceSearchAction --- # New-ComplianceSearchAction @@ -141,6 +142,9 @@ 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. @@ -149,7 +153,6 @@ 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 @@ -159,6 +162,9 @@ 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. @@ -167,7 +173,6 @@ 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 @@ -177,6 +182,9 @@ 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. @@ -185,7 +193,6 @@ 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 @@ -195,6 +202,9 @@ 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`. @@ -206,7 +216,6 @@ 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 @@ -216,6 +225,9 @@ 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. @@ -224,7 +236,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Export Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -235,6 +246,8 @@ 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. @@ -256,7 +269,6 @@ 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 @@ -266,6 +278,9 @@ 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. @@ -280,7 +295,6 @@ 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 @@ -290,6 +304,9 @@ 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. @@ -298,7 +315,6 @@ 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 @@ -308,6 +324,9 @@ 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. @@ -316,7 +335,6 @@ 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 @@ -326,6 +344,9 @@ 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: @@ -338,7 +359,6 @@ 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 @@ -348,13 +368,15 @@ 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 @@ -364,6 +386,9 @@ 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. @@ -377,7 +402,6 @@ The IncludeSharePointDocumentVersions parameter specifies whether to export prev Type: Boolean Parameter Sets: Export Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -387,13 +411,15 @@ 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 @@ -403,6 +429,9 @@ 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. @@ -415,7 +444,6 @@ 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 @@ -425,6 +453,9 @@ 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. @@ -437,7 +468,6 @@ 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 @@ -447,6 +477,9 @@ 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. @@ -455,7 +488,6 @@ 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 @@ -465,6 +497,9 @@ 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. @@ -481,7 +516,6 @@ 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 @@ -491,6 +525,9 @@ 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: @@ -502,7 +539,6 @@ 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 @@ -512,13 +548,15 @@ 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 @@ -528,13 +566,15 @@ 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 @@ -544,6 +584,9 @@ 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. @@ -554,7 +597,6 @@ 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 @@ -564,6 +606,9 @@ 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. @@ -572,7 +617,6 @@ 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 @@ -582,13 +626,15 @@ 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 @@ -598,6 +644,9 @@ 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: @@ -613,7 +662,6 @@ 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 @@ -623,6 +671,9 @@ 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: @@ -635,7 +686,6 @@ 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 @@ -645,6 +695,9 @@ 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. @@ -655,7 +708,6 @@ 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 @@ -665,6 +717,9 @@ 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. @@ -683,7 +738,6 @@ 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 @@ -693,6 +747,9 @@ 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). @@ -703,7 +760,6 @@ 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 @@ -713,13 +769,15 @@ 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 @@ -729,6 +787,9 @@ 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. @@ -737,7 +798,6 @@ 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/exchange/New-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md index cf258e62c7..99f2d49266 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesecurityfilter +schema: 2.0.0 +title: New-ComplianceSecurityFilter --- # New-ComplianceSecurityFilter @@ -75,6 +76,9 @@ 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. @@ -87,7 +91,6 @@ 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 @@ -97,13 +100,15 @@ 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 @@ -113,6 +118,9 @@ 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. @@ -125,7 +133,6 @@ 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 @@ -135,6 +142,9 @@ 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`. @@ -144,7 +154,6 @@ 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 @@ -154,13 +163,15 @@ 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 @@ -170,6 +181,9 @@ 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). @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ 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 @@ -213,7 +229,6 @@ 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 @@ -223,13 +238,15 @@ 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/exchange/New-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md similarity index 89% rename from exchange/exchange-ps/exchange/New-ComplianceTag.md rename to exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md index 9de8c0fca4..b56930ed62 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancetag +schema: 2.0.0 +title: New-ComplianceTag --- # New-ComplianceTag @@ -75,13 +76,15 @@ 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 @@ -91,13 +94,15 @@ 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 @@ -107,6 +112,9 @@ Accept wildcard characters: False ``` ### -RetentionAction + +> Applicable: Security & Compliance + The RetentionAction parameter specifies the action for the label. Valid values are: - Delete @@ -115,9 +123,8 @@ The RetentionAction parameter specifies the action for the label. Valid values a ```yaml Type: String -Parameter Sets: PriorityCleanup +Parameter Sets: Default, PriorityCleanup Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -126,20 +133,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: Security & Compliance +### -RetentionDuration -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Security & Compliance -### -RetentionDuration The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: - A positive integer. @@ -147,9 +144,8 @@ The RetentionDuration parameter specifies the number of days to retain the conte ```yaml Type: Unlimited -Parameter Sets: PriorityCleanup +Parameter Sets: Default, PriorityCleanup Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -158,20 +154,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Unlimited -Parameter Sets: Default -Aliases: -Applicable: Security & Compliance +### -RetentionType -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Security & Compliance -### -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 @@ -181,9 +167,8 @@ The RetentionType parameter specifies whether the retention duration is calculat ```yaml Type: String -Parameter Sets: PriorityCleanup +Parameter Sets: Default, PriorityCleanup Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -192,27 +177,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: Security & Compliance +### -AutoApprovalPeriod -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Security & Compliance -### -AutoApprovalPeriod {{ Fill AutoApprovalPeriod Description }} ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -222,13 +196,15 @@ 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 @@ -238,13 +214,15 @@ 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 @@ -254,6 +232,9 @@ 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`. @@ -263,7 +244,6 @@ 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 @@ -273,6 +253,9 @@ 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 @@ -285,7 +268,6 @@ 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 @@ -295,6 +277,9 @@ 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` @@ -328,7 +313,6 @@ You use the second variable as the value for this parameter. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -338,6 +322,9 @@ 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. @@ -351,7 +338,6 @@ 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 @@ -361,6 +347,9 @@ 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. @@ -369,7 +358,6 @@ 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 @@ -379,6 +367,9 @@ 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. @@ -388,7 +379,6 @@ 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 @@ -398,13 +388,15 @@ 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 @@ -414,6 +406,9 @@ 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]},]}'` @@ -428,7 +423,6 @@ 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 @@ -438,13 +432,15 @@ 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 @@ -454,13 +450,15 @@ 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 @@ -470,13 +468,15 @@ 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,13 +486,15 @@ 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/exchange/New-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md similarity index 90% rename from exchange/exchange-ps/exchange/New-DataClassification.md rename to exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md index ee21f6fc1a..4e752c120f 100644 --- a/exchange/exchange-ps/exchange/New-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dataclassification +schema: 2.0.0 +title: New-DataClassification --- # New-DataClassification @@ -57,13 +58,15 @@ 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 @@ -73,13 +76,15 @@ 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/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 @@ -89,6 +94,9 @@ 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. @@ -97,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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 @@ -123,6 +132,9 @@ 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`. @@ -132,7 +144,6 @@ 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 @@ -142,13 +153,15 @@ 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 @@ -158,6 +171,9 @@ 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). @@ -168,7 +184,6 @@ 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 @@ -178,13 +193,15 @@ 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/exchange/New-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md index fb8c9ddfeb..d81d7d666c 100644 --- a/exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dataencryptionpolicy +schema: 2.0.0 +title: New-DataEncryptionPolicy --- # New-DataEncryptionPolicy @@ -49,13 +50,15 @@ 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 @@ -65,6 +68,9 @@ 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). @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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`. @@ -92,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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 @@ -118,13 +127,15 @@ 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 @@ -134,6 +145,9 @@ 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. @@ -143,7 +157,6 @@ 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 @@ -153,13 +166,15 @@ 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/exchange/New-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md similarity index 91% rename from exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md index 13c5232ad5..3ae22d5b37 100644 --- a/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-databaseavailabilitygroup +schema: 2.0.0 +title: New-DatabaseAvailabilityGroup --- # New-DatabaseAvailabilityGroup @@ -81,13 +82,15 @@ 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 @@ -97,13 +100,15 @@ 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 @@ -113,6 +118,9 @@ 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,7 +130,6 @@ 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 @@ -132,13 +139,15 @@ 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 @@ -148,13 +157,15 @@ 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 @@ -164,13 +175,15 @@ 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,6 +193,9 @@ 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 @@ -189,7 +205,6 @@ 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 @@ -199,13 +214,15 @@ 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 @@ -215,13 +232,15 @@ 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 @@ -231,13 +250,15 @@ 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 @@ -247,13 +268,15 @@ 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/exchange/New-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md similarity index 86% rename from exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md index cdf95fa60f..44e6098813 100644 --- a/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-databaseavailabilitygroupnetwork +schema: 2.0.0 +title: New-DatabaseAvailabilityGroupNetwork --- # New-DatabaseAvailabilityGroupNetwork @@ -47,13 +48,15 @@ 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 @@ -63,13 +66,15 @@ 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 @@ -79,6 +84,9 @@ 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,7 +96,6 @@ 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,13 +105,15 @@ 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 @@ -114,13 +123,15 @@ 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,13 +141,15 @@ 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 @@ -146,13 +159,15 @@ 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 @@ -162,13 +177,15 @@ 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 @@ -178,13 +195,15 @@ 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/exchange/New-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md similarity index 87% rename from exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md index 42534c6c9d..6910ba92c2 100644 --- a/exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-deliveryagentconnector +schema: 2.0.0 +title: New-DeliveryAgentConnector --- # New-DeliveryAgentConnector @@ -62,13 +63,15 @@ 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 @@ -78,13 +81,15 @@ 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 @@ -94,13 +99,15 @@ 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 @@ -110,13 +117,15 @@ 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 @@ -126,6 +135,9 @@ 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,7 +147,6 @@ 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 @@ -145,6 +156,9 @@ 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. @@ -153,7 +167,6 @@ 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 @@ -163,6 +176,9 @@ 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. @@ -171,7 +187,6 @@ 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 @@ -181,13 +196,15 @@ 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 @@ -197,13 +214,15 @@ 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 @@ -213,6 +232,9 @@ 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) @@ -226,7 +248,6 @@ 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 @@ -236,13 +257,15 @@ 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 @@ -252,6 +275,9 @@ 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. @@ -260,7 +286,6 @@ 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 @@ -270,13 +295,15 @@ 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/exchange/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md index b8386092bb..e6591cf10a 100644 --- a/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconditionalaccesspolicy +schema: 2.0.0 +title: New-DeviceConditionalAccessPolicy --- # New-DeviceConditionalAccessPolicy @@ -54,13 +55,15 @@ 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 @@ -70,13 +73,15 @@ 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 @@ -86,6 +91,9 @@ 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,7 +103,6 @@ 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 @@ -105,6 +112,9 @@ 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. @@ -114,7 +124,6 @@ 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 @@ -124,6 +133,9 @@ 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. @@ -132,7 +144,6 @@ 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 @@ -142,13 +153,15 @@ 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/exchange/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md index 102c007035..f88c237297 100644 --- a/exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconditionalaccessrule +schema: 2.0.0 +title: New-DeviceConditionalAccessRule --- # New-DeviceConditionalAccessRule @@ -103,6 +104,9 @@ 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 @@ -113,7 +117,6 @@ The Policy parameter specifies the mobile device conditional access policy that Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -123,6 +126,9 @@ 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. @@ -131,7 +137,6 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -141,6 +146,9 @@ Accept wildcard characters: False ``` ### -AccountName + +> Applicable: Security & Compliance + The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. @@ -150,7 +158,6 @@ 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 @@ -160,6 +167,9 @@ 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. @@ -169,7 +179,6 @@ The AccountUserName parameter specifies the account user name. Valid values for Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -179,6 +188,9 @@ 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. @@ -194,7 +206,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -204,6 +215,9 @@ 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. @@ -216,7 +230,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -226,6 +239,9 @@ 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. @@ -238,7 +254,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -248,6 +263,9 @@ 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. @@ -264,7 +282,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -274,6 +291,9 @@ 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. @@ -289,7 +309,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -299,6 +318,9 @@ 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. @@ -314,7 +336,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -324,6 +345,9 @@ 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. @@ -339,7 +363,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -349,6 +372,9 @@ 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. @@ -364,7 +390,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -374,6 +399,9 @@ 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,7 +414,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -396,6 +423,9 @@ 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. @@ -411,7 +441,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -421,6 +450,9 @@ 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. @@ -437,7 +469,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -447,6 +478,9 @@ 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. @@ -459,7 +493,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -469,6 +502,9 @@ 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. @@ -481,7 +517,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -491,6 +526,9 @@ 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. @@ -503,7 +541,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -513,6 +550,9 @@ Accept wildcard characters: False ``` ### -AntiVirusSignatureStatus + +> Applicable: Security & Compliance + The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. @@ -524,7 +564,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -534,6 +573,9 @@ Accept wildcard characters: False ``` ### -AntiVirusStatus + +> Applicable: Security & Compliance + The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. @@ -545,7 +587,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -555,6 +596,9 @@ 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 @@ -570,7 +614,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -580,6 +623,9 @@ Accept wildcard characters: False ``` ### -AutoUpdateStatus + +> Applicable: Security & Compliance + The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates @@ -595,7 +641,6 @@ This setting is available only on Windows 8.1 RT devices. Type: CAAutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -605,6 +650,9 @@ 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. @@ -617,7 +665,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -627,6 +674,9 @@ 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. @@ -643,7 +693,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -653,6 +702,9 @@ 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`. @@ -662,7 +714,6 @@ 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 @@ -672,13 +723,15 @@ 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 @@ -688,6 +741,9 @@ 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. @@ -697,7 +753,6 @@ The EmailAddress parameter specifies the email address. Valid values are: Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -707,6 +762,9 @@ 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. @@ -719,7 +777,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -729,6 +786,9 @@ 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. @@ -738,7 +798,6 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -748,6 +807,9 @@ 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 @@ -759,7 +821,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -769,6 +830,9 @@ 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. @@ -781,7 +845,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -791,6 +854,9 @@ 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. @@ -806,7 +872,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -816,6 +881,9 @@ 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. @@ -832,7 +900,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -842,6 +909,9 @@ 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. @@ -852,7 +922,6 @@ 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 @@ -862,6 +931,9 @@ 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: @@ -952,7 +1024,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -962,6 +1033,9 @@ Accept wildcard characters: False ``` ### -PasswordComplexity + +> Applicable: Security & Compliance + The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. @@ -971,7 +1045,6 @@ The PasswordComplexity parameter specifies the password complexity. Valid values Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -981,6 +1054,9 @@ 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. @@ -997,7 +1073,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1007,6 +1082,9 @@ 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. @@ -1023,7 +1101,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1033,6 +1110,9 @@ 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. @@ -1042,7 +1122,6 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1052,6 +1131,9 @@ 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. @@ -1068,7 +1150,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1078,6 +1159,9 @@ 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: @@ -1091,7 +1175,6 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1101,6 +1184,9 @@ 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. @@ -1117,7 +1203,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1127,6 +1212,9 @@ 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: @@ -1142,7 +1230,6 @@ 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 @@ -1152,6 +1239,9 @@ 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. @@ -1167,7 +1257,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1177,6 +1266,9 @@ 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: @@ -1198,7 +1290,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1208,6 +1299,9 @@ 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. @@ -1218,7 +1312,6 @@ The RequireEmailProfile parameter specifies whether an email profile is required Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1228,6 +1321,9 @@ 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. @@ -1240,7 +1336,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1250,6 +1345,9 @@ 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. @@ -1262,7 +1360,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1272,6 +1369,9 @@ 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: @@ -1351,7 +1451,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1361,6 +1460,9 @@ 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. @@ -1375,7 +1477,6 @@ This setting is available only on Windows 8.1 RT devices. Type: CAUserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1385,13 +1486,15 @@ 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 @@ -1401,6 +1504,9 @@ 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. @@ -1413,7 +1519,6 @@ 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 @@ -1423,6 +1528,9 @@ 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`. @@ -1433,7 +1541,6 @@ 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/exchange/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md index 67e19df788..182abb3722 100644 --- a/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconfigurationpolicy +schema: 2.0.0 +title: New-DeviceConfigurationPolicy --- # New-DeviceConfigurationPolicy @@ -54,13 +55,15 @@ 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 @@ -70,13 +73,15 @@ 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 @@ -86,6 +91,9 @@ 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,7 +103,6 @@ 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 @@ -105,6 +112,9 @@ 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. @@ -114,7 +124,6 @@ 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 @@ -124,6 +133,9 @@ 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. @@ -132,7 +144,6 @@ 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 @@ -142,13 +153,15 @@ 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/exchange/New-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md index e4505ceb8f..da9ab8e07e 100644 --- a/exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconfigurationrule +schema: 2.0.0 +title: New-DeviceConfigurationRule --- # New-DeviceConfigurationRule @@ -102,6 +103,9 @@ 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 @@ -112,7 +116,6 @@ The Policy parameter specifies the mobile device configuration policy that this Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -122,6 +125,9 @@ 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. @@ -130,7 +136,6 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -140,6 +145,9 @@ Accept wildcard characters: False ``` ### -AccountName + +> Applicable: Security & Compliance + The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. @@ -149,7 +157,6 @@ 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 @@ -159,6 +166,9 @@ 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. @@ -168,7 +178,6 @@ The AccountUserName parameter specifies the account user name. Valid values for Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -178,6 +187,9 @@ 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. @@ -193,7 +205,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -203,6 +214,9 @@ 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. @@ -215,7 +229,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -225,6 +238,9 @@ 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. @@ -237,7 +253,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -247,6 +262,9 @@ 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. @@ -263,7 +281,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -273,6 +290,9 @@ 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. @@ -288,7 +308,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -298,6 +317,9 @@ 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. @@ -313,7 +335,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -323,6 +344,9 @@ 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. @@ -338,7 +362,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -348,6 +371,9 @@ 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. @@ -360,7 +386,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -370,6 +395,9 @@ 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. @@ -385,7 +413,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -395,6 +422,9 @@ 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. @@ -411,7 +441,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -421,6 +450,9 @@ 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. @@ -433,7 +465,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -443,6 +474,9 @@ 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. @@ -455,7 +489,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -465,6 +498,9 @@ 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. @@ -477,7 +513,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -487,6 +522,9 @@ Accept wildcard characters: False ``` ### -AntiVirusSignatureStatus + +> Applicable: Security & Compliance + The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. @@ -498,7 +536,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -508,6 +545,9 @@ Accept wildcard characters: False ``` ### -AntiVirusStatus + +> Applicable: Security & Compliance + The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. @@ -519,7 +559,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -529,6 +568,9 @@ 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 @@ -544,7 +586,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -554,6 +595,9 @@ Accept wildcard characters: False ``` ### -AutoUpdateStatus + +> Applicable: Security & Compliance + The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates @@ -569,7 +613,6 @@ This setting is available only on Windows 8.1 RT devices. Type: AutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -579,6 +622,9 @@ 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. @@ -591,7 +637,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -601,6 +646,9 @@ 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. @@ -617,7 +665,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -627,6 +674,9 @@ 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`. @@ -636,7 +686,6 @@ 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 @@ -646,13 +695,15 @@ 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 @@ -662,6 +713,9 @@ 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. @@ -671,7 +725,6 @@ The EmailAddress parameter specifies the email address. Valid values are: Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -681,6 +734,9 @@ 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. @@ -693,7 +749,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -703,6 +758,9 @@ 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. @@ -712,7 +770,6 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -722,6 +779,9 @@ 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 @@ -733,7 +793,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -743,6 +802,9 @@ 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. @@ -755,7 +817,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -765,6 +826,9 @@ 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. @@ -780,7 +844,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -790,6 +853,9 @@ 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. @@ -806,7 +872,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -816,6 +881,9 @@ 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. @@ -826,7 +894,6 @@ 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 @@ -836,6 +903,9 @@ 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: @@ -926,7 +996,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -936,6 +1005,9 @@ Accept wildcard characters: False ``` ### -PasswordComplexity + +> Applicable: Security & Compliance + The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. @@ -945,7 +1017,6 @@ The PasswordComplexity parameter specifies the password complexity. Valid values Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -955,6 +1026,9 @@ 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. @@ -971,7 +1045,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -981,6 +1054,9 @@ 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. @@ -997,7 +1073,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1007,6 +1082,9 @@ 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. @@ -1016,7 +1094,6 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1026,6 +1103,9 @@ 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. @@ -1042,7 +1122,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1052,6 +1131,9 @@ 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: @@ -1065,7 +1147,6 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1075,6 +1156,9 @@ 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. @@ -1091,7 +1175,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1101,6 +1184,9 @@ 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: @@ -1116,7 +1202,6 @@ 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 @@ -1126,6 +1211,9 @@ 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. @@ -1141,7 +1229,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1151,6 +1238,9 @@ 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: @@ -1172,7 +1262,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1182,6 +1271,9 @@ 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. @@ -1192,7 +1284,6 @@ The RequireEmailProfile parameter specifies whether an email profile is required Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1202,6 +1293,9 @@ 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. @@ -1214,7 +1308,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1224,6 +1317,9 @@ 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. @@ -1236,7 +1332,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1246,6 +1341,9 @@ 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: @@ -1325,7 +1423,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1335,6 +1432,9 @@ 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. @@ -1349,7 +1449,6 @@ This setting is available only on Windows 8.1 RT devices. Type: UserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1359,13 +1458,15 @@ 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 @@ -1375,6 +1476,9 @@ 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. @@ -1387,7 +1491,6 @@ 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 @@ -1397,6 +1500,9 @@ 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`. @@ -1407,7 +1513,6 @@ 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/exchange/New-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md index 13317afc2d..0b69ff9bd1 100644 --- a/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-devicetenantpolicy +schema: 2.0.0 +title: New-DeviceTenantPolicy --- # New-DeviceTenantPolicy @@ -53,13 +54,15 @@ 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 @@ -69,6 +72,9 @@ 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,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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. @@ -115,7 +125,6 @@ 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 @@ -125,13 +134,15 @@ 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/exchange/New-DeviceTenantRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DeviceTenantRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md index 214a1d7524..9020e37111 100644 --- a/exchange/exchange-ps/exchange/New-DeviceTenantRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-devicetenantrule +schema: 2.0.0 +title: New-DeviceTenantRule --- # New-DeviceTenantRule @@ -56,6 +57,9 @@ 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 @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ 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. @@ -85,7 +91,6 @@ The BlockUnsupportedDevices parameter specifies whether to block access to your Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -95,6 +100,9 @@ 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`. @@ -104,7 +112,6 @@ 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 @@ -114,13 +121,15 @@ 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 @@ -130,6 +139,9 @@ 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. @@ -140,7 +152,6 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -150,13 +161,15 @@ 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/exchange/New-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md similarity index 87% rename from exchange/exchange-ps/exchange/New-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md index f6466a1301..0d904e74ab 100644 --- a/exchange/exchange-ps/exchange/New-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-distributiongroup +schema: 2.0.0 +title: New-DistributionGroup --- # New-DistributionGroup @@ -84,6 +85,9 @@ 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. @@ -92,7 +96,6 @@ 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 @@ -102,6 +105,9 @@ 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: @@ -126,7 +132,6 @@ 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 @@ -136,6 +141,9 @@ 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: @@ -155,7 +163,6 @@ 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 @@ -165,6 +172,9 @@ 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: @@ -176,7 +186,6 @@ 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 @@ -186,6 +195,9 @@ 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. @@ -197,7 +209,6 @@ 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 @@ -207,6 +218,9 @@ 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`. @@ -216,7 +230,6 @@ 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 @@ -226,13 +239,15 @@ 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 @@ -242,6 +257,9 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill Description Description }} @@ -250,7 +268,6 @@ 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 @@ -260,6 +277,9 @@ 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. @@ -270,7 +290,6 @@ 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 @@ -280,6 +299,9 @@ 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,7 +310,6 @@ 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 @@ -298,6 +319,9 @@ 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. @@ -310,7 +334,6 @@ 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 @@ -320,6 +343,9 @@ 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. @@ -328,7 +354,6 @@ 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 @@ -338,6 +363,9 @@ 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 @@ -376,7 +404,6 @@ 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 @@ -386,6 +413,9 @@ 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. @@ -395,7 +425,6 @@ 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 @@ -405,6 +434,9 @@ 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. @@ -415,7 +447,6 @@ 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 @@ -425,6 +456,9 @@ 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 @@ -446,7 +480,6 @@ 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 @@ -456,6 +489,9 @@ 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 @@ -475,7 +511,6 @@ 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 @@ -485,6 +520,9 @@ 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. @@ -496,7 +534,6 @@ 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 @@ -506,13 +543,15 @@ 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 @@ -522,6 +561,9 @@ 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: @@ -535,7 +577,6 @@ 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 @@ -545,13 +586,15 @@ 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 @@ -561,6 +604,9 @@ 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. @@ -572,7 +618,6 @@ 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 @@ -582,6 +627,9 @@ 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. @@ -590,7 +638,6 @@ 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 @@ -600,6 +647,9 @@ 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). @@ -608,7 +658,6 @@ 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 @@ -618,6 +667,9 @@ 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. @@ -630,7 +682,6 @@ 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 @@ -640,6 +691,9 @@ 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. @@ -651,7 +705,6 @@ 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 @@ -661,13 +714,15 @@ 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/exchange/New-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/New-DkimSigningConfig.md rename to exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md index 5bd296a8ba..585bbc9db3 100644 --- a/exchange/exchange-ps/exchange/New-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dkimsigningconfig +schema: 2.0.0 +title: New-DkimSigningConfig --- # New-DkimSigningConfig @@ -48,6 +49,9 @@ 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). @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,6 +110,9 @@ 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. @@ -112,7 +122,6 @@ The BodyCanonicalization parameter specifies the canonicalization algorithm that Type: CanonicalizationType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -122,6 +131,9 @@ 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,7 +143,6 @@ 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 @@ -141,6 +152,9 @@ 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. @@ -150,7 +164,6 @@ The HeaderCanonicalization parameter specifies the canonicalization algorithm th Type: CanonicalizationType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -160,6 +173,9 @@ 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) @@ -171,7 +187,6 @@ 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 @@ -181,13 +196,15 @@ 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/exchange/New-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md index 17a536c78d..129010c1e8 100644 --- a/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpcompliancepolicy +schema: 2.0.0 +title: New-DlpCompliancePolicy --- # New-DlpCompliancePolicy @@ -153,13 +154,15 @@ 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 @@ -169,13 +172,15 @@ 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 @@ -185,6 +190,9 @@ 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`. @@ -194,7 +202,6 @@ 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 @@ -204,13 +211,15 @@ 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 @@ -220,13 +229,15 @@ 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 @@ -236,13 +247,15 @@ 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 @@ -252,6 +265,9 @@ 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. @@ -264,7 +280,6 @@ 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 @@ -274,6 +289,9 @@ 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. @@ -286,7 +304,6 @@ 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 @@ -296,6 +313,9 @@ 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 @("")`. @@ -309,7 +329,6 @@ Currently, supported values are: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -319,6 +338,9 @@ 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). @@ -331,7 +353,6 @@ You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMember Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -341,6 +362,9 @@ 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). @@ -355,7 +379,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -365,13 +388,15 @@ 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 @@ -381,13 +406,15 @@ 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 @@ -397,6 +424,9 @@ 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: @@ -413,7 +443,6 @@ You can't specify inclusions and exclusions in the same policy. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -423,6 +452,9 @@ 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: `"","",...""`. @@ -437,7 +469,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -447,6 +478,9 @@ 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: `"","",...""`. @@ -461,7 +495,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -471,6 +504,9 @@ 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. @@ -479,7 +515,6 @@ 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 @@ -489,13 +524,15 @@ 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 @@ -505,6 +542,9 @@ 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`. @@ -532,7 +572,6 @@ 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 @@ -542,6 +581,9 @@ 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. @@ -553,7 +595,6 @@ 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 @@ -563,13 +604,15 @@ 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 @@ -579,13 +622,15 @@ 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 @@ -595,6 +640,9 @@ 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: @@ -617,7 +665,6 @@ 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 @@ -626,13 +673,15 @@ 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 @@ -641,6 +690,9 @@ 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). @@ -653,7 +705,6 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDri Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -663,6 +714,9 @@ 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). @@ -677,7 +731,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -687,6 +740,9 @@ 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: `"","",...""`. @@ -697,7 +753,6 @@ 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 @@ -707,6 +762,9 @@ 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: `"","",...""`. @@ -717,7 +775,6 @@ 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 @@ -727,6 +784,9 @@ 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. @@ -735,7 +795,6 @@ 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 @@ -745,6 +804,9 @@ 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). @@ -753,7 +815,6 @@ 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 @@ -763,6 +824,9 @@ 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: @@ -779,7 +843,6 @@ 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: @@ -803,7 +869,6 @@ 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: @@ -827,7 +895,6 @@ 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 @@ -837,13 +904,15 @@ 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 @@ -853,13 +922,15 @@ 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 @@ -869,6 +940,9 @@ 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. @@ -879,7 +953,6 @@ 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. @@ -899,7 +975,6 @@ 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 @@ -925,13 +1002,15 @@ 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 @@ -941,6 +1020,9 @@ 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: `"","",...""`. @@ -949,7 +1031,6 @@ 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: `"","",...""`. @@ -967,7 +1051,6 @@ 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. @@ -989,7 +1075,6 @@ 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 @@ -999,6 +1084,9 @@ 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. @@ -1011,7 +1099,6 @@ 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 @@ -1021,13 +1108,15 @@ 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 @@ -1037,13 +1126,15 @@ 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/exchange/New-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DlpComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md index 177d38fa19..032c416ce4 100644 --- a/exchange/exchange-ps/exchange/New-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpcompliancerule +schema: 2.0.0 +title: New-DlpComplianceRule --- # New-DlpComplianceRule @@ -326,13 +327,15 @@ 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 @@ -342,6 +345,9 @@ 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 @@ -353,7 +359,6 @@ 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 @@ -363,6 +368,9 @@ 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. @@ -373,7 +381,6 @@ 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 @@ -383,13 +390,15 @@ 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 @@ -399,6 +408,9 @@ 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"}`. @@ -410,7 +422,6 @@ 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 @@ -420,6 +431,9 @@ 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. @@ -430,7 +444,6 @@ For syntax details, see Example 3. Type: String Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -440,13 +453,15 @@ 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 @@ -456,6 +471,9 @@ 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"` @@ -470,7 +488,6 @@ 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 @@ -480,6 +497,9 @@ 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. @@ -490,7 +510,6 @@ 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 @@ -500,6 +519,9 @@ 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. @@ -508,7 +530,6 @@ Use the EnforcePortalAccess parameter to control whether external users are requ Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -518,6 +539,9 @@ 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. @@ -530,7 +554,6 @@ 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 @@ -540,13 +563,15 @@ 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 @@ -556,6 +581,9 @@ 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. @@ -565,7 +593,6 @@ 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 @@ -575,6 +602,9 @@ 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. @@ -585,7 +615,6 @@ 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 @@ -595,13 +624,15 @@ 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 @@ -611,6 +642,9 @@ 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`. @@ -620,7 +654,6 @@ 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 @@ -630,6 +663,9 @@ 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`. @@ -638,7 +674,6 @@ 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 @@ -648,6 +683,9 @@ 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"})})})`. @@ -660,7 +698,6 @@ 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 @@ -670,13 +707,15 @@ 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 @@ -686,13 +725,15 @@ 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 @@ -702,6 +743,9 @@ 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. @@ -713,7 +757,6 @@ 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 @@ -723,6 +766,9 @@ 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. @@ -734,7 +780,6 @@ 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 @@ -744,6 +789,9 @@ 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"`. @@ -752,7 +800,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -762,6 +809,9 @@ 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. @@ -771,7 +821,6 @@ 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 @@ -781,6 +830,9 @@ 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. @@ -791,7 +843,6 @@ 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 @@ -801,6 +852,9 @@ 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. @@ -809,7 +863,6 @@ This parameter applies to Sharepoint and Onedrive workloads. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -819,6 +872,9 @@ 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. @@ -827,7 +883,6 @@ This parameter applies to Sharepoint and Onedrive workloads. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -837,6 +892,9 @@ 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. @@ -846,7 +904,6 @@ The DocumentIsPasswordProtected parameter specifies a condition for the DLP rule Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -856,6 +913,9 @@ 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. @@ -865,7 +925,6 @@ The DocumentIsUnsupported parameter specifies a condition for the DLP rule that Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -875,6 +934,9 @@ 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"`. @@ -885,7 +947,6 @@ 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 @@ -895,6 +956,9 @@ 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. @@ -903,7 +967,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -913,6 +976,9 @@ 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"` @@ -925,7 +991,6 @@ 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 @@ -935,6 +1000,9 @@ 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: @@ -953,7 +1021,6 @@ 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 @@ -962,6 +1029,9 @@ 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. @@ -970,7 +1040,6 @@ 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 @@ -979,6 +1048,9 @@ 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. @@ -987,7 +1059,6 @@ 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 @@ -997,13 +1068,15 @@ 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 @@ -1013,6 +1086,9 @@ 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"=""},...)`. @@ -1041,7 +1117,6 @@ 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 @@ -1051,6 +1126,9 @@ 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. @@ -1060,7 +1138,6 @@ The EnforcePortalAccess parameter specifies whether external recipients are requ Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1070,6 +1147,9 @@ 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). @@ -1088,7 +1168,6 @@ This parameter works with the following conditions or exceptions only: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1098,6 +1177,9 @@ 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. @@ -1108,7 +1190,6 @@ 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 @@ -1118,6 +1199,9 @@ 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"` @@ -1132,7 +1216,6 @@ 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 @@ -1142,6 +1225,9 @@ 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. @@ -1152,7 +1238,6 @@ 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 @@ -1162,6 +1247,9 @@ 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. @@ -1172,7 +1260,6 @@ 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 @@ -1182,6 +1269,9 @@ 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"})})})`. @@ -1192,7 +1282,6 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1202,13 +1291,15 @@ 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 @@ -1218,13 +1309,15 @@ 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 @@ -1234,6 +1327,9 @@ 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. @@ -1245,7 +1341,6 @@ 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 @@ -1255,6 +1350,9 @@ 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"`. @@ -1263,7 +1361,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1273,6 +1370,9 @@ 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. @@ -1283,7 +1383,6 @@ 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 @@ -1293,6 +1392,9 @@ 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. @@ -1301,7 +1403,6 @@ This parameter applies to Sharepoint and Onedrive workloads. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1311,6 +1412,9 @@ 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. @@ -1319,7 +1423,6 @@ This parameter applies to Sharepoint and Onedrive workloads. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1329,6 +1432,9 @@ 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. @@ -1338,7 +1444,6 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1348,6 +1453,9 @@ 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. @@ -1357,7 +1465,6 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the DLP r Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1367,6 +1474,9 @@ 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. @@ -1375,7 +1485,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1385,6 +1494,9 @@ 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"`. @@ -1395,7 +1507,6 @@ 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 @@ -1405,6 +1516,9 @@ 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"` @@ -1417,7 +1531,6 @@ 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 @@ -1427,6 +1540,9 @@ 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: @@ -1445,7 +1561,6 @@ 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 @@ -1455,6 +1570,9 @@ 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. @@ -1463,7 +1581,6 @@ 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 @@ -1473,6 +1590,9 @@ 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"` @@ -1487,7 +1607,6 @@ 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 @@ -1497,6 +1616,9 @@ 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. @@ -1507,7 +1629,6 @@ 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 @@ -1517,6 +1638,9 @@ 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"`. @@ -1525,7 +1649,6 @@ 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 @@ -1535,6 +1658,9 @@ 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. @@ -1546,7 +1672,6 @@ 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 @@ -1556,6 +1681,9 @@ 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. @@ -1567,7 +1695,6 @@ 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 @@ -1577,6 +1704,9 @@ 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. @@ -1587,7 +1717,6 @@ 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 @@ -1597,6 +1726,9 @@ 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. @@ -1605,7 +1737,6 @@ 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 @@ -1615,6 +1746,9 @@ 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: @@ -1633,7 +1767,6 @@ 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 @@ -1643,6 +1776,9 @@ 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. @@ -1660,7 +1796,6 @@ 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 @@ -1670,6 +1805,9 @@ 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. @@ -1679,7 +1817,6 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the DLP Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1689,6 +1826,9 @@ 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 @@ -1729,7 +1869,6 @@ 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 @@ -1739,6 +1878,9 @@ 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 @@ -1779,7 +1921,6 @@ 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 @@ -1789,13 +1930,15 @@ 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 @@ -1805,6 +1948,9 @@ 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 @@ -1845,7 +1991,6 @@ 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 @@ -1855,6 +2000,9 @@ 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 @@ -1895,7 +2043,6 @@ 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 @@ -1905,6 +2052,9 @@ 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. @@ -1913,7 +2063,6 @@ 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 @@ -1923,6 +2072,9 @@ 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. @@ -1935,7 +2087,6 @@ You can specify values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1945,6 +2096,9 @@ 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. @@ -1953,7 +2107,6 @@ 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 @@ -1963,6 +2116,9 @@ 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. @@ -1971,7 +2127,6 @@ 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 @@ -1981,6 +2136,9 @@ 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"` @@ -1995,7 +2153,6 @@ 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 @@ -2005,6 +2162,9 @@ 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. @@ -2015,7 +2175,6 @@ 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 @@ -2025,6 +2184,9 @@ 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. @@ -2035,7 +2197,6 @@ 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 @@ -2045,6 +2206,9 @@ 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. @@ -2053,7 +2217,6 @@ 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 @@ -2063,6 +2226,9 @@ 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. @@ -2071,7 +2237,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2081,6 +2246,9 @@ 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 @@ -2093,7 +2261,6 @@ 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 @@ -2103,13 +2270,15 @@ 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 @@ -2119,6 +2288,9 @@ 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. @@ -2127,7 +2299,6 @@ 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 @@ -2137,6 +2308,9 @@ 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"` @@ -2151,7 +2325,6 @@ 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 @@ -2161,6 +2334,9 @@ 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. @@ -2171,7 +2347,6 @@ 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 @@ -2181,6 +2356,9 @@ 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"`. @@ -2189,7 +2367,6 @@ 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 @@ -2199,6 +2376,9 @@ 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. @@ -2210,7 +2390,6 @@ 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 @@ -2220,6 +2399,9 @@ 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. @@ -2233,7 +2415,6 @@ 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 @@ -2243,6 +2424,9 @@ 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. @@ -2254,7 +2438,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2264,6 +2447,9 @@ 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. @@ -2275,7 +2461,6 @@ 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 @@ -2285,6 +2470,9 @@ 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. @@ -2295,7 +2483,6 @@ 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 @@ -2305,6 +2492,9 @@ 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. @@ -2313,7 +2503,6 @@ 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 @@ -2323,13 +2512,15 @@ 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 @@ -2339,6 +2530,9 @@ 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 @@ -2368,7 +2562,6 @@ 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 @@ -2378,13 +2571,15 @@ 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 @@ -2394,6 +2589,9 @@ 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: @@ -2412,7 +2610,6 @@ 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 @@ -2422,6 +2619,9 @@ 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. @@ -2439,7 +2639,6 @@ 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 @@ -2449,13 +2648,15 @@ 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 @@ -2465,6 +2666,9 @@ 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. @@ -2473,7 +2677,6 @@ 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 @@ -2483,6 +2686,9 @@ 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: @@ -2497,7 +2703,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: PswsHashtable Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2507,6 +2712,9 @@ 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. @@ -2519,7 +2727,6 @@ 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 @@ -2529,6 +2736,9 @@ 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. @@ -2542,7 +2752,6 @@ You can specify multiple values separated by commas. The values WithoutJustifica Type: OverrideOption[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2552,13 +2761,15 @@ 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 @@ -2568,13 +2779,15 @@ 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 @@ -2584,6 +2797,9 @@ 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): @@ -2597,7 +2813,6 @@ 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 @@ -2607,13 +2822,15 @@ 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 @@ -2623,13 +2840,15 @@ 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 @@ -2639,6 +2858,9 @@ 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 }} @@ -2649,7 +2871,6 @@ 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 @@ -2659,13 +2880,15 @@ 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 @@ -2675,13 +2898,15 @@ 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 @@ -2691,13 +2916,15 @@ 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 @@ -2707,6 +2934,9 @@ 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). @@ -2717,7 +2947,6 @@ To enter multiple values, use the following syntax: `"Value1","Value2",..."Value Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2727,6 +2956,9 @@ 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. @@ -2736,7 +2968,6 @@ 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 @@ -2746,13 +2977,15 @@ 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 @@ -2762,6 +2995,9 @@ 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. @@ -2775,7 +3011,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2785,6 +3020,9 @@ 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 @@ -2796,7 +3034,6 @@ 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 @@ -2806,13 +3043,15 @@ 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 @@ -2822,6 +3061,9 @@ 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. @@ -2832,7 +3074,6 @@ 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 @@ -2842,6 +3083,9 @@ 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: @@ -2856,7 +3100,6 @@ 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 @@ -2866,6 +3109,9 @@ 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. @@ -2875,7 +3121,6 @@ The ProcessingLimitExceeded parameter specifies a condition for the DLP rule tha Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2885,6 +3130,9 @@ 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: @@ -2896,7 +3144,6 @@ The Quarantine parameter specifies an action that quarantines messages. Valid va Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2906,6 +3153,9 @@ 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 @@ -2946,7 +3196,6 @@ 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 @@ -2956,6 +3205,9 @@ 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 @@ -2996,7 +3248,6 @@ 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 @@ -3006,6 +3257,9 @@ 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. @@ -3014,7 +3268,6 @@ 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 @@ -3024,13 +3277,15 @@ 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 @@ -3040,6 +3295,9 @@ 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. @@ -3048,7 +3306,6 @@ 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 @@ -3058,6 +3315,9 @@ 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. @@ -3068,7 +3328,6 @@ 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 @@ -3078,6 +3337,9 @@ 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. @@ -3089,7 +3351,6 @@ 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 @@ -3099,6 +3360,9 @@ 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. @@ -3110,7 +3374,6 @@ The ReportSeverityLevel parameter specifies the severity level of the incident r Type: RuleSeverity Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3120,13 +3383,15 @@ 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 @@ -3136,13 +3401,15 @@ 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 @@ -3152,6 +3419,9 @@ 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 @@ -3162,7 +3432,6 @@ 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 @@ -3172,6 +3441,9 @@ 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 @@ -3212,7 +3484,6 @@ 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 @@ -3222,6 +3493,9 @@ 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 @@ -3262,7 +3536,6 @@ 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 @@ -3272,6 +3545,9 @@ 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. @@ -3290,7 +3566,6 @@ 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 @@ -3300,6 +3575,9 @@ 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. @@ -3308,7 +3586,6 @@ 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 @@ -3318,6 +3595,9 @@ 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. @@ -3330,7 +3610,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3340,6 +3619,9 @@ 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. @@ -3348,7 +3630,6 @@ 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 @@ -3358,6 +3639,9 @@ 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. @@ -3366,7 +3650,6 @@ 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 @@ -3376,6 +3659,9 @@ 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. @@ -3386,7 +3672,6 @@ 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 @@ -3396,6 +3681,9 @@ 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) @@ -3408,7 +3696,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3418,6 +3705,9 @@ 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. @@ -3427,7 +3717,6 @@ The StopPolicyProcessing parameter specifies an action that stops processing mor Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3437,6 +3726,9 @@ 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"` @@ -3451,7 +3743,6 @@ 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 @@ -3461,6 +3752,9 @@ 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. @@ -3471,7 +3765,6 @@ 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 @@ -3481,6 +3774,9 @@ 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. @@ -3491,7 +3787,6 @@ 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 @@ -3501,6 +3796,9 @@ 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. @@ -3509,7 +3807,6 @@ 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 @@ -3519,13 +3816,15 @@ 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 @@ -3535,13 +3834,15 @@ 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 @@ -3551,6 +3852,9 @@ 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. @@ -3559,7 +3863,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3569,13 +3872,15 @@ 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 @@ -3585,13 +3890,15 @@ 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 @@ -3601,6 +3908,9 @@ 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 @@ -3613,7 +3923,6 @@ 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/exchange/New-DlpEdmSchema.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md similarity index 96% rename from exchange/exchange-ps/exchange/New-DlpEdmSchema.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md index 27c440830a..588b9cb532 100644 --- a/exchange/exchange-ps/exchange/New-DlpEdmSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpedmschema +schema: 2.0.0 +title: New-DlpEdmSchema --- # New-DlpEdmSchema @@ -44,6 +45,9 @@ 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`). @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/New-DlpFingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DlpFingerprint.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md index cbd457cd29..dc4ff3f983 100644 --- a/exchange/exchange-ps/exchange/New-DlpFingerprint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpfingerprint +schema: 2.0.0 +title: New-DlpFingerprint --- # New-DlpFingerprint @@ -48,6 +49,9 @@ 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`). @@ -56,7 +60,6 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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,13 +108,15 @@ 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 @@ -117,13 +126,15 @@ 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 @@ -133,13 +144,15 @@ 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/exchange/New-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md index 10ac021e60..1c7d4ccbbb 100644 --- a/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpkeyworddictionary +schema: 2.0.0 +title: New-DlpKeywordDictionary --- # New-DlpKeywordDictionary @@ -63,13 +64,15 @@ 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 @@ -79,6 +82,9 @@ 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`. @@ -88,7 +94,6 @@ 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 @@ -98,13 +103,15 @@ 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 @@ -114,13 +121,15 @@ 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 @@ -130,13 +139,15 @@ 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 @@ -146,13 +157,15 @@ 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 @@ -162,13 +175,15 @@ 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/exchange/New-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/New-DlpPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md index 705a5e5e46..febdffde4b 100644 --- a/exchange/exchange-ps/exchange/New-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlppolicy +schema: 2.0.0 +title: New-DlpPolicy --- # New-DlpPolicy @@ -54,13 +55,15 @@ 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 @@ -70,6 +73,9 @@ 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`. @@ -79,7 +85,6 @@ 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,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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 @@ -121,6 +130,9 @@ 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. @@ -133,7 +145,6 @@ 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 @@ -143,6 +154,9 @@ 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"...}`. @@ -151,7 +165,6 @@ 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 @@ -161,13 +174,15 @@ 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 @@ -177,13 +192,15 @@ 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 @@ -193,6 +210,9 @@ 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`). @@ -201,7 +221,6 @@ 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 @@ -211,13 +230,15 @@ 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/exchange/New-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md similarity index 94% rename from exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md index 961c0d2e48..a8739f1827 100644 --- a/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtype +schema: 2.0.0 +title: New-DlpSensitiveInformationType --- # New-DlpSensitiveInformationType @@ -58,6 +59,9 @@ 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. @@ -66,7 +70,6 @@ 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 @@ -76,13 +79,15 @@ 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/exchange/new-fingerprint) or the Examples section. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -92,13 +97,15 @@ 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 @@ -108,13 +115,15 @@ 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 @@ -124,6 +133,9 @@ 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`. @@ -133,7 +145,6 @@ 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,13 +154,15 @@ 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 @@ -159,6 +172,9 @@ 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). @@ -169,7 +185,6 @@ 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 @@ -179,13 +194,15 @@ 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 @@ -195,13 +212,15 @@ 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/exchange/New-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md similarity index 95% rename from exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md rename to exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md index ff65bcc045..17de006289 100644 --- a/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtyperulepackage +schema: 2.0.0 +title: New-DlpSensitiveInformationTypeRulePackage --- # New-DlpSensitiveInformationTypeRulePackage @@ -45,6 +46,9 @@ 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`). @@ -53,7 +57,6 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/New-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md index 548bcc5965..1e5de58395 100644 --- a/exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-dynamicdistributiongroup +schema: 2.0.0 +title: New-DynamicDistributionGroup --- # New-DynamicDistributionGroup @@ -106,6 +107,9 @@ 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. @@ -114,7 +118,6 @@ 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 @@ -124,6 +127,9 @@ 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. @@ -141,7 +147,6 @@ 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 @@ -151,6 +156,9 @@ 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. @@ -170,7 +178,6 @@ 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 @@ -180,6 +187,9 @@ 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: @@ -204,7 +214,6 @@ 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 @@ -214,6 +223,9 @@ 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: @@ -233,7 +245,6 @@ 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 @@ -243,6 +254,9 @@ 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. @@ -253,7 +267,6 @@ 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 @@ -263,6 +276,9 @@ 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. @@ -273,7 +289,6 @@ 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 @@ -283,6 +298,9 @@ 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. @@ -293,7 +311,6 @@ 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 @@ -303,6 +320,9 @@ 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. @@ -313,7 +333,6 @@ 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 @@ -323,6 +342,9 @@ 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. @@ -333,7 +355,6 @@ 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 @@ -343,6 +364,9 @@ 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. @@ -353,7 +377,6 @@ 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 @@ -363,6 +386,9 @@ 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. @@ -373,7 +399,6 @@ 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 @@ -383,6 +408,9 @@ 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. @@ -393,7 +421,6 @@ 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 @@ -403,6 +430,9 @@ 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. @@ -413,7 +443,6 @@ 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 @@ -423,6 +452,9 @@ 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. @@ -433,7 +465,6 @@ 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 @@ -443,6 +474,9 @@ 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. @@ -453,7 +487,6 @@ 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 @@ -463,6 +496,9 @@ 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. @@ -473,7 +509,6 @@ 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 @@ -483,6 +518,9 @@ 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. @@ -493,7 +531,6 @@ 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 @@ -503,6 +540,9 @@ 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. @@ -513,7 +553,6 @@ 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 @@ -523,6 +562,9 @@ 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. @@ -533,7 +575,6 @@ 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 @@ -543,6 +584,9 @@ 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. @@ -553,7 +597,6 @@ 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 @@ -563,6 +606,9 @@ 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. @@ -573,7 +619,6 @@ 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 @@ -583,6 +628,9 @@ 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. @@ -593,7 +641,6 @@ 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 @@ -603,6 +650,9 @@ 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`. @@ -612,7 +662,6 @@ 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 @@ -622,6 +671,9 @@ 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. @@ -630,7 +682,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -640,6 +691,9 @@ 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. @@ -648,7 +702,6 @@ 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 @@ -658,6 +711,9 @@ 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. @@ -666,7 +722,6 @@ 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 @@ -676,6 +731,9 @@ 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 @@ -693,7 +751,6 @@ 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 @@ -703,6 +760,9 @@ 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. @@ -714,7 +774,6 @@ 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 @@ -724,6 +783,9 @@ 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: @@ -743,7 +805,6 @@ 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 @@ -753,13 +814,15 @@ 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 @@ -769,6 +832,9 @@ 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 @@ -786,7 +852,6 @@ 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 @@ -796,6 +861,9 @@ 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. @@ -808,7 +876,6 @@ 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 @@ -818,13 +885,15 @@ 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/exchange/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md similarity index 93% rename from exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md index f070348810..57b6e59c3a 100644 --- a/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-eopprotectionpolicyrule +schema: 2.0.0 +title: New-EOPProtectionPolicyRule --- # New-EOPProtectionPolicyRule @@ -57,6 +58,9 @@ 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. @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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: @@ -88,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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: @@ -111,7 +119,6 @@ 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 @@ -121,6 +128,9 @@ 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: @@ -134,7 +144,6 @@ 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 @@ -144,13 +153,15 @@ 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 @@ -160,6 +171,9 @@ 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. @@ -169,7 +183,6 @@ 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 @@ -179,6 +192,9 @@ 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. @@ -193,7 +209,6 @@ 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 @@ -203,13 +218,15 @@ 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 @@ -219,6 +236,9 @@ 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 @@ -234,7 +254,6 @@ 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 @@ -244,6 +263,9 @@ 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 @@ -261,7 +283,6 @@ 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 @@ -271,6 +292,9 @@ 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. @@ -281,7 +305,6 @@ 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 @@ -291,13 +314,15 @@ 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 @@ -307,6 +332,9 @@ 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 @@ -322,7 +350,6 @@ 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 @@ -332,6 +359,9 @@ 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 @@ -349,7 +379,6 @@ 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 @@ -359,13 +388,15 @@ 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/exchange/New-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md index d888a64122..b1ad1dc9b4 100644 --- a/exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-ecpvirtualdirectory +schema: 2.0.0 +title: New-EcpVirtualDirectory --- # New-EcpVirtualDirectory @@ -54,13 +55,15 @@ 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 @@ -70,6 +73,9 @@ 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,7 +85,6 @@ 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,13 +94,15 @@ 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 @@ -105,6 +112,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,6 +136,9 @@ 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. @@ -136,7 +148,6 @@ 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 @@ -146,6 +157,9 @@ 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. @@ -158,7 +172,6 @@ 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 @@ -168,6 +181,9 @@ 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. @@ -176,7 +192,6 @@ 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 @@ -186,6 +201,9 @@ 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. @@ -194,7 +212,6 @@ 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 @@ -204,13 +221,15 @@ 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 @@ -220,6 +239,9 @@ 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. @@ -231,7 +253,6 @@ 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 @@ -241,6 +262,9 @@ 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 @@ -254,7 +278,6 @@ 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 @@ -264,13 +287,15 @@ 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 @@ -280,13 +305,15 @@ 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/exchange/New-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md similarity index 90% rename from exchange/exchange-ps/exchange/New-EdgeSubscription.md rename to exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md index e7c67b1d70..dd7140a787 100644 --- a/exchange/exchange-ps/exchange/New-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-edgesubscription +schema: 2.0.0 +title: New-EdgeSubscription --- # New-EdgeSubscription @@ -69,6 +70,9 @@ 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. @@ -79,7 +83,6 @@ 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 @@ -89,6 +92,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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 @@ -124,13 +131,15 @@ 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 @@ -140,6 +149,9 @@ 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. @@ -148,7 +160,6 @@ 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 @@ -158,6 +169,9 @@ 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`). @@ -168,7 +182,6 @@ 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 @@ -178,6 +191,9 @@ 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. @@ -186,7 +202,6 @@ 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 @@ -196,6 +211,9 @@ 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: @@ -207,7 +225,6 @@ 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 @@ -217,13 +234,15 @@ 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 @@ -233,13 +252,15 @@ 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/exchange/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md similarity index 87% rename from exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md index f961f43a6f..fa2b56848e 100644 --- a/exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-edgesyncserviceconfig +schema: 2.0.0 +title: New-EdgeSyncServiceConfig --- # New-EdgeSyncServiceConfig @@ -61,6 +62,9 @@ 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. @@ -69,7 +73,6 @@ 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 @@ -79,6 +82,9 @@ 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,7 +94,6 @@ 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,6 +103,9 @@ 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. @@ -106,7 +114,6 @@ 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 @@ -116,13 +123,15 @@ 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,6 +141,9 @@ 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. @@ -140,7 +152,6 @@ 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 @@ -150,6 +161,9 @@ 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. @@ -158,7 +172,6 @@ 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 @@ -168,6 +181,9 @@ 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. @@ -176,7 +192,6 @@ 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 @@ -186,13 +201,15 @@ 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 @@ -202,6 +219,9 @@ 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) @@ -213,7 +233,6 @@ 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 @@ -223,6 +242,9 @@ 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. @@ -231,7 +253,6 @@ 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 @@ -241,6 +262,9 @@ 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: @@ -259,7 +283,6 @@ 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 @@ -269,6 +292,9 @@ 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: @@ -287,7 +313,6 @@ 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 @@ -297,13 +322,15 @@ 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 @@ -313,6 +340,9 @@ 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. @@ -321,7 +351,6 @@ 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 @@ -331,6 +360,9 @@ 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. @@ -339,7 +371,6 @@ 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 @@ -349,13 +380,15 @@ 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 @@ -365,13 +398,15 @@ 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/exchange/New-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/New-EmailAddressPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md index 966babe33d..b910d6e5df 100644 --- a/exchange/exchange-ps/exchange/New-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-emailaddresspolicy +schema: 2.0.0 +title: New-EmailAddressPolicy --- # New-EmailAddressPolicy @@ -173,13 +174,15 @@ 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 @@ -189,6 +192,9 @@ 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`: @@ -208,7 +214,6 @@ 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 @@ -218,6 +223,9 @@ 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`. @@ -230,7 +238,6 @@ 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 @@ -240,6 +247,9 @@ 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: @@ -259,7 +269,6 @@ 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 @@ -269,6 +278,9 @@ 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. @@ -279,7 +291,6 @@ 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 @@ -289,6 +300,9 @@ 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'"`. @@ -308,7 +322,6 @@ 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 @@ -318,6 +331,9 @@ 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. @@ -330,7 +346,6 @@ 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 @@ -340,6 +355,9 @@ 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. @@ -352,7 +370,6 @@ 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 @@ -362,6 +379,9 @@ 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. @@ -374,7 +394,6 @@ 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 @@ -384,6 +403,9 @@ 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. @@ -396,7 +418,6 @@ 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 @@ -406,6 +427,9 @@ 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. @@ -418,7 +442,6 @@ 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 @@ -428,6 +451,9 @@ 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. @@ -440,7 +466,6 @@ 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 @@ -450,6 +475,9 @@ 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. @@ -462,7 +490,6 @@ 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 @@ -472,6 +499,9 @@ 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. @@ -484,7 +514,6 @@ 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 @@ -494,6 +523,9 @@ 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. @@ -506,7 +538,6 @@ 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 @@ -516,6 +547,9 @@ 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. @@ -528,7 +562,6 @@ 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 @@ -538,6 +571,9 @@ 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. @@ -550,7 +586,6 @@ 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 @@ -560,6 +595,9 @@ 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. @@ -572,7 +610,6 @@ 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 @@ -582,6 +619,9 @@ 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. @@ -594,7 +634,6 @@ 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 @@ -604,6 +643,9 @@ 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. @@ -616,7 +658,6 @@ 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 @@ -626,6 +667,9 @@ 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. @@ -638,7 +682,6 @@ 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 @@ -648,6 +691,9 @@ 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. @@ -660,7 +706,6 @@ 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 @@ -670,6 +715,9 @@ 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. @@ -682,7 +730,6 @@ 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 @@ -692,6 +739,9 @@ 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. @@ -704,7 +754,6 @@ 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 @@ -714,6 +763,9 @@ 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`. @@ -723,7 +775,6 @@ 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 @@ -733,6 +784,9 @@ 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. @@ -748,7 +802,6 @@ 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 @@ -758,6 +811,9 @@ 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. @@ -766,7 +822,6 @@ 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 @@ -776,6 +831,9 @@ 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. @@ -798,7 +856,6 @@ 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 @@ -808,6 +865,9 @@ 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. @@ -818,7 +878,6 @@ 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 @@ -828,6 +887,9 @@ 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: @@ -843,7 +905,6 @@ 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 @@ -853,13 +914,15 @@ 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/exchange/New-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md similarity index 92% rename from exchange/exchange-ps/exchange/New-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md index 5d957d9ce7..1ba82fc644 100644 --- a/exchange/exchange-ps/exchange/New-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-exchangecertificate +schema: 2.0.0 +title: New-ExchangeCertificate --- # New-ExchangeCertificate @@ -180,6 +181,9 @@ 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. @@ -192,7 +196,6 @@ 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 @@ -202,6 +205,9 @@ 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`. @@ -211,7 +217,6 @@ 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 @@ -221,6 +226,9 @@ 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. @@ -229,7 +237,6 @@ 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 @@ -239,6 +246,9 @@ 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. @@ -254,7 +264,6 @@ 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 @@ -264,6 +273,9 @@ 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. @@ -272,7 +284,6 @@ 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 @@ -282,6 +293,9 @@ 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. @@ -290,7 +304,6 @@ 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 @@ -300,6 +313,9 @@ 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. @@ -312,7 +328,6 @@ 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 @@ -322,6 +337,9 @@ 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: @@ -333,7 +351,6 @@ 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 @@ -343,6 +360,9 @@ 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: @@ -359,7 +379,6 @@ 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 @@ -369,6 +388,9 @@ 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. @@ -377,7 +399,6 @@ 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 @@ -387,6 +408,9 @@ 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. @@ -395,7 +419,6 @@ 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 @@ -405,13 +428,15 @@ 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 @@ -421,6 +446,9 @@ 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 @@ -431,7 +459,6 @@ 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 @@ -441,6 +468,9 @@ 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. @@ -450,7 +480,6 @@ 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 @@ -460,6 +489,9 @@ 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. @@ -474,7 +506,6 @@ 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 @@ -484,6 +515,9 @@ 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 @@ -497,7 +531,6 @@ 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 @@ -507,6 +540,9 @@ 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. @@ -528,7 +564,6 @@ 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 @@ -538,13 +573,15 @@ 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 @@ -554,6 +591,9 @@ 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. @@ -576,7 +616,6 @@ 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 @@ -586,13 +625,15 @@ 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/exchange/New-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md similarity index 93% rename from exchange/exchange-ps/exchange/New-ExchangeSettings.md rename to exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md index abedc962ae..75369bce95 100644 --- a/exchange/exchange-ps/exchange/New-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-exchangesettings +schema: 2.0.0 +title: New-ExchangeSettings --- # New-ExchangeSettings @@ -44,6 +45,9 @@ 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ 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`. @@ -79,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,6 +112,9 @@ 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. @@ -113,7 +123,6 @@ 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 @@ -123,13 +132,15 @@ 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/exchange/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md similarity index 95% rename from exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md index c126bc6fbf..fdc713381a 100644 --- a/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-exophishsimoverriderule +schema: 2.0.0 +title: New-ExoPhishSimOverrideRule --- # New-ExoPhishSimOverrideRule @@ -47,6 +48,9 @@ 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 @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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`. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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 @@ -143,6 +154,9 @@ 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). @@ -156,7 +170,6 @@ 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 @@ -166,13 +179,15 @@ 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 @@ -182,13 +197,15 @@ 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/exchange/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md index e962547317..f36cb53083 100644 --- a/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-exosecopsoverriderule +schema: 2.0.0 +title: New-ExoSecOpsOverrideRule --- # New-ExoSecOpsOverrideRule @@ -46,6 +47,9 @@ 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 @@ -57,7 +61,6 @@ 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 @@ -67,13 +70,15 @@ 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 @@ -83,13 +88,15 @@ 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 @@ -99,13 +106,15 @@ 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,13 +124,15 @@ 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 @@ -131,13 +142,15 @@ 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/exchange/New-FeatureConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md similarity index 96% rename from exchange/exchange-ps/exchange/New-FeatureConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md index 2f093ab5f4..dd28bb74a7 100644 --- a/exchange/exchange-ps/exchange/New-FeatureConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md @@ -1,9 +1,11 @@ --- +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/exchange/new-featureconfiguration -applicable: Security & Compliance -title: New-FeatureConfiguration schema: 2.0.0 +title: New-FeatureConfiguration --- # New-FeatureConfiguration @@ -71,13 +73,15 @@ 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 @@ -87,6 +91,9 @@ 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 @@ -95,7 +102,6 @@ The FeatureScenario parameter specifies the scenario for the feature configurati Type: PolicyScenario Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -105,6 +111,9 @@ Accept wildcard characters: False ``` ### -Mode + +> Applicable: Security & Compliance + The Mode parameter specifies feature configuration mode. Valid values are: - Enable: The feature configuration is enabled. @@ -114,7 +123,6 @@ The Mode parameter specifies feature configuration mode. Valid values are: Type: PolicyMode Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -124,13 +132,15 @@ 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 @@ -140,13 +150,15 @@ 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 @@ -156,6 +168,9 @@ 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`. @@ -165,7 +180,6 @@ 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 @@ -175,13 +189,15 @@ 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 @@ -191,13 +207,15 @@ 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/exchange/New-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md similarity index 88% rename from exchange/exchange-ps/exchange/New-FederationTrust.md rename to exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md index b1f50c5c62..bd748141a4 100644 --- a/exchange/exchange-ps/exchange/New-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-federationtrust +schema: 2.0.0 +title: New-FederationTrust --- # New-FederationTrust @@ -64,13 +65,15 @@ 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 @@ -80,6 +83,9 @@ 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. @@ -88,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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. @@ -106,7 +114,6 @@ 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 @@ -116,13 +123,15 @@ 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 @@ -132,6 +141,9 @@ 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. @@ -140,7 +152,6 @@ 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 @@ -150,6 +161,9 @@ 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. @@ -158,7 +172,6 @@ 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 @@ -168,6 +181,9 @@ 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`. @@ -177,7 +193,6 @@ 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 @@ -187,13 +202,15 @@ 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,13 +220,15 @@ 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 @@ -219,6 +238,9 @@ 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. @@ -229,7 +251,6 @@ 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 @@ -239,6 +260,9 @@ 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. @@ -247,7 +271,6 @@ 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 @@ -257,13 +280,15 @@ 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/exchange/New-FilePlanPropertyAuthority.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md similarity index 95% rename from exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md index 4d11d7b876..5a5d1b666a 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertyauthority -applicable: Security & Compliance -title: New-FilePlanPropertyAuthority schema: 2.0.0 +title: New-FilePlanPropertyAuthority --- # New-FilePlanPropertyAuthority @@ -39,13 +41,15 @@ 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 @@ -55,6 +59,9 @@ 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. @@ -64,7 +71,6 @@ 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 @@ -74,13 +80,15 @@ 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/exchange/New-FilePlanPropertyCategory.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md similarity index 95% rename from exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md index acdefd1244..27a5bab6f6 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertycategor -applicable: Security & Compliance -title: New-FilePlanPropertyCategory schema: 2.0.0 +title: New-FilePlanPropertyCategory --- # New-FilePlanPropertyCategory @@ -39,13 +41,15 @@ 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 @@ -55,6 +59,9 @@ 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. @@ -64,7 +71,6 @@ 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 @@ -74,13 +80,15 @@ 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/exchange/New-FilePlanPropertyCitation.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md similarity index 94% rename from exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md index 80625e0af9..74214d43c8 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertycitation -applicable: Security & Compliance -title: New-FilePlanPropertyCitation schema: 2.0.0 +title: New-FilePlanPropertyCitation --- # New-FilePlanPropertyCitation @@ -39,13 +41,15 @@ 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 @@ -55,13 +59,15 @@ 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 @@ -71,13 +77,15 @@ 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 @@ -87,6 +95,9 @@ 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. @@ -96,7 +107,6 @@ 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 @@ -106,13 +116,15 @@ 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/exchange/New-FilePlanPropertyDepartment.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md similarity index 95% rename from exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md index 8d084f8c09..2d7be93543 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertydepartment -applicable: Security & Compliance -title: New-FilePlanPropertyDepartment schema: 2.0.0 +title: New-FilePlanPropertyDepartment --- # New-FilePlanPropertyDepartment @@ -39,13 +41,15 @@ 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 @@ -55,6 +59,9 @@ 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. @@ -64,7 +71,6 @@ 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 @@ -74,13 +80,15 @@ 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/exchange/New-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md similarity index 95% rename from exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md index f32d9f3ac4..08d05f5cb4 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertyreferenceid -applicable: Security & Compliance -title: New-FilePlanPropertyReferenceId schema: 2.0.0 +title: New-FilePlanPropertyReferenceId --- # New-FilePlanPropertyReferenceId @@ -39,13 +41,15 @@ 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 @@ -55,6 +59,9 @@ 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. @@ -64,7 +71,6 @@ 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 @@ -74,13 +80,15 @@ 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/exchange/New-FilePlanPropertySubCategory.md b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md similarity index 94% rename from exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md rename to exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md index ceff1b7f3e..402f06868a 100644 --- a/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/new-fileplanpropertysubcategory -applicable: Security & Compliance -title: New-FilePlanPropertySubCategory schema: 2.0.0 +title: New-FilePlanPropertySubCategory --- # New-FilePlanPropertySubCategory @@ -39,13 +41,15 @@ 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 @@ -55,6 +59,9 @@ 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 @@ -65,7 +72,6 @@ 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 @@ -75,6 +81,9 @@ 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,7 +93,6 @@ 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 @@ -94,13 +102,15 @@ 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/exchange/New-Fingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md similarity index 92% rename from exchange/exchange-ps/exchange/New-Fingerprint.md rename to exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md index b2d1f80558..b37ac13ceb 100644 --- a/exchange/exchange-ps/exchange/New-Fingerprint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-fingerprint +schema: 2.0.0 +title: New-Fingerprint --- # New-Fingerprint @@ -48,6 +49,9 @@ 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`). @@ -56,7 +60,6 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,13 +108,15 @@ 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/exchange/New-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md similarity index 91% rename from exchange/exchange-ps/exchange/New-ForeignConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md index 354a0c1d76..4ec681d2de 100644 --- a/exchange/exchange-ps/exchange/New-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-foreignconnector +schema: 2.0.0 +title: New-ForeignConnector --- # New-ForeignConnector @@ -53,13 +54,15 @@ 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 @@ -69,6 +72,9 @@ 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. @@ -88,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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,7 +115,6 @@ 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 @@ -117,6 +124,9 @@ 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. @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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 @@ -151,6 +162,9 @@ 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"`. @@ -159,7 +173,6 @@ 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 @@ -169,13 +182,15 @@ 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/exchange/New-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md similarity index 89% rename from exchange/exchange-ps/exchange/New-GlobalAddressList.md rename to exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md index 990ae4ba24..c9c3c19871 100644 --- a/exchange/exchange-ps/exchange/New-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-globaladdresslist +schema: 2.0.0 +title: New-GlobalAddressList --- # New-GlobalAddressList @@ -90,13 +91,15 @@ 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 @@ -106,6 +109,9 @@ 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. @@ -123,7 +129,6 @@ 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 @@ -133,6 +138,9 @@ 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. @@ -150,7 +158,6 @@ 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 @@ -160,6 +167,9 @@ 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. @@ -170,7 +180,6 @@ 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 @@ -180,6 +189,9 @@ 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. @@ -190,7 +202,6 @@ 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,6 +211,9 @@ 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. @@ -210,7 +224,6 @@ 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 @@ -220,6 +233,9 @@ 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. @@ -230,7 +246,6 @@ 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 @@ -240,6 +255,9 @@ 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. @@ -250,7 +268,6 @@ 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 @@ -260,6 +277,9 @@ 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. @@ -270,7 +290,6 @@ 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 @@ -280,6 +299,9 @@ 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. @@ -290,7 +312,6 @@ 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 @@ -300,6 +321,9 @@ 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. @@ -310,7 +334,6 @@ 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 @@ -320,6 +343,9 @@ 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. @@ -330,7 +356,6 @@ 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 @@ -340,6 +365,9 @@ 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. @@ -350,7 +378,6 @@ 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 @@ -360,6 +387,9 @@ 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. @@ -370,7 +400,6 @@ 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 @@ -380,6 +409,9 @@ 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. @@ -390,7 +422,6 @@ 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 @@ -400,6 +431,9 @@ 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. @@ -410,7 +444,6 @@ 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,6 +453,9 @@ 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. @@ -430,7 +466,6 @@ 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 @@ -440,6 +475,9 @@ 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. @@ -450,7 +488,6 @@ 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 @@ -460,6 +497,9 @@ 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. @@ -470,7 +510,6 @@ 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 @@ -480,6 +519,9 @@ 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. @@ -490,7 +532,6 @@ 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 @@ -500,6 +541,9 @@ 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. @@ -510,7 +554,6 @@ 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 @@ -520,6 +563,9 @@ 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`. @@ -529,7 +575,6 @@ 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 @@ -539,6 +584,9 @@ 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. @@ -547,7 +595,6 @@ 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 @@ -557,6 +604,9 @@ 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: @@ -572,7 +622,6 @@ 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 @@ -582,13 +631,15 @@ 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/exchange/New-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md index 68a8cdeb6a..c8261bb0d4 100644 --- a/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-holdcompliancepolicy +schema: 2.0.0 +title: New-HoldCompliancePolicy --- # New-HoldCompliancePolicy @@ -52,13 +53,15 @@ 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 @@ -68,13 +71,15 @@ 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 @@ -84,6 +89,9 @@ 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,7 +101,6 @@ 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,6 +110,9 @@ 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. @@ -112,7 +122,6 @@ 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 @@ -122,6 +131,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocation + +> Applicable: Security & Compliance + The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - A mailbox @@ -142,7 +154,6 @@ 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 @@ -152,6 +163,9 @@ 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. @@ -160,7 +174,6 @@ 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 @@ -170,13 +183,15 @@ 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 @@ -186,6 +201,9 @@ 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"`. @@ -196,7 +214,6 @@ 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 @@ -206,13 +223,15 @@ 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/exchange/New-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-HoldComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md index 9ebebdb7c5..cdc3e128ab 100644 --- a/exchange/exchange-ps/exchange/New-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-holdcompliancerule +schema: 2.0.0 +title: New-HoldComplianceRule --- # New-HoldComplianceRule @@ -53,13 +54,15 @@ 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 @@ -69,13 +72,15 @@ 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 @@ -85,13 +90,15 @@ 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 @@ -101,6 +108,9 @@ 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`. @@ -110,7 +120,6 @@ 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 @@ -120,6 +129,9 @@ 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". @@ -128,7 +140,6 @@ 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 @@ -138,6 +149,9 @@ 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". @@ -146,7 +160,6 @@ 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 @@ -156,6 +169,9 @@ 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). @@ -164,7 +180,6 @@ 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 @@ -174,13 +189,15 @@ 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 @@ -190,6 +207,9 @@ 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. @@ -199,7 +219,6 @@ The HoldContent parameter specifies the hold duration for the preservation rule. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -209,6 +228,9 @@ 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 @@ -221,7 +243,6 @@ 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 @@ -231,13 +252,15 @@ 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/exchange/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md index c11691fd96..08fddf8050 100644 --- a/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedcontentfilterpolicy +schema: 2.0.0 +title: New-HostedContentFilterPolicy --- # New-HostedContentFilterPolicy @@ -102,6 +103,9 @@ 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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. @@ -110,7 +114,6 @@ 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 @@ -120,6 +123,9 @@ 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 @@ -139,7 +145,6 @@ 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 @@ -149,13 +154,15 @@ 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 @@ -165,6 +172,9 @@ 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). @@ -177,7 +187,6 @@ 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 @@ -187,6 +196,9 @@ 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). @@ -199,7 +211,6 @@ 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 @@ -209,6 +220,9 @@ 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). @@ -221,7 +235,6 @@ 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 @@ -231,6 +244,9 @@ 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). @@ -243,7 +259,6 @@ 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 @@ -253,6 +268,9 @@ 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 @@ -269,7 +287,6 @@ 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 @@ -279,6 +296,9 @@ 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. @@ -293,7 +313,6 @@ 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 @@ -303,6 +322,9 @@ 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). @@ -311,7 +333,6 @@ 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 @@ -321,6 +342,9 @@ 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`. @@ -330,7 +354,6 @@ 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 @@ -340,13 +363,15 @@ 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 @@ -356,13 +381,15 @@ 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 @@ -372,6 +399,9 @@ 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. @@ -381,7 +411,6 @@ 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 @@ -391,6 +420,9 @@ 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. @@ -400,7 +432,6 @@ 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 @@ -410,13 +441,15 @@ 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 @@ -426,13 +459,15 @@ 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 @@ -442,13 +477,15 @@ 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 @@ -458,13 +495,15 @@ 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 @@ -474,13 +513,15 @@ 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 @@ -490,13 +531,15 @@ 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 @@ -506,6 +549,9 @@ 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. @@ -515,7 +561,6 @@ 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 @@ -525,6 +570,9 @@ 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 @@ -541,7 +589,6 @@ 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 @@ -551,6 +598,9 @@ 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). @@ -564,7 +614,6 @@ 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 @@ -574,6 +623,9 @@ 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 @@ -590,7 +642,6 @@ 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 @@ -600,6 +651,9 @@ 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. @@ -610,7 +664,6 @@ 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 @@ -620,6 +673,9 @@ 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. @@ -630,7 +686,6 @@ 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 @@ -640,6 +695,9 @@ 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. @@ -650,7 +708,6 @@ 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 @@ -660,6 +717,9 @@ 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. @@ -670,7 +730,6 @@ 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 @@ -680,6 +739,9 @@ 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. @@ -689,7 +751,6 @@ 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 @@ -699,6 +760,9 @@ 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. @@ -712,7 +776,6 @@ 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 @@ -722,6 +785,9 @@ 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. @@ -734,7 +800,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -744,6 +809,9 @@ 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. @@ -754,7 +822,6 @@ 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 @@ -764,6 +831,9 @@ 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. @@ -774,7 +844,6 @@ 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 @@ -784,6 +853,9 @@ 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. @@ -794,7 +866,6 @@ 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 @@ -804,6 +875,9 @@ 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. @@ -814,7 +888,6 @@ 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 @@ -824,6 +897,9 @@ 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. @@ -834,7 +910,6 @@ 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 @@ -844,6 +919,9 @@ 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. @@ -853,7 +931,6 @@ 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 @@ -863,6 +940,9 @@ 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. @@ -873,7 +953,6 @@ 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 @@ -883,6 +962,9 @@ 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. @@ -892,7 +974,6 @@ 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 @@ -902,6 +983,9 @@ 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. @@ -912,7 +996,6 @@ 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 @@ -922,6 +1005,9 @@ 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. @@ -932,7 +1018,6 @@ 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 @@ -942,6 +1027,9 @@ 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. @@ -951,7 +1039,6 @@ 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 @@ -961,6 +1048,9 @@ 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. @@ -971,7 +1061,6 @@ 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 @@ -981,6 +1070,9 @@ 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 @@ -994,7 +1086,6 @@ 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 @@ -1004,6 +1095,9 @@ 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 @@ -1020,7 +1114,6 @@ 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 @@ -1030,6 +1123,9 @@ 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. @@ -1044,7 +1140,6 @@ 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 @@ -1054,6 +1149,9 @@ 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. @@ -1065,7 +1163,6 @@ 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 @@ -1075,6 +1172,9 @@ 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 @@ -1091,7 +1191,6 @@ 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 @@ -1101,13 +1200,15 @@ 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 @@ -1117,6 +1218,9 @@ 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 @@ -1130,7 +1234,6 @@ 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 @@ -1140,6 +1243,9 @@ 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. @@ -1156,7 +1262,6 @@ To empty the list, use the value $null. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1166,6 +1271,9 @@ 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). @@ -1179,7 +1287,6 @@ 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 @@ -1189,6 +1296,9 @@ 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 @@ -1205,7 +1315,6 @@ 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 @@ -1215,6 +1324,9 @@ 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. @@ -1226,7 +1338,6 @@ 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 @@ -1236,6 +1347,9 @@ 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. @@ -1246,7 +1360,6 @@ 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 @@ -1257,6 +1370,8 @@ 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. @@ -1267,7 +1382,6 @@ 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 @@ -1277,13 +1391,15 @@ 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/exchange/New-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md similarity index 93% rename from exchange/exchange-ps/exchange/New-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md index 427202c583..0ca3548bf4 100644 --- a/exchange/exchange-ps/exchange/New-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedcontentfilterrule +schema: 2.0.0 +title: New-HostedContentFilterRule --- # New-HostedContentFilterRule @@ -54,6 +55,9 @@ 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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. @@ -62,7 +66,6 @@ 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 @@ -72,6 +75,9 @@ 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: @@ -86,7 +92,6 @@ 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 @@ -96,13 +101,15 @@ 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 @@ -112,6 +119,9 @@ 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`. @@ -121,7 +131,6 @@ 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 @@ -131,13 +140,15 @@ 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 @@ -147,13 +158,15 @@ 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 @@ -163,6 +176,9 @@ 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 @@ -178,7 +194,6 @@ 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 @@ -188,6 +203,9 @@ 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 @@ -205,7 +223,6 @@ 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 @@ -215,6 +232,9 @@ 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: @@ -229,7 +249,6 @@ 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 @@ -239,13 +258,15 @@ 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 @@ -255,6 +276,9 @@ 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 @@ -270,7 +294,6 @@ 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 @@ -280,6 +303,9 @@ 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 @@ -297,7 +323,6 @@ 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 @@ -307,13 +332,15 @@ 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/exchange/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md index 6f78d93176..7e4967a6a8 100644 --- a/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedoutboundspamfilterpolicy +schema: 2.0.0 +title: New-HostedOutboundSpamFilterPolicy --- # New-HostedOutboundSpamFilterPolicy @@ -56,13 +57,15 @@ 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 @@ -72,6 +75,9 @@ 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. @@ -83,7 +89,6 @@ Type: OutboundRecipientLimitsExceededAction Parameter Sets: (All) Aliases: Accepted values: Alert, BlockUserForToday, BlockUser -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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). @@ -122,7 +132,6 @@ Type: AutoForwardingMode Parameter Sets: (All) Aliases: Accepted values: Automatic, Off, On -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -132,6 +141,9 @@ 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. @@ -140,7 +152,6 @@ 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 @@ -150,6 +161,9 @@ 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. @@ -159,7 +173,6 @@ 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 @@ -169,6 +182,9 @@ 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: @@ -180,7 +196,6 @@ 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 @@ -190,6 +205,9 @@ 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. @@ -200,7 +218,6 @@ 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 @@ -210,13 +227,15 @@ 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 @@ -226,13 +245,15 @@ 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 @@ -242,13 +263,15 @@ 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 @@ -258,13 +281,15 @@ 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/exchange/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md similarity index 92% rename from exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md index 721a9bd38a..b0379f9f4e 100644 --- a/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedoutboundspamfilterrule +schema: 2.0.0 +title: New-HostedOutboundSpamFilterRule --- # New-HostedOutboundSpamFilterRule @@ -51,6 +52,9 @@ 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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. @@ -59,7 +63,6 @@ Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -69,6 +72,9 @@ 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: @@ -83,7 +89,6 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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`. @@ -118,7 +128,6 @@ 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 @@ -128,6 +137,9 @@ 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. @@ -139,7 +151,6 @@ 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 @@ -149,6 +160,9 @@ 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 @@ -164,7 +178,6 @@ 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 @@ -174,6 +187,9 @@ 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 @@ -189,7 +205,6 @@ 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 @@ -199,13 +214,15 @@ 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 @@ -215,6 +232,9 @@ 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 @@ -230,7 +250,6 @@ 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 @@ -240,6 +259,9 @@ 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 @@ -255,7 +277,6 @@ 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 @@ -265,6 +286,9 @@ 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: @@ -279,7 +303,6 @@ 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 @@ -289,13 +312,15 @@ 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 @@ -305,13 +330,15 @@ 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/exchange/New-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md similarity index 92% rename from exchange/exchange-ps/exchange/New-HybridConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md index a345872239..7c25bb0d00 100644 --- a/exchange/exchange-ps/exchange/New-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-hybridconfiguration +schema: 2.0.0 +title: New-HybridConfiguration --- # New-HybridConfiguration @@ -64,6 +65,9 @@ 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: @@ -78,7 +82,6 @@ You can specify multiple servers separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -88,6 +91,9 @@ 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,7 +103,6 @@ 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,13 +112,15 @@ 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 @@ -123,6 +130,9 @@ 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. @@ -131,7 +141,6 @@ 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 @@ -141,6 +150,9 @@ 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). @@ -154,7 +166,6 @@ 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 @@ -164,6 +175,9 @@ 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. @@ -172,7 +186,6 @@ 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 @@ -182,6 +195,9 @@ 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. @@ -199,7 +215,6 @@ 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 @@ -209,13 +224,15 @@ 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 @@ -225,6 +242,9 @@ 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). @@ -240,7 +260,6 @@ 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 @@ -250,6 +269,9 @@ 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. @@ -258,7 +280,6 @@ The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -268,6 +289,9 @@ 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). @@ -283,7 +307,6 @@ 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 @@ -293,6 +316,9 @@ 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. @@ -303,7 +329,6 @@ 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 @@ -313,6 +338,9 @@ 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. @@ -326,7 +354,6 @@ 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 @@ -336,6 +363,9 @@ 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. @@ -348,7 +378,6 @@ You can specify multiple servers separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -358,13 +387,15 @@ 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/exchange/New-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/New-InboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md index ab3f7a8b2d..1a5e8650e2 100644 --- a/exchange/exchange-ps/exchange/New-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-inboundconnector +schema: 2.0.0 +title: New-InboundConnector --- # New-InboundConnector @@ -76,13 +77,15 @@ 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 @@ -92,6 +95,9 @@ 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. @@ -100,7 +106,6 @@ You can specify multiple domains separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -110,6 +115,9 @@ 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. @@ -118,7 +126,6 @@ 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,13 +135,15 @@ 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 @@ -144,6 +153,9 @@ 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. @@ -157,7 +169,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -167,13 +178,15 @@ 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 @@ -183,6 +196,9 @@ 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`. @@ -192,7 +208,6 @@ 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 @@ -202,6 +217,9 @@ 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. @@ -214,7 +232,6 @@ 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 @@ -224,6 +241,9 @@ 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. @@ -233,7 +253,6 @@ 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 @@ -243,6 +262,9 @@ 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. @@ -255,7 +277,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -265,6 +286,9 @@ 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. @@ -274,7 +298,6 @@ 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 @@ -284,13 +307,15 @@ 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 @@ -300,13 +325,15 @@ 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 @@ -316,6 +343,9 @@ 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. @@ -324,7 +354,6 @@ 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 @@ -334,6 +363,9 @@ 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. @@ -343,7 +375,6 @@ 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 @@ -353,6 +384,9 @@ 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 @@ -364,7 +398,6 @@ 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 @@ -374,6 +407,9 @@ 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. @@ -385,7 +421,6 @@ 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 @@ -395,6 +430,9 @@ 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. @@ -406,7 +444,6 @@ 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 @@ -416,13 +453,15 @@ 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 @@ -432,6 +471,9 @@ 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. @@ -447,7 +489,6 @@ IPv6 addresses are not supported. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -457,13 +498,15 @@ 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 @@ -473,6 +516,9 @@ 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. @@ -489,7 +535,6 @@ 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 @@ -499,6 +544,9 @@ 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. @@ -507,7 +555,6 @@ 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 @@ -517,13 +564,15 @@ 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/exchange/New-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md similarity index 85% rename from exchange/exchange-ps/exchange/New-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md index a3b0fe0e83..23d10ff8a6 100644 --- a/exchange/exchange-ps/exchange/New-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-inboxrule +schema: 2.0.0 +title: New-InboxRule --- # New-InboxRule @@ -130,13 +131,15 @@ 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 @@ -146,6 +149,9 @@ 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 @@ -161,7 +167,6 @@ 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 @@ -171,13 +176,15 @@ 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 @@ -187,13 +194,15 @@ 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 @@ -203,6 +212,9 @@ 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). @@ -211,7 +223,6 @@ 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 @@ -221,6 +232,9 @@ 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 @@ -254,7 +268,6 @@ 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 @@ -264,6 +277,9 @@ 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. @@ -276,7 +292,6 @@ 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 @@ -286,6 +301,9 @@ 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`. @@ -295,7 +313,6 @@ 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 @@ -305,6 +322,9 @@ 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: @@ -326,7 +346,6 @@ 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 @@ -336,6 +355,9 @@ 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. @@ -345,7 +367,6 @@ 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 @@ -355,6 +376,9 @@ 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 @@ -388,7 +412,6 @@ 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 @@ -398,6 +421,9 @@ 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. @@ -406,7 +432,6 @@ 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 @@ -416,6 +441,9 @@ 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. @@ -428,7 +456,6 @@ 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 @@ -438,6 +465,9 @@ 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 @@ -458,7 +488,6 @@ 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 @@ -468,6 +497,9 @@ 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 @@ -485,7 +517,6 @@ 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 @@ -495,6 +526,9 @@ 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. @@ -507,7 +541,6 @@ 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 @@ -517,6 +550,9 @@ 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. @@ -528,7 +564,6 @@ 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 @@ -538,6 +573,9 @@ 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. @@ -546,7 +584,6 @@ 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 @@ -556,6 +593,9 @@ 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. @@ -568,7 +608,6 @@ 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 @@ -578,6 +617,9 @@ 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 @@ -598,7 +640,6 @@ 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 @@ -608,6 +649,9 @@ 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. @@ -619,7 +663,6 @@ 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 @@ -629,6 +672,9 @@ 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. @@ -640,7 +686,6 @@ 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 @@ -650,6 +695,9 @@ 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. @@ -661,7 +709,6 @@ 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 @@ -671,6 +718,9 @@ 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. @@ -682,7 +732,6 @@ 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 @@ -692,6 +741,9 @@ 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". @@ -702,7 +754,6 @@ 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 @@ -712,6 +763,9 @@ 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". @@ -722,7 +776,6 @@ 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 @@ -732,6 +785,9 @@ 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. @@ -742,7 +798,6 @@ 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 @@ -752,6 +807,9 @@ 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. @@ -763,7 +821,6 @@ 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 @@ -773,6 +830,9 @@ 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 @@ -790,7 +850,6 @@ 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 @@ -800,6 +859,9 @@ 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. @@ -812,7 +874,6 @@ 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 @@ -822,6 +883,9 @@ 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. @@ -834,7 +898,6 @@ 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 @@ -844,6 +907,9 @@ 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 @@ -856,7 +922,6 @@ 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 @@ -866,6 +931,9 @@ 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: @@ -886,7 +954,6 @@ 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 @@ -896,6 +963,9 @@ 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: @@ -916,7 +986,6 @@ 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 @@ -926,6 +995,9 @@ 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 @@ -939,7 +1011,6 @@ 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 @@ -949,6 +1020,9 @@ 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 @@ -967,7 +1041,6 @@ 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 @@ -977,6 +1050,9 @@ 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. @@ -985,7 +1061,6 @@ 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 @@ -995,6 +1070,9 @@ 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 @@ -1010,7 +1088,6 @@ 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 @@ -1020,6 +1097,9 @@ 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 @@ -1035,7 +1115,6 @@ 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 @@ -1045,6 +1124,9 @@ 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 @@ -1062,7 +1144,6 @@ 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 @@ -1072,6 +1153,9 @@ 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. @@ -1084,7 +1168,6 @@ 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 @@ -1094,6 +1177,9 @@ 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. @@ -1105,7 +1191,6 @@ 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 @@ -1115,6 +1200,9 @@ 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. @@ -1123,7 +1211,6 @@ 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 @@ -1133,6 +1220,9 @@ 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. @@ -1145,7 +1235,6 @@ 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 @@ -1155,6 +1244,9 @@ 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 @@ -1172,7 +1264,6 @@ 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 @@ -1182,6 +1273,9 @@ 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. @@ -1191,7 +1285,6 @@ 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 @@ -1201,6 +1294,9 @@ 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 @@ -1211,7 +1307,6 @@ 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 @@ -1221,6 +1316,9 @@ 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 @@ -1241,7 +1339,6 @@ 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 @@ -1251,6 +1348,9 @@ 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: @@ -1272,7 +1372,6 @@ 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 @@ -1282,6 +1381,9 @@ 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. @@ -1293,7 +1395,6 @@ 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 @@ -1303,6 +1404,9 @@ 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. @@ -1314,7 +1418,6 @@ 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 @@ -1324,6 +1427,9 @@ 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. @@ -1335,7 +1441,6 @@ 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 @@ -1345,6 +1450,9 @@ 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. @@ -1356,7 +1464,6 @@ 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 @@ -1366,6 +1473,9 @@ 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. @@ -1375,7 +1485,6 @@ 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 @@ -1385,13 +1494,15 @@ 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 @@ -1401,6 +1512,9 @@ 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". @@ -1411,7 +1525,6 @@ 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 @@ -1421,6 +1534,9 @@ 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". @@ -1431,7 +1547,6 @@ 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 @@ -1441,6 +1556,9 @@ 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. @@ -1451,7 +1569,6 @@ 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 @@ -1461,6 +1578,9 @@ 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 @@ -1476,7 +1596,6 @@ 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 @@ -1486,6 +1605,9 @@ 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. @@ -1496,7 +1618,6 @@ 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 @@ -1506,6 +1627,9 @@ 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. @@ -1517,7 +1641,6 @@ 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 @@ -1527,6 +1650,9 @@ 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 @@ -1544,7 +1670,6 @@ 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 @@ -1554,6 +1679,9 @@ Accept wildcard characters: False ``` ### -SoftDeleteMessage + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SoftDeleteMessage Description }} @@ -1562,7 +1690,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1572,6 +1699,9 @@ 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. @@ -1581,7 +1711,6 @@ 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 @@ -1591,6 +1720,9 @@ 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. @@ -1603,7 +1735,6 @@ 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 @@ -1613,6 +1744,9 @@ 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. @@ -1625,7 +1759,6 @@ 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 @@ -1635,13 +1768,15 @@ 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 @@ -1651,6 +1786,9 @@ 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 @@ -1663,7 +1801,6 @@ 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 @@ -1673,6 +1810,9 @@ 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: @@ -1693,7 +1833,6 @@ 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 @@ -1703,6 +1842,9 @@ 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: @@ -1723,7 +1865,6 @@ 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 @@ -1733,6 +1874,9 @@ 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 @@ -1746,7 +1890,6 @@ 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/exchange/New-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md index 0e1826be8c..3538d9c052 100644 --- a/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy +schema: 2.0.0 +title: New-InformationBarrierPolicy --- # New-InformationBarrierPolicy @@ -90,13 +91,15 @@ 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 @@ -106,13 +109,15 @@ 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 @@ -122,13 +127,15 @@ 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 @@ -138,6 +145,9 @@ 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"). @@ -148,7 +158,6 @@ You can't use this parameter with the SegmentsBlocked parameter. Type: MultiValuedProperty Parameter Sets: OrganizationSegmentsAllowed Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -158,6 +167,9 @@ 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"). @@ -168,7 +180,6 @@ You can't use this parameter with the SegmentsAllowed parameter. Type: MultiValuedProperty Parameter Sets: OrganizationSegmentsBlocked Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -178,13 +189,15 @@ 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 @@ -194,13 +207,15 @@ 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 @@ -210,6 +225,9 @@ 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. @@ -218,7 +236,6 @@ 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 @@ -228,13 +245,15 @@ 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 @@ -244,6 +263,9 @@ 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 @@ -254,7 +276,6 @@ Type: EopInformationBarrierPolicyState Parameter Sets: (All) Aliases: Accepted values: Inactive, Active -Applicable: Security & Compliance Required: False Position: Named @@ -264,13 +285,15 @@ 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/exchange/New-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md similarity index 91% rename from exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md index 4e22683783..d01406c2ed 100644 --- a/exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-intraorganizationconnector +schema: 2.0.0 +title: New-IntraOrganizationConnector --- # New-IntraOrganizationConnector @@ -49,13 +50,15 @@ 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 @@ -65,13 +68,15 @@ 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 @@ -81,6 +86,9 @@ 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. @@ -89,7 +97,6 @@ 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 @@ -99,6 +106,9 @@ 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`. @@ -108,7 +118,6 @@ 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 @@ -118,6 +127,9 @@ 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. @@ -126,7 +138,6 @@ 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 @@ -136,6 +147,9 @@ 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. @@ -144,7 +158,6 @@ 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 @@ -154,6 +167,9 @@ 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. @@ -162,7 +178,6 @@ 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 @@ -172,13 +187,15 @@ 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/exchange/New-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md similarity index 88% rename from exchange/exchange-ps/exchange/New-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md index 2812bcf0ef..6c547fa5c9 100644 --- a/exchange/exchange-ps/exchange/New-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md @@ -1,12 +1,13 @@ --- -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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-journalrule +schema: 2.0.0 +title: New-JournalRule --- # New-JournalRule @@ -50,13 +51,15 @@ This example creates and enables a journal rule. The rule applies to all email m ## 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 journal rule. The name of the rule can be up to 64 characters long. ```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 @@ -66,6 +69,9 @@ Accept wildcard characters: False ``` ### -JournalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The JournalEmailAddress parameter specifies a recipient object to which journal reports are sent. You can use any value that uniquely identifies the recipient. For example: - Name @@ -79,7 +85,6 @@ The JournalEmailAddress parameter specifies a recipient object to which journal Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether the journal rule is enabled or disabled. If the rule is disabled, it isn't applied to any email 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 @@ -142,6 +153,9 @@ Accept wildcard characters: False ``` ### -Recipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recipient parameter specifies the SMTP address of a mailbox, contact, or distribution group to journal. If you specify a distribution group, all recipients in that distribution group are journaled. All messages sent to or from a recipient are journaled. To journal messages from all recipients, don't use this parameter. @@ -150,7 +164,6 @@ To journal messages from all recipients, don't use this parameter. 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 @@ -160,6 +173,9 @@ Accept wildcard characters: False ``` ### -Scope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Scope parameter specifies the scope of email messages to which the journal rule is applied. Valid values for this parameter are as follows: - Global: Global rules process all email messages that pass through a Transport service. This includes email messages that were already processed by the external and internal rules. The default value is Global. @@ -170,7 +186,6 @@ The Scope parameter specifies the scope of email messages to which the journal r Type: JournalRuleScope Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -180,13 +195,15 @@ 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/exchange/New-Label.md b/exchange/exchange-ps/ExchangePowerShell/New-Label.md similarity index 94% rename from exchange/exchange-ps/exchange/New-Label.md rename to exchange/exchange-ps/ExchangePowerShell/New-Label.md index ccfa3a9d5e..c0ed602390 100644 --- a/exchange/exchange-ps/exchange/New-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Label.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/policy-and-compliance/new-label applicable: Security & Compliance -title: New-Label -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/policy-and-compliance/new-label +schema: 2.0.0 +title: New-Label --- # New-Label @@ -117,13 +118,15 @@ This example create a new label named "New Label" with a display name "My New La ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the sensitivity label. 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 @@ -133,13 +136,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name for the sensitivity label. The display name appears in any client that supports sensitivity labels. This includes Word, Excel, PowerPoint, Outlook, SharePoint, Teams, and Power BI. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -149,13 +154,15 @@ Accept wildcard characters: False ``` ### -Tooltip + +> Applicable: Security & Compliance + The ToolTip parameter specifies the default tooltip and sensitivity label description that's seen by users. It the value contains spaces, enclose the value in quotation marks ("). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -165,6 +172,9 @@ Accept wildcard characters: False ``` ### -AdvancedSettings + +> Applicable: Security & Compliance + The AdvancedSettings parameter enables specific features and capabilities for a sensitivity label. Specify this parameter with the identity (name or GUID) of the sensitivity label, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value. @@ -195,7 +205,6 @@ Supported settings for built-in labeling: Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -205,6 +214,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterAlignment + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterAlignment parameter specifies the footer alignment. Valid values are: - Left @@ -217,7 +229,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -227,6 +238,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterEnabled + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterEnabled parameter enables or disables the Apply Content Marking Footer action for the label. Valid values are: - $true: The Apply Content Marking Footer action is enabled. @@ -236,7 +250,6 @@ The ApplyContentMarkingFooterEnabled parameter enables or disables the Apply Con Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -246,6 +259,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontColor + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontColor parameter specifies the color of the footer text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -254,7 +270,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -264,6 +279,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontName + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontName parameter specifies the font of the footer text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -274,7 +292,6 @@ This parameter is supported only by the Azure Information Protection unified lab Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -284,6 +301,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontSize + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontSize parameter specifies the font size (in points) of the footer text. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -292,7 +312,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -302,6 +321,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterMargin + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterMargin parameter specifies the size (in points) of the footer margin. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -312,7 +334,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -322,6 +343,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterText + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterText parameter specifies the footer text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -330,7 +354,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -340,6 +363,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderAlignment + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderAlignment parameter specifies the header alignment. Valid values are: - Left @@ -352,7 +378,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -362,6 +387,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderEnabled + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderEnabled parameter enables or disables the Apply Content Marking Header action for the label. Valid values are: - $true: The Apply Content Marking Header action is enabled. @@ -371,7 +399,6 @@ The ApplyContentMarkingHeaderEnabled parameter enables or disables the Apply Con Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -381,6 +408,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontColor + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontColor parameter specifies the color of the header text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -389,7 +419,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -399,6 +428,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontName + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontName parameter specifies the font of the header text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -407,7 +439,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -417,6 +448,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontSize + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontSize parameter specifies the font size (in points) of the header text. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -425,7 +459,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -435,6 +468,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderMargin + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderMargin parameter specifies the size (in points) of the header margin. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -445,7 +481,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -455,6 +490,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderText + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderText parameter specifies the header text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -463,7 +501,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -473,6 +510,9 @@ Accept wildcard characters: False ``` ### -ApplyDynamicWatermarkingEnabled + +> Applicable: Security & Compliance + **Note**: This parameter is Generally Available only for labels with admin-defined permissions. Support for label with user-defined permissions is currently in Public Preview, isn't available in all organizations, and is subject to change. The ApplyDynamicWatermarkingEnabled parameter enables dynamic watermarking for a specific label that applies encryption. Valid values are: @@ -486,7 +526,6 @@ You set the watermark text with the DynamicWatermarkDisplay parameter. For more Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -496,6 +535,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingEnabled + +> Applicable: Security & Compliance + The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarking Header action for the label. Valid values are: - $true: The Apply Watermarking Header action is enabled. @@ -505,7 +547,6 @@ The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarkin Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -515,6 +556,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontColor + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontColor parameter specifies the color of the watermark text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -523,7 +567,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -533,6 +576,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontName + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontName parameter specifies the font of the watermark text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -541,7 +587,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -551,6 +596,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontSize + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontSize parameter specifies the font size (in points) of the watermark text. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -559,7 +607,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -569,6 +616,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingLayout + +> Applicable: Security & Compliance + The ApplyWaterMarkingLayout parameter specifies the watermark alignment. Valid values are: - Horizontal @@ -580,7 +630,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+WaterMarkingLayout Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -590,6 +639,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingText + +> Applicable: Security & Compliance + The ApplyWaterMarkingText parameter specifies the watermark text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -598,7 +650,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -608,13 +659,15 @@ Accept wildcard characters: False ``` ### -ColumnAssetCondition + +> 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 @@ -624,13 +677,15 @@ 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 @@ -640,13 +695,15 @@ Accept wildcard characters: False ``` ### -Conditions + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MulitValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -656,6 +713,9 @@ 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`. @@ -665,7 +725,6 @@ 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 @@ -675,6 +734,9 @@ Accept wildcard characters: False ``` ### -ContentType + +> Applicable: Security & Compliance + The ContentType parameter specifies where the sensitivity label can be applied. Valid values are: - File @@ -691,7 +753,6 @@ Values can be combined, for example: "File, Email, PurviewAssets". Type: MipLabelContentType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -701,13 +762,15 @@ Accept wildcard characters: False ``` ### -DefaultContentLabel + +> Applicable: Security & Compliance + The DefaultContentLabel specifies a label that can be automatically applied to meetings created in a labeled Teams channel. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -717,6 +780,9 @@ Accept wildcard characters: False ``` ### -DynamicWatermarkDisplay + +> Applicable: Security & Compliance + **Note**: This parameter is Generally Available only for labels with admin-defined permissions. Support for label with user-defined permissions is currently in Public Preview, isn't available in all organizations, and is subject to change. The DynamicWatermarkDisplay parameter specifies the watermark text to display for a given label. This parameter supports text and the following special tokens: @@ -730,7 +796,6 @@ This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled param Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -740,6 +805,9 @@ Accept wildcard characters: False ``` ### -EncryptionAipTemplateScopes + +> Applicable: Security & Compliance + The EncryptionAipTemplateScopes parameter specifies that the label is still published and usable in the AIP classic client. An example value is `"['allcompany@labelaction.onmicrosoft.com','admin@labelaction.onmicrosoft.com']"`. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -748,7 +816,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -758,6 +825,9 @@ Accept wildcard characters: False ``` ### -EncryptionContentExpiredOnDateInDaysOrNever + +> Applicable: Security & Compliance + The EncryptionContentExpiredOnDateInDaysOrNever parameter specifies when the encrypted content expires. Valid values are: - An integer (number of days) @@ -769,7 +839,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -779,6 +848,9 @@ Accept wildcard characters: False ``` ### -EncryptionDoNotForward + +> Applicable: Security & Compliance + The EncryptionDoNotForward parameter specifies whether the Do Not Forward template is applied. Valid values are: - $true: The Do Not Forward template is applied. @@ -790,7 +862,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -800,6 +871,9 @@ Accept wildcard characters: False ``` ### -EncryptionDoubleKeyEncryptionUrl + +> Applicable: Security & Compliance + The feature for this parameter is currently in Public Preview, and is not available to everyone. The EncryptionDoubleKeyEncryptionUrl parameter specifies the Double Key Encryption endpoint URL. @@ -812,7 +886,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -822,6 +895,9 @@ Accept wildcard characters: False ``` ### -EncryptionEnabled + +> Applicable: Security & Compliance + The EncryptionEnabled parameter specifies whether encryption in enabled. Valid values are: - $true: Encryption is enabled. @@ -831,7 +907,6 @@ The EncryptionEnabled parameter specifies whether encryption in enabled. Valid v Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -841,6 +916,9 @@ Accept wildcard characters: False ``` ### -EncryptionEncryptOnly + +> Applicable: Security & Compliance + The EncryptionEncryptOnly parameter specifies whether the encrypt-only template is applied. Valid values are: - $true: The encrypt-only template is applied. @@ -852,7 +930,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -862,13 +939,15 @@ Accept wildcard characters: False ``` ### -EncryptionLinkedTemplateId + +> 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 @@ -878,6 +957,9 @@ Accept wildcard characters: False ``` ### -EncryptionOfflineAccessDays + +> Applicable: Security & Compliance + The EncryptionOfflineAccessDays parameter specifies the number of days that offline access is allowed. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -886,7 +968,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -896,6 +977,9 @@ Accept wildcard characters: False ``` ### -EncryptionPromptUser + +> Applicable: Security & Compliance + The EncryptionPromptUser parameter specifies whether to set the label with user defined permission in Word, Excel, and PowerPoint. Valid values are: - $true: The label is set with user defined permissions in Word, Excel and PowerPoint. @@ -907,7 +991,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -917,6 +1000,9 @@ Accept wildcard characters: False ``` ### -EncryptionProtectionType + +> Applicable: Security & Compliance + The EncryptionProtectionType parameter specifies the protection type for encryption. Valid values are: - Template @@ -929,7 +1015,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+SupportedProtectionType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -939,6 +1024,9 @@ Accept wildcard characters: False ``` ### -EncryptionRightsDefinitions + +> Applicable: Security & Compliance + The EncryptionRightsDefinitions parameter specifies the rights users have when accessing protected. This parameter uses the syntax `Identity1:Rights1,Rights2;Identity2:Rights3,Rights4`. For example, `john@contoso.com:VIEW,EDIT;microsoft.com:VIEW`. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false and the EncryptionProtectionType parameter value is Template. @@ -947,7 +1035,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: EncryptionRightsDefinitionsParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -957,6 +1044,9 @@ Accept wildcard characters: False ``` ### -EncryptionRightsUrl + +> Applicable: Security & Compliance + The EncryptionRightsUrl parameter specifies the URL for hold your own key (HYOK) protection. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -965,7 +1055,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -975,6 +1064,9 @@ Accept wildcard characters: False ``` ### -EncryptionTemplateId + +> Applicable: Security & Compliance + The EncryptionTemplateId parameter lets you convert an existing protection template from Azure Information Protection to a new sensitivity label. Specify the template by its ID that you can identify by running the [Get-AipServiceTemplate](https://learn.microsoft.com/powershell/module/aipservice/get-aipservicetemplate) cmdlet from the [AIPService PowerShell module](https://learn.microsoft.com/powershell/module/aipservice). This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -983,7 +1075,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -993,13 +1084,15 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Security & Compliance + The Identity parameter is used to migrate an existing Azure Information Protection label by specifying a GUID value. ```yaml Type: MasterIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1009,13 +1102,15 @@ Accept wildcard characters: False ``` ### -LabelActions + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1025,6 +1120,9 @@ Accept wildcard characters: False ``` ### -LocaleSettings + +> Applicable: Security & Compliance + The LocaleSettings parameter specifies one or more localized label names or label Tooltips in different languages. Regions include all region codes supported in Office Client applications. Valid values use the following syntax: - Label display names: `{"localeKey":"DisplayName","Settings":[{"Key":"en-us","Value":"English display name"},{"Key":"de-de","Value":"Deutscher Anzeigename"},{"Key":"es-es","Value":"Nombre para mostrar en español"}]}` @@ -1034,7 +1132,6 @@ The LocaleSettings parameter specifies one or more localized label names or labe Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1044,13 +1141,15 @@ Accept wildcard characters: False ``` ### -MigrationId + +> 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 @@ -1060,6 +1159,9 @@ Accept wildcard characters: False ``` ### -ParentId + +> Applicable: Security & Compliance + The ParentId parameter specifies the parent label that you want this label to be under (a sublabel). You can use any value that uniquely identifies the parent sensitivity label. For example: - Name @@ -1070,7 +1172,6 @@ The ParentId parameter specifies the parent label that you want this label to be Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1080,13 +1181,15 @@ Accept wildcard characters: False ``` ### -SchematizedDataCondition + +> 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 @@ -1096,13 +1199,15 @@ Accept wildcard characters: False ``` ### -Setting + +> 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 @@ -1112,13 +1217,15 @@ Accept wildcard characters: False ``` ### -Settings + +> 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 @@ -1128,6 +1235,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowAccessToGuestUsers + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowAccessToGuestUsers parameter enables or disables access to guest users. Valid values are: - $true: Guest access is enabled. @@ -1139,7 +1249,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1149,6 +1258,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowEmailFromGuestUsers + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowEmailFromGuestUsers parameter enables or disables email from guest users. Valid values are: - $true: Email from guest users is enabled. @@ -1160,7 +1272,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1170,6 +1281,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowFullAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowFullAccess parameter enables or disables full access. Valid values are: - $true: Full access is enabled. @@ -1181,7 +1295,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1191,6 +1304,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowLimitedAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowLimitedAccess parameter enables or disables limited access. Valid values are: - $true: Limited access is enabled. @@ -1202,7 +1318,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1212,6 +1327,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionBlockAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionBlockAccess parameter blocks access. Valid values are: - $true: Access is blocked. @@ -1223,7 +1341,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1233,6 +1350,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionEnabled + +> Applicable: Security & Compliance + The SiteAndGroupProtectionEnabled parameter enables or disables the Site and Group Protection action for the label. Valid values are: - $true: The Site and Group Protection action is enabled. @@ -1242,7 +1362,6 @@ The SiteAndGroupProtectionEnabled parameter enables or disables the Site and Gro Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1252,13 +1371,15 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionLevel + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: SiteAndGroupProtectionLevelParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1268,6 +1389,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionPrivacy + +> Applicable: Security & Compliance + The SiteAndGroupProtectionPrivacy parameter specifies the privacy level for the labe. Valid values are: - Public @@ -1279,7 +1403,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+GroupProtectionPrivacy Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1289,6 +1412,9 @@ Accept wildcard characters: False ``` ### -SiteExternalSharingControlType + +> Applicable: Security & Compliance + The SiteExternalSharingControlType parameter specifies the external user sharing setting for the label. Valid values are: - ExternalUserAndGuestSharing @@ -1307,7 +1433,6 @@ These correspond to the following settings through the admin center: Type: Microsoft.Office.CompliancePolicy.Tasks.SiteExternalSharingControlType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1317,6 +1442,9 @@ Accept wildcard characters: False ``` ### -TeamsAllowedPresenters + +> Applicable: Security & Compliance + The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Valid values are: - Everyone @@ -1329,7 +1457,6 @@ The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AllowedPresenters Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1339,6 +1466,9 @@ Accept wildcard characters: False ``` ### -TeamsAllowMeetingChat + +> Applicable: Security & Compliance + The TeamsAllowMeetingChat parameter controls whether chat is available in Teams meetings. Valid values are: - Enabled @@ -1350,7 +1480,6 @@ The TeamsAllowMeetingChat parameter controls whether chat is available in Teams Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.MeetingChatMode Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1360,13 +1489,15 @@ Accept wildcard characters: False ``` ### -TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch + +> Applicable: Security & Compliance + {{ Fill TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1376,6 +1507,9 @@ Accept wildcard characters: False ``` ### -TeamsBypassLobbyForDialInUsers + +> Applicable: Security & Compliance + The TeamsBypassLobbyForDialInUsers parameter controls the lobby experience for dial-in users who join Teams meetings. Valid values are: - $true: Dial in users bypass the lobby when joining Teams meetings. @@ -1386,7 +1520,6 @@ The TeamsBypassLobbyForDialInUsers parameter controls the lobby experience for d Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1396,13 +1529,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelProtectionEnabled + +> Applicable: Security & Compliance + {{ Fill TeamsChannelProtectionEnabled Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1412,13 +1547,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithExternalTenants + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithExternalTenants Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1428,13 +1565,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithPrivateTeamsOnly + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithPrivateTeamsOnly Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1444,13 +1583,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithSameLabelOnly + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithSameLabelOnly Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1460,6 +1601,9 @@ Accept wildcard characters: False ``` ### -TeamsCopyRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsCopyRestrictionEnforced parameter controls whether chat messages in Teams meetings can be copied to the clipboard. Valid values are: - $true: Chat messages can be copied to the clipboard. @@ -1471,7 +1615,6 @@ The value $null (blank) allows users to configure this setting in the Teams app. Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1481,6 +1624,9 @@ Accept wildcard characters: False ``` ### -TeamsEndToEndEncryptionEnabled + +> Applicable: Security & Compliance + The TeamsEndToEndEncryptionEnabled parameter controls video stream encryption in Teams meetings. Valid values are: - $true: Video stream encryption is enabled. @@ -1493,7 +1639,6 @@ The value $null (blank) allows users to configure this setting in the Teams app. Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1503,6 +1648,9 @@ Accept wildcard characters: False ``` ### -TeamsLobbyBypassScope + +> Applicable: Security & Compliance + The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Teams meetings. Valid values are: - Everyone @@ -1517,7 +1665,6 @@ The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.LobbyBypassScope Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1527,6 +1674,9 @@ Accept wildcard characters: False ``` ### -TeamsLobbyRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsLobbyRestrictionEnforced parameter controls whether participants bypass the lobby when joining Teams meetings. Valid values are: - $true: Users bypass the lobby when joining Teams meetings. @@ -1537,7 +1687,6 @@ The TeamsLobbyRestrictionEnforced parameter controls whether participants bypass Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1547,6 +1696,9 @@ Accept wildcard characters: False ``` ### -TeamsPresentersRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsPresentersRestrictionEnforced parameter controls whether presenter restrictions are enabled in Teams meetings. Valid values are: - $true: Presenter restrictions are enabled in Teams meetings. @@ -1557,7 +1709,6 @@ The TeamsPresentersRestrictionEnforced parameter controls whether presenter rest Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1567,6 +1718,9 @@ Accept wildcard characters: False ``` ### -TeamsProtectionEnabled + +> Applicable: Security & Compliance + The TeamsProtectionEnabled parameter controls whether Teams protection is enabled in Teams meetings. Valid values are: - $true: Teams protection is enabled in Teams meetings. @@ -1576,7 +1730,6 @@ The TeamsProtectionEnabled parameter controls whether Teams protection is enable Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1586,6 +1739,9 @@ Accept wildcard characters: False ``` ### -TeamsRecordAutomatically + +> Applicable: Security & Compliance + The TeamsRecordAutomatically parameter controls whether Teams meetings are automatically recorded after they start. Valid values are: - $true: Teams meetings are automatically recorded after they start. @@ -1596,7 +1752,6 @@ The TeamsRecordAutomatically parameter controls whether Teams meetings are autom Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1606,6 +1761,9 @@ Accept wildcard characters: False ``` ### -TeamsVideoWatermark + +> Applicable: Security & Compliance + The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams meetings. Valid values are: - None @@ -1617,7 +1775,6 @@ The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WaterMarkProtectionValues Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1627,6 +1784,9 @@ Accept wildcard characters: False ``` ### -TeamsWhoCanRecord + +> Applicable: Security & Compliance + The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid values are: - Organizer @@ -1638,7 +1798,6 @@ The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid va Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WhoCanRecordOptions Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1648,13 +1807,15 @@ 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/exchange/New-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-LabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md index ce59ac07c5..c1cf3f02ff 100644 --- a/exchange/exchange-ps/exchange/New-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-labelpolicy applicable: Security & Compliance -title: New-LabelPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-labelpolicy +schema: 2.0.0 +title: New-LabelPolicy --- # New-LabelPolicy @@ -60,13 +61,15 @@ This example creates the sensitivity label policy named Research and Development ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the 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: 1 @@ -76,6 +79,9 @@ Accept wildcard characters: False ``` ### -Labels + +> Applicable: Security & Compliance + The Labels parameter specifies the sensitivity labels that are associated with the policy. You can use any value that uniquely identifies the label. For example: - Name @@ -88,7 +94,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -98,6 +103,9 @@ Accept wildcard characters: False ``` ### -AdvancedSettings + +> Applicable: Security & Compliance + The AdvancedSettings parameter enables client-specific features and capabilities for the sensitivity label policy. Specify this parameter with the identity (name or GUID) of the policy, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value. @@ -134,7 +142,6 @@ Additionally, for Power BI: Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -144,13 +151,15 @@ 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 @@ -160,6 +169,9 @@ 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`. @@ -169,7 +181,6 @@ 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 @@ -179,6 +190,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocation + +> Applicable: Security & Compliance + The ExchangeLocation parameter specifies the mailboxes to include in the policy. A valid value is a mailbox. To specify the mailbox, you can use any value that uniquely identifies it. For example: @@ -194,7 +208,6 @@ 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 @@ -204,6 +217,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocationException + +> Applicable: Security & Compliance + The ExchangeLocationException parameter specifies the mailboxes to exclude when you use the value All for the ExchangeLocation parameter. A valid value is a mailbox. To specify the mailbox, you can use any value that uniquely identifies it. For example: @@ -219,7 +235,6 @@ 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 @@ -229,6 +244,9 @@ 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. @@ -237,7 +255,6 @@ 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 @@ -247,13 +264,15 @@ Accept wildcard characters: False ``` ### -MigrationId + +> 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 @@ -263,6 +282,9 @@ Accept wildcard characters: False ``` ### -ModernGroupLocation + +> Applicable: Security & Compliance + The ModernGroupLocation parameter specifies the Microsoft 365 Groups to include in the policy. To identify the Microsoft 365 Group, you must use the primary SMTP 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"`. @@ -271,7 +293,6 @@ 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 @@ -281,13 +302,15 @@ Accept wildcard characters: False ``` ### -ModernGroupLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -297,13 +320,15 @@ Accept wildcard characters: False ``` ### -OneDriveLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -313,13 +338,15 @@ Accept wildcard characters: False ``` ### -OneDriveLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -329,6 +356,9 @@ 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. @@ -337,7 +367,6 @@ 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 @@ -347,13 +376,15 @@ Accept wildcard characters: False ``` ### -PublicFolderLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -363,13 +394,15 @@ Accept wildcard characters: False ``` ### -Setting + +> 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 @@ -379,13 +412,15 @@ Accept wildcard characters: False ``` ### -Settings + +> 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 @@ -395,13 +430,15 @@ Accept wildcard characters: False ``` ### -SharePointLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -411,13 +448,15 @@ Accept wildcard characters: False ``` ### -SharePointLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -427,13 +466,15 @@ Accept wildcard characters: False ``` ### -SkypeLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -443,13 +484,15 @@ Accept wildcard characters: False ``` ### -SkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -459,13 +502,15 @@ 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/exchange/New-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md index 1182270b7a..ea203278a0 100644 --- a/exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-m365dataatrestencryptionpolicy applicable: Exchange Online -title: New-M365DataAtRestEncryptionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-m365dataatrestencryptionpolicy +schema: 2.0.0 +title: New-M365DataAtRestEncryptionPolicy --- # New-M365DataAtRestEncryptionPolicy @@ -47,13 +48,15 @@ This example creates a Microsoft 365 data-at-rest multi-workload encryption poli ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the Microsoft 365 data-at-rest 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: 0 @@ -63,6 +66,9 @@ Accept wildcard characters: False ``` ### -AzureKeyIDs + +> Applicable: Exchange Online + The AzureKeyIDs parameter specifies the URL of the encryption key in the Azure Key Vault that's used for encryption. For example, `https://contoso.vault.azure.net/keys/key1/`. You can specify multiple values separated by commas using the following syntax: `"AzureKeyID1","AzureKeyID2",..."AzureKeyIDN"`. @@ -71,7 +77,6 @@ You can specify multiple values separated by commas using the following syntax: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -81,6 +86,9 @@ 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`. @@ -90,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online + The Description parameter specifies an optional description for the policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -116,13 +125,15 @@ 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 @@ -132,6 +143,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -141,7 +155,6 @@ The Enabled parameter specifies whether the policy is enabled or disabled. Valid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -151,13 +164,15 @@ 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/exchange/New-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md similarity index 85% rename from exchange/exchange-ps/exchange/New-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailContact.md index fcccb631e5..3ffa71b360 100644 --- a/exchange/exchange-ps/exchange/New-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailcontact applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MailContact -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailcontact +schema: 2.0.0 +title: New-MailContact --- # New-MailContact @@ -58,6 +59,9 @@ This example creates a new mail contact named Chris Ashton. ## 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 mail contact. 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. @@ -66,7 +70,6 @@ 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 @@ -76,6 +79,9 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -84,7 +90,6 @@ 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, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -94,6 +99,9 @@ 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: @@ -118,7 +126,6 @@ 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 @@ -128,6 +135,9 @@ 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: @@ -147,7 +157,6 @@ 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 @@ -157,6 +166,9 @@ 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`. @@ -166,7 +178,6 @@ 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 @@ -176,6 +187,9 @@ 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 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 ("). If you don't use the DisplayName parameter, the value of the Name parameter is used for the display name. @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ 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. @@ -202,7 +218,6 @@ 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 @@ -212,13 +227,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FirstName parameter specifies the user's first name. ```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 @@ -228,13 +245,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Initials parameter specifies the user's middle initials. ```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 @@ -244,13 +263,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LastName parameter specifies the user's last name. ```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 @@ -260,6 +281,9 @@ Accept wildcard characters: False ``` ### -MacAttachmentFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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) @@ -276,7 +300,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -286,6 +309,9 @@ Accept wildcard characters: False ``` ### -MessageBodyFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -301,7 +327,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -311,6 +336,9 @@ Accept wildcard characters: False ``` ### -MessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -326,7 +354,6 @@ The MessageFormat and MessageBodyFormat parameters are interdependent: Type: MessageFormat 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 @@ -336,6 +363,9 @@ 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 mail contact. A moderator approves messages sent to the mail contact 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 @@ -353,7 +383,6 @@ You need to use this parameter to specify at least one moderator when you set th 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 @@ -363,6 +392,9 @@ 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. @@ -374,7 +406,6 @@ 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 @@ -384,6 +415,9 @@ 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 new contact 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: @@ -397,7 +431,6 @@ 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 @@ -407,6 +440,9 @@ 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. @@ -419,7 +455,6 @@ 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 @@ -429,6 +464,9 @@ 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. @@ -441,7 +479,6 @@ 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 @@ -451,6 +488,9 @@ Accept wildcard characters: False ``` ### -UsePreferMessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -460,7 +500,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -470,13 +509,15 @@ 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/exchange/New-MailMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md similarity index 90% rename from exchange/exchange-ps/exchange/New-MailMessage.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md index c016c6ef01..e8fca62f75 100644 --- a/exchange/exchange-ps/exchange/New-MailMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailmessage applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MailMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailmessage +schema: 2.0.0 +title: New-MailMessage --- # New-MailMessage @@ -83,13 +84,15 @@ This example creates an email message in the Drafts folder with the subject and ## PARAMETERS ### -Body + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Body parameter specifies the content of the body section of the new email message. ```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: 1 @@ -99,13 +102,15 @@ Accept wildcard characters: False ``` ### -BodyFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BodyFormat parameter specifies the format of the message body. The values can be PlainText, Rtf (Rich Text Format), or Html. By default, if the BodyFormat parameter isn't specified when the Body parameter is used, the message body is rendered in plain text. ```yaml Type: MailBodyFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -115,6 +120,9 @@ 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`. @@ -124,7 +132,6 @@ 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 @@ -134,6 +141,9 @@ 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,7 +152,6 @@ 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 @@ -152,13 +161,15 @@ Accept wildcard characters: False ``` ### -Subject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Subject parameter specifies the content of the subject field of the new email message. ```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 @@ -168,13 +179,15 @@ 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/exchange/New-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md similarity index 86% rename from exchange/exchange-ps/exchange/New-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailUser.md index e468b87dcb..9405543144 100644 --- a/exchange/exchange-ps/exchange/New-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailuser applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MailUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailuser +schema: 2.0.0 +title: New-MailUser --- # New-MailUser @@ -234,6 +235,9 @@ This example creates a new mail user for Ed Meadows in the contoso.com cloud-bas ## 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 mail user. 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. @@ -242,7 +246,6 @@ 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 @@ -252,15 +255,17 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. ```yaml Type: ProxyAddress -Parameter Sets: DisabledUser, EnabledUser +Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -269,20 +274,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: ProxyAddress -Parameter Sets: FederatedUser, MicrosoftOnlineServicesID -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +### -FederatedIdentity -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online, Exchange Online Protection -### -FederatedIdentity This parameter is available only in the cloud-based service. The FederatedIdentity parameter associates an on-premises Active Directory user with a user in the cloud. @@ -291,7 +286,6 @@ The FederatedIdentity parameter associates an on-premises Active Directory user Type: String Parameter Sets: FederatedUser, MicrosoftOnlineServicesFederatedUser Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -301,13 +295,15 @@ Accept wildcard characters: False ``` ### -MicrosoftOnlineServicesID + +> Applicable: Exchange Online, Exchange Online Protection + The MicrosoftOnlineServicesID parameter specifies the user ID for the object. This parameter only applies to objects in the cloud-based service. It isn't available for on-premises deployments. ```yaml Type: WindowsLiveId -Parameter Sets: MicrosoftOnlineServicesID, MicrosoftOnlineServicesFederatedUser +Parameter Sets: MicrosoftOnlineServicesID, MicrosoftOnlineServicesFederatedUser, EnableRoomMailboxAccount Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -316,20 +312,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: WindowsLiveId -Parameter Sets: EnableRoomMailboxAccount -Aliases: -Applicable: Exchange Online, Exchange Online Protection +### -Password -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -### -Password The Password parameter specifies the password for the user's account. You can use the following methods as a value for this parameter: @@ -342,7 +328,6 @@ You can use the following methods as a value for this parameter: Type: SecureString Parameter Sets: EnabledUser, HVEAccount, LOBAppAccount, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -352,6 +337,9 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UserPrincipalName parameter specifies the name of a system user in an email address format (for example, ed@contoso.com). @@ -360,7 +348,6 @@ The UserPrincipalName parameter specifies the name of a system user in an email Type: String Parameter Sets: EnabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -370,6 +357,9 @@ 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: @@ -394,7 +384,6 @@ 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 @@ -404,6 +393,9 @@ 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: @@ -423,7 +415,6 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t Type: MailboxIdParameter Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -433,6 +424,9 @@ 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`. @@ -442,7 +436,6 @@ 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 @@ -452,6 +445,9 @@ 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 mail user. The display name is visible in the Exchange admin center, in address lists, and in 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. @@ -460,7 +456,6 @@ 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 @@ -470,6 +465,9 @@ 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. @@ -478,7 +476,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -488,13 +485,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FirstName parameter specifies the user's first name. ```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 @@ -504,6 +503,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -512,7 +514,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service 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 @@ -522,13 +523,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Initials parameter specifies the user's middle initials. ```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 @@ -538,13 +541,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LastName parameter specifies the user's last name. ```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 @@ -554,6 +559,9 @@ 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. @@ -562,7 +570,6 @@ 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 @@ -572,6 +579,9 @@ 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. @@ -580,7 +590,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: LOBAppAccount Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -590,6 +599,9 @@ Accept wildcard characters: False ``` ### -MacAttachmentFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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) @@ -606,7 +618,6 @@ The MacAttachmentFormat and MessageFormat parameters are interdependent: Type: MacAttachmentFormat Parameter Sets: DisabledUser, EnabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -616,6 +627,9 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service This parameter is reserved for internal Microsoft use. @@ -624,7 +638,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -634,6 +647,9 @@ Accept wildcard characters: False ``` ### -MessageBodyFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -649,7 +665,6 @@ The MessageFormat and MessageBodyFormat parameters are interdependent: Type: MessageBodyFormat Parameter Sets: DisabledUser, EnabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -659,6 +674,9 @@ Accept wildcard characters: False ``` ### -MessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -675,7 +693,6 @@ Therefore, if you want to change the MessageFormat parameter from Mime to Text, Type: MessageFormat Parameter Sets: DisabledUser, EnabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -685,6 +702,9 @@ 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 @@ -702,7 +722,6 @@ You need to use this parameter to specify at least one moderator when you set th 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 @@ -712,6 +731,9 @@ 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. @@ -723,7 +745,6 @@ 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 @@ -733,6 +754,9 @@ 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 new mail user 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: @@ -746,7 +770,6 @@ 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 @@ -756,6 +779,9 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only in on-premises Exchange. The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. @@ -768,7 +794,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -778,6 +803,9 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: - $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. @@ -791,7 +819,6 @@ A user's experience in any of these management interfaces is still controlled by 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 @@ -801,6 +828,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: @@ -812,7 +842,6 @@ The ResetPasswordOnNextLogon parameter specifies whether the user must change th Type: Boolean Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -822,6 +851,9 @@ 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). The maximum length is 20 characters. @@ -830,7 +862,6 @@ The SamAccountName parameter (also known as the pre-Windows 2000 user account or Type: String Parameter Sets: DisabledUser, EnabledUser, FederatedUser, MicrosoftOnlineServicesID Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -840,6 +871,9 @@ 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. @@ -852,7 +886,6 @@ 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 @@ -862,6 +895,9 @@ Accept wildcard characters: False ``` ### -UsePreferMessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -871,7 +907,6 @@ The UsePreferMessageFormat specifies whether the message format settings configu Type: Boolean Parameter Sets: DisabledUser, EnabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -881,13 +916,15 @@ 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/exchange/New-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/New-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md index 8a4bb79a06..82af70ca5a 100644 --- a/exchange/exchange-ps/exchange/New-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-Mailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailbox +schema: 2.0.0 +title: New-Mailbox --- # New-Mailbox @@ -808,6 +809,9 @@ This example assumes that you've already created a mail-enabled security group n ## 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 mailbox. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). In the cloud-based service, many special characters aren't allowed in the Name value (for example, ö, ü, or ä). For more information, see [Error when you try to create a username that contains a special character in Microsoft 365](https://learn.microsoft.com/office/troubleshoot/office-suite-issues/username-contains-special-character). @@ -816,7 +820,6 @@ In the cloud-based service, many special characters aren't allowed in the Name v 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 @@ -826,6 +829,9 @@ Accept wildcard characters: False ``` ### -AccountDisabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AccountDisabled switch specifies that the user account associated with the mailbox is disabled. You don't need to specify a value with this switch. @@ -836,7 +842,6 @@ The mailbox is created, and the associated account is created, but the account i Type: SwitchParameter Parameter Sets: DisabledUser Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -846,6 +851,9 @@ 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 create arbitration mailboxes. You don't need to specify a value with this switch. @@ -856,9 +864,8 @@ To create arbitration mailboxes that are used to store audit log settings or dat ```yaml Type: SwitchParameter -Parameter Sets: Arbitration +Parameter Sets: Arbitration, Migration Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -867,20 +874,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SwitchParameter -Parameter Sets: Migration -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -ArchiveDomain -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -ArchiveDomain 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. @@ -891,7 +888,6 @@ 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 @@ -901,6 +897,9 @@ Accept wildcard characters: False ``` ### -Discovery + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Discovery switch is required to create Discovery mailboxes. You don't need to specify a value with this switch. Discovery mailboxes are created as target mailboxes for Discovery searches. After being created or enabled, a Discovery mailbox can't be repurposed or converted to another type of mailbox. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). @@ -909,7 +908,6 @@ 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, Exchange Online Required: True Position: Named @@ -919,6 +917,9 @@ Accept wildcard characters: False ``` ### -EnableRoomMailboxAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The EnableRoomMailboxAccount parameter specifies whether to enable the disabled user account that's associated with this room mailbox. Valid values are: @@ -936,7 +937,6 @@ A room mailbox in Exchange Online is created with associated an account that has Type: Boolean Parameter Sets: EnableRoomMailboxAccount Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -946,6 +946,9 @@ Accept wildcard characters: False ``` ### -Equipment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Equipment switch is required to create 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). @@ -954,7 +957,6 @@ 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, Exchange Online Required: True Position: Named @@ -964,6 +966,9 @@ Accept wildcard characters: False ``` ### -FederatedIdentity + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FederatedIdentity parameter associates an on-premises Active Directory user with a user in the cloud. @@ -972,7 +977,6 @@ The FederatedIdentity parameter associates an on-premises Active Directory user Type: String Parameter Sets: FederatedUser, MicrosoftOnlineServicesFederatedUser Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -982,15 +986,17 @@ Accept wildcard characters: False ``` ### -InactiveMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The InactiveMailbox parameter specifies the inactive mailbox that you want to recover. To find inactive mailboxes, run the command `Get-Mailbox -InactiveMailboxOnly | Format-List Name,PrimarySmtpAddress,DistinguishedName,ExchangeGuid` and then use the DistinguishedName or ExchangeGuid property values to identify the inactive mailbox for this parameter (only those values are guaranteed to be unique for inactive mailboxes). ```yaml Type: MailboxIdParameter -Parameter Sets: InactiveMailbox +Parameter Sets: InactiveMailbox, User Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -999,20 +1005,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: MailboxIdParameter -Parameter Sets: User -Aliases: -Applicable: Exchange Online +### -LinkedDomainController -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -LinkedDomainController 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. @@ -1023,7 +1019,6 @@ This parameter is required only if you're creating a linked mailbox. Type: String Parameter Sets: Linked, LinkedRoomMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1033,6 +1028,9 @@ 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: @@ -1046,7 +1044,6 @@ The LinkedMasterAccount parameter specifies the master account in the forest whe Type: UserIdParameter Parameter Sets: Linked, LinkedRoomMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1056,6 +1053,9 @@ 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 create linked resource mailboxes. You don't need to specify a value with this switch. @@ -1066,7 +1066,6 @@ 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 @@ -1076,15 +1075,17 @@ Accept wildcard characters: False ``` ### -MicrosoftOnlineServicesID + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MicrosoftOnlineServicesID parameter specifies the user ID for the object. This parameter applies only to objects in the cloud-based service and is used instead of the UserPrincipalName parameter. The MicrosoftOnlineServicesID parameter isn't available in on-premises deployments. ```yaml Type: WindowsLiveId -Parameter Sets: MicrosoftOnlineServicesFederatedUser, MicrosoftOnlineServicesFederatedUser +Parameter Sets: MicrosoftOnlineServicesFederatedUser, MicrosoftOnlineServicesFederatedUser, EnableRoomMailboxAccount Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -1093,27 +1094,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: WindowsLiveId -Parameter Sets: EnableRoomMailboxAccount -Aliases: -Applicable: Exchange Online +### -Migration -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -### -Migration The Migration switch is required to create migration mailboxes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Migration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -1123,6 +1113,9 @@ Accept wildcard characters: False ``` ### -Password + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Password parameter specifies the password for the mailbox (the user account that's associated with the mailbox). This parameter isn't required if you're creating a linked mailbox, resource mailbox, or shared mailbox, because the associated user accounts are disabled for these types of mailboxes. You can use the following methods as a value for this parameter: @@ -1133,9 +1126,8 @@ You can use the following methods as a value for this parameter: ```yaml Type: SecureString -Parameter Sets: User, MicrosoftOnlineServicesID, RemoteArchive +Parameter Sets: User, MicrosoftOnlineServicesID, RemoteArchive, Arbitration, DisabledUser, Discovery, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -1144,20 +1136,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecureString -Parameter Sets: Arbitration, DisabledUser, Discovery, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration RemovedMailbox, Room, Shared -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -PublicFolder -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -PublicFolder The PublicFolder switch is required to create public folder mailboxes. 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. @@ -1168,7 +1150,6 @@ The first public folder mailbox created in your Exchange organization is the pri Type: SwitchParameter Parameter Sets: PublicFolder Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -1178,6 +1159,9 @@ Accept wildcard characters: False ``` ### -RemovedMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -1186,7 +1170,6 @@ This parameter is reserved for internal Microsoft use. Type: RemovedMailboxIdParameter Parameter Sets: RemovedMailbox Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -1196,6 +1179,9 @@ Accept wildcard characters: False ``` ### -Room + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Room switch is required to create 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). @@ -1208,7 +1194,6 @@ When you use this switch in Exchange Online, an account with a random, unknown p Type: SwitchParameter Parameter Sets: EnableRoomMailboxAccount, Room Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -1218,6 +1203,9 @@ Accept wildcard characters: False ``` ### -Shared + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Shared switch is required to create 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. The mailbox isn't associated with any of the users that can log on. It's associated with a disabled user account. @@ -1226,7 +1214,6 @@ 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, Exchange Online Required: True Position: Named @@ -1236,6 +1223,9 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. @@ -1244,9 +1234,8 @@ In the cloud-based service, use the MicrosoftOnlineServicesID parameter instead. ```yaml Type: String -Parameter Sets: User, Arbitration, AuditLog, RemoteArchive +Parameter Sets: User, Arbitration, AuditLog, RemoteArchive, AuxAuditLog, DisabledUser,Discovery, EnableRoomMailboxAccount, Equipment, Linked, LinkedRoomMailbox, Migration, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1255,20 +1244,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: AuxAuditLog, DisabledUser,Discovery, EnableRoomMailboxAccount, Equipment, Linked, LinkedRoomMailbox, Migration, Room, Shared, SupervisoryReviewPolicyMailbox -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -ActiveSyncMailboxPolicy -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -ActiveSyncMailboxPolicy 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 @@ -1281,7 +1260,6 @@ If you don't use this parameter, the default mobile device mailbox policy is use Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1291,6 +1269,9 @@ 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: @@ -1305,7 +1286,6 @@ For more information about address book policies, see [Address book policies in Type: AddressBookMailboxPolicyIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1315,6 +1295,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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: @@ -1339,7 +1322,6 @@ 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 Required: False Position: Named @@ -1349,6 +1331,9 @@ 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: @@ -1368,7 +1353,6 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t Type: MailboxIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, DisabledUser, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1378,13 +1362,15 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Archive switch specifies that an archive mailbox is created for this 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 @@ -1394,6 +1380,9 @@ 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: @@ -1406,7 +1395,6 @@ The ArchiveDatabase parameter specifies the Exchange database that contains the Type: DatabaseIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1416,6 +1404,9 @@ 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 create audit log mailboxes. You don't need to specify a value with this switch. @@ -1428,7 +1419,6 @@ To create other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: AuditLog Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1438,6 +1428,9 @@ 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 create auxiliary audit log mailboxes. You don't need to specify a value with this switch. @@ -1450,7 +1443,6 @@ To create other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: AuxAuditLog Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -1460,6 +1452,9 @@ 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`. @@ -1469,7 +1464,6 @@ 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 @@ -1479,6 +1473,9 @@ 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 mailbox database that contains the mailbox. You can use any value that uniquely identifies the database. For example: @@ -1493,7 +1490,6 @@ Use the Get-MailboxDatabase cmdlet to see the available mailbox databases. Type: DatabaseIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1503,6 +1499,9 @@ 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 mailbox. The display name is visible in the Exchange admin center, in address lists, and in 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. @@ -1511,7 +1510,6 @@ 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 @@ -1521,6 +1519,9 @@ 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. @@ -1529,7 +1530,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1539,13 +1539,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FirstName parameter specifies the user's first name. ```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 @@ -1555,6 +1557,9 @@ 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. @@ -1563,7 +1568,6 @@ 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 Required: False Position: Named @@ -1573,6 +1577,9 @@ Accept wildcard characters: False ``` ### -HoldForMigration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. You need to use this parameter when you create the first public folder, which is called the hierarchy mailbox, in your organization. @@ -1583,7 +1590,6 @@ Use this parameter only if you plan to migrate legacy Exchange 2010 public folde Type: SwitchParameter Parameter Sets: PublicFolder Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1593,6 +1599,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -1601,7 +1610,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service 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 @@ -1611,13 +1619,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Initials parameter specifies the user's middle initials. ```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 @@ -1627,13 +1637,15 @@ Accept wildcard characters: False ``` ### -IsExcludedFromServingHierarchy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. ```yaml Type: Boolean Parameter Sets: PublicFolder Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1643,13 +1655,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LastName parameter specifies the user's last name. ```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 @@ -1659,6 +1673,9 @@ 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 credentials to use to access the domain controller specified by the LinkedDomainController parameter. This parameter is optional, even if you're enabling a linked mailbox. @@ -1669,7 +1686,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: Linked, LinkedRoomMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1679,6 +1695,9 @@ Accept wildcard characters: False ``` ### -MailboxPlan + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxPlan parameter specifies the mailbox plan to apply to the mailbox. You can use any value that uniquely identifies the mailbox plan. For example: @@ -1697,7 +1716,6 @@ You can see the available mailbox plans by using the Get-MailboxPlan cmdlet. Type: MailboxPlanIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, DisabledUser, FederatedUser, InactiveMailbox, MicrosoftOnlineServicesFederatedUser, RemoteArchive, RemovedMailbox Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1707,6 +1725,9 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments. @@ -1719,7 +1740,6 @@ To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the Type: String Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1729,6 +1749,9 @@ 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. @@ -1737,7 +1760,6 @@ The ManagedFolderMailboxPolicy parameter specifies the managed folder mailbox po Type: MailboxPolicyIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1747,6 +1769,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicyAllowed + +> Applicable: Exchange Server 2010 + This parameter is available only 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 Microsoft Outlook earlier than Office Outlook 2007. You don't need to specify a value with this switch. @@ -1759,7 +1784,6 @@ Outlook 2003 Service Pack 3 clients are supported but are provided limited funct Type: SwitchParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1769,6 +1793,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 @@ -1786,7 +1813,6 @@ You need to use this parameter to specify at least one moderator when you set th Type: MultiValuedProperty Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1796,6 +1822,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -1807,7 +1836,6 @@ You use the ModeratedBy parameter to specify the moderators. Type: Boolean Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1817,13 +1845,15 @@ Accept wildcard characters: False ``` ### -Office + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Office parameter specifies the user's physical office name or number. ```yaml Type: String Parameter Sets: LinkedRoomMailbox, Room Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1833,6 +1863,9 @@ Accept wildcard characters: False ``` ### -OrganizationalUnit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OrganizationalUnit parameter specifies the location in Active Directory where the new mailbox 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: @@ -1846,7 +1879,6 @@ 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 Required: False Position: Named @@ -1856,13 +1888,15 @@ Accept wildcard characters: False ``` ### -Phone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Phone parameter specifies the user's telephone number. ```yaml Type: String Parameter Sets: LinkedRoomMailbox, Room Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1872,6 +1906,9 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. If you use the PrimarySmtpAddress parameter to specify the primary email address, the command sets the EmailAddressPolicyEnabled property of the mailbox to False, which means the email addresses of the mailbox aren't automatically updated by email address policies. @@ -1880,7 +1917,6 @@ 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, Exchange Online Required: False Position: Named @@ -1890,6 +1926,9 @@ Accept wildcard characters: False ``` ### -ProxyEmailAddress + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ProxyEmailAddress Description }} @@ -1898,7 +1937,6 @@ This parameter is available only in the cloud-based service. Type: Object Parameter Sets: Arbitration Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1908,6 +1946,9 @@ 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. @@ -1916,7 +1957,6 @@ The RemoteArchive switch specifies that a remote archive mailbox is created for Type: SwitchParameter Parameter Sets: RemoteArchive Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1926,6 +1966,9 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: - $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. @@ -1939,7 +1982,6 @@ A user's experience in any of these management interfaces is still controlled by 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 @@ -1949,6 +1991,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: - $true: The user is required to change their password the next time they log on to their mailbox. @@ -1958,7 +2003,6 @@ The ResetPasswordOnNextLogon parameter specifies whether the user is required to 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 @@ -1968,13 +2012,15 @@ Accept wildcard characters: False ``` ### -ResourceCapacity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResourceCapacity parameter specifies the capacity of the resource mailbox. For example, you can use this parameter to identify the number of seats in a conference room (room mailbox) or in a vehicle (equipment mailbox). A valid value is an integer. ```yaml Type: Int32 Parameter Sets: Room Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1984,6 +2030,9 @@ 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 you want applied to this mailbox. You can use any value that uniquely identifies the policy. For example: @@ -2002,7 +2051,6 @@ If you don't use this parameter, the retention policy named Default MRM Policy i Type: MailboxPolicyIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2012,6 +2060,9 @@ Accept wildcard characters: False ``` ### -RoleAssignmentPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RoleAssignmentPolicy parameter specifies the role assignment policy that's applied to the mailbox. You can use any value that uniquely identifies the role assignment policy. For example: - Name @@ -2026,7 +2077,6 @@ Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment pol Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2036,6 +2086,9 @@ Accept wildcard characters: False ``` ### -RoomMailboxPassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. Use the RoomMailboxPassword parameter to configure the password for the account that's associated with the room mailbox when that account is enabled and able to log in (the EnableRoomMailboxAccount parameter is set to the value $true). @@ -2060,7 +2113,6 @@ To configure the password for a room mailbox account in Exchange Online, use [Up Type: SecureString Parameter Sets: EnableRoomMailboxAccount Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2070,6 +2122,9 @@ 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). The maximum length is 20 characters. @@ -2078,7 +2133,6 @@ The SamAccountName parameter (also known as the pre-Windows 2000 user account or Type: String Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2088,6 +2142,9 @@ Accept wildcard characters: False ``` ### -SendModerationNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -2100,7 +2157,6 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab Type: TransportModerationNotificationFlags Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2110,6 +2166,9 @@ Accept wildcard characters: False ``` ### -SharingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SharingPolicy parameter specifies the sharing policy that's applied to the mailbox. You can use any value that uniquely identifies the sharing policy. For example: @@ -2126,7 +2185,6 @@ If you don't use this parameter, the sharing policy named Default Sharing Policy Type: SharingPolicyIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2136,6 +2194,9 @@ 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. @@ -2144,7 +2205,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -2154,6 +2214,9 @@ Accept wildcard characters: False ``` ### -TargetAllMDBs + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2162,7 +2225,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, FederatedUser, InactiveMailbox, Linked, LinkedRoomMailbox, MicrosoftOnlineServicesFederatedUser, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2172,6 +2234,9 @@ Accept wildcard characters: False ``` ### -ThrottlingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ThrottlingPolicy parameter specifies the throttling policy that's applied to the mailbox. You can use any value that uniquely identifies the throttling policy. For example: @@ -2188,7 +2253,6 @@ By default, no throttling policy is applied to the mailbox. Type: ThrottlingPolicyIdParameter Parameter Sets: User, MicrosoftOnlineServicesID, Arbitration, AuditLog, AuxAuditLog, DisabledUser, Discovery, EnableRoomMailboxAccount, Equipment, InactiveMailbox, Linked, LinkedRoomMailbox, Migration, PublicFolder, RemoteArchive, RemovedMailbox, Room, Shared, SupervisoryReviewPolicyMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2198,13 +2262,15 @@ 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/exchange/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md similarity index 88% rename from exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md index 38f9329045..b32a306254 100644 --- a/exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxauditlogsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MailboxAuditLogSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxauditlogsearch +schema: 2.0.0 +title: New-MailboxAuditLogSearch --- # New-MailboxAuditLogSearch @@ -65,6 +66,9 @@ This example returns entries from the mailbox audit logs of all users in organiz ## PARAMETERS ### -EndDate + +> Applicable: Exchange Server 2010, 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". @@ -73,7 +77,6 @@ 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 Required: True Position: Named @@ -83,6 +86,9 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Server 2010, 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". @@ -91,7 +97,6 @@ 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 Required: True Position: Named @@ -101,13 +106,15 @@ Accept wildcard characters: False ``` ### -StatusMailRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StatusMailRecipients parameter specifies the email address where the search results are sent. 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: True Position: Named @@ -117,6 +124,9 @@ 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`. @@ -126,7 +136,6 @@ 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,6 +145,9 @@ 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. @@ -144,7 +156,6 @@ 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 @@ -154,6 +165,9 @@ Accept wildcard characters: False ``` ### -ExternalAccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalAccess parameter specifies whether to return only audit log entries for mailbox access by users that are outside of your organization. In Exchange Online, this parameter returns audit log entries for mailbox access by Microsoft datacenter administrators. Valid values are: $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. @@ -164,7 +178,6 @@ $false: Audit log entries for mailbox access by external users or Microsoft data 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 @@ -174,6 +187,9 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The GroupMailbox switch is required to include Microsoft 365 Groups in the search. You don't need to specify a value with this switch. @@ -182,7 +198,6 @@ The GroupMailbox switch is required to include Microsoft 365 Groups in the searc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -192,6 +207,9 @@ Accept wildcard characters: False ``` ### -HasAttachments + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The HasAttachments parameter filters the search by messages that have attachments. Valid values are: - $true: Only messages with attachments are included in the search. @@ -201,7 +219,6 @@ The HasAttachments parameter filters the search by messages that have attachment Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -211,6 +228,9 @@ Accept wildcard characters: False ``` ### -LogonTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LogonTypes parameter specifies the type of logons. Valid values are: - Admin: Audit log entries for mailbox access by administrator logons are returned. @@ -224,7 +244,6 @@ You can enter 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 Required: False Position: Named @@ -234,6 +253,9 @@ Accept wildcard characters: False ``` ### -Mailboxes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailboxes parameter specifies the mailbox to retrieve mailbox audit log entries from. 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"`. @@ -244,7 +266,6 @@ 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, Exchange Online Required: False Position: Named @@ -254,13 +275,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the search. 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: False Position: Named @@ -270,6 +293,9 @@ Accept wildcard characters: False ``` ### -Operations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Operations parameter filters the search results by the operations that are logged by mailbox audit logging. Valid values are: - Copy @@ -291,7 +317,6 @@ 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 Required: False Position: Named @@ -301,13 +326,15 @@ Accept wildcard characters: False ``` ### -ShowDetails + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowDetails switch specifies that details of each log entry are retrieved. 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 @@ -317,13 +344,15 @@ 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/exchange/New-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md similarity index 84% rename from exchange/exchange-ps/exchange/New-MailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md index a16092d137..32a6135153 100644 --- a/exchange/exchange-ps/exchange/New-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxdatabase applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-MailboxDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxdatabase +schema: 2.0.0 +title: New-MailboxDatabase --- # New-MailboxDatabase @@ -66,13 +67,15 @@ This example creates the mailbox database DB1 on the Mailbox server named Server ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the new mailbox database. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). ```yaml Type: String -Parameter Sets: NonRecovery +Parameter Sets: NonRecovery, Recovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,27 +84,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: Recovery -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Recovery -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Recovery The Recovery switch specifies that the new database is designated as a recovery database. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Recovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -111,6 +103,9 @@ 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,7 +117,6 @@ The Server parameter specifies the Exchange server where you want to run this co Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -132,13 +126,15 @@ Accept wildcard characters: False ``` ### -AutoDagExcludeFromMonitoring + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagExcludeFromMonitoring parameter specifies that the database being created should not be monitored by managed availability. ```yaml Type: Boolean Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -148,6 +144,9 @@ 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`. @@ -157,7 +156,6 @@ 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,13 +165,15 @@ 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 @@ -183,13 +183,15 @@ Accept wildcard characters: False ``` ### -EdbFilePath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EdbFilePath parameter specifies the path to the database files. The default location is `%ExchangeInstallPath%Mailbox\\.edb`. ```yaml Type: EdbFilePath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -199,6 +201,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromInitialProvisioning + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromInitialProvisioning switch specifies that this database is temporarily not considered by the mailbox provisioning load balancer. You don't need to specify a value with this switch. If you use this switch, new mailboxes aren't added automatically to this database. @@ -207,7 +212,6 @@ If you use this switch, new mailboxes aren't added automatically to this databas Type: SwitchParameter Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -217,13 +221,15 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioning + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromProvisioning parameter specifies whether this database is considered by the mailbox provisioning load balancer. If the IsExcludedFromProvisioning parameter is set to $true, no new mailboxes are automatically added to this database. ```yaml Type: Boolean Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -233,13 +239,15 @@ Accept wildcard characters: False ``` ### -IsSuspendedFromProvisioning + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsSuspendedFromProvisioning parameter specifies whether this database is temporarily considered by the mailbox provisioning load balancer. ```yaml Type: Boolean Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -249,13 +257,15 @@ Accept wildcard characters: False ``` ### -LogFolderPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogFolderPath parameter specifies the folder location for log files.The default location is `%ExchangeInstallPath%Mailbox\` ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -265,13 +275,15 @@ Accept wildcard characters: False ``` ### -OfflineAddressBook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OfflineAddressBook parameter specifies the associated offline address book (OAB) for the new mailbox database. ```yaml Type: OfflineAddressBookIdParameter Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -281,6 +293,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PublicFolderDatabase parameter specifies the associated public folder database for the new mailbox database. You can use any value that uniquely identifies the public folder database. For example: - Name @@ -291,7 +306,6 @@ The PublicFolderDatabase parameter specifies the associated public folder databa Type: DatabaseIdParameter Parameter Sets: NonRecovery Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -301,13 +315,15 @@ Accept wildcard characters: False ``` ### -SkipDatabaseLogFolderCreation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -317,13 +333,15 @@ 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/exchange/New-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/New-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md index 56a97e1c20..f16d975fdf 100644 --- a/exchange/exchange-ps/exchange/New-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxexportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-MailboxExportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxexportrequest +schema: 2.0.0 +title: New-MailboxExportRequest --- # New-MailboxExportRequest @@ -161,6 +162,9 @@ This example exports all messages from Kweku's Inbox to the .pst file InPlaceHol ## PARAMETERS ### -Mailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013 + The Mailbox parameter specifies 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. @@ -180,9 +184,8 @@ In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdP ```yaml Type: MailboxOrMailUserIdParameter -Parameter Sets: Mailbox +Parameter Sets: Mailbox, MailboxExportRequest, MailboxComplianceExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: True Position: 1 @@ -191,27 +194,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: MailboxLocationIdParameter -Parameter Sets: MailboxExportRequest, MailboxComplianceExportRequest -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -ComplianceStorePath -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019 -### -ComplianceStorePath This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: MailboxComplianceExportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -221,6 +213,9 @@ Accept wildcard characters: False ``` ### -FilePath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FilePath parameter specifies the network share path of the .pst file to which data is exported, for example, \\\\SERVER01\\PST Files\\exported.pst. You need to grant the following permission to the group Exchange Trusted Subsystem to the network share where you want to export or import PST files: @@ -234,7 +229,6 @@ If you don't grant this permission, you will receive an error message stating th Type: LongPath Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -244,13 +238,15 @@ Accept wildcard characters: False ``` ### -RemoteCredential + +> Applicable: Exchange Server 2013, Exchange Server 2016 + This parameter is reserved for internal Microsoft use. ```yaml Type: PSCredential -Parameter Sets: Mailbox, MailboxExportRequest +Parameter Sets: Mailbox, MailboxExportRequest, MailboxComplianceExportRequest Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -259,20 +255,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: PSCredential -Parameter Sets: MailboxComplianceExportRequest -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -AcceptLargeDataLoss -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -AcceptLargeDataLoss The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -283,7 +269,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,6 +278,9 @@ Accept wildcard characters: False ``` ### -AssociatedMessagesCopyOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. By default, associated messages are copied. This parameter accepts the following values: - DoNotCopy: The associated messages aren't copied. @@ -305,7 +293,6 @@ Content filtering doesn't apply to associated messages. Type: FAICopyOption Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -315,6 +302,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -325,7 +315,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -335,13 +324,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BatchName parameter specifies a descriptive name for exporting a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxExportRequest cmdlet. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -351,13 +342,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -367,6 +360,9 @@ 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`. @@ -376,7 +372,6 @@ 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 @@ -386,6 +381,9 @@ Accept wildcard characters: False ``` ### -ConflictResolutionOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: - ForceCopy @@ -399,7 +397,6 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl Type: ConflictResolutionOption Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -409,6 +406,9 @@ Accept wildcard characters: False ``` ### -ContentFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **Important**: You can't use this parameter to export between two dates. If you try, you'll get system convert errors. You can export from a specific date, or export to a specific date, but not both. The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. @@ -426,7 +426,6 @@ 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 @@ -436,6 +435,9 @@ Accept wildcard characters: False ``` ### -ContentFilterLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ContentFilterLanguage parameter specifies the language being used in the ContentFilter parameter for string searches. 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). @@ -444,7 +446,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -454,13 +455,15 @@ 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 @@ -470,6 +473,9 @@ Accept wildcard characters: False ``` ### -ExcludeDumpster + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch. If you don't use this switch, the Recoverable Items folder is copied with the following subfolders: @@ -482,7 +488,6 @@ If you don't use this switch, the Recoverable Items folder is copied with the fo Type: SwitchParameter Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -492,6 +497,9 @@ Accept wildcard characters: False ``` ### -ExcludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExcludeFolders parameter specifies the list of folders to exclude during the export. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -528,7 +536,6 @@ To exclude the Recoverable Items folder, you must use the ExcludeDumpster parame Type: String[] Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -538,6 +545,9 @@ Accept wildcard characters: False ``` ### -IncludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IncludeFolders parameter specifies the list of folders to include during the export. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -574,7 +584,6 @@ The Recoverable Items folder is always included if you don't use the ExcludeDump Type: String[] Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -584,13 +593,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -600,13 +611,15 @@ Accept wildcard characters: False ``` ### -IsArchive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsArchive switch specifies that you're exporting from the user's archive. 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 @@ -616,6 +629,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -631,7 +647,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -641,6 +656,9 @@ Accept wildcard characters: False ``` ### -MRSServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSServer parameter specifies the FQDN of the Client Access server on which the instance of the Microsoft Exchange Mailbox Replication service (MRS) is running. This parameter is used for debugging purposes only. Use this parameter only if directed by support personnel. @@ -649,7 +667,6 @@ The MRSServer parameter specifies the FQDN of the Client Access server on which Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -659,6 +676,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple export requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an export request for a user's mailbox that has the alias Kweku and specify the value of this parameter as PC1toArchive, the identity of this export request is Kweku\\PC1toArchive. If you don't specify a name using this parameter, Exchange generates up to 10 request names per mailbox, which is MailboxExportX (where X = 0-9). The identity of the request is displayed and searchable as `\MailboxExportX`. @@ -667,7 +687,6 @@ If you don't specify a name using this parameter, Exchange generates up to 10 re Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -677,13 +696,15 @@ Accept wildcard characters: False ``` ### -PreferredMessageFormat + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MessageCopyFormat Parameter Sets: MailboxComplianceExportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -693,6 +714,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lower @@ -707,7 +731,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -717,13 +740,15 @@ Accept wildcard characters: False ``` ### -RemoteHostName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Fqdn Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -733,6 +758,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -746,7 +774,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: MailboxComplianceExportRequest, MailboxExportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -756,13 +783,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SkipMerging parameter specifies steps in the export that should be skipped. This parameter is used primarily for debugging purposes. ```yaml Type: SkippableMergeComponent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -772,13 +801,15 @@ Accept wildcard characters: False ``` ### -SourceRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SourceRootFolder parameter specifies the root folder of the mailbox from which data is exported. If this parameter isn't specified, the command exports all folders. ```yaml Type: String Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -788,6 +819,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -796,7 +830,6 @@ If you use this switch, the request is queued, but the request won't reach the s Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -806,13 +839,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend 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 @@ -822,13 +857,15 @@ Accept wildcard characters: False ``` ### -TargetRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetRootFolder parameter specifies the top-level folder in which to export data. If you don't specify this parameter, the command exports folders to the top of the folder structure in the target .pst file. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. ```yaml Type: String Parameter Sets: Mailbox, MailboxExportRequest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -838,13 +875,15 @@ 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 @@ -854,13 +893,15 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: RequestWorkloadType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/New-MailboxFolder.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md index 8edb27513b..ef63aea4b9 100644 --- a/exchange/exchange-ps/exchange/New-MailboxFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MailboxFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxfolder +schema: 2.0.0 +title: New-MailboxFolder --- # New-MailboxFolder @@ -52,13 +53,15 @@ This example creates the folder named Personal in the root folder hierarchy of y ## 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 new folder. 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 @@ -68,6 +71,9 @@ Accept wildcard characters: False ``` ### -Parent + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Parent parameter specifies where to create the new mailbox folder. 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. @@ -95,7 +101,6 @@ 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: True Position: Named @@ -105,6 +110,9 @@ 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`. @@ -114,7 +122,6 @@ 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 @@ -124,6 +131,9 @@ 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. @@ -132,7 +142,6 @@ 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 @@ -142,13 +151,15 @@ 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/exchange/New-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/New-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md index f037f6aba2..06f9dc244b 100644 --- a/exchange/exchange-ps/exchange/New-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboximportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MailboxImportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboximportrequest +schema: 2.0.0 +title: New-MailboxImportRequest --- # New-MailboxImportRequest @@ -160,6 +161,9 @@ This example imports all of the .pst files on a shared folder. Each .pst file na ## PARAMETERS ### -Mailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013 + The Mailbox parameter specifies the destination mailbox where the content is being imported to. 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. @@ -179,9 +183,8 @@ In Exchange 2016 CU6 or earlier, this parameter is the type MailboxOrMailUserIdP ```yaml Type: MailboxOrMailUserIdParameter -Parameter Sets: Mailbox +Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: True Position: 1 @@ -190,20 +193,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: MailboxLocationIdParameter -Parameter Sets: MailboxLocationId -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online +### -AzureBlobStorageAccountUri -Required: True -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -AzureBlobStorageAccountUri This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -212,7 +205,6 @@ This parameter is reserved for internal Microsoft use. Type: Uri Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -222,6 +214,9 @@ Accept wildcard characters: False ``` ### -AzureSharedAccessSignatureToken + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -230,7 +225,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -240,6 +234,9 @@ Accept wildcard characters: False ``` ### -FilePath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FilePath parameter specifies the network share path of the .pst file from which data is imported, for example, \\\\SERVER01\\PST Files\\ToImport.pst. @@ -255,7 +252,6 @@ If you don't grant this permission, you will receive an error message stating th Type: LongPath Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -265,6 +261,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -275,7 +274,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -285,6 +283,9 @@ Accept wildcard characters: False ``` ### -AssociatedMessagesCopyOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. By default, associated messages are copied. This parameter accepts the following values: - DoNotCopy: The associated messages aren't copied. @@ -297,7 +298,6 @@ Content filtering doesn't apply to associated messages. Type: FAICopyOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -307,6 +307,9 @@ Accept wildcard characters: False ``` ### -AzureStatusPublishEndpointInfo + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -315,7 +318,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -325,6 +327,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -335,7 +340,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th 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 @@ -345,13 +349,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BatchName parameter specifies a descriptive name for importing a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxImportRequest cmdlet. ```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 @@ -361,13 +367,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value of the CompletedRequestAgeLimit parameter is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -377,6 +385,9 @@ 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`. @@ -386,7 +397,6 @@ 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 @@ -396,6 +406,9 @@ Accept wildcard characters: False ``` ### -ConflictResolutionOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: - ForceCopy (Exchange 2016 or later) @@ -409,7 +422,6 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl Type: ConflictResolutionOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -419,13 +431,15 @@ Accept wildcard characters: False ``` ### -ContentCodePage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ContentCodePage parameter specifies the specific code page to use for an ANSI pst file. ANSI pst files are used in Outlook 97 to Outlook 2002. You can find the valid values in the [Code Page Identifiers](https://learn.microsoft.com/windows/win32/intl/code-page-identifiers) topic. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -435,6 +449,9 @@ 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. @@ -443,7 +460,6 @@ 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 @@ -453,6 +469,9 @@ Accept wildcard characters: False ``` ### -ExcludeDumpster + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch. If you don't use this switch, the Recoverable Items folder is copied with the following subfolders: @@ -465,7 +484,6 @@ If you don't use this switch, the Recoverable Items folder is copied with the fo 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 @@ -475,6 +493,9 @@ Accept wildcard characters: False ``` ### -ExcludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeFolders parameter specifies the list of folders to exclude during the import. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -511,7 +532,6 @@ If the TargetRootFolder parameter isn't specified when the Recoverable Items fol 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 @@ -521,6 +541,9 @@ Accept wildcard characters: False ``` ### -IncludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeFolders parameter specifies the list of folders to include during the import. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -555,7 +578,6 @@ Wildcard characters can't be used in folder names. 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 @@ -565,6 +587,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -573,7 +598,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -583,13 +607,15 @@ Accept wildcard characters: False ``` ### -IsArchive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsArchive switch specifies that you're importing the .pst file into the user's archive. 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 @@ -599,6 +625,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -614,7 +643,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -624,6 +652,9 @@ Accept wildcard characters: False ``` ### -MigrationBatch + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use @@ -632,7 +663,6 @@ This parameter is reserved for internal Microsoft use Type: MigrationBatchIdParameter Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -642,13 +672,15 @@ Accept wildcard characters: False ``` ### -MigrationMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: MailboxIdParameter, AzureImportRequest Parameter Sets: MailboxLocationId Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -658,6 +690,9 @@ Accept wildcard characters: False ``` ### -MigrationUser + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -666,7 +701,6 @@ This parameter is reserved for internal Microsoft use. Type: MigrationUserIdParameter Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -676,6 +710,9 @@ Accept wildcard characters: False ``` ### -MRSContentFilterSasUri + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -684,7 +721,6 @@ This parameter is reserved for internal Microsoft use. Type: Uri Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -694,6 +730,9 @@ Accept wildcard characters: False ``` ### -MRSServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSServer parameter specifies the FQDN of the Client Access server on which the instance of the Microsoft Exchange Mailbox Replication service (MRS) is running. This parameter is used for debugging purposes only. Use this parameter only if directed by support personnel. @@ -702,7 +741,6 @@ The MRSServer parameter specifies the FQDN of the Client Access server on which Type: Fqdn Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -712,6 +750,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple import requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an import request for a user's mailbox that has the alias Kweku and specify the value of this parameter as PC1toArchive, the identity of this import request is Kweku\\PC1toArchive. If you don't specify a name using this parameter, Exchange generates up to 10 request names per mailbox, which is MailboxImportX (where X = 0-9). The identity of the request is displayed and searchable as `\MailboxImportX`. @@ -720,7 +761,6 @@ If you don't specify a name using this parameter, Exchange generates up to 10 re 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 @@ -730,6 +770,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Priority parameter specifies the order in which this request should be processed in the request queue. Requests are processed in order, based on server health, status, priority and last update time. @@ -738,7 +781,6 @@ The Priority parameter specifies the order in which this request should be proce Type: RequestPriority Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -748,6 +790,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -761,7 +806,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: MailboxLocationId, AzureImportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -771,6 +815,9 @@ Accept wildcard characters: False ``` ### -SkipInitialConnectionValidation + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -779,7 +826,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -789,13 +835,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies steps in the import that should be skipped. This parameter is used primarily for debugging purposes. ```yaml Type: SkippableMergeComponent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -805,13 +853,15 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: MigrationEndpointIdParameter Parameter Sets: MailboxLocationId, AzureImportRequest Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -821,13 +871,15 @@ Accept wildcard characters: False ``` ### -SourceRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceRootFolder parameter specifies the root folder of the .pst file from which data is imported. When specified, the folder hierarchy outside the value of the SourceRootFolder parameter isn't imported, and the SourceRootFolder parameter is mapped to the TargetRootFolder parameter. If this parameter isn't specified, the command imports all folders. ```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 @@ -837,6 +889,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -845,7 +900,6 @@ If you use this switch, the request is queued, but the request won't reach the s 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 @@ -855,13 +909,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```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 @@ -871,13 +927,15 @@ Accept wildcard characters: False ``` ### -TargetRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetRootFolder parameter specifies the top-level mailbox folder that the imported content is placed in. If you don't specify this parameter, the command imports folders to the top of the folder structure in the target mailbox or archive. If the folder already exists, content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. ```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 @@ -887,13 +945,15 @@ 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 @@ -903,6 +963,9 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> 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. @@ -911,7 +974,6 @@ This parameter is reserved for internal Microsoft use. Type: RequestWorkloadType Parameter Sets: Mailbox, MailboxLocationId Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/New-MailboxRepairRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md index b5e267cdc2..acc86d8245 100644 --- a/exchange/exchange-ps/exchange/New-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxrepairrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-MailboxRepairRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxrepairrequest +schema: 2.0.0 +title: New-MailboxRepairRequest --- # New-MailboxRepairRequest @@ -94,6 +95,9 @@ This example creates a variable that identifies Ann Beebe's mailbox and then use ## PARAMETERS ### -Database + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Database parameter repairs or detects corruption in all mailboxes in the specified database. You can use any value that uniquely identifies the database. For example: - Name @@ -108,7 +112,6 @@ To avoid performance issues, you're limited to one active database repair reques Type: DatabaseIdParameter Parameter Sets: Database Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -118,6 +121,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Mailbox parameter specifies the mailbox that you want to repair or detect corruption in. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -137,7 +143,6 @@ You can't use this parameter with the Database parameter. Type: MailboxIdParameter Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -147,6 +152,9 @@ 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 you want to repair or detect corruption in. Use this parameter with the Database parameter. Run the Get-MailboxStatistics cmdlet to find the mailbox GUID for a mailbox. @@ -155,7 +163,6 @@ Run 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 @@ -165,6 +172,9 @@ Accept wildcard characters: False ``` ### -CorruptionType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CorruptionType parameter specifies the type of corruption that you want to detect and repair. You can use the following values: - AbandonedMoveDestination\*: Exchange 2016 or later, but only with the Database parameter, not the Mailbox parameter. @@ -215,7 +225,6 @@ You can specify multiple values separated by commas. Type: MailboxStoreCorruptionType[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -225,6 +234,9 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Archive switch specifies whether to repair or detect corruption the archive mailbox that's associated with the specified mailbox. You don't need to specify a value with this switch. If you don't use this switch, only the primary mailbox is included. @@ -235,7 +247,6 @@ You can't use this switch with the Database parameter. Type: SwitchParameter Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -245,6 +256,9 @@ 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`. @@ -254,7 +268,6 @@ 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 @@ -264,13 +277,15 @@ Accept wildcard characters: False ``` ### -DetectOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DetectOnly switch specifies that you want to report errors, but not fix them. 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 @@ -280,13 +295,15 @@ 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 @@ -296,6 +313,9 @@ 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. This switch runs the command immediately without waiting to be dispatched by workload management. @@ -304,7 +324,6 @@ This switch runs the command immediately without waiting to be dispatched by wor Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -314,13 +333,15 @@ 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/exchange/New-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md index 43a1b13892..9823bf33cc 100644 --- a/exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxrestorerequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MailboxRestoreRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxrestorerequest +schema: 2.0.0 +title: New-MailboxRestoreRequest --- # New-MailboxRestoreRequest @@ -263,6 +264,9 @@ In Exchange Online, this example restores the content of the inactive, disconnec ## PARAMETERS ### -CrossTenantRestore + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -271,7 +275,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: CrossTenantRestore Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -281,6 +284,9 @@ Accept wildcard characters: False ``` ### -RemoteCredential + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -289,7 +295,6 @@ This parameter is reserved for internal Microsoft use. Type: PSCredential Parameter Sets: SourceMailbox Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -299,6 +304,9 @@ Accept wildcard characters: False ``` ### -RemoteDatabaseGuid + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -307,7 +315,6 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: SourceMailbox Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -317,6 +324,9 @@ Accept wildcard characters: False ``` ### -RemoteHostName + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -325,7 +335,6 @@ This parameter is reserved for internal Microsoft use. Type: Fqdn Parameter Sets: SourceMailbox Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -335,6 +344,9 @@ Accept wildcard characters: False ``` ### -RemoteRestoreType + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -343,7 +355,6 @@ This parameter is reserved for internal Microsoft use. Type: RemoteRestoreType Parameter Sets: SourceMailbox Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -353,6 +364,9 @@ 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 the identity of the database from which you're restoring the soft-deleted or disconnected mailbox. You can use any value that uniquely identifies the database. For example: @@ -365,7 +379,6 @@ The SourceDatabase parameter specifies the identity of the database from which y Type: DatabaseIdParameter Parameter Sets: Default, MigrationLocalMailboxRestore Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -375,6 +388,9 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -383,7 +399,6 @@ This parameter is reserved for internal Microsoft use. Type: MigrationEndpointIdParameter Parameter Sets: CrossTenantRestore Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -393,6 +408,9 @@ Accept wildcard characters: False ``` ### -SourceExchangeGuid + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -401,7 +419,6 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: CrossTenantRestore Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -411,13 +428,15 @@ Accept wildcard characters: False ``` ### -SourceMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceMailbox parameter specifies the soft-deleted mailbox that you want to restore. The best way to identify the soft-deleted mailbox is by its GUID value. You can find the GUID value by running the following command: Get-Mailbox -SoftDeletedMailbox. ```yaml Type: SourceMailbox Parameter Sets: SourceMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -427,6 +446,9 @@ Accept wildcard characters: False ``` ### -SourceStoreMailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The SourceStoreMailbox parameter specifies the MailboxGUID of the source mailbox that you want to restore content from. @@ -437,7 +459,6 @@ You can find the MailboxGUID by running the Get-MailboxStatistics cmdlet. Type: StoreMailboxIdParameter Parameter Sets: Default, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -447,6 +468,9 @@ Accept wildcard characters: False ``` ### -SourceTenant + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -455,7 +479,6 @@ This parameter is reserved for internal Microsoft use. Type: SmtpDomain Parameter Sets: CrossTenantRestore Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -465,6 +488,9 @@ Accept wildcard characters: False ``` ### -TargetMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetMailbox parameter specifies the GUID of the target mailbox or mail user where you want to restore content to. The target mailbox or mail user needs to exist before you can run this command successfully. You can find the GUID value for the mailbox or mail user by running the Get-Mailbox or Get-MailUser cmdlets. @@ -475,9 +501,8 @@ In Exchange 2013 or earlier, this parameter is the type MailboxOrMailUserIdParam ```yaml Type: MailboxLocationIdParameter -Parameter Sets: CrossTenantRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox +Parameter Sets: Default, RemoteMailboxRestoreMailboxId, CrossTenantRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -486,20 +511,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxOrMailUserIdParameter -Parameter Sets: Default, RemoteMailboxRestoreMailboxId -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 +### -AcceptLargeDataLoss -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -AcceptLargeDataLoss The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later or Exchange Online, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -510,7 +525,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -520,6 +534,9 @@ Accept wildcard characters: False ``` ### -AllowLegacyDNMismatch + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowLegacyDNMismatch switch specifies that the operation should continue if the LegacyExchangeDN of the source physical mailbox and the target mailbox don't match. You don't need to specify a value with this switch. By default, this cmdlet checks to make sure that the LegacyExchangeDN on the source physical mailbox is present on the target user in the form of the LegacyExchangeDN or an X500 proxy address that corresponds to the LegacyExchangeDN. This check prevents you from accidentally restoring a source mailbox into the incorrect target mailbox. @@ -530,7 +547,6 @@ By default, this cmdlet checks to make sure that the LegacyExchangeDN on the sou 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 @@ -540,6 +556,9 @@ Accept wildcard characters: False ``` ### -AssociatedMessagesCopyOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. Valid values are: - DoNotCopy: The associated messages aren't copied. @@ -552,7 +571,6 @@ Content filtering doesn't apply to associated messages. Type: FAICopyOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -562,6 +580,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -574,7 +595,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th 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 @@ -584,13 +604,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BatchName parameter specifies a descriptive name for restoring a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxRestoreRequest cmdlet. ```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 @@ -600,13 +622,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the status of a completed restore request is set to Completed. If this parameter is set to a value of 0, the status is cleared immediately instead of being changed to Completed. ```yaml Type: Unlimited Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -616,6 +640,9 @@ 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`. @@ -625,7 +652,6 @@ 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 @@ -635,6 +661,9 @@ Accept wildcard characters: False ``` ### -ConflictResolutionOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are: - ForceCopy @@ -648,7 +677,6 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl Type: ConflictResolutionOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -658,6 +686,9 @@ Accept wildcard characters: False ``` ### -ContentFilter + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`. @@ -675,7 +706,6 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH Type: String Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -685,6 +715,9 @@ Accept wildcard characters: False ``` ### -ContentFilterLanguage + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ContentFilterLanguage parameter specifies the language being used in the ContentFilter parameter for string searches. @@ -695,7 +728,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -705,6 +737,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2010, 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. @@ -713,7 +748,6 @@ 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, Exchange Online Required: False Position: Named @@ -723,6 +757,9 @@ Accept wildcard characters: False ``` ### -ExcludeDumpster + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch. If you don't use this switch, the Recoverable Items folder is copied with the following subfolders: @@ -735,7 +772,6 @@ If you don't use this switch, the Recoverable Items folder is copied with the fo 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 @@ -745,6 +781,9 @@ Accept wildcard characters: False ``` ### -ExcludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeFolders parameter specifies the list of folders to exclude during the restore request. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -779,7 +818,6 @@ Wildcard characters can't be used in folder names. 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 @@ -789,6 +827,9 @@ Accept wildcard characters: False ``` ### -IncludeFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeFolders parameter specifies the list of folder to include during the restore request. Folder names aren't case-sensitive, and there are no character restrictions. Use the following syntax: @@ -823,7 +864,6 @@ Wildcard characters can't be used in folder names. 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 @@ -833,6 +873,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -841,7 +884,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -851,6 +893,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -868,7 +913,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -878,6 +922,9 @@ Accept wildcard characters: False ``` ### -MRSServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSServer parameter specifies the FQDN of the Client Access server on which the instance of the Microsoft Exchange Mailbox Replication service (MRS) is running. This parameter is used for debugging purposes only. Use this parameter only if directed by support personnel. @@ -886,7 +933,6 @@ The MRSServer parameter specifies the FQDN of the Client Access server on which Type: Fqdn Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -896,6 +942,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple restore requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an export request for a user's mailbox that has the alias Kweku and specify the value of this parameter as RestoreFailedMoves, the identity of this export request is Kweku\\RestoreFailedMoves. If you didn't specify a name for the restore request when it was created, Exchange automatically generates the default name MailboxRestore. Exchange generates up to 10 names, starting with MailboxRestore and then MailboxRestoreX (where X = 1-9). @@ -904,7 +953,6 @@ If you didn't specify a name for the restore request when it was created, Exchan 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 @@ -914,6 +962,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: @@ -931,7 +982,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: Default, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -941,6 +991,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: @@ -956,7 +1009,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -966,6 +1018,9 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values: - FolderACLs @@ -979,7 +1034,6 @@ Use this parameter only if a restore request fails because of folder rules, fold Type: SkippableMergeComponent[] Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -989,6 +1043,9 @@ Accept wildcard characters: False ``` ### -SourceIsArchive + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceIsArchive switch specifies that the source mailbox is an archive mailbox. You don't need to specify a value with this switch. You can use this switch only with the SourceMailbox parameter. @@ -997,7 +1054,6 @@ You can use this switch only with the SourceMailbox parameter. Type: SwitchParameter Parameter Sets: SourceMailboxMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1007,13 +1063,15 @@ Accept wildcard characters: False ``` ### -SourceRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceRootFolder parameter specifies the root folder of the mailbox from which data is restored. If this parameter isn't specified, the command restores all folders. ```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 @@ -1023,6 +1081,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -1031,7 +1092,6 @@ If you use this switch, the request is queued, but the request won't reach the s 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 @@ -1041,13 +1101,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```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 @@ -1057,13 +1119,15 @@ Accept wildcard characters: False ``` ### -TargetIsArchive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetIsArchive switch specifies that the content is restored into the specified target mailbox's archive. 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 @@ -1073,6 +1137,9 @@ Accept wildcard characters: False ``` ### -TargetRootFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetRootFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. **Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users. @@ -1081,7 +1148,6 @@ The TargetRootFolder parameter specifies the top-level folder in which to restor 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 @@ -1091,6 +1157,9 @@ Accept wildcard characters: False ``` ### -TargetType + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetType parameter specifies the type of mailbox that's the target for the restore operation. Valid values are: - Archive @@ -1101,7 +1170,6 @@ The TargetType parameter specifies the type of mailbox that's the target for the Type: TargetTypeComponent Parameter Sets: CrossTenantRestore, MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, SourceMailbox Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1111,13 +1179,15 @@ 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 @@ -1127,6 +1197,9 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> 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. @@ -1135,7 +1208,6 @@ This parameter is reserved for internal Microsoft use. Type: RequestWorkloadType Parameter Sets: MigrationLocalMailboxRestore, RemoteMailboxRestoreMailboxLocationId, RemoteMailboxRestoreMailboxId, SourceMailbox Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md similarity index 88% rename from exchange/exchange-ps/exchange/New-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md index 8c7db70175..6a660c5e4c 100644 --- a/exchange/exchange-ps/exchange/New-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MailboxSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mailboxsearch +schema: 2.0.0 +title: New-MailboxSearch --- # New-MailboxSearch @@ -103,6 +104,9 @@ In on-premises Exchange, this example creates an In-Place Hold named Hold for al ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a friendly name for the search. If the value contains spaces, enclose the value in quotation marks ("). The value of this parameter is used to create the top-level folder that holds the search results in the target mailbox that's specified by the TargetMailbox parameter. @@ -111,7 +115,6 @@ The value of this parameter is used to create the top-level folder that holds th 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 @@ -121,6 +124,9 @@ Accept wildcard characters: False ``` ### -AllPublicFolderSources + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). @@ -130,7 +136,6 @@ The AllPublicFolderSources parameter specifies whether to include all public fol Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -140,6 +145,9 @@ Accept wildcard characters: False ``` ### -AllSourceMailboxes + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). @@ -149,7 +157,6 @@ The AllSourceMailboxes parameter specifies whether to include all mailboxes in t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -159,6 +166,9 @@ 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`. @@ -168,7 +178,6 @@ 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 @@ -178,13 +187,15 @@ 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 search. The description isn't displayed to users. 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, Exchange Online Required: False Position: Named @@ -194,6 +205,9 @@ 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. @@ -202,7 +216,6 @@ 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 @@ -212,6 +225,9 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The DoNotIncludeArchive switch specifies that archive mailboxes are not included in the search. You don't need to specify a value with this switch. @@ -222,7 +238,6 @@ By default, archive mailboxes are included in the search. To exclude archive mai Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -232,6 +247,9 @@ Accept wildcard characters: False ``` ### -EndDate + +> Applicable: Exchange Server 2010, 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". @@ -240,7 +258,6 @@ 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 Required: False Position: Named @@ -250,6 +267,9 @@ Accept wildcard characters: False ``` ### -EstimateOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EstimateOnly switch specifies that only an estimate of the number of items that will be returned is provided. You don't need to specify a value with this switch. If you don't use this switch, messages are copied to the target mailbox. @@ -258,7 +278,6 @@ If you don't use this switch, messages are copied to the target mailbox. 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 @@ -268,6 +287,9 @@ Accept wildcard characters: False ``` ### -ExcludeDuplicateMessages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeDuplicateMessages parameter eliminates duplication of messages in search results. Valid values are: - $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. @@ -277,7 +299,6 @@ The ExcludeDuplicateMessages parameter eliminates duplication of messages in sea 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 @@ -287,6 +308,9 @@ 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. @@ -295,7 +319,6 @@ 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 Required: False Position: Named @@ -305,13 +328,15 @@ Accept wildcard characters: False ``` ### -IncludeKeywordStatistics + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeKeywordStatistics switch returns keyword statistics (number of instances for each keyword) in search 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 @@ -321,6 +346,9 @@ Accept wildcard characters: False ``` ### -IncludeUnsearchableItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeUnsearchableItems switch specifies that items that couldn't be indexed by Exchange Search should be included in the results. You don't need to specify a value with this switch. Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you need to place unsearchable items on hold, you need to create an indefinite hold (a hold without specifying any search parameters, which provides functionality similar to Litigation Hold. @@ -329,7 +357,6 @@ Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you 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 @@ -339,6 +366,9 @@ Accept wildcard characters: False ``` ### -InPlaceHoldEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. @@ -352,7 +382,6 @@ If you attempt to place a hold but don't specify mailboxes using the SourceMailb 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 @@ -362,13 +391,15 @@ Accept wildcard characters: False ``` ### -InPlaceHoldIdentity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 Required: False Position: Named @@ -378,6 +409,9 @@ Accept wildcard characters: False ``` ### -ItemHoldPeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all mailbox items or the items that are returned in the search query results). The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. @@ -387,7 +421,6 @@ The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold 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 @@ -397,6 +430,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Language parameter specifies a locale for the 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). @@ -405,7 +441,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -415,6 +450,9 @@ Accept wildcard characters: False ``` ### -LogLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LogLevel parameter specifies the logging level for the search. Valid values are: - Suppress: No logs are kept. @@ -425,7 +463,6 @@ The LogLevel parameter specifies the logging level for the search. Valid values Type: LoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -435,6 +472,9 @@ Accept wildcard characters: False ``` ### -MessageTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MessageTypes parameter specifies the message types to include in the search query. Valid values are: - Contacts @@ -454,7 +494,6 @@ The default value is blank ($null), which means all message types are included. Type: KindKeyword[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -464,6 +503,9 @@ Accept wildcard characters: False ``` ### -Recipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recipients parameter specifies one or more recipients to include in the search query. Messages that have the specified recipients in the To, Cc, and Bcc fields are returned in the search results. You can specify multiple recipients separated by commas. @@ -472,7 +514,6 @@ You can specify multiple recipients separated by commas. 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 @@ -482,6 +523,9 @@ Accept wildcard characters: False ``` ### -SearchDumpster + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The SearchDumpster switch specifies whether the dumpster is searched. You don't need to specify a value with this switch. @@ -492,7 +536,6 @@ The dumpster is a storage area in the mailbox where deleted items are temporaril Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -502,6 +545,9 @@ Accept wildcard characters: False ``` ### -SearchQuery + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SearchQuery parameter specifies keywords for the search query 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). If you use this parameter with other search query parameters, the query combines these parameters by using the AND operator. @@ -518,7 +564,6 @@ The other search query parameters are: 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 @@ -528,6 +573,9 @@ Accept wildcard characters: False ``` ### -Senders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Senders parameter specifies one or more senders to include in the search query. Messages that have the specified sender are returned in the search results. Senders can include users, distribution groups (messages sent by members of the group), SMTP addresses, or domains. You can specify multiple senders separated by commas. If the value contains spaces, enclose the value in quotation marks ("). @@ -536,7 +584,6 @@ You can specify multiple senders separated by commas. If the value contains spac 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 @@ -546,6 +593,9 @@ Accept wildcard characters: False ``` ### -SourceMailboxes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceMailboxes parameter specifies the identity of one or more mailboxes to be searched. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -570,7 +620,6 @@ To enable In-Place Hold on the search results, you need to set the AllSourceMail Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -580,6 +629,9 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Server 2010, 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". @@ -588,7 +640,6 @@ 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 Required: False Position: Named @@ -598,6 +649,9 @@ Accept wildcard characters: False ``` ### -StatusMailRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StatusMailRecipients parameter specifies one or more recipients to receive a status email message upon completion of the search. You can use any value that uniquely identifies the recipient. For example: - Name @@ -613,7 +667,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -623,6 +676,9 @@ 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 destination mailbox where the search results are copied. You can use any value that uniquely identifies themailbox. For example: - Name @@ -640,7 +696,6 @@ The TargetMailbox parameter specifies the destination mailbox where the search r 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 @@ -650,13 +705,15 @@ 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 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, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md index 0dd0822a20..b7328fd705 100644 --- a/exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-malwarefilterpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MalwareFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-malwarefilterpolicy +schema: 2.0.0 +title: New-MalwareFilterPolicy --- # New-MalwareFilterPolicy @@ -72,13 +73,15 @@ This example creates a new malware filter policy named Contoso Malware Filter Po ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Name parameter specifies the unique name of the malware filter policy. 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, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -88,6 +91,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: @@ -100,7 +106,6 @@ The Action parameter specifies the action to take when malware is detected in a Type: MalwareFilteringAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -110,13 +115,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -126,6 +133,9 @@ Accept wildcard characters: False ``` ### -BypassInboundMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: @@ -137,7 +147,6 @@ The BypassInboundMessages parameter enables or disables malware filtering on inc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,6 +156,9 @@ Accept wildcard characters: False ``` ### -BypassOutboundMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: @@ -158,7 +170,6 @@ The BypassOutboundMessages parameter enables or disables malware filtering on ou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -168,6 +179,9 @@ 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`. @@ -177,7 +191,6 @@ 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 @@ -187,6 +200,9 @@ Accept wildcard characters: False ``` ### -CustomAlertText + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CustomAlertText parameter specifies the custom text to use in the replacement attachment named Malware Alert Text.txt. If the value contains spaces, enclose the value in quotation marks ("). @@ -197,7 +213,6 @@ This parameter is meaningful only when the value of the Action parameter is Dele Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -207,6 +222,9 @@ Accept wildcard characters: False ``` ### -CustomExternalBody + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -218,7 +236,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -228,6 +245,9 @@ Accept wildcard characters: False ``` ### -CustomExternalSubject + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomExternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -239,7 +259,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -249,6 +268,9 @@ Accept wildcard characters: False ``` ### -CustomFromAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomFromAddress parameter specifies the custom From address to use in notification messages for malware detections in messages from internal or external senders. This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -262,7 +284,6 @@ This parameter is meaningful only when the value of the CustomNotifications para Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -272,6 +293,9 @@ Accept wildcard characters: False ``` ### -CustomFromName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomFromName parameter specifies the custom From name to use in notification messages for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -285,7 +309,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -295,6 +318,9 @@ Accept wildcard characters: False ``` ### -CustomInternalBody + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomInternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -306,7 +332,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -316,6 +341,9 @@ Accept wildcard characters: False ``` ### -CustomInternalSubject + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomInternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -327,7 +355,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -337,6 +364,9 @@ Accept wildcard characters: False ``` ### -CustomNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomNotifications parameter enables or disables the customization of notification messages for malware detections. Valid values are: - $true: Replace the default values used in notification messages with the values of the CustomFromAddress, CustomFromName, CustomExternalSubject, CustomExternalBody, CustomInternalSubject and CustomInternalBody parameters. @@ -353,7 +383,6 @@ This parameter is meaningful only when the value of at least one of the followin 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 @@ -363,6 +392,9 @@ 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. @@ -371,7 +403,6 @@ 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 @@ -381,6 +412,9 @@ Accept wildcard characters: False ``` ### -EnableExternalSenderAdminNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. @@ -392,7 +426,6 @@ The EnableExternalSenderAdminNotifications parameter enables or disables sending 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 @@ -402,6 +435,9 @@ Accept wildcard characters: False ``` ### -EnableExternalSenderNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: @@ -413,7 +449,6 @@ The EnableExternalSenderNotifications parameter enables or disables sending noti Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -423,6 +458,9 @@ Accept wildcard characters: False ``` ### -EnableFileFilter + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: @@ -438,7 +476,6 @@ You specify the action for detected files using the FileTypeAction parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -448,6 +485,9 @@ Accept wildcard characters: False ``` ### -EnableInternalSenderAdminNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. @@ -459,7 +499,6 @@ The EnableInternalSenderAdminNotifications parameter enables or disables sending 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 @@ -469,6 +508,9 @@ Accept wildcard characters: False ``` ### -EnableInternalSenderNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: @@ -480,7 +522,6 @@ The EnableInternalSenderNotifications parameter enables or disables sending noti Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -490,6 +531,9 @@ Accept wildcard characters: False ``` ### -ExternalSenderAdminAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ExternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from external senders. This parameter is meaningful only if the value of the EnableExternalSenderAdminNotifications parameter is $true. @@ -498,7 +542,6 @@ This parameter is meaningful only if the value of the EnableExternalSenderAdminN Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -508,6 +551,9 @@ Accept wildcard characters: False ``` ### -FileTypeAction + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: @@ -521,7 +567,6 @@ This parameter is meaningful only when the value of the EnableFileFilter paramet Type: FileTypeFilteringAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -531,6 +576,9 @@ Accept wildcard characters: False ``` ### -FileTypes + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The FileTypes parameter specifies the file types that are automatically blocked by the common attachments filter, regardless of content. The default values are: @@ -549,7 +597,6 @@ To add or remove file types without affecting the other file type entries, see t Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -559,6 +606,9 @@ Accept wildcard characters: False ``` ### -InternalSenderAdminAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The InternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from internal senders. This parameter is meaningful only if the value of the EnableInternalSenderAdminNotifications parameter is $true. @@ -567,7 +617,6 @@ This parameter is meaningful only if the value of the EnableInternalSenderAdminN Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -577,6 +626,9 @@ Accept wildcard characters: False ``` ### -QuarantineTag + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The QuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as malware. You can use any value that uniquely identifies the quarantine policy. For example: @@ -595,7 +647,6 @@ 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 @@ -605,6 +656,9 @@ Accept wildcard characters: False ``` ### -RecommendedPolicyType + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. 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. @@ -613,7 +667,6 @@ The RecommendedPolicyType parameter is used for Standard and Strict policy creat Type: RecommendedPolicyType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -623,13 +676,15 @@ 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 @@ -639,6 +694,9 @@ Accept wildcard characters: False ``` ### -ZapEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: @@ -650,7 +708,6 @@ The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md similarity index 86% rename from exchange/exchange-ps/exchange/New-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md index ad4f6ad019..dd22c9e1c9 100644 --- a/exchange/exchange-ps/exchange/New-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-malwarefilterrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MalwareFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-malwarefilterrule +schema: 2.0.0 +title: New-MalwareFilterRule --- # New-MalwareFilterRule @@ -55,13 +56,15 @@ This example creates a new malware filter rule named Contoso Recipients with the ## 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 malware filter 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 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -MalwareFilterPolicy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule. You can use any value that uniquely identifies the policy. For example: @@ -85,7 +91,6 @@ You can't specify the default malware filter policy, and you can't specify a pol Type: MalwareFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -95,13 +100,15 @@ Accept wildcard characters: False ``` ### -Comments + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -111,6 +118,9 @@ 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`. @@ -120,7 +130,6 @@ 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 @@ -130,6 +139,9 @@ 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,7 +150,6 @@ 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 @@ -148,13 +159,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Enabled parameter enables or disables the malware filter rule. Valid input for this parameter is $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 @@ -164,13 +177,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -180,6 +195,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -195,7 +213,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -205,6 +222,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -222,7 +242,6 @@ If you remove the group after you create the rule, no exception is made for mess Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -232,6 +251,9 @@ 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: @@ -246,7 +268,6 @@ 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 @@ -256,13 +277,15 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -272,6 +295,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -287,7 +313,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -297,6 +322,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -314,7 +342,6 @@ If you remove the group after you create the rule, no action is taken on message Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -324,13 +351,15 @@ 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/exchange/New-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md similarity index 95% rename from exchange/exchange-ps/exchange/New-ManagedContentSettings.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md index 1d10f3fbcb..b14693d7c6 100644 --- a/exchange/exchange-ps/exchange/New-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managedcontentsettings applicable: Exchange Server 2010 -title: New-ManagedContentSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managedcontentsettings +schema: 2.0.0 +title: New-ManagedContentSettings --- # New-ManagedContentSettings @@ -66,13 +67,15 @@ This example creates managed content settings CS-Exec-Calendar for the Calendar ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies a unique name for the managed content settings. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -82,13 +85,15 @@ 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. ```yaml Type: ELCFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -98,6 +103,9 @@ Accept wildcard characters: False ``` ### -MessageClass + +> Applicable: Exchange Server 2010 + The MessageClass parameter specifies the message type to which any expiration and journaling configuration settings within these content settings apply. The parameter value can be a well-known message type such as Calendar items, a specific message class such as IPM.NOTE.SMIME, or a custom message class. The following well-known message types can be used: @@ -130,7 +138,6 @@ Valid parameter values for custom message classes include: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -140,6 +147,9 @@ Accept wildcard characters: False ``` ### -AddressForJournaling + +> Applicable: Exchange Server 2010 + The AddressForJournaling parameter specifies the journaling recipient where journaled messages are sent. You can use any value that uniquely identifies the recipient. For example: - Name @@ -155,7 +165,6 @@ This parameter is required if the JournalingEnabled parameter is set to $true. Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -165,13 +174,15 @@ Accept wildcard characters: False ``` ### -AgeLimitForRetention + +> Applicable: Exchange Server 2010 + The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date the item was delivered, or the date an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -181,6 +192,9 @@ 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`. @@ -190,7 +204,6 @@ 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 @@ -200,13 +213,15 @@ 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 @@ -216,13 +231,15 @@ Accept wildcard characters: False ``` ### -JournalingEnabled + +> Applicable: Exchange Server 2010 + The JournalingEnabled parameter specifies that journaling is enabled when set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -232,13 +249,15 @@ Accept wildcard characters: False ``` ### -LabelForJournaling + +> Applicable: Exchange Server 2010 + The LabelForJournaling parameter specifies a label that's attached to an item. This label is used by the destination store to determine the content of the item and enforce the appropriate policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -248,6 +267,9 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling + +> Applicable: Exchange Server 2010 + The MessageFormatForJournaling parameter specifies the message format that an item should be journaled in. You can use the following values: - UseMsg Outlook .msg format @@ -257,7 +279,6 @@ The MessageFormatForJournaling parameter specifies the message format that an it Type: JournalingFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -267,6 +288,9 @@ Accept wildcard characters: False ``` ### -MoveToDestinationFolder + +> Applicable: Exchange Server 2010 + The MoveToDestinationFolder parameter specifies the destination folder for a move action. The destination folder must be an existing managed custom folder. If it isn't, an error is returned. If the MoveToDestinationFolder parameter isn't present, and the value of the RetentionAction parameter is MoveToFolder, an error is returned. @@ -275,7 +299,6 @@ The destination folder must be an existing managed custom folder. If it isn't, a Type: ELCFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -285,6 +308,9 @@ Accept wildcard characters: False ``` ### -RetentionAction + +> Applicable: Exchange Server 2010 + The RetentionAction parameter specifies one of the following actions: - Mark as past retention limit @@ -299,7 +325,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -309,13 +334,15 @@ Accept wildcard characters: False ``` ### -RetentionEnabled + +> Applicable: Exchange Server 2010 + The RetentionEnabled parameter specifies that retention is enabled when set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -325,6 +352,9 @@ Accept wildcard characters: False ``` ### -TriggerForRetention + +> Applicable: Exchange Server 2010 + The TriggerForRetention parameter specifies the date that's considered as the start date for the retention period. An item can reach its retention limit a specific number of days after the item was delivered or after it was moved to a folder. Valid values include: @@ -340,7 +370,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionDateType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -350,13 +379,15 @@ 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/exchange/New-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ManagedFolder.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md index da5d39bc23..a61cb50733 100644 --- a/exchange/exchange-ps/exchange/New-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managedfolder applicable: Exchange Server 2010 -title: New-ManagedFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managedfolder +schema: 2.0.0 +title: New-ManagedFolder --- # New-ManagedFolder @@ -89,6 +90,9 @@ This example creates an instance of the default folder Inbox. ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies a unique name for the managed folder object in Active Directory. The name can have up to 65 characters. Whereas the FolderName parameter specifies the folder name as displayed to users in clients, the Name parameter is used by Exchange administration tools to represent the managed folder object. The Name parameter shouldn't be confused with the FolderName parameter. @@ -97,7 +101,6 @@ The Name parameter shouldn't be confused with the FolderName parameter. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -107,6 +110,9 @@ Accept wildcard characters: False ``` ### -DefaultFolderType + +> Applicable: Exchange Server 2010 + The DefaultFolderType parameter specifies the type of default folder to create, such as Inbox or Deleted Items. A managed folder mailbox policy can have only one managed folder of each default folder type. Additional default folders of a particular type, such as Inbox, can be created and added to different mailbox policies. This allows you to assign different managed content settings for a particular default folder type for different sets of users. @@ -138,7 +144,6 @@ The default folder types that you can specify are: Type: DefaultManagedFolderType Parameter Sets: ManagedDefaultFolder Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -148,6 +153,9 @@ Accept wildcard characters: False ``` ### -FolderName + +> Applicable: Exchange Server 2010 + The FolderName parameter specifies the folder name as it appears in users' mailboxes. The folder name can have up to 255 characters. You can't set the FolderName parameter for managed default folders, such as Inbox. The FolderName parameter shouldn't be confused with the Name parameter. @@ -156,7 +164,6 @@ The FolderName parameter shouldn't be confused with the Name parameter. Type: String Parameter Sets: ManagedCustomFolder Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -166,13 +173,15 @@ Accept wildcard characters: False ``` ### -BaseFolderOnly + +> Applicable: Exchange Server 2010 + The BaseFolderOnly parameter specifies whether the managed content settings should be applied only to the managed folder or to the folder and all its subfolders. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -182,13 +191,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010 + The Comment parameter specifies the default administrator comment to be displayed with the folder in Microsoft Office Outlook 2007 and Microsoft Office Outlook Web App. The comment can have up to 255 characters, including spaces. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -198,6 +209,9 @@ 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`. @@ -207,7 +221,6 @@ 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 @@ -217,13 +230,15 @@ 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 @@ -233,13 +248,15 @@ Accept wildcard characters: False ``` ### -LocalizedComment + +> Applicable: Exchange Server 2010 + The LocalizedComment parameter specifies localized administrator comments and their languages. When the language setting of Outlook 2007 matches one of the locales specified in this parameter, the corresponding localized comment is displayed. Comments must be in the form ISOLanguageCode:Comment (for example, -LocalizedComment EN-US:"This is a localized comment in U.S. English"). ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -249,13 +266,15 @@ Accept wildcard characters: False ``` ### -LocalizedFolderName + +> Applicable: Exchange Server 2010 + The LocalizedFolderName parameter specifies the localized folder names and their languages. When the language setting of Outlook 2007 matches one of the locales specified in this parameter, the corresponding localized folder name is displayed. Folder names must be in the form ISOLanguageCode:FolderName (for example, -LocalizedFolderName EN-US:"Business Critical"). ```yaml Type: MultiValuedProperty Parameter Sets: ManagedCustomFolder Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -265,13 +284,15 @@ Accept wildcard characters: False ``` ### -MustDisplayCommentEnabled + +> Applicable: Exchange Server 2010 + The MustDisplayCommentEnabled parameter specifies whether to set a flag used by Outlook 2007 to prevent users from minimizing a folder comment (that's visible in Outlook 2007 and Outlook Web App). If the MustDisplayCommentEnabled parameter is present and set to $true, the parameter sets a flag used by Outlook 2007 to prevent users from minimizing a folder comment. If the parameter isn't present or is set to $false, users can minimize the comment. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -281,13 +302,15 @@ Accept wildcard characters: False ``` ### -StorageQuota + +> Applicable: Exchange Server 2010 + The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB. ```yaml Type: Unlimited Parameter Sets: ManagedCustomFolder Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -297,13 +320,15 @@ 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/exchange/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md index 0a4c872b09..771ca46499 100644 --- a/exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managedfoldermailboxpolicy applicable: Exchange Server 2010 -title: New-ManagedFolderMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managedfoldermailboxpolicy +schema: 2.0.0 +title: New-ManagedFolderMailboxPolicy --- # New-ManagedFolderMailboxPolicy @@ -48,13 +49,15 @@ This example creates the managed folder mailbox policy My Managed Folder Mailbox ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies the name of the new managed folder mailbox policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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 @@ -99,13 +106,15 @@ Accept wildcard characters: False ``` ### -ManagedFolderLinks + +> Applicable: Exchange Server 2010 + The ManagedFolderLinks parameter specifies the list of managed folders to which the managed folder mailbox policy is to be linked. ```yaml Type: ELCFolderIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -115,13 +124,15 @@ 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/exchange/New-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md similarity index 89% rename from exchange/exchange-ps/exchange/New-ManagementRole.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md index ba2b48a05a..7a4d7cb1ba 100644 --- a/exchange/exchange-ps/exchange/New-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managementrole applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-ManagementRole -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managementrole +schema: 2.0.0 +title: New-ManagementRole --- # New-ManagementRole @@ -85,13 +86,15 @@ In on-premises Exchange, this example creates the unscoped management role In-ho ## 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 role. The maximum length of the name is 64 characters. If the name contains spaces, enclose the name 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: True Position: 1 @@ -101,13 +104,15 @@ Accept wildcard characters: False ``` ### -Parent + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Parent parameter specifies the identity of the role to copy. If the name of the role contains spaces, enclose the name in quotation marks ("). If you specify the Parent parameter, you can't use the UnScopedTopLevel switch. ```yaml Type: RoleIdParameter Parameter Sets: NewDerivedRole Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -117,6 +122,9 @@ 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). @@ -131,7 +139,6 @@ You can't use this switch with the Parent parameter. Type: SwitchParameter Parameter Sets: UnScopedTopLevelRole Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -141,6 +148,9 @@ 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`. @@ -150,7 +160,6 @@ 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 @@ -160,13 +169,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Description parameter specifies the description that's displayed when the management role is viewed using the Get-ManagementRole cmdlet. Enclose the description 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 @@ -176,6 +187,9 @@ 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,7 +198,6 @@ 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,6 +207,9 @@ Accept wildcard characters: False ``` ### -EnabledCmdlets + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EnabledCmdlets parameter specifies the cmdlets that are copied from the parent role. You can specify multiple values separated by commas. You can only use this parameter with the Parent parameter when you copy a role. @@ -202,7 +218,6 @@ You can only use this parameter with the Parent parameter when you copy a role. Type: String[] Parameter Sets: NewDerivedRole Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -212,6 +227,9 @@ 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. @@ -222,7 +240,6 @@ 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 @@ -232,13 +249,15 @@ 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/exchange/New-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md similarity index 90% rename from exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md index 9cd0581b13..86b301fdc4 100644 --- a/exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managementroleassignment applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-ManagementRoleAssignment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managementroleassignment +schema: 2.0.0 +title: New-ManagementRoleAssignment --- # New-ManagementRoleAssignment @@ -177,13 +178,15 @@ This example assigns the Mail Recipients role to the Contoso Sub - Seattle role ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, one will be created automatically. ```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 @@ -193,6 +196,9 @@ Accept wildcard characters: False ``` ### -App + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The App parameter specifies the service principal to assign the management role to. Specifically, the ObjectId GUID value from the output of the Get-ServicePrincipal cmdlet (for example, 6233fba6-0198-4277-892f-9275bf728bcc). @@ -205,7 +211,6 @@ You can't use this parameter with the SecurityGroup, Policy, or User cmdlets. Type: ServicePrincipalIdParameter Parameter Sets: App Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -215,6 +220,9 @@ Accept wildcard characters: False ``` ### -Computer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Computer parameter specifies the name of the computer to assign the management role to. @@ -225,7 +233,6 @@ You can't use this parameter with the SecurityGroup, User, or Policy parameters. Type: ComputerIdParameter Parameter Sets: Computer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -235,6 +242,9 @@ Accept wildcard characters: False ``` ### -Policy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Policy parameter specifies the name of the management role assignment policy to assign the management role to. If the value contains spaces, enclose the value in quotation marks ("). The IsEndUserRole property of the role you specify using the Role parameter must be set to $true. @@ -245,7 +255,6 @@ You can't use this parameter with the App, SecurityGroup, Computer, or User para Type: MailboxPolicyIdParameter Parameter Sets: Policy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -255,6 +264,9 @@ 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 existing role to assign. You can use any value that uniquely identifies the role. For example: - Name @@ -269,7 +281,6 @@ If you use the App parameter, you can't specify admin or user roles; you can onl Type: RoleIdParameter 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 @@ -279,6 +290,9 @@ Accept wildcard characters: False ``` ### -SecurityGroup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SecurityGroup parameter specifies the name of the management role group or mail-enabled universal security group to assign the management role to. If the value contains spaces, enclose the value in quotation marks ("). You can't use this parameter with the App, Policy, Computer, or User parameters. @@ -287,7 +301,6 @@ You can't use this parameter with the App, Policy, Computer, or User parameters. Type: SecurityGroupIdParameter Parameter Sets: SecurityGroup Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -297,6 +310,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The User parameter specifies the user to assign the management role to. For the best results, we recommend using the following values: @@ -310,7 +326,6 @@ You can't use this parameter with the App, SecurityGroup, Computer, or Policy pa Type: UserIdParameter Parameter Sets: User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -320,6 +335,9 @@ 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`. @@ -329,7 +347,6 @@ 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 @@ -339,6 +356,9 @@ 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 specifies the existing configuration scope to associate with this management role assignment. If you use the CustomConfigWriteScope parameter you can't use the ExclusiveConfigWriteScope parameter. If the management scope name contains spaces, enclose the name in quotation marks ("). @@ -347,7 +367,6 @@ The CustomConfigWriteScope parameter specifies the existing configuration scope Type: ManagementScopeIdParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,13 +376,15 @@ 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 specifies the existing recipient-based management scope to associate with this management role assignment. If the management scope name contains spaces, enclose the name in quotation marks ("). If you use the CustomRecipientWriteScope parameter, you can't use the RecipientOrganizationalUnitScope or ExclusiveRecipientWriteScope parameters. ```yaml Type: ManagementScopeIdParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -373,6 +394,9 @@ Accept wildcard characters: False ``` ### -CustomResourceScope + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The CustomResourceScope parameter specifies the custom management scope to associate with this management role assignment. You can use any value that uniquely identifies the management scope. For example: @@ -389,7 +413,6 @@ You use this parameter with the App parameter to assign permissions to service p Type: ManagementScopeIdParameter Parameter Sets: App Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -399,13 +422,15 @@ 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 switch specifies whether the user or USG assigned to the role can delegate the role to other users or groups. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: SecurityGroup, User, App Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -415,6 +440,9 @@ 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. @@ -423,7 +451,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -433,6 +460,9 @@ 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 specifies the exclusive configuration-based management scope to associate with the new role assignment. If you use the ExclusiveConfigWriteScope parameter, you can't use the CustomConfigWriteScope parameter. If the scope name contains spaces, enclose the name in quotation marks ("). @@ -441,7 +471,6 @@ The ExclusiveConfigWriteScope parameter specifies the exclusive configuration-ba Type: ManagementScopeIdParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -451,13 +480,15 @@ 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 specifies the exclusive recipient-based management scope to associate with the new role assignment. If you use the ExclusiveRecipientWriteScope parameter, you can't use the CustomRecipientWriteScope or RecipientOrganizationalUnitScope parameters. If the scope name contains spaces, enclose the name in quotation marks ("). ```yaml Type: ManagementScopeIdParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -467,6 +498,9 @@ 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. @@ -477,7 +511,6 @@ 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 @@ -487,6 +520,9 @@ 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 specifies the administrative unit to scope the new role assignment to. @@ -497,7 +533,6 @@ 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 @@ -507,6 +542,9 @@ Accept wildcard characters: False ``` ### -RecipientGroupScope + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RecipientGroupScope parameter specifies a group to consider for scoping the role assignment. Individual members of the specified group (not nested groups) are considered as in scope for the assignment. You can use any value that uniquely identifies the group: Name, DistinguishedName, GUID, or DisplayName. @@ -515,7 +553,6 @@ The RecipientGroupScope parameter specifies a group to consider for scoping the Type: GroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -525,13 +562,15 @@ 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 specifies the OU to scope the new role assignment to. If you use the RecipientOrganizationalUnitScope parameter, you can't use the CustomRecipientWriteScope or ExclusiveRecipientWriteScope parameters. To specify an OU, use the syntax: domain/ou. If the OU name contains spaces, enclose the domain and OU in quotation marks ("). ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -541,6 +580,9 @@ Accept wildcard characters: False ``` ### -RecipientRelativeWriteScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRelativeWriteScope parameter specifies the type of restriction to apply to a recipient scope. The available types are None, Organization, MyGAL, Self, and MyDistributionGroups. The RecipientRelativeWriteScope parameter is automatically set when the CustomRecipientWriteScope or RecipientOrganizationalUnitScope parameters are used. Even though the NotApplicable, OU, MyDirectReports, CustomRecipientScope, MyExecutive, MailboxICanDelegate and ExclusiveRecipientScope values appear in the syntax block for this parameter, they can't be used directly on the command line. They are used internally by the cmdlet. @@ -549,7 +591,6 @@ Even though the NotApplicable, OU, MyDirectReports, CustomRecipientScope, MyExec Type: RecipientWriteScopeType Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -559,6 +600,9 @@ 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). @@ -571,7 +615,6 @@ Unscoped top-level management roles can only contain custom scripts or non-Excha Type: SwitchParameter Parameter Sets: Computer, Policy, SecurityGroup, User Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -581,13 +624,15 @@ 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/exchange/New-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md similarity index 92% rename from exchange/exchange-ps/exchange/New-ManagementScope.md rename to exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md index c2fcc0e2d9..6f63a0f0ff 100644 --- a/exchange/exchange-ps/exchange/New-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-managementscope applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-ManagementScope -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-managementscope +schema: 2.0.0 +title: New-ManagementScope --- # New-ManagementScope @@ -127,13 +128,15 @@ This example creates the Seattle Databases scope and sets a database restriction ## 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 management scope. The name can be up to 64 characters. If the name contains spaces, enclose the name 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: True Position: 1 @@ -143,6 +146,9 @@ Accept wildcard characters: False ``` ### -DatabaseList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DatabaseList parameter specifies a list of databases to which the scope should be applied. You can use any value that uniquely identifies the database. For example: @@ -159,7 +165,6 @@ You can't use this parameter with the DatabaseRestrictionFilter, ServerList, Rec Type: DatabaseIdParameter[] Parameter Sets: DatabaseList Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -169,6 +174,9 @@ Accept wildcard characters: False ``` ### -DatabaseRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DatabaseRestrictionFilter parameter uses OPATH filter syntax to specify the databases that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. @@ -188,7 +196,6 @@ You can't use this parameter with the RecipientRestrictionFilter, ServerRestrict Type: String Parameter Sets: DatabaseFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -198,6 +205,9 @@ Accept wildcard characters: False ``` ### -RecipientRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"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. @@ -215,7 +225,6 @@ You can't use this parameter with the DatabaseRestrictionFilter, DatabaseList, S Type: String Parameter Sets: RecipientFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -225,6 +234,9 @@ Accept wildcard characters: False ``` ### -ServerList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ServerList parameter specifies a list of servers to which the scope should be applied. You can use any value that uniquely identifies the server. For example: @@ -242,7 +254,6 @@ You can't use this parameter with the RecipientRestrictionFilter, RecipientRoot, Type: ServerIdParameter[] Parameter Sets: ServerList Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -252,6 +263,9 @@ Accept wildcard characters: False ``` ### -ServerRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ServerRestrictionFilter parameter uses OPATH filter syntax to specify the servers that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. @@ -271,7 +285,6 @@ You can't use this parameter wit the RecipientRestrictionFilter, RecipientRoot, Type: String Parameter Sets: ServerFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -281,6 +294,9 @@ 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`. @@ -290,7 +306,6 @@ 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 @@ -300,6 +315,9 @@ 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. @@ -308,7 +326,6 @@ 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 @@ -318,6 +335,9 @@ 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 switch specifies that the role should be an exclusive scope. You don't need to specify a value with this switch. When you create exclusive management scopes, only users or universal security groups (USG) assigned exclusive scopes that contain objects to be modified can access those objects. Users or USGs that aren't assigned an exclusive scope that contains the objects immediately lose access to those objects. @@ -326,7 +346,6 @@ When you create exclusive management scopes, only users or universal security gr Type: SwitchParameter Parameter Sets: DatabaseList, DatabaseFilter, RecipientFilter, ServerList, ServerFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -336,6 +355,9 @@ 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. Use this switch to create an exclusive scope without showing the warning that the exclusive scope takes effect immediately. @@ -344,7 +366,6 @@ Use this switch to create an exclusive scope without showing the warning that th Type: SwitchParameter Parameter Sets: DatabaseList, DatabaseFilter, RecipientFilter, ServerList, ServerFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -354,6 +375,9 @@ Accept wildcard characters: False ``` ### -RecipientRoot + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an 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 @@ -367,7 +391,6 @@ You can't use this parameter with the ServerRestrictionFilter or DatabaseRestric Type: OrganizationalUnitIdParameter Parameter Sets: RecipientFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -377,13 +400,15 @@ 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/exchange/New-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md index 54765cae91..5b2f3f6a22 100644 --- a/exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mapivirtualdirectory applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-MapiVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mapivirtualdirectory +schema: 2.0.0 +title: New-MapiVirtualDirectory --- # New-MapiVirtualDirectory @@ -55,6 +56,9 @@ This example creates a new MAPI virtual directory that has the following configu ## 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`. @@ -64,7 +68,6 @@ 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 @@ -74,13 +77,15 @@ 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 @@ -90,6 +95,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags + +> Applicable: 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. @@ -102,7 +110,6 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -112,6 +119,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList + +> Applicable: 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. @@ -121,7 +131,6 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,6 +140,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking + +> Applicable: 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. @@ -143,7 +155,6 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -153,6 +164,9 @@ Accept wildcard characters: False ``` ### -ExternalUrl + +> Applicable: 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 enforces the Secure Sockets Layer (SSL) protocol and uses the default SSL port. This parameter uses the syntax: `https:///mapi`. For example, `https://external.contoso.com/mapi`. @@ -163,7 +177,6 @@ When you use the InternalUrl or ExternalUrl parameters, you need to specify one Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -173,6 +186,9 @@ Accept wildcard characters: False ``` ### -IISAuthenticationMethods + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values for this parameter are: - Basic @@ -190,7 +206,6 @@ For more information about the different authentication methods, see [Understand Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -200,6 +215,9 @@ Accept wildcard characters: False ``` ### -InternalUrl + +> Applicable: 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 enforces the Secure Sockets Layer (SSL) protocol and uses the default SSL port. This parameter uses the syntax: `https:///mapi`. For example, `https://internal.contoso.com/mapi`. @@ -210,7 +228,6 @@ When you use the InternalUrl or ExternalUrl parameters, you need to specify one Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -220,6 +237,9 @@ Accept wildcard characters: False ``` ### -Role + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The Role parameter species the configuration for the virtual directory. Valid values are: @@ -233,7 +253,6 @@ Client connections are proxied from the Client Access services to the backend se Type: VirtualDirectoryRole Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -243,6 +262,9 @@ 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 @@ -254,7 +276,6 @@ 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 @@ -264,13 +285,15 @@ Accept wildcard characters: False ``` ### -WebSiteName + +> Applicable: 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 2016, Exchange Server 2019 Required: False Position: Named @@ -280,13 +303,15 @@ 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/exchange/New-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md similarity index 89% rename from exchange/exchange-ps/exchange/New-MessageClassification.md rename to exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md index 2692993652..1fbc50fe2b 100644 --- a/exchange/exchange-ps/exchange/New-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-messageclassification applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MessageClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-messageclassification +schema: 2.0.0 +title: New-MessageClassification --- # New-MessageClassification @@ -73,13 +74,15 @@ In on-premises Exchange, this example creates a locale-specific (Spanish - Spain ## 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 message classification. 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 @@ -89,6 +92,9 @@ 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 title of the message classification that's displayed in Outlook and selected by users. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks ("). The message classification XML file must be present on the sender's computer for the display name to be displayed. @@ -97,7 +103,6 @@ The message classification XML file must be present on the sender's computer for 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 @@ -107,6 +112,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional on in on-premises Exchange. The Locale parameter specifies a locale-specific version of an existing message classification. You use the -Name parameter to identify the existing message classification, and the SenderDescription parameter to specify the descriptive text in another language. @@ -117,7 +125,6 @@ A valid value for this parameter is a supported culture code value from the Micr Type: CultureInfo Parameter Sets: Localized Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -127,13 +134,15 @@ Accept wildcard characters: False ``` ### -SenderDescription + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SenderDescription parameter specifies the detailed text that's shown to Outlook senders when they select a message classification to apply to a message before they send the message. The maximum length is 1024 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: Named @@ -143,6 +152,9 @@ Accept wildcard characters: False ``` ### -ClassificationID + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ClassificationID parameter specifies the classification ID (GUID) of an existing message classification that you want to import and use in your Exchange organization. Use this parameter if you're configuring message classifications that span two Exchange forests in the same organization. To find the ClassificationID value of the message classification, replace `` with the name of the message classification and run the following command: `Get-MessageClassification -Identity ""`. @@ -151,7 +163,6 @@ To find the ClassificationID value of the message classification, replace ` 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`. @@ -170,7 +184,6 @@ 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 @@ -180,6 +193,9 @@ Accept wildcard characters: False ``` ### -DisplayPrecedence + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: - Highest @@ -198,7 +214,6 @@ Although Outlook only lets a user specify a single classification for a message, Type: ClassificationDisplayPrecedenceLevel Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -208,6 +223,9 @@ 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. @@ -218,7 +236,6 @@ 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 @@ -228,6 +245,9 @@ Accept wildcard characters: False ``` ### -PermissionMenuVisible + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: - $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. @@ -237,7 +257,6 @@ The PermissionMenuVisible parameter specifies whether the values that you entere 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 @@ -247,6 +266,9 @@ Accept wildcard characters: False ``` ### -RecipientDescription + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RecipientDescription parameter specifies the detailed text that's shown to Outlook recipient when they receive a message that has the message classification applied. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks ("). If you don't use this parameter, the value of the SenderDescription parameter is used. @@ -255,7 +277,6 @@ If you don't use this parameter, the value of the SenderDescription parameter is 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 @@ -265,6 +286,9 @@ Accept wildcard characters: False ``` ### -RetainClassificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetainClassificationEnabled parameter specifies whether the message classification should persist with the message if the message is forwarded or replied to. The default value is $true. @@ -273,7 +297,6 @@ The default value is $true. 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 @@ -283,13 +306,15 @@ 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/exchange/New-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md similarity index 93% rename from exchange/exchange-ps/exchange/New-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md index e17cdd2090..a93923ad66 100644 --- a/exchange/exchange-ps/exchange/New-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-migrationbatch applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MigrationBatch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-migrationbatch +schema: 2.0.0 +title: New-MigrationBatch --- # New-MigrationBatch @@ -585,6 +586,9 @@ A Google Workspace migration batch is created that uses the CSV migration file g ## PARAMETERS ### -UserIds + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserIds parameter specifies the users that you want to copy from an existing migration batch (for example, if a previous migration was partially successful). You identify a user by email address or by their Guid property value from the Get-MigrationUser cmdlet. You can specify multiple users separated by commas. The users that you specify for this parameter must be defined in an existing migration batch. @@ -595,7 +599,6 @@ To disable the migration of the users in the original migration batch, use the D Type: MultiValuedProperty Parameter Sets: PreexistingUserIds Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -605,6 +608,9 @@ Accept wildcard characters: False ``` ### -Users + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Users parameter specifies the users that you want to copy from an existing migration batch (for example, if a previous migration was partially successful). You identify the users by using the Get-MigrationUser cmdlet. For example: $Failed = Get-MigrationUser -Status Failed @@ -619,7 +625,6 @@ To disable the migration of the users in the original migration batch, use the D Type: MultiValuedProperty Parameter Sets: Preexisting, PreexistingUsers Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -629,6 +634,9 @@ Accept wildcard characters: False ``` ### -Analyze + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Analyze Description }} @@ -637,7 +645,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Analysis Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -647,6 +654,9 @@ Accept wildcard characters: False ``` ### -ManagedGmailTeams + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ManagedGmailTeams Description }} @@ -655,7 +665,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ManagedGmailTeams Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -665,13 +674,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies an unique name for the migration batch on each system (Exchange On-premises or Exchange Online). 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, Exchange Online Required: True Position: Named @@ -681,6 +692,9 @@ Accept wildcard characters: False ``` ### -CSVData + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CSVData parameter specifies the CSV file that contains information about the user mailboxes to be moved or migrated. The required attributes in the header row of the CSV file vary depending on the type of migration. For more information, see [CSV files for mailbox migration](https://learn.microsoft.com/exchange/csv-files-for-mailbox-migration-exchange-2013-help). 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`). @@ -689,9 +703,8 @@ A valid value for this parameter requires you to read the file to a byte-encoded ```yaml Type: Byte[] -Parameter Sets: Abch, Analysis, FolderMove, Local, LocalPublicFolder, Offboarding, XO1, PublicFolderToUnifiedGroup, GoogleResourceOnboarding, PointInTimeRecoveryProvisionOnly, PointInTimeRecovery +Parameter Sets: Abch, Analysis, FolderMove, Local, LocalPublicFolder, Offboarding, XO1, PublicFolderToUnifiedGroup, GoogleResourceOnboarding, PointInTimeRecoveryProvisionOnly, PointInTimeRecovery, Onboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -700,20 +713,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Byte[] -Parameter Sets: Onboarding -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Local -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Local This parameter is available only in on-premises Exchange. The Local switch specifies a local move (mailboxes are moved to a different mailbox database in the same Active Directory forest). You don't need to specify a value with this switch. @@ -722,7 +725,6 @@ The Local switch specifies a local move (mailboxes are moved to a different mail Type: SwitchParameter Parameter Sets: Local Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -732,6 +734,9 @@ Accept wildcard characters: False ``` ### -SourcePublicFolderDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SourcePublicFolderDatabase parameter specifies the source public folder database that's used in a public folder migration. You can use any value that uniquely identifies the database. For example: @@ -744,7 +749,6 @@ The SourcePublicFolderDatabase parameter specifies the source public folder data Type: DatabaseIdParameter Parameter Sets: LocalPublicFolder Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -754,6 +758,9 @@ Accept wildcard characters: False ``` ### -AdoptPreexisting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AdoptPreexisting Description }} @@ -762,7 +769,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding, Local, Offboarding, GoogleResourceOnboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -772,6 +778,9 @@ Accept wildcard characters: False ``` ### -AllowIncrementalSyncs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: @@ -783,7 +792,6 @@ The AllowIncrementalSyncs parameter specifies whether to enable or disable incre Type: Boolean Parameter Sets: PreexistingUserIds, Preexisting, Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, Abch, WorkflowTemplate Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -793,6 +801,9 @@ Accept wildcard characters: False ``` ### -AllowUnknownColumnsInCsv + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. @@ -802,7 +813,6 @@ The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -812,6 +822,9 @@ Accept wildcard characters: False ``` ### -ArchiveDomain + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ArchiveDomain Description }} @@ -820,7 +833,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: Onboarding, Offboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -830,6 +842,9 @@ Accept wildcard characters: False ``` ### -ArchiveOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ArchiveOnly switch specifies that only archive mailboxes are migrated for the users in the migration batch (primary mailboxes aren't migrated). You don't need to specify a value with this switch. You can only use this switch for local moves and remote move migrations. @@ -840,7 +855,6 @@ You can use the TargetArchiveDatabases parameter to specify the database to migr Type: SwitchParameter Parameter Sets: Local, Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -850,6 +864,9 @@ Accept wildcard characters: False ``` ### -AutoComplete + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoComplete switch forces the finalization of the individual mailboxes as soon as the mailbox has completed initial synchronization. You don't need to specify a value with this switch. You can only use this switch for local moves and remote move migrations. @@ -860,7 +877,6 @@ If you don't use this switch, you need to run the Complete-MigrationBatch cmdlet Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -870,6 +886,9 @@ Accept wildcard characters: False ``` ### -AutoProvisioning + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AutoProvisioning Description }} @@ -878,7 +897,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -888,6 +906,9 @@ Accept wildcard characters: False ``` ### -AutoRetryCount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AutoRetryCount parameter specifies the number of attempts to restart the migration batch to migrate mailboxes that encountered errors. @@ -896,7 +917,6 @@ The AutoRetryCount parameter specifies the number of attempts to restart the mig Type: Int32 Parameter Sets: PreexistingUserIds, Preexisting, Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, Abch, WorkflowTemplate Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -906,6 +926,9 @@ Accept wildcard characters: False ``` ### -AutoStart + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoStart switch immediately starts the processing of the new migration batch. You don't need to specify a value with this switch. If you don't use this switch, you need to manually start the migration batch by using the Start-MigrationBatch cmdlet. @@ -914,7 +937,6 @@ If you don't use this switch, you need to manually start the migration batch by Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -924,6 +946,9 @@ Accept wildcard characters: False ``` ### -AvoidMergeOverlap + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AvoidMergeOverlap Description }} @@ -932,7 +957,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -942,6 +966,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. @@ -952,7 +979,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, FolderMove Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -962,6 +988,9 @@ Accept wildcard characters: False ``` ### -CompleteAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. @@ -977,7 +1006,6 @@ In Exchange Online PowerShell, if you specify a date/time value without a time z Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -987,6 +1015,9 @@ 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`. @@ -996,7 +1027,6 @@ 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 @@ -1006,6 +1036,9 @@ Accept wildcard characters: False ``` ### -ContentFilter + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service for IMAP migration and Google Workspace migration. The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that match the ContentFilter parameter will be moved to Exchange online. For example: @@ -1020,7 +1053,6 @@ You can specify the language by using the ContentFilterLanguage parameter. Type: String Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1030,6 +1062,9 @@ Accept wildcard characters: False ``` ### -ContentFilterLanguage + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service for IMAP migration and Google Workspace migration. The ContentFilterLanguage parameter specifies the language being used in the ContentFilter parameter for string searches. @@ -1040,7 +1075,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1050,6 +1084,9 @@ Accept wildcard characters: False ``` ### -DataFusion + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DataFusion Description }} @@ -1058,7 +1095,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1068,13 +1104,15 @@ Accept wildcard characters: False ``` ### -DisableOnCopy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DisableOnCopy switch disables the original migration job item for a user if you're copying users from an existing batch to a new batch by using the UserIds or Users parameters. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: PreexistingUserIds, Preexisting, PreexistingUsers Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1084,6 +1122,9 @@ Accept wildcard characters: False ``` ### -DisallowExistingUsers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DisallowExistingUsers switch prevents the migration of mailboxes that are currently defined in a different migration batch. You don't need to specify a value with this switch. @@ -1094,7 +1135,6 @@ A validation warning is displayed for any pre-existing mailbox in the target des Type: SwitchParameter Parameter Sets: Local, Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1104,6 +1144,9 @@ 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. @@ -1112,7 +1155,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: PreexistingUserIds, Preexisting, Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, Abch, WorkflowTemplate Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1122,6 +1164,9 @@ Accept wildcard characters: False ``` ### -ExcludeDumpsters + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExcludeDumpsters switch specifies whether to migrate public folder mailboxes without including the contents of the Recoverable Items folder (formerly known as the dumpster). You don't need to specify a value with this switch. @@ -1132,7 +1177,6 @@ You use this switch only in public folder migrations from Exchange 2013 or later Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1142,6 +1186,9 @@ Accept wildcard characters: False ``` ### -ExcludeFolders + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration or Google Workspace migration, the ExcludeFolders parameter specifies mailbox folders that you don't want to migrate from the source email system to the cloud-based mailboxes. Specify the value as a string array and separate multiple folder names with commas. @@ -1177,7 +1224,6 @@ Wildcard characters can't be used in folder names. Type: MultiValuedProperty Parameter Sets: Onboarding, Analysis Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1187,6 +1233,9 @@ Accept wildcard characters: False ``` ### -ForwardingDisposition + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ForwardingDisposition Description }} @@ -1195,7 +1244,6 @@ This parameter is available only in the cloud-based service. Type: GmailForwardingDisposition Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1205,13 +1253,15 @@ Accept wildcard characters: False ``` ### -GoogleResource + +> Applicable: Exchange Online + {{ Fill GoogleResource Description }} ```yaml Type: SwitchParameter Parameter Sets: GoogleResourceOnboarding Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -1221,6 +1271,9 @@ Accept wildcard characters: False ``` ### -IncludeFolders + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration or Google Workspace migration, the IncludeFolders parameter specifies mailbox folders that you want to migrate from the on-premises email system to the cloud-based mailboxes. Specify the value as a string array and separate multiple folder names with commas. @@ -1256,7 +1309,6 @@ Wildcard characters can't be used in folder names. Type: MultiValuedProperty Parameter Sets: Onboarding, Analysis Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1266,6 +1318,9 @@ Accept wildcard characters: False ``` ### -IncludeOtherContacts + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeOtherContacts Description }} @@ -1274,7 +1329,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1284,6 +1338,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -1299,7 +1356,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: Onboarding, Offboarding, LocalPublicFolder, PublicFolderToUnifiedGroup, FolderMove Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1309,6 +1365,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Locale parameter specifies the language for the migration batch. @@ -1319,7 +1378,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: PreexistingUserIds, Preexisting, Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, Abch, WorkflowTemplate Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1329,6 +1387,9 @@ Accept wildcard characters: False ``` ### -MigrateTasks + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MigrateTasks Description }} @@ -1337,7 +1398,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1347,6 +1407,9 @@ Accept wildcard characters: False ``` ### -MoveOptions + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MoveOptions parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. Don't use this parameter with the SkipMoving parameter. @@ -1355,7 +1418,6 @@ Don't use this parameter with the SkipMoving parameter. Type: MultiValuedProperty Parameter Sets: Onboarding, Local, Offboarding, FolderMove Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1365,6 +1427,9 @@ Accept wildcard characters: False ``` ### -NotificationEmails + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NotificationEmails parameter specifies one or more email addresses that migration status reports are sent to. Specify the value as a string array, and separate multiple email addresses with commas. If you don't use this parameter, the status report isn't sent. @@ -1373,7 +1438,6 @@ If you don't use this parameter, the status report isn't sent. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1383,6 +1447,9 @@ 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. @@ -1391,7 +1458,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: PreexistingUserIds, Onboarding, Local, Offboarding, PublicFolderToUnifiedGroup, WorkflowTemplate, PreexistingUsers, GoogleResourceOnboarding, FolderMove, Analysis, PointInTimeRecoveryProvisionOnly, PointInTimeRecovery Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1401,6 +1467,9 @@ Accept wildcard characters: False ``` ### -PrimaryOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrimaryOnly switch specifies that only primary mailboxes are migrated for the users in the migration batch that also have archive mailboxes (archive mailboxes aren't migrated). You don't need to specify a value with this switch. You can only use this switch for local moves and remote move migrations. @@ -1411,7 +1480,6 @@ You can only use this switch for local moves and remote move migrations. Type: SwitchParameter Parameter Sets: Local, Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1421,6 +1489,9 @@ Accept wildcard characters: False ``` ### -PublicFolderToUnifiedGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The PublicFolderToUnifiedGroup switch specifies a migration from public folders to Microsoft 365 Groups. You don't need to specify a value with this switch. @@ -1429,7 +1500,6 @@ The PublicFolderToUnifiedGroup switch specifies a migration from public folders Type: SwitchParameter Parameter Sets: PublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -1439,6 +1509,9 @@ Accept wildcard characters: False ``` ### -RemoveOnCopy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RemoveOnCopy Description }} @@ -1447,7 +1520,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding, Local, Offboarding, GoogleResourceOnboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1457,6 +1529,9 @@ Accept wildcard characters: False ``` ### -RenamePrimaryCalendar + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RenamePrimaryCalendar Description }} @@ -1465,7 +1540,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1475,6 +1549,9 @@ Accept wildcard characters: False ``` ### -ReportInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails. By default, emailed reports are sent every 24 hours for a batch. Setting this value to 0 indicates that reports should never be sent for this batch. @@ -1485,7 +1562,6 @@ This parameter should only be used in the cloud-based service. Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1495,6 +1571,9 @@ Accept wildcard characters: False ``` ### -Restore + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Restore Description }} @@ -1503,7 +1582,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1513,6 +1591,9 @@ Accept wildcard characters: False ``` ### -SimplifiedSwitchOver + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SimplifiedSwitchOver Description }} @@ -1521,7 +1602,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1531,6 +1611,9 @@ Accept wildcard characters: False ``` ### -SkipCalendar + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SkipCalendar switch specifies that you want to skip calendar migration during Google Workspace onboarding. You don't need to specify a value with this switch. @@ -1539,7 +1622,6 @@ The SkipCalendar switch specifies that you want to skip calendar migration durin Type: SwitchParameter Parameter Sets: Onboarding, ManagedGmailTeams Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1549,6 +1631,9 @@ Accept wildcard characters: False ``` ### -SkipContacts + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SkipContacts switch specifies that you want to skip contact migration during Google Workspace onboarding. You don't need to specify a value with this switch. @@ -1557,7 +1642,6 @@ The SkipContacts switch specifies that you want to skip contact migration during Type: SwitchParameter Parameter Sets: Onboarding, ManagedGmailTeams Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1567,6 +1651,9 @@ Accept wildcard characters: False ``` ### -SkipDelegates + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipDelegates Description }} @@ -1575,7 +1662,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding, GoogleResourceOnboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1585,6 +1671,9 @@ Accept wildcard characters: False ``` ### -SkipDetails + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipDetails Description }} @@ -1593,7 +1682,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Analysis Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1603,6 +1691,9 @@ Accept wildcard characters: False ``` ### -SkipMail + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SkipMail switch specifies that you want to skip mail migration during Google Workspace onboarding. You don't need to specify a value with this switch. @@ -1611,7 +1702,6 @@ The SkipMail switch specifies that you want to skip mail migration during Google Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1621,13 +1711,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. ```yaml Type: MultiValuedProperty Parameter Sets: Onboarding, Offboarding, LocalPublicFolder, XO1, GoogleResourceOnboarding Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1637,6 +1729,9 @@ Accept wildcard characters: False ``` ### -SkipMoving + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1645,7 +1740,6 @@ The SkipMoving parameter specifies the stages of the migration that you want to Type: MultiValuedProperty Parameter Sets: Local, Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1655,6 +1749,9 @@ Accept wildcard characters: False ``` ### -SkipProvisioning + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SkipProvisioning Description }} @@ -1663,7 +1760,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Onboarding, GoogleResourceOnboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1673,13 +1769,15 @@ Accept wildcard characters: False ``` ### -SkipReports + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipReports switch specifies that you want to skip automatic reporting for the migration. 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 @@ -1689,6 +1787,9 @@ Accept wildcard characters: False ``` ### -SkipRules + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SkipRules switch specifies that you want to skip rule migration during Google Workspace onboarding. You don't need to specify a value with this switch. @@ -1697,7 +1798,6 @@ The SkipRules switch specifies that you want to skip rule migration during Googl Type: SwitchParameter Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1707,6 +1807,9 @@ Accept wildcard characters: False ``` ### -SkipSteps + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SkipSteps parameter specifies the steps in the staged Exchange migration that you want to skip. Valid values are: @@ -1720,7 +1823,6 @@ This parameter is only enforced for staged Exchange migrations. Type: SkippableMigrationSteps[] Parameter Sets: PreexistingUserIds, Preexisting, Onboarding, Local, Offboarding, LocalPublicFolder, XO1, PublicFolderToUnifiedGroup, Abch, WorkflowTemplate Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1730,6 +1832,9 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceEndpoint parameter specifies the migration endpoint to use for the source of the migration batch. You create the migration endpoint by using the New-MigrationEndpoint cmdlet. You can use any value that uniquely identifies the migration endpoint. For example: - Name (the Identity property value) @@ -1741,7 +1846,6 @@ This parameter defines the settings that are used to connect to the server where Type: MigrationEndpointIdParameter Parameter Sets: Onboarding, PublicFolderToUnifiedGroup, GoogleResourceOnboarding, Analysis Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1751,6 +1855,9 @@ Accept wildcard characters: False ``` ### -SourcePFPrimaryMailboxGuid + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SourcePFPrimaryMailboxGuid Description }} @@ -1759,7 +1866,6 @@ This parameter is available only in the cloud-based service. Type: Guid Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1769,6 +1875,9 @@ Accept wildcard characters: False ``` ### -StartAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this 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". @@ -1782,7 +1891,6 @@ In Exchange Online PowerShell, if you specify a date/time value without a time z Type: DateTime Parameter Sets: Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1792,6 +1900,9 @@ Accept wildcard characters: False ``` ### -TargetArchiveDatabases + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. You can use any value that uniquely identifies the database. For example: - Name @@ -1808,7 +1919,6 @@ You can only use this parameter for local moves and remote move migrations. Type: MultiValuedProperty Parameter Sets: Local, Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1818,6 +1928,9 @@ Accept wildcard characters: False ``` ### -TargetDatabases + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetDatabases parameter specifies the identity of the database that you're moving mailboxes to. You can use any value that uniquely identifies the database. For example: - Name @@ -1836,7 +1949,6 @@ If you don't use this parameter for a local move, the cmdlet uses the automatic Type: MultiValuedProperty Parameter Sets: Onboarding, Local, Offboarding, XO1, Abch Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1846,6 +1958,9 @@ Accept wildcard characters: False ``` ### -TargetDeliveryDomain + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetDeliveryDomain parameter specifies the FQDN of the external email address created in the source forest for the mail-enabled user when the migration batch is complete. This parameter is required for remote move onboarding and remote offboarding migration batches @@ -1854,7 +1969,6 @@ This parameter is required for remote move onboarding and remote offboarding mig Type: String Parameter Sets: Onboarding, Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1864,6 +1978,9 @@ Accept wildcard characters: False ``` ### -TargetEndpoint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetEndpoint parameter specifies the migration endpoint to use for the destination of the migration batch. You create the migration endpoint by using the New-MigrationEndpoint cmdlet. You can use any value that uniquely identifies the migration endpoint. For example: - Name (the Identity property value) @@ -1875,7 +1992,6 @@ This parameter defines the settings that are used to connect to the destination Type: MigrationEndpointIdParameter Parameter Sets: Offboarding Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1885,6 +2001,9 @@ Accept wildcard characters: False ``` ### -TimeZone + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TimeZone parameter specifies the time zone of the administrator who submits the migration batch. A valid value for this parameter is a supported time zone key name (for example, `"Pacific Standard Time"`). @@ -1901,7 +2020,6 @@ In Exchange Online, the default value is `UTC`. Type: ExTimeZoneValue Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1911,13 +2029,15 @@ 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 @@ -1927,6 +2047,9 @@ Accept wildcard characters: False ``` ### -WorkflowControlFlags + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are: - None (This is the default value) @@ -1939,7 +2062,6 @@ Don't use this parameter unless you're directed to do so by Microsoft Customer S Type: MigrationWorkflowControlFlags Parameter Sets: Local, Onboarding Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1949,13 +2071,15 @@ Accept wildcard characters: False ``` ### -WorkflowTemplate + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkflowTemplate parameter specifies advanced controls for the steps that are performed in the migration. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. ```yaml Type: String Parameter Sets: WorkflowTemplate Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1965,6 +2089,9 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1973,7 +2100,6 @@ This parameter is reserved for internal Microsoft use. Type: RequestWorkloadType Parameter Sets: Local Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1983,6 +2109,9 @@ Accept wildcard characters: False ``` ### -XMLData + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill XMLData Description }} @@ -1991,7 +2120,6 @@ This parameter is available only in the cloud-based service. Type: Byte[] Parameter Sets: Onboarding Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md similarity index 91% rename from exchange/exchange-ps/exchange/New-MigrationEndpoint.md rename to exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md index f7429f506d..41a2ac9a6c 100644 --- a/exchange/exchange-ps/exchange/New-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-migrationendpoint applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MigrationEndpoint -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-migrationendpoint +schema: 2.0.0 +title: New-MigrationEndpoint --- # New-MigrationEndpoint @@ -297,13 +298,15 @@ This example creates an IMAP migration endpoint that supports 50 concurrent migr ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name you give to the new migration endpoint. You can use the Name parameter when you run the New-MigrationBatch cmdlet. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -313,13 +316,15 @@ Accept wildcard characters: False ``` ### -Autodiscover + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + For an Exchange migration, the Autodiscover switch specifies whether to get other connection settings for the on-premises server from the Autodiscover service. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -329,13 +334,15 @@ Accept wildcard characters: False ``` ### -Compliance + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Compliance switch specifies that the endpoint type is compliance. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Compliance Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -345,15 +352,17 @@ Accept wildcard characters: False ``` ### -Credentials + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Credentials parameter specifies the credentials to connect to the source or target endpoint for all Exchange migration types. 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). ```yaml Type: PSCredential -Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, PublicFolder, Compliance, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder, LegacyPublicFolderToUnifiedGroup +Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, PublicFolder, Compliance, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder, LegacyPublicFolderToUnifiedGroup, ExchangeRemoteMove, PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -362,27 +371,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: PSCredential -Parameter Sets: ExchangeRemoteMove, PSTImport -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -EmailAddress -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -EmailAddress The EmailAddress parameter specifies the email address used by the Autodiscover service or in some cases used to validate the endpoint when you specify the connection settings manually. ```yaml Type: SmtpAddress -Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover +Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -391,20 +389,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SmtpAddress -Parameter Sets: ExchangeOutlookAnywhere, Gmail -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -ExchangeOutlookAnywhere -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -ExchangeOutlookAnywhere This parameter is available only in the cloud-based service. The ExchangeOutlookAnywhere switch specifies the type of endpoint for staged and cutover migrations. You don't need to specify a value with this switch. @@ -413,7 +401,6 @@ The ExchangeOutlookAnywhere switch specifies the type of endpoint for staged and Type: SwitchParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -423,13 +410,15 @@ Accept wildcard characters: False ``` ### -ExchangeRemoteMove + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExchangeRemoteMove switch specifies the type of endpoint for cross-forest moves and remote move migrations in a hybrid deployment. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeRemoteMove Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -439,6 +428,9 @@ Accept wildcard characters: False ``` ### -Gmail + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Gmail switch specifies the type of endpoint for Google Workspace migrations. You don't need to specify a value with this switch. @@ -447,7 +439,6 @@ The Gmail switch specifies the type of endpoint for Google Workspace migrations. Type: SwitchParameter Parameter Sets: Gmail Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -457,6 +448,9 @@ Accept wildcard characters: False ``` ### -IMAP + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IMAP switch specifies the type of endpoint for IMAP migrations. You don't need to specify a value with this switch. @@ -465,7 +459,6 @@ The IMAP switch specifies the type of endpoint for IMAP migrations. You don't ne Type: SwitchParameter Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -475,6 +468,9 @@ Accept wildcard characters: False ``` ### -OAuthCode + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill OAuthCode Description }} @@ -483,7 +479,6 @@ This parameter is available only in the cloud-based service. Type: SecureString Parameter Sets: GoogleMarketplaceApp Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -493,6 +488,9 @@ Accept wildcard characters: False ``` ### -PSTImport + +> 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. @@ -501,7 +499,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -511,6 +508,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -519,7 +519,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: PublicFolder, MrsProxyPublicFolder Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -529,6 +528,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabaseServerLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -537,7 +539,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -547,13 +548,15 @@ Accept wildcard characters: False ``` ### -PublicFolderToUnifiedGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Microsoft 365 Groups. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -563,6 +566,9 @@ Accept wildcard characters: False ``` ### -RemoteServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteServer parameter specifies the FQDN of the remote server, which depends on the protocol type for moves: - For cross-forest moves and remote move migrations, this parameter refers to the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. @@ -572,7 +578,6 @@ The RemoteServer parameter specifies the FQDN of the remote server, which depend Type: Fqdn Parameter Sets: ExchangeRemoteMove, PSTImport, IMAP, Compliance, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -582,6 +587,9 @@ Accept wildcard characters: False ``` ### -RpcProxyServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN will be the same as your Outlook on the web URL; for example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server. @@ -590,9 +598,8 @@ This parameter is required only when you don't use the Autodiscover parameter. ```yaml Type: Fqdn -Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup +Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -601,20 +608,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Fqdn -Parameter Sets: ExchangeOutlookAnywhere -Aliases: -Applicable: Exchange Online +### -ServiceAccountKeyFileData -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -ServiceAccountKeyFileData This parameter is available only in the cloud-based service. The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. @@ -625,7 +622,6 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: Gmail Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -635,15 +631,17 @@ Accept wildcard characters: False ``` ### -SourceMailboxLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SourceMailboxLegacyDN parameter specifies the LegacyExchangeDN value of an on-premises mailbox that's used to test the ability of the migration service to create a connection using this endpoint. The cmdlet tries to access this mailbox using the credentials for the administrator account specified in the command. ```yaml Type: String -Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup +Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -652,20 +650,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere -Aliases: -Applicable: Exchange Online +### -AcceptUntrustedCertificates -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -AcceptUntrustedCertificates This parameter is available only in the cloud-based service. {{ Fill AcceptUntrustedCertificates Description }} @@ -674,7 +662,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, IMAP Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -684,6 +671,9 @@ Accept wildcard characters: False ``` ### -ApplicationId + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ApplicationId Description }} @@ -692,7 +682,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ExchangeRemoteMove Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -702,6 +691,9 @@ Accept wildcard characters: False ``` ### -AppSecretKeyVaultUrl + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AppSecretKeyVaultUrl Description }} @@ -710,7 +702,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ExchangeRemoteMove Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -720,6 +711,9 @@ Accept wildcard characters: False ``` ### -Authentication + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Authentication parameter specifies the authentication method used by the on-premises mail server. If you don't include this parameter, Basic authentication is used. @@ -728,7 +722,6 @@ The Authentication parameter specifies the authentication method used by the on- Type: AuthenticationMethod Parameter Sets: ExchangeOutlookAnywhere, IMAP, PublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -738,6 +731,9 @@ 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`. @@ -747,7 +743,6 @@ 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 @@ -757,6 +752,9 @@ 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. @@ -765,7 +763,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, ExchangeRemoteMove, PSTImport, IMAP, Gmail, PublicFolder, Compliance, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -775,6 +772,9 @@ Accept wildcard characters: False ``` ### -ExchangeServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the mailboxes that will be migrated. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. @@ -785,7 +785,6 @@ This parameter is required only when you don't use the Autodiscover parameter. Type: String Parameter Sets: ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -795,6 +794,9 @@ Accept wildcard characters: False ``` ### -MailboxPermission + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxPermission parameter specifies what permissions to use to access the source mailbox during Outlook Anywhere onboarding (staged Exchange migration and cutover Exchange migration). @@ -812,7 +814,6 @@ This parameter can't be used for creating non-Outlook Anywhere migration endpoin Type: MigrationMailboxPermission Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -822,13 +823,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentIncrementalSyncs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxConcurrentIncrementalSyncs parameter specifies the maximum number of incremental syncs allowed per endpoint. The default value is 20. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -838,13 +841,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMigrations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that are migrated during initial sync. This parameter is applicable for all migration types. The default value is 100. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -854,6 +859,9 @@ Accept wildcard characters: False ``` ### -NspiServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The NspiServer parameter specifies the remote Name Service Provider Interface (NSPI) server location for cutover and staged migrations. You must provide the FQDN of the server. @@ -862,7 +870,6 @@ The NspiServer parameter specifies the remote Name Service Provider Interface (N Type: String Parameter Sets: ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -872,6 +879,9 @@ 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. @@ -880,7 +890,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -890,6 +899,9 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration, the Port parameter specifies the TCP port number used by the migration process to connect to the remote server. This parameter is required when you want to migrate data from an on-premises IMAP server to cloud-based mailboxes. @@ -898,7 +910,6 @@ For an IMAP migration, the Port parameter specifies the TCP port number used by Type: Int32 Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -908,6 +919,9 @@ Accept wildcard characters: False ``` ### -RedirectUri + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RedirectUri Description }} @@ -916,7 +930,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: GoogleMarketplaceApp Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -926,6 +939,9 @@ Accept wildcard characters: False ``` ### -RemoteTenant + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RemoteTenant Description }} @@ -934,7 +950,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ExchangeRemoteMove Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -944,6 +959,9 @@ Accept wildcard characters: False ``` ### -Security + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl. @@ -952,7 +970,6 @@ For an IMAP migration, the Security parameter specifies the encryption method us Type: IMAPSecurityMechanism Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -962,13 +979,15 @@ Accept wildcard characters: False ``` ### -SkipVerification + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipVerification switch specifies whether to skip verifying that the remote server is reachable when creating a migration endpoint. 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 @@ -978,6 +997,9 @@ Accept wildcard characters: False ``` ### -TestMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The TestMailbox parameter specifies an Exchange Online mailbox used as the target by the migration service to verify the connection using this endpoint. You can use any value that uniquely identifies the mailbox. For example: @@ -1001,7 +1023,6 @@ This parameter is only used to create Outlook Anywhere migration endpoints. Type: MailboxIdParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail, GoogleMarketplaceApp, PublicFolder, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1011,13 +1032,15 @@ 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/exchange/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md index 6d4e325288..26eb8ce86c 100644 --- a/exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-mobiledevicemailboxpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-MobileDeviceMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-mobiledevicemailboxpolicy +schema: 2.0.0 +title: New-MobileDeviceMailboxPolicy --- # New-MobileDeviceMailboxPolicy @@ -117,6 +118,9 @@ This example creates the mobile device mailbox policy Contoso Policy that has se ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the mobile device mailbox policy. You can use any value that uniquely identifies the policy. For example: - Name @@ -129,7 +133,6 @@ The name of the built-in mobile device mailbox policy is Default. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -139,6 +142,9 @@ 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. Valid input for this parameter is $true or $false. The default value is $true. @@ -147,7 +153,6 @@ The AllowApplePushNotifications parameter specifies whether push notifications a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -157,6 +162,9 @@ Accept wildcard characters: False ``` ### -AllowBluetooth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are: - Allow (this is the default value). @@ -171,7 +179,6 @@ The value Disable disables synchronization between Outlook for Android and the O Type: BluetoothType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -181,13 +188,15 @@ Accept wildcard characters: False ``` ### -AllowBrowser + +> Applicable: 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 device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't affect non-Microsoft browsers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -197,13 +206,15 @@ Accept wildcard characters: False ``` ### -AllowCamera + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowCamera parameter specifies whether the mobile device's camera is allowed. Valid input for this parameter is $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 Required: False Position: Named @@ -213,13 +224,15 @@ Accept wildcard characters: False ``` ### -AllowConsumerEmail + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowConsumerEmail parameter specifies whether the user can configure a personal email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access to email accounts using non-Microsoft mobile device email programs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -229,13 +242,15 @@ Accept wildcard characters: False ``` ### -AllowDesktopSync + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowDesktopSync parameter specifies whether the mobile device can synchronize with a desktop computer through a cable. Valid input for this parameter is $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 Required: False Position: Named @@ -245,13 +260,15 @@ Accept wildcard characters: False ``` ### -AllowExternalDeviceManagement + +> Applicable: 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 mobile device. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -261,6 +278,9 @@ Accept wildcard characters: False ``` ### -AllowGooglePushNotifications + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AllowGooglePushNotifications parameter controls whether the user can receive push notifications from Google for Outlook on the web for devices. Valid input for this parameter is $true or $false. The default value is $true. @@ -269,7 +289,6 @@ The AllowGooglePushNotifications parameter controls whether the user can receive Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -279,13 +298,15 @@ Accept wildcard characters: False ``` ### -AllowHTMLEmail + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowHTMLEmail parameter specifies whether HTML-formatted email is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -295,13 +316,15 @@ Accept wildcard characters: False ``` ### -AllowInternetSharing + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowInternetSharing parameter specifies whether the mobile device can be used as a modem to connect a computer to the Internet. This process is also known as tethering. Valid input for this parameter is $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 Required: False Position: Named @@ -311,13 +334,15 @@ Accept wildcard characters: False ``` ### -AllowIrDA + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -327,6 +352,9 @@ Accept wildcard characters: False ``` ### -AllowMicrosoftPushNotifications + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AllowMicrosoftPushNotifications parameter specifies whether push notifications are enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. @@ -335,7 +363,6 @@ The AllowMicrosoftPushNotifications parameter specifies whether push notificatio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -345,13 +372,15 @@ Accept wildcard characters: False ``` ### -AllowMobileOTAUpdate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowMobileOTAUpdate parameter specifies whether the policy can be sent to the mobile device over a cellular data connection. Valid input for this parameter is $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 Required: False Position: Named @@ -361,6 +390,9 @@ Accept wildcard characters: False ``` ### -AllowNonProvisionableDevices + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowNonProvisionableDevices parameter specifies whether all mobile devices can synchronize with Exchange. Valid input for this parameter is $true or $false. The default value is $true. When set to $true, this parameter enables all mobile devices to synchronize with Exchange, regardless of whether the device can enforce all settings that are defined by the policy. This also includes mobile devices managed by a separate device management system. When set to $false, this parameter blocks mobile devices that aren't provisioned from synchronizing with Exchange. @@ -369,7 +401,6 @@ When set to $true, this parameter enables all mobile devices to synchronize with Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -379,13 +410,15 @@ Accept wildcard characters: False ``` ### -AllowPOPIMAPEmail + +> Applicable: 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 mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access by non-Microsoft email programs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -395,13 +428,15 @@ Accept wildcard characters: False ``` ### -AllowRemoteDesktop + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowRemoteDesktop parameter specifies whether the mobile device can initiate a remote desktop connection. Valid input for this parameter is $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 Required: False Position: Named @@ -411,13 +446,15 @@ Accept wildcard characters: False ``` ### -AllowSimplePassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSimplePassword parameter specifies whether a simple password is allowed on the mobile device. A simple password is a password that has a specific pattern, such as 1111 or 1234. Valid input for this parameter is $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 Required: False Position: Named @@ -427,6 +464,9 @@ Accept wildcard characters: False ``` ### -AllowSMIMEEncryptionAlgorithmNegotiation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the mobile device can negotiate the encryption algorithm if a recipient's certificate doesn't support the specified encryption algorithm. Valid values for this parameter are: - AllowAnyAlgorithmNegotiation @@ -439,7 +479,6 @@ The default value is AllowAnyAlgorithmNegotiation. Type: SMIMEEncryptionAlgorithmNegotiationType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -449,13 +488,15 @@ Accept wildcard characters: False ``` ### -AllowSMIMESoftCerts + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -465,13 +506,15 @@ Accept wildcard characters: False ``` ### -AllowStorageCard + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowStorageCard parameter specifies whether the mobile device can access information stored on a storage card. Valid input for this parameter is $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 Required: False Position: Named @@ -481,13 +524,15 @@ Accept wildcard characters: False ``` ### -AllowTextMessaging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowTextMessaging parameter specifies whether text messaging is allowed from the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -497,13 +542,15 @@ Accept wildcard characters: False ``` ### -AllowUnsignedApplications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -513,13 +560,15 @@ Accept wildcard characters: False ``` ### -AllowUnsignedInstallationPackages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages are allowed to run on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -529,13 +578,15 @@ Accept wildcard characters: False ``` ### -AllowWiFi + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowWiFi parameter specifies whether wireless Internet access is allowed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -545,13 +596,15 @@ Accept wildcard characters: False ``` ### -AlphanumericPasswordRequired + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AlphanumericPasswordRequired parameter specifies whether the password for the mobile device must be alphanumeric. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -561,13 +614,15 @@ Accept wildcard characters: False ``` ### -ApprovedApplicationList + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApprovedApplicationList parameter specifies a configured list of approved applications for the device. ```yaml Type: ApprovedApplicationCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -577,6 +632,9 @@ Accept wildcard characters: False ``` ### -AttachmentsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AttachmentsEnabled parameter specifies whether attachments can be downloaded on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. When set to $false, this parameter blocks the user from downloading attachments on the mobile device. @@ -585,7 +643,6 @@ When set to $false, this parameter blocks the user from downloading attachments Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -595,6 +652,9 @@ 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`. @@ -604,7 +664,6 @@ 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 @@ -614,6 +673,9 @@ Accept wildcard characters: False ``` ### -DeviceEncryptionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This setting is supported by Outlook for iOS and Android. The DeviceEncryptionEnabled parameter specifies whether encryption is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. @@ -624,7 +686,6 @@ When this parameter is set to $true, device encryption is enabled on the mobile Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -634,6 +695,9 @@ Accept wildcard characters: False ``` ### -DevicePolicyRefreshInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DevicePolicyRefreshInterval parameter specifies how often the policy is sent to the mobile device. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -644,7 +708,6 @@ The default value is Unlimited. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -654,6 +717,9 @@ 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. @@ -662,7 +728,6 @@ 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 @@ -672,13 +737,15 @@ Accept wildcard characters: False ``` ### -IrmEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -688,6 +755,9 @@ 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. Valid input for this parameter is $true or $false. The default value for the built-in mobile device mailbox policy named Default is $true. The default value for new mobile device mailbox policies that you create is $false. There can be only one default policy. If another policy is currently set as the default, and you set this parameter to $true, this policy becomes the default policy. The value of this parameter on the other policy is automatically changed to $false, and that policy is no longer the default policy. @@ -696,7 +766,6 @@ There can be only one default policy. If another policy is currently set as the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -706,6 +775,9 @@ Accept wildcard characters: False ``` ### -MaxAttachmentSize + +> Applicable: 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 device. Valid input for this parameter is a size value between 0 and 2147482624 bytes (approximately 2 GB), or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4096 or 4KB. @@ -720,7 +792,6 @@ The maximum value is 1024 bytes (one kilobyte) less than two gigabytes (2\*1024^ Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -730,6 +801,9 @@ Accept wildcard characters: False ``` ### -MaxCalendarAgeFilter + +> Applicable: 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 mobile device. Valid values for this parameter are: - All @@ -744,7 +818,6 @@ The default value is All. Type: CalendarAgeFilterType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -754,6 +827,9 @@ Accept wildcard characters: False ``` ### -MaxEmailAgeFilter + +> Applicable: 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 mobile device. Valid values for this parameter are: - All @@ -769,7 +845,6 @@ The default value is All. Type: EmailAgeFilterType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -779,6 +854,9 @@ Accept wildcard characters: False ``` ### -MaxEmailBodyTruncationSize + +> Applicable: 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 mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4KB or 4096. @@ -787,7 +865,6 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -797,6 +874,9 @@ Accept wildcard characters: False ``` ### -MaxEmailHTMLBodyTruncationSize + +> Applicable: 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 truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4KB or 4096. @@ -805,7 +885,6 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -815,6 +894,9 @@ Accept wildcard characters: False ``` ### -MaxInactivityTimeLock + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). @@ -824,7 +906,6 @@ The MaxInactivityTimeLock parameter specifies the length of time that the mobile Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -834,6 +915,9 @@ Accept wildcard characters: False ``` ### -MaxPasswordFailedAttempts + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxPasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the mobile device. You can enter any number from 4 through 16 or the value Unlimited. The default value is Unlimited. @@ -842,7 +926,6 @@ You can enter any number from 4 through 16 or the value Unlimited. The default v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -852,6 +935,9 @@ Accept wildcard characters: False ``` ### -MinPasswordComplexCharacters + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are: - Lower case letters. @@ -874,7 +960,6 @@ For Windows Phone 10 devices, the value specifies the following password complex Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -884,6 +969,9 @@ Accept wildcard characters: False ``` ### -MinPasswordLength + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This setting is supported by Outlook for Android. The MinPasswordLength parameter specifies the minimum number of characters in the mobile device password. @@ -894,7 +982,6 @@ You can enter any number from 1 through 16 or the value $null. The default value Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -904,6 +991,9 @@ Accept wildcard characters: False ``` ### -PasswordEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordEnabled parameter specifies whether a password is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. When set to $true, this parameter requires the user to set a password on the mobile device. @@ -912,7 +1002,6 @@ When set to $true, this parameter requires the user to set a password on the mob Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -922,6 +1011,9 @@ Accept wildcard characters: False ``` ### -PasswordExpiration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). @@ -931,7 +1023,6 @@ The PasswordExpiration parameter specifies how long a password can be used on a Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -941,6 +1032,9 @@ Accept wildcard characters: False ``` ### -PasswordHistory + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordHistory parameter specifies the number of unique new passwords that need to be created on the mobile device before an old password can be reused. You can enter any number from 0 through 50. The default value is 0. @@ -949,7 +1043,6 @@ You can enter any number from 0 through 50. The default value is 0. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -959,6 +1052,9 @@ Accept wildcard characters: False ``` ### -PasswordRecoveryEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordRecoveryEnabled parameter specifies whether the recovery password for the mobile device is stored in Exchange. Valid input for this parameter is $true or $false. The default value is $false. When set to $true, this parameter enables you to store the recovery password for the mobile device in Exchange. The recovery password can be viewed from Outlook on the web or the Exchange admin center. @@ -967,7 +1063,6 @@ When set to $true, this parameter enables you to store the recovery password for Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -977,13 +1072,15 @@ Accept wildcard characters: False ``` ### -RequireDeviceEncryption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireDeviceEncryption parameter specifies whether encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -993,13 +1090,15 @@ Accept wildcard characters: False ``` ### -RequireEncryptedSMIMEMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireEncryptedSMIMEMessages parameter specifies whether the mobile device must send encrypted S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1009,6 +1108,9 @@ Accept wildcard characters: False ``` ### -RequireEncryptionSMIMEAlgorithm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireEncryptionSMIMEAlgorithm parameter specifies the algorithm that's required to encrypt S/MIME messages on a mobile device. The valid values for this parameter are: - DES @@ -1023,7 +1125,6 @@ The default value is TripleDES. Type: EncryptionSMIMEAlgorithmType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1033,13 +1134,15 @@ Accept wildcard characters: False ``` ### -RequireManualSyncWhenRoaming + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireManualSyncWhenRoaming parameter specifies whether the mobile device must synchronize manually while roaming. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1049,6 +1152,9 @@ Accept wildcard characters: False ``` ### -RequireSignedSMIMEAlgorithm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireSignedSMIMEAlgorithm parameter specifies the algorithm that's used to sign S/MIME messages on the mobile device. Valid values for this parameter are SHA1 or MD5. The default value is SHA1. @@ -1057,7 +1163,6 @@ Valid values for this parameter are SHA1 or MD5. The default value is SHA1. Type: SignedSMIMEAlgorithmType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1067,13 +1172,15 @@ Accept wildcard characters: False ``` ### -RequireSignedSMIMEMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireSignedSMIMEMessages parameter specifies whether the mobile device must send signed S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1083,6 +1190,9 @@ Accept wildcard characters: False ``` ### -RequireStorageCardEncryption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireStorageCardEncryption parameter specifies whether storage card encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter to $true. @@ -1091,7 +1201,6 @@ Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1101,13 +1210,15 @@ Accept wildcard characters: False ``` ### -UnapprovedInROMApplicationList + +> Applicable: 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 on the mobile device. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1117,13 +1228,15 @@ Accept wildcard characters: False ``` ### -UNCAccessEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1133,13 +1246,15 @@ 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 @@ -1149,13 +1264,15 @@ Accept wildcard characters: False ``` ### -WSSAccessEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory. ```yaml Type: Boolean 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/exchange/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md similarity index 87% rename from exchange/exchange-ps/exchange/New-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md index 85f5f280eb..256d2f35cb 100644 --- a/exchange/exchange-ps/exchange/New-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-moverequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-MoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-moverequest +schema: 2.0.0 +title: New-MoveRequest --- # New-MoveRequest @@ -283,6 +284,9 @@ This example creates a batch move request for all mailboxes on the database DB01 ## 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 the following values: - GUID @@ -297,7 +301,6 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c Type: MailboxOrMailUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -307,6 +310,9 @@ Accept wildcard characters: False ``` ### -Outbound + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Outbound switch specifies that this mailbox move is a cross-forest move and is being initiated from the source forest. You don't need to specify a value with this switch. You can't use this switch with the Remote switch. @@ -315,7 +321,6 @@ You can't use this switch with the Remote switch. Type: SwitchParameter Parameter Sets: MigrationOutbound, MigrationOutboundCrossTenant Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -325,6 +330,9 @@ Accept wildcard characters: False ``` ### -Remote + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Remote switch specifies that the move is outside of your organization and is being initiated from the target forest. You don't need to specify a value with this switch. You can't use this switch with the Outbound switch. @@ -333,7 +341,6 @@ You can't use this switch with the Outbound switch. Type: SwitchParameter Parameter Sets: MigrationRemote, MigrationRemoteCrossTenant Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -343,15 +350,17 @@ Accept wildcard characters: False ``` ### -RemoteCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteCredential parameter specifies the username and password of an administrator who has permission to perform the mailbox move. 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). ```yaml Type: PSCredential -Parameter Sets: MigrationRemoteLegacy +Parameter Sets: MigrationRemoteLegacy, MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -360,27 +369,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: PSCredential -Parameter Sets: MigrationOutbound, MigrationRemote -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -RemoteGlobalCatalog -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -RemoteGlobalCatalog The RemoteGlobalCatalog parameter specifies the fully qualified domain name (FQDN) of the global catalog server for the remote forest. ```yaml Type: Fqdn -Parameter Sets: MigrationRemoteLegacy +Parameter Sets: MigrationRemoteLegacy, MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -389,27 +387,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Fqdn -Parameter Sets: MigrationOutbound, MigrationRemote -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -RemoteHostName -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -RemoteHostName The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox. ```yaml Type: Fqdn Parameter Sets: MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -419,6 +406,9 @@ Accept wildcard characters: False ``` ### -RemoteLegacy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoteLegacy switch specifies that this mailbox move is from a remote forest that has only Exchange 2010 servers installed. You don't need to specify a value with this switch. @@ -427,7 +417,6 @@ The RemoteLegacy switch specifies that this mailbox move is from a remote forest Type: SwitchParameter Parameter Sets: MigrationRemoteLegacy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -437,13 +426,15 @@ Accept wildcard characters: False ``` ### -TargetDeliveryDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetDeliveryDomain parameter specifies the FQDN of the external email address created in the source forest for the mail-enabled user when the move request is complete. This parameter is allowed only when performing remote moves with the Remote, RemoteLegacy, or Outbound parameter. ```yaml Type: Fqdn -Parameter Sets: MigrationOutboundCrossTenant, MigrationRemoteCrossTenant +Parameter Sets: MigrationOutboundCrossTenant, MigrationRemoteCrossTenant, MigrationOutbound, MigrationRemote, MigrationRemoteLegacy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -452,20 +443,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Fqdn -Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -AcceptLargeDataLoss -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -AcceptLargeDataLoss The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later or Exchange Online, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -476,7 +457,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -486,6 +466,9 @@ Accept wildcard characters: False ``` ### -AllowLargeItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllowLargeItems switch specifies that items larger than the target mailbox limits are copied without failure. You don't need to specify a value with this switch. @@ -496,7 +479,6 @@ You can't use this switch with the LargeItemLimit parameter. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -506,13 +488,15 @@ Accept wildcard characters: False ``` ### -ArchiveDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ArchiveDomain parameter specifies the FQDN of the external domain to which you're moving the archive. This parameter is used for moving the archive to a cloud-based service. ```yaml Type: String Parameter Sets: MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -522,6 +506,9 @@ Accept wildcard characters: False ``` ### -ArchiveOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ArchiveOnly switch specifies that you're moving only the personal archive associated with the mailbox. You don't need to specify a value with this switch. You can't use this switch with the PrimaryOnly switch. @@ -530,7 +517,6 @@ You can't use this switch with the PrimaryOnly switch. Type: SwitchParameter Parameter Sets: MigrationOutbound, MigrationRemote, MigrationLocal Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -540,6 +526,9 @@ Accept wildcard characters: False ``` ### -ArchiveTargetDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ArchiveTargetDatabase parameter specifies the destination mailbox database for the personal archive. You can use any value that uniquely identifies the database. For example: @@ -554,7 +543,6 @@ If you don't use this parameter, the archive is moved to the same database as th Type: DatabaseIdParameter Parameter Sets: MigrationRemote, MigrationLocal, MigrationRemoteCrossTenant Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -564,6 +552,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -576,7 +567,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th 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 @@ -586,13 +576,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BatchName parameter specifies a descriptive name for moving a batch of mailboxes. You can then use the name in the BatchName parameter as a search string when you use the Get-MoveRequest cmdlet. ```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 @@ -602,6 +594,9 @@ Accept wildcard characters: False ``` ### -CompleteAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompleteAfter parameter specifies a delay before the request is completed. The request is started, but not completed until the date/time you specify with this 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". @@ -617,7 +612,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -627,13 +621,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -643,6 +639,9 @@ 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`. @@ -652,7 +651,6 @@ 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 @@ -662,6 +660,9 @@ 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. @@ -670,7 +671,6 @@ 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 @@ -680,6 +680,9 @@ Accept wildcard characters: False ``` ### -DoNotPreserveMailboxSignature + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DoNotPreserveMailboxSignature switch specifies that the move doesn't preserve the mailbox mapping signature. You don't need to specify a value with this switch. @@ -690,7 +693,6 @@ We recommend that you use this switch only if the move request fails because the Type: SwitchParameter Parameter Sets: MigrationLocal Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -700,6 +702,9 @@ Accept wildcard characters: False ``` ### -ForceOffline + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceOffline switch forces the mailbox move to be performed in offline mode. You don't need to specify a value with this switch. Moving a mailbox in offline mode means the user will have no access to email during the mailbox move. @@ -708,7 +713,6 @@ Moving a mailbox in offline mode means the user will have no access to email dur Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -718,6 +722,9 @@ Accept wildcard characters: False ``` ### -ForcePull + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ForcePull switch specifies that the type of local move should be a Pull move. You don't need to specify a value with this switch. @@ -728,7 +735,6 @@ You use this parameter only for local moves. Type: SwitchParameter Parameter Sets: MigrationLocal Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -738,6 +744,9 @@ Accept wildcard characters: False ``` ### -ForcePush + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ForcePush switch specifies that the type of local move should be a Push move. You don't need to specify a value with this switch. @@ -748,7 +757,6 @@ You use this parameter only for local moves. Type: SwitchParameter Parameter Sets: MigrationLocal Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -758,6 +766,9 @@ Accept wildcard characters: False ``` ### -IgnoreRuleLimitErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013 The IgnoreRuleLimitErrors switch specifies that the command doesn't move the user's rules to the target server running Exchange. You don't need to specify a value with this switch. @@ -766,7 +777,6 @@ The IgnoreRuleLimitErrors switch specifies that the command doesn't move the use Type: SwitchParameter Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy, MigrationLocal Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -776,6 +786,9 @@ Accept wildcard characters: False ``` ### -IncrementalSyncInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -786,7 +799,6 @@ Valid values are from 00:00:00 to 120.00:00:00 (120 days). The default value is Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -796,6 +808,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -804,7 +819,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -814,6 +828,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -831,7 +848,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -841,6 +857,9 @@ Accept wildcard characters: False ``` ### -MoveOptions + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MoveOptions parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. Don't use this parameter with the SkipMoving parameter. @@ -849,7 +868,6 @@ Don't use this parameter with the SkipMoving parameter. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -859,6 +877,9 @@ Accept wildcard characters: False ``` ### -MRSServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSServer parameter specifies the FQDN of the Client Access server on which the instance of the Microsoft Exchange Mailbox Replication service (MRS) is running. This parameter is used for debugging purposes only. Use this parameter only if directed by support personnel. @@ -867,7 +888,6 @@ The MRSServer parameter specifies the FQDN of the Client Access server on which Type: Fqdn Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy, MigrationLocal Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -877,6 +897,9 @@ Accept wildcard characters: False ``` ### -PreventCompletion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreventCompletion switch specifies whether to run the move request, but not allow it to complete. You don't need to specify a value with this switch. Instead of this switch, we recommend using the CompleteAfter parameter. @@ -885,7 +908,6 @@ Instead of this switch, we recommend using the CompleteAfter parameter. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -895,6 +917,9 @@ Accept wildcard characters: False ``` ### -PrimaryOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrimaryOnly switch specifies that the command should only move the primary mailbox (the personal archive isn't moved). You don't need to specify a value with this switch. You use this switch only if the user has a personal archive that you don't want to move. If the user doesn't have personal archive, don't use this switch. @@ -905,7 +930,6 @@ You can't use this switch with the ArchiveOnly sitch. Type: SwitchParameter Parameter Sets: MigrationOutbound, MigrationRemote, MigrationLocal Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -915,6 +939,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: @@ -932,7 +959,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -942,6 +968,9 @@ 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. This parameter is reserved for internal Microsoft use. @@ -950,7 +979,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -960,6 +988,9 @@ Accept wildcard characters: False ``` ### -ProxyToMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ProxyToMailbox parameter specifies the move destination by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example: @@ -979,7 +1010,6 @@ The ProxyToMailbox parameter specifies the move destination by the location of t Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -989,6 +1019,9 @@ Accept wildcard characters: False ``` ### -RemoteArchiveTargetDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteArchiveTargetDatabase parameter specifies the name of the target database in the remote forest to which you're moving the personal archive. Use this parameter when moving users with archives from the local forest to a remote forest. For moves from a remote forest to the local forest, use the ArchiveTargetDatabase parameter. If you use this parameter, you must specify the Remote or RemoteLegacy parameter. @@ -997,7 +1030,6 @@ If you use this parameter, you must specify the Remote or RemoteLegacy parameter Type: String Parameter Sets: MigrationOutbound Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1007,13 +1039,15 @@ Accept wildcard characters: False ``` ### -RemoteOrganizationName + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1023,6 +1057,9 @@ Accept wildcard characters: False ``` ### -RemoteTargetDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteTargetDatabase parameter specifies the name of the target database in the remote forest. Use this parameter when moving mailboxes from the local forest to a remote forest. For moves from a remote forest to the local forest, use the TargetDatabase parameter. If you use this parameter, you must specify the Remote or RemoteLegacy parameter. @@ -1031,7 +1068,6 @@ If you use this parameter, you must specify the Remote or RemoteLegacy parameter Type: String Parameter Sets: MigrationOutbound, MigrationRemote Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1041,6 +1077,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -1054,7 +1093,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1064,6 +1102,9 @@ Accept wildcard characters: False ``` ### -SkipMoving + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -1072,7 +1113,6 @@ The SkipMoving parameter specifies the stages of the move that you want to skip Type: SkippableMoveComponent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1082,6 +1122,9 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SourceEndpoint Description }} @@ -1090,7 +1133,6 @@ This parameter is available only in the cloud-based service. Type: MigrationEndpointIdParameter Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy, MigrationLocal, MigrationRemoteCrossTenant Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1100,6 +1142,9 @@ Accept wildcard characters: False ``` ### -StartAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this 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". @@ -1115,7 +1160,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1125,6 +1169,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -1133,7 +1180,6 @@ If you use this switch, the request is queued, but the request won't reach the s 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 @@ -1143,13 +1189,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```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 @@ -1159,6 +1207,9 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendWhenReadyToComplete switch specifies whether to suspend the move request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch. Instead of this switch, we recommend that you use the CompleteAfter parameter. @@ -1167,7 +1218,6 @@ Instead of this switch, we recommend that you use the CompleteAfter parameter. 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 @@ -1177,6 +1227,9 @@ 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 specifies the destination mailbox database for the mailbox. You can use any value that uniquely identifies the database. For example: @@ -1191,7 +1244,6 @@ If you don't use this parameter, the automatic distribution logic will select a Type: DatabaseIdParameter Parameter Sets: MigrationRemote, MigrationRemoteLegacy, MigrationLocal, MigrationRemoteCrossTenant Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1201,6 +1253,9 @@ 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. You can use this switch to test a mailbox's readiness to be moved, and to view any errors that will occur without adding the mailbox to the move request queue. @@ -1209,7 +1264,6 @@ You can use this switch to test a mailbox's readiness to be moved, and to view a 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 @@ -1219,6 +1273,9 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> 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. @@ -1227,7 +1284,6 @@ This parameter is reserved for internal Microsoft use. Type: RequestWorkloadType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md similarity index 94% rename from exchange/exchange-ps/exchange/New-OMEConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md index 8be7fb364c..d77134a538 100644 --- a/exchange/exchange-ps/exchange/New-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-omeconfiguration applicable: Exchange Online -title: New-OMEConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-omeconfiguration +schema: 2.0.0 +title: New-OMEConfiguration --- # New-OMEConfiguration @@ -53,13 +54,15 @@ This example creates a new OME configuration named "Contoso Marketing" with the ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies a unique name for the OME configuration object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). ```yaml Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -BackgroundColor + +> Applicable: Exchange Online + The BackgroundColor parameter specifies the background color. Valid values are: - An available HTML hexadecimal (hex triplet) color code value (for example, `0x000000` is white). @@ -81,7 +87,6 @@ For more information, see [Add your organization's brand to your encrypted messa Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -91,13 +96,15 @@ 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 @@ -107,13 +114,15 @@ Accept wildcard characters: False ``` ### -DisclaimerText + +> Applicable: Exchange Online + The DisclaimerText parameter specifies the disclaimer text in the email that contains the encrypted message. The maximum length is 1024 characters. 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 @@ -123,13 +132,15 @@ Accept wildcard characters: False ``` ### -EmailText + +> Applicable: Exchange Online + The EmailText parameter specifies the default text that accompanies encrypted email messages. The default text appears above the instructions for viewing encrypted messages. The maximum length is 1024 characters. 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 @@ -139,6 +150,9 @@ Accept wildcard characters: False ``` ### -ExternalMailExpiryInDays + +> Applicable: Exchange Online + This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. @@ -149,7 +163,6 @@ In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is Type: String Parameter Sets: Int32 Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -159,6 +172,9 @@ Accept wildcard characters: False ``` ### -Image + +> Applicable: Exchange Online + The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. 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`). @@ -171,7 +187,6 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -181,13 +196,15 @@ Accept wildcard characters: False ``` ### -IntroductionText + +> Applicable: Exchange Online + The IntroductionText parameter specifies the default text that accompanies encrypted email messages. The default text appears below the recipient email address for viewing the encrypted message. 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 @@ -197,6 +214,9 @@ Accept wildcard characters: False ``` ### -OTPEnabled + +> Applicable: Exchange Online + The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: - $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. @@ -206,7 +226,6 @@ The OTPEnabled parameter specifies whether to allow recipients to use a one-time Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,13 +235,15 @@ Accept wildcard characters: False ``` ### -PortalText + +> Applicable: Exchange Online + The PortalText parameter specifies the text that appears at the top of the encrypted email viewing portal. The maximum length is 128 characters. 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 @@ -232,13 +253,15 @@ Accept wildcard characters: False ``` ### -PrivacyStatementUrl + +> Applicable: Exchange Online + {{ Fill PrivacyStatementUrl Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -248,13 +271,15 @@ Accept wildcard characters: False ``` ### -ReadButtonText + +> Applicable: Exchange Online + The ReadButtonText parameter specifies the text that appears on the "Read Message" button. 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 @@ -264,6 +289,9 @@ Accept wildcard characters: False ``` ### -SocialIdSignIn + +> Applicable: Exchange Online + The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, etc). Valid values are: - $true: Social network ID sign in is allowed. This is the default value. @@ -273,7 +301,6 @@ The SocialIdSignIn parameter specifies whether a user is allowed to view an encr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -283,13 +310,15 @@ 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/exchange/New-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md similarity index 88% rename from exchange/exchange-ps/exchange/New-OabVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md index 7732f3db5a..27bf4728b7 100644 --- a/exchange/exchange-ps/exchange/New-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-oabvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-OabVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-oabvirtualdirectory +schema: 2.0.0 +title: New-OabVirtualDirectory --- # New-OabVirtualDirectory @@ -58,6 +59,9 @@ This example creates an OAB virtual directory on CASServer01 and configures the ## 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`. @@ -67,7 +71,6 @@ 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 @@ -77,13 +80,15 @@ 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 @@ -93,6 +98,9 @@ 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. @@ -105,7 +113,6 @@ 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 @@ -115,6 +122,9 @@ 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. @@ -124,7 +134,6 @@ 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 @@ -134,6 +143,9 @@ 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. @@ -146,7 +158,6 @@ 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 @@ -156,13 +167,15 @@ 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 @@ -172,13 +185,15 @@ 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 @@ -188,13 +203,15 @@ 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 @@ -204,13 +221,15 @@ Accept wildcard characters: False ``` ### -PollInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PollInterval parameter specifies the time interval in minutes that the distribution service polls the offline address book generation server for updates. The default value is 480 minutes (8 hours). ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -220,13 +239,15 @@ Accept wildcard characters: False ``` ### -Recovery + +> 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: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,6 +257,9 @@ Accept wildcard characters: False ``` ### -RequireSSL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: - $true: SSL encryption is required to connect to the virtual directory. This is the default value. @@ -245,7 +269,6 @@ The RequireSSL parameter specifies whether the client connection to the virtual Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,6 +278,9 @@ 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. @@ -266,7 +292,6 @@ 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 @@ -276,6 +301,9 @@ 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 @@ -287,7 +315,6 @@ The Server parameter specifies the Exchange server that hosts the virtual direct Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,13 +324,15 @@ 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 @@ -313,13 +342,15 @@ 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/exchange/New-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md similarity index 92% rename from exchange/exchange-ps/exchange/New-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md index cc267ae497..6ab2ed7946 100644 --- a/exchange/exchange-ps/exchange/New-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-offlineaddressbook applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-OfflineAddressBook -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-offlineaddressbook +schema: 2.0.0 +title: New-OfflineAddressBook --- # New-OfflineAddressBook @@ -89,13 +90,15 @@ If you configure OABs to use public folder distribution, but your organization d ## 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 OAB. 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 @@ -105,6 +108,9 @@ 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 or global address lists that are included in the OAB. You can use any value that uniquely identifies the address list. For example: - Name @@ -119,7 +125,6 @@ You can find the identify values of address lists and global address lists by us Type: AddressBookBaseIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -129,6 +134,9 @@ 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`. @@ -138,7 +146,6 @@ 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 @@ -148,13 +155,15 @@ Accept wildcard characters: False ``` ### -DiffRetentionPeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DiffRetentionPeriod parameter specifies the number of days that the OAB difference files are stored on the server. Valid values are integers from 7 to 1825, or the value unlimited. The default value is 30. ```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 @@ -164,6 +173,9 @@ 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,7 +184,6 @@ 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 @@ -182,6 +193,9 @@ Accept wildcard characters: False ``` ### -GeneratingMailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GeneratingMailbox parameter specifies the arbitration mailbox where the OAB is generated. Specifically, the arbitration mailbox must contain the OrganizationCapabilityOABGen value for the PersistedCapability property. An arbitration mailbox with this capability is also known as an organization mailbox. You can use any value that uniquely identifies the mailbox. For example: @@ -205,7 +219,6 @@ A single organization mailbox can generate multiple OABs (you can use the same v Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -215,6 +228,9 @@ Accept wildcard characters: False ``` ### -GlobalWebDistributionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are: @@ -228,7 +244,6 @@ In Exchange 2013 CU7 or later, we recommend that you use the value $true for thi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,6 +253,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsDefault parameter specifies whether the OAB is used by all mailboxes and mailbox databases that don't have an OAB specified. Valid values are: - $true: The OAB is the default OAB. @@ -247,7 +265,6 @@ The IsDefault parameter specifies whether the OAB is used by all mailboxes and m 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 @@ -257,6 +274,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabase + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The PublicFolderDatabase parameter specifies the public folder database that's used to distribute the OAB. You can use any value that uniquely identifies the database. For example: @@ -271,7 +291,6 @@ To use this parameter, the PublicFolderDistributionEnabled parameter must be set Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -281,6 +300,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDistributionEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The PublicFolderDistributionEnabled parameter specifies whether the OAB is distributed via public folders. If the value of the PublicFolderDistributionEnabled parameter is $true, the OAB is distributed via public folders. @@ -289,7 +311,6 @@ The PublicFolderDistributionEnabled parameter specifies whether the OAB is distr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -299,6 +320,9 @@ Accept wildcard characters: False ``` ### -Schedule + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Schedule parameter specifies the interval for generating the OAB in Exchange 2010 or earlier. @@ -327,7 +351,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -337,6 +360,9 @@ 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: @@ -352,7 +378,6 @@ 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 @@ -362,6 +387,9 @@ Accept wildcard characters: False ``` ### -ShadowMailboxDistributionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are: @@ -375,7 +403,6 @@ The value of this parameter is only meaningful if you have multiple organization Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -385,6 +412,9 @@ Accept wildcard characters: False ``` ### -SkipPublicFolderInitialization + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The SkipPublicFolderInitialization switch specifies whether to skip the immediate creation of the OAB public folders if you're creating an OAB that uses public folder distribution. You don't need to specify a value with this switch. @@ -395,7 +425,6 @@ The OAB isn't available for download until the next site folder maintenance cycl Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -405,6 +434,9 @@ Accept wildcard characters: False ``` ### -Versions + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Versions parameter specifies the OAB versions that are generated for client download. Valid values are: @@ -417,7 +449,6 @@ The Versions parameter specifies the OAB versions that are generated for client Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -427,6 +458,9 @@ Accept wildcard characters: False ``` ### -VirtualDirectories + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The VirtualDirectories parameter specifies the OAB virtual directories that accept requests to download the OAB. These locations are advertised in the Autodiscover service. @@ -449,7 +483,6 @@ In Exchange 2013 CU7 or later, we recommend that you set the GlobalWebDistributi Type: VirtualDirectoryIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -459,13 +492,15 @@ 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/exchange/New-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md similarity index 92% rename from exchange/exchange-ps/exchange/New-OnPremisesOrganization.md rename to exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md index bca7a914de..a88b1e955a 100644 --- a/exchange/exchange-ps/exchange/New-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-onpremisesorganization applicable: Exchange Online, Exchange Online Protection -title: New-OnPremisesOrganization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-onpremisesorganization +schema: 2.0.0 +title: New-OnPremisesOrganization --- # New-OnPremisesOrganization @@ -47,13 +48,15 @@ This example creates the OnPremisesOrganization object ExchangeMail in a Microso ## PARAMETERS ### -Name + +> Applicable: Exchange Online, Exchange Online Protection + The Name parameter specifies a friendly name for the on-premises Exchange organization object in the Microsoft 365 organization. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -63,13 +66,15 @@ Accept wildcard characters: False ``` ### -HybridDomains + +> Applicable: Exchange Online, Exchange Online Protection + The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -79,13 +84,15 @@ Accept wildcard characters: False ``` ### -InboundConnector + +> Applicable: Exchange Online, Exchange Online Protection + The InboundConnector parameter specifies the name of the inbound connector configured in Microsoft 365 for a hybrid deployment configured with an on-premises Exchange organization. ```yaml Type: InboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -95,13 +102,15 @@ Accept wildcard characters: False ``` ### -OrganizationGuid + +> Applicable: Exchange Online, Exchange Online Protection + The OrganizationGuid parameter specifies the globally unique identifier (GUID) of the on-premises Exchange organization object in the Microsoft 365 organization. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -111,13 +120,15 @@ Accept wildcard characters: False ``` ### -OutboundConnector + +> Applicable: Exchange Online, Exchange Online Protection + The OutboundConnector parameter specifies the name of the outbound connector configured on the EOP service for a hybrid deployment configured with an on-premises Exchange organization. ```yaml Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -127,13 +138,15 @@ 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 @@ -143,6 +156,9 @@ 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`. @@ -152,7 +168,6 @@ 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 @@ -162,13 +177,15 @@ Accept wildcard characters: False ``` ### -OrganizationName + +> Applicable: Exchange Online, Exchange Online Protection + The OrganizationName parameter specifies the Active Directory object name of the on-premises Exchange organization. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -178,13 +195,15 @@ Accept wildcard characters: False ``` ### -OrganizationRelationship + +> Applicable: Exchange Online, Exchange Online Protection + The OrganizationRelationship parameter specifies the organization relationship configured by the Hybrid Configuration wizard on the Microsoft 365 organization as part of a hybrid deployment with an on-premises Exchange organization. This organization relationship defines the federated sharing features enabled on the Microsoft 365 organization. ```yaml Type: OrganizationRelationshipIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -194,13 +213,15 @@ 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/exchange/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md similarity index 86% rename from exchange/exchange-ps/exchange/New-OrganizationRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md index 3e6caf94c5..a8a722cd59 100644 --- a/exchange/exchange-ps/exchange/New-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-organizationrelationship applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-OrganizationRelationship -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-organizationrelationship +schema: 2.0.0 +title: New-OrganizationRelationship --- # New-OrganizationRelationship @@ -91,13 +92,15 @@ The requesting organization only receives free/busy information with the time. ## 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 organization relationship. The maximum length is 64 characters. ```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: 1 @@ -107,13 +110,15 @@ Accept wildcard characters: False ``` ### -DomainNames + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DomainNames parameter specifies the SMTP domains of the external organization. You can specify multiple domains separated by commas (for example, "contoso.com","northamerica.contoso.com"), limited to 238 domains in one request. ```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: True Position: Named @@ -123,6 +128,9 @@ Accept wildcard characters: False ``` ### -ArchiveAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. @@ -132,7 +140,6 @@ The ArchiveAccessEnabled parameter specifies whether the organization relationsh 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 @@ -142,6 +149,9 @@ 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`. @@ -151,7 +161,6 @@ 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 @@ -161,6 +170,9 @@ Accept wildcard characters: False ``` ### -DeliveryReportEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. @@ -172,7 +184,6 @@ For message tracking to work in a cross-premises Exchange scenario, this paramet 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 @@ -182,6 +193,9 @@ 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. @@ -190,7 +204,6 @@ 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 @@ -200,6 +213,9 @@ 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 to enable the organization relationship. Valid values are: - $true: The organization relationship is enabled. This is the default value. @@ -209,7 +225,6 @@ The Enabled parameter specifies whether to enable the organization relationship. 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 @@ -219,6 +234,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. @@ -230,7 +248,6 @@ You control the free/busy access level and scope by using the FreeBusyAccessLeve 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 @@ -240,6 +257,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are: - None: No free/busy access. @@ -252,7 +272,6 @@ This parameter is only meaningful when the FreeBusyAccessEnabled parameter value Type: FreeBusyAccessLevel 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 @@ -262,6 +281,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example: - Name @@ -275,7 +297,6 @@ This parameter is only meaningful when the FreeBusyAccessEnabled parameter value Type: GroupIdParameter 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 @@ -285,6 +306,9 @@ Accept wildcard characters: False ``` ### -MailboxMoveCapability + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The MailboxMoveCapability parameter is used in cross-tenant mailbox migrations. Valid values are: @@ -300,7 +324,6 @@ For more information, see [Cross-tenant mailbox migration](https://learn.microso Type: MailboxMoveCapability Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -310,6 +333,9 @@ Accept wildcard characters: False ``` ### -MailboxMoveEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. @@ -319,7 +345,6 @@ The MailboxMoveEnabled parameter specifies whether the organization relationship 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 @@ -329,6 +354,9 @@ Accept wildcard characters: False ``` ### -MailboxMovePublishedScopes + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The MailboxMovePublishedScopes parameter is used in cross-tenant mailbox migrations to specify the mail-enabled security groups whose members are allowed to migrate. You can use any value that uniquely identifies the group. For example: @@ -346,7 +374,6 @@ For more information, see [Cross-tenant mailbox migration](https://learn.microso Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -356,6 +383,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. @@ -367,7 +397,6 @@ You control the MailTips access level by using the MailTipsAccessLevel parameter 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 @@ -377,6 +406,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessLevel parameter specifies the level of MailTips data that's externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. @@ -389,7 +421,6 @@ This parameter is only meaningful when the MailTipsAccessEnabled parameter value Type: MailTipsAccessLevel 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 @@ -399,6 +430,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example: - Name @@ -422,7 +456,6 @@ This restriction only applies to mailboxes, mail users, and mail contacts. It do Type: GroupIdParameter 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 @@ -432,6 +465,9 @@ Accept wildcard characters: False ``` ### -OAuthApplicationId + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The OAuthApplicationId is used in cross-tenant mailbox migrations to specify the application ID of the mailbox migration app that you consented to. For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). @@ -440,7 +476,6 @@ The OAuthApplicationId is used in cross-tenant mailbox migrations to specify the Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -450,13 +485,15 @@ Accept wildcard characters: False ``` ### -OrganizationContact + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OrganizationContact parameter specifies the email address that can be used to contact the external organization (for example, administrator@fourthcoffee.com). ```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 @@ -466,6 +503,9 @@ Accept wildcard characters: False ``` ### -PhotosEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. @@ -475,7 +515,6 @@ The PhotosEnabled parameter specifies whether photos for users in the internal o 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 @@ -485,13 +524,15 @@ Accept wildcard characters: False ``` ### -TargetApplicationUri + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetApplicationUri parameter specifies the target Uniform Resource Identifier (URI) of the external organization. The TargetApplicationUri parameter is specified by Exchange when requesting a delegated token for the external organization to fetch free and busy information, for example, mail.contoso.com. ```yaml Type: Uri 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 @@ -501,13 +542,15 @@ Accept wildcard characters: False ``` ### -TargetAutodiscoverEpr + +> Applicable: Exchange Server 2010, 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, for example, `https://contoso.com/autodiscover/autodiscover.svc/wssecurity`. Exchange uses the Autodiscover service to automatically detect the correct Exchange server endpoint to use for external requests. ```yaml Type: Uri 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 @@ -517,13 +560,15 @@ Accept wildcard characters: False ``` ### -TargetOwaURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook Web App) URL of the external organization defined in the organization relationship. It's used for Outlook on the web redirection in a cross-premise Exchange scenario. Configuring this attribute enables users in the organization to use their current Outlook on the web URL to access Outlook on the web in the external organization. ```yaml Type: Uri 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 @@ -533,6 +578,9 @@ Accept wildcard characters: False ``` ### -TargetSharingEpr + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services for the external organization. If you use this parameter, this URL is always used to reach the external Exchange server. The URL that's specified by the TargetAutodiscoverEpr parameter isn't used to locate the external Exchange server. @@ -541,7 +589,6 @@ If you use this parameter, this URL is always used to reach the external Exchang Type: Uri 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 @@ -551,13 +598,15 @@ 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/exchange/New-OrganizationSegment.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationSegment.md similarity index 97% rename from exchange/exchange-ps/exchange/New-OrganizationSegment.md rename to exchange/exchange-ps/ExchangePowerShell/New-OrganizationSegment.md index a8a7015875..53fa9d343e 100644 --- a/exchange/exchange-ps/exchange/New-OrganizationSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationSegment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-organizationsegment applicable: Security & Compliance -title: New-OrganizationSegment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-organizationsegment +schema: 2.0.0 +title: New-OrganizationSegment --- # New-OrganizationSegment @@ -58,13 +59,15 @@ In this example, we defined a segment called LocalFTE that includes people who a ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the organization segment. 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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,6 +98,9 @@ Accept wildcard characters: False ``` ### -UserGroupFilter + +> Applicable: Security & Compliance + The UserGroupFilter parameter uses OPATH filter syntax to specify the members of the organization segment. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"MemberOf -eq 'Engineering Department'"` or `"ExtensionAttribute1 -eq 'DayTrader'"`). - 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. @@ -108,7 +116,6 @@ Use the same property for all of your segments, and verify that your segments do Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -118,13 +125,15 @@ 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/exchange/New-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md similarity index 93% rename from exchange/exchange-ps/exchange/New-OutboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md index 2121c66207..3f4d4eb7e3 100644 --- a/exchange/exchange-ps/exchange/New-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-outboundconnector applicable: Exchange Online, Exchange Online Protection -title: New-OutboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-outboundconnector +schema: 2.0.0 +title: New-OutboundConnector --- # New-OutboundConnector @@ -63,13 +64,15 @@ This example creates the Outbound connector named Contoso Outbound Connector wit ## PARAMETERS ### -Name + +> Applicable: Exchange Online, Exchange Online Protection + The Name parameter specifies the unique name for the connector. 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: 1 @@ -79,6 +82,9 @@ Accept wildcard characters: False ``` ### -AllAcceptedDomains + +> Applicable: Exchange Online, Exchange Online Protection + The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. @@ -90,7 +96,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -100,6 +105,9 @@ 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. @@ -113,7 +121,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -123,13 +130,15 @@ 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 @@ -139,6 +148,9 @@ 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`. @@ -148,7 +160,6 @@ 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 @@ -158,6 +169,9 @@ Accept wildcard characters: False ``` ### -ConnectorSource + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorSource parameter specifies how the connector is created. Valid values are: - Default: The connector is manually created. This is the default value when you use this cmdlet, and we recommend that you don't change this value. @@ -168,7 +182,6 @@ The ConnectorSource parameter specifies how the connector is created. Valid valu Type: TenantConnectorSource Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -178,6 +191,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid values are: - Partner: The connector services domains that are external to your organization. @@ -187,7 +203,6 @@ The ConnectorType parameter specifies a category for the domains that are servic Type: TenantConnectorType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -197,6 +212,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online, Exchange Online Protection + The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are: - $true: The connector is enabled. This is the default value. @@ -206,7 +224,6 @@ The Enabled parameter specifies whether to enable or disable the Outbound connec Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -216,6 +233,9 @@ Accept wildcard characters: False ``` ### -IsTransportRuleScoped + +> Applicable: Exchange Online, Exchange Online Protection + The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. @@ -227,7 +247,6 @@ You scope a transport rule to an Outbound connector by using the RouteMessageOut Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -237,13 +256,15 @@ Accept wildcard characters: False ``` ### -LinkForModifiedConnector + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -253,6 +274,9 @@ Accept wildcard characters: False ``` ### -RecipientDomains + +> Applicable: Exchange Online, Exchange Online Protection + The RecipientDomains parameter specifies the domains that the Outbound connector routes mail to. You can specify multiple domains separated by commas. 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. @@ -261,7 +285,6 @@ You can use a wildcard character to specify all subdomains of a specified domain Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -271,6 +294,9 @@ Accept wildcard characters: False ``` ### -RouteAllMessagesViaOnPremises + +> Applicable: Exchange Online, Exchange Online Protection + The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system in hybrid organizations. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. @@ -282,7 +308,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -292,6 +317,9 @@ Accept wildcard characters: False ``` ### -SenderRewritingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. @@ -303,7 +331,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -313,6 +340,9 @@ Accept wildcard characters: False ``` ### -SmartHosts + +> Applicable: Exchange Online, Exchange Online Protection + The SmartHosts parameter specifies the smart host that the Outbound connector uses to route mail. Valid values are: - FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record: For example, mail.contoso.com. @@ -327,7 +357,6 @@ This parameter is required if you use the value $false for the UseMxRecord param Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -337,6 +366,9 @@ Accept wildcard characters: False ``` ### -TestMode + +> Applicable: Exchange Online, Exchange Online Protection + The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. @@ -346,7 +378,6 @@ The TestMode parameter specifies whether you want to enabled or disable test mod Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -356,6 +387,9 @@ Accept wildcard characters: False ``` ### -TlsDomain + +> Applicable: Exchange Online, Exchange Online Protection + The TlsDomain parameter specifies the domain name that the Outbound connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. A valid value for this parameter is an SMTP domain. Wildcards are supported to specify all subdomains of a domain (for example, \*.contoso.com), but you can't embed the wildcard character within the domain (for example, domain.\*.contoso.com). @@ -366,7 +400,6 @@ This parameter meaningful only when the TlsSettings value is DomainValidation. Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -376,6 +409,9 @@ Accept wildcard characters: False ``` ### -TlsSettings + +> Applicable: Exchange Online, Exchange Online Protection + The TlsSettings parameter specifies the TLS authentication level that's used for outbound TLS connections established by this Outbound connector. Valid values are: - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. @@ -387,7 +423,6 @@ The TlsSettings parameter specifies the TLS authentication level that's used for Type: TlsAuthLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -397,6 +432,9 @@ Accept wildcard characters: False ``` ### -UseMXRecord + +> Applicable: Exchange Online, Exchange Online Protection + The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: - $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. @@ -406,7 +444,6 @@ The UseMXRecord parameter enables or disables DNS routing for the connector. Val Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -416,13 +453,15 @@ 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/exchange/New-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md similarity index 86% rename from exchange/exchange-ps/exchange/New-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md index 871a1233f5..de55ce1d4a 100644 --- a/exchange/exchange-ps/exchange/New-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-outlookprotectionrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-OutlookProtectionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-outlookprotectionrule +schema: 2.0.0 +title: New-OutlookProtectionRule --- # New-OutlookProtectionRule @@ -58,13 +59,15 @@ This example applies the AD RMS template named Template-Contoso to messages sent ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the rule. ```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 @@ -74,13 +77,15 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionTemplate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplyRightsProtectionTemplate parameter specifies the AD RMS template to apply to the message. An AD RMS template can be specified using the template name. Use the Get-RMSTemplate cmdlet to retrieve templates from your AD RMS server. ```yaml Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -90,6 +95,9 @@ 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`. @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether the Outlook protection rules are enabled. New Outlook protection rules are enabled by default. To create a rule without enabling it, set the Enabled parameter to $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 @@ -143,6 +154,9 @@ 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. Use this switch to hide the confirmation prompt when you create rules without any conditions (rules without conditions apply to all messages). @@ -151,7 +165,6 @@ Use this switch to hide the confirmation prompt when you create rules without an 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,13 +174,15 @@ Accept wildcard characters: False ``` ### -FromDepartment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FromDepartment parameter specifies the sender's department as a condition. The user's department property is compared with the value specified. ```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 @@ -177,13 +192,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Priority parameter specifies whether to set the order of processing of Outlook protection rules. Rules with a lower priority value are executed first. ```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 @@ -193,6 +210,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SentTo parameter specifies one or more recipients as a rule condition. You can use any value that uniquely identifies the internal recipient. For example: - Name @@ -214,7 +234,6 @@ This parameter doesn't accept wildcard characters. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -224,6 +243,9 @@ Accept wildcard characters: False ``` ### -SentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SentToScope parameter specifies the message scope as a condition. You can use one of the following values: - InOrganization: This value is for messages sent to recipients within the organization. @@ -233,7 +255,6 @@ The SentToScope parameter specifies the message scope as a condition. You can us Type: ToUserScope Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -243,13 +264,15 @@ Accept wildcard characters: False ``` ### -UserCanOverride + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserCanOverride parameter specifies whether users can override actions taken by Outlook protection rules. By default, users can override actions taken by Outlook protection rules. When set to $false, the UserCanOverride parameter prevents the user from overriding the rule when sending the message. ```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 @@ -259,13 +282,15 @@ 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/exchange/New-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md similarity index 91% rename from exchange/exchange-ps/exchange/New-OutlookProvider.md rename to exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md index 8552c51259..c928dcb938 100644 --- a/exchange/exchange-ps/exchange/New-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-outlookprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-OutlookProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-outlookprovider +schema: 2.0.0 +title: New-OutlookProvider --- # New-OutlookProvider @@ -52,13 +53,15 @@ This example creates the AutoDiscoverConfig object Autodiscover1 and the specifi ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter provides the common name of the AutoDiscoverConfig object. This can be a user-friendly name for identification. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ 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,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,13 +110,15 @@ 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/exchange/New-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md index b25a96ccdb..8b4e5e8c6e 100644 --- a/exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-owamailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-OwaMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-owamailboxpolicy +schema: 2.0.0 +title: New-OwaMailboxPolicy --- # New-OwaMailboxPolicy @@ -48,13 +49,15 @@ This example creates the Outlook on the web mailbox policy named Corporate. ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the new 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 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IsDefault switch specifies whether the policy is the default policy. You don't need to specify a value with this switch. @@ -111,7 +121,6 @@ If another policy is currently set as the default, using this switch replaces th Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -121,13 +130,15 @@ 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/exchange/New-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md index 703e02a8bd..8cd20fd1cc 100644 --- a/exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-owavirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-OwaVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-owavirtualdirectory +schema: 2.0.0 +title: New-OwaVirtualDirectory --- # New-OwaVirtualDirectory @@ -58,6 +59,9 @@ This example creates the Outlook on the web virtual directory in an IIS website ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -66,7 +70,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: 1 @@ -76,13 +79,15 @@ Accept wildcard characters: False ``` ### -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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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`. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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,6 +154,9 @@ 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. @@ -155,7 +169,6 @@ 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 @@ -165,6 +178,9 @@ 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. @@ -174,7 +190,6 @@ 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 @@ -184,6 +199,9 @@ 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. @@ -196,7 +214,6 @@ 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 @@ -206,6 +223,9 @@ 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 @@ -235,7 +255,6 @@ Although you can specify any of these values, whether or not the authentication Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -245,13 +264,15 @@ 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. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -261,13 +282,15 @@ 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. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,13 +300,15 @@ 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 @@ -293,6 +318,9 @@ 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. @@ -304,7 +332,6 @@ 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 @@ -314,6 +341,9 @@ 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 @@ -325,7 +355,6 @@ 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 @@ -335,13 +364,15 @@ 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 @@ -351,13 +382,15 @@ 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/exchange/New-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md similarity index 89% rename from exchange/exchange-ps/exchange/New-PartnerApplication.md rename to exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md index d0ef93326f..bd022d31d4 100644 --- a/exchange/exchange-ps/exchange/New-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-partnerapplication applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-PartnerApplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-partnerapplication +schema: 2.0.0 +title: New-PartnerApplication --- # New-PartnerApplication @@ -73,13 +74,15 @@ This example creates a new HRApp partner application named HRApp. ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the partner application. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -89,13 +92,15 @@ Accept wildcard characters: False ``` ### -ApplicationIdentifier + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplicationIdentifier parameter specifies a unique application identifier for the partner application that uses an authorization server. When specifying a value for the ApplicationIdentifier parameter, you must also use the UseAuthServer parameter. ```yaml Type: String Parameter Sets: ACSTrustApplication Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -105,6 +110,9 @@ Accept wildcard characters: False ``` ### -AuthMetadataUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AuthMetadataUrl parameter specifies the URL that Exchange can retrieve the AuthMetadata document from for a partner application that doesn't use an authorization server. When specifying the AuthMetadataUrl parameter for a partner application, you can't specify the ApplicationIdentifier and UseAuthServer parameters. @@ -113,7 +121,6 @@ The AuthMetadataUrl parameter specifies the URL that Exchange can retrieve the A Type: String Parameter Sets: AuthMetadataUrl Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -123,13 +130,15 @@ Accept wildcard characters: False ``` ### -AcceptSecurityIdentifierInformation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptSecurityIdentifierInformation parameter specifies whether Exchange should accept security identifiers (SIDs) from another trusted Active Directory forest for the partner application. By default, new partner applications are configured to not accept SIDs from another forest. If you're in deployment with a trusted forest, set the parameter to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -139,6 +148,9 @@ Accept wildcard characters: False ``` ### -AccountType + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: - OrganizationalAccount (This is the default value) @@ -148,7 +160,6 @@ The AccountType parameter specifies the type of Microsoft account that's require Type: SupportedAccountType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -158,6 +169,9 @@ Accept wildcard characters: False ``` ### -ActAsPermissions + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -166,7 +180,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -176,6 +189,9 @@ Accept wildcard characters: False ``` ### -AppOnlyPermissions + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -184,7 +200,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -194,6 +209,9 @@ 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`. @@ -203,7 +221,6 @@ 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 @@ -213,6 +230,9 @@ 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. @@ -221,7 +241,6 @@ 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 @@ -231,13 +250,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether the partner application is enabled. By default, new partner applications are enabled. Set the parameter to $false to create the application configuration in a disabled state. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -247,6 +268,9 @@ Accept wildcard characters: False ``` ### -IssuerIdentifier + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -255,7 +279,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -265,13 +288,15 @@ Accept wildcard characters: False ``` ### -LinkedAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LinkedAccount parameter specifies a linked Active Directory user account for the application. Exchange evaluates Role Based Access Control (RBAC) permissions for the linked account when authorizing a token used to perform a task. ```yaml Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -281,6 +306,9 @@ Accept wildcard characters: False ``` ### -Realm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Realm parameter specifies a security realm for the partner application. If the token is from a domain that's not an accepted domain, Exchange checks the realm specified in the token. In such a scenario, only tokens with the same realm specified in the partner application can access Exchange resources. @@ -289,7 +317,6 @@ The Realm parameter specifies a security realm for the partner application. If t Type: String Parameter Sets: ACSTrustApplication Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -299,6 +326,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch. @@ -309,7 +339,6 @@ We don't recommend using this switch in a production environment. Type: SwitchParameter Parameter Sets: AuthMetadataUrl Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -319,13 +348,15 @@ 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/exchange/New-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md index cf3415db3c..6b3721e083 100644 --- a/exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-phishsimoverridepolicy applicable: Exchange Online -title: New-PhishSimOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-phishsimoverridepolicy +schema: 2.0.0 +title: New-PhishSimOverridePolicy --- # New-PhishSimOverridePolicy @@ -46,13 +47,15 @@ This example creates the phishing simulation override policy named PhishSimOverr ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name will be PhishSimOverridePolicy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -62,13 +65,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -78,6 +83,9 @@ 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`. @@ -87,7 +95,6 @@ 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 @@ -97,13 +104,15 @@ 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 @@ -113,6 +122,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the policy is enabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -122,7 +134,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -132,6 +143,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -140,7 +154,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -150,6 +163,9 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + In Exchange Online 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. The WhatIf switch doesn't work in Security & Compliance PowerShell. @@ -158,7 +174,6 @@ The WhatIf switch doesn't work in Security & Compliance PowerShell. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/New-PolicyTipConfig.md rename to exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md index c32359ad77..96681f510e 100644 --- a/exchange/exchange-ps/exchange/New-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-policytipconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-PolicyTipConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-policytipconfig +schema: 2.0.0 +title: New-PolicyTipConfig --- # New-PolicyTipConfig @@ -54,6 +55,9 @@ This example sets the informational URL in Policy Tips to the value `https://www ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the custom Policy Tip you want to modify. Valid input for this parameter is one of the following values: - `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. @@ -65,7 +69,6 @@ There can be only one custom Policy Tip with the value Url for the Name paramete Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -75,13 +78,15 @@ Accept wildcard characters: False ``` ### -Value + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Value parameter specifies the text that's displayed by the Policy Tip. 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, Exchange Online Required: True Position: Named @@ -91,6 +96,9 @@ 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`. @@ -100,7 +108,6 @@ 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,6 +117,9 @@ 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. @@ -118,7 +128,6 @@ 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 @@ -128,13 +137,15 @@ 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/exchange/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md similarity index 91% rename from exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md index fd597096d0..2962031ed9 100644 --- a/exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-powershellvirtualdirectory applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-PowerShellVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-powershellvirtualdirectory +schema: 2.0.0 +title: New-PowerShellVirtualDirectory --- # New-PowerShellVirtualDirectory @@ -55,13 +56,15 @@ This example creates a Windows PowerShell virtual directory and configures it to ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide will have the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks ("). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -71,13 +74,15 @@ Accept wildcard characters: False ``` ### -BasicAuthentication + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BasicAuthentication parameter specifies whether Basic authentication is enabled on the PowerShell virtual directory. The valid values are $true and $false. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -87,6 +92,9 @@ 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`. @@ -96,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,6 +131,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags + +> Applicable: 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. @@ -134,7 +146,6 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -144,6 +155,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList + +> Applicable: 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. @@ -153,7 +167,6 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -163,6 +176,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking + +> Applicable: 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. @@ -175,7 +191,6 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -185,13 +200,15 @@ Accept wildcard characters: False ``` ### -ExternalUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalUrl parameter specifies the external URL that the PowerShell virtual directory points to. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -201,13 +218,15 @@ Accept wildcard characters: False ``` ### -InternalUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalUrl parameter specifies the internal URL that the PowerShell virtual directory points to. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -217,13 +236,15 @@ Accept wildcard characters: False ``` ### -RequireSSL + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireSSL parameter specifies whether the PowerShell virtual directory should require that the client connection be made using Secure Sockets Layer (SSL). The valid values are $true and $false. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -233,6 +254,9 @@ 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. @@ -244,7 +268,6 @@ 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 @@ -254,6 +277,9 @@ 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 @@ -265,7 +291,6 @@ 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 @@ -275,13 +300,15 @@ 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 @@ -291,13 +318,15 @@ Accept wildcard characters: False ``` ### -WindowsAuthentication + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the PowerShell virtual directory. The valid values are $true and $false. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md similarity index 94% rename from exchange/exchange-ps/exchange/New-ProtectionAlert.md rename to exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md index f0b41f21ed..7e3fd26570 100644 --- a/exchange/exchange-ps/exchange/New-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-protectionalert applicable: Security & Compliance -title: New-ProtectionAlert -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-protectionalert +schema: 2.0.0 +title: New-ProtectionAlert --- # New-ProtectionAlert @@ -77,6 +78,9 @@ This example creates an alert policy that triggers an alert whenever anyone in t ## PARAMETERS ### -Category + +> Applicable: Security & Compliance + The Category parameter specifies a category for the alert policy. Valid values are: - AccessGovernance @@ -94,7 +98,6 @@ When an activity occurs that matches the conditions of the alert policy, the ale Type: AlertRuleCategory Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -104,13 +107,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the alert 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: Named @@ -120,13 +125,15 @@ Accept wildcard characters: False ``` ### -NotifyUser + +> Applicable: Security & Compliance + The NotifyUser parameter specifies the SMTP address of the user who receives notification messages for the alert policy. You can specify multiple values separated by commas. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -136,6 +143,9 @@ Accept wildcard characters: False ``` ### -ThreatType + +> Applicable: Security & Compliance + The ThreatType parameter specifies the type of activities that are monitored by the alert policy. Valid values are: - Activity @@ -149,7 +159,6 @@ You can't change this value after you create the alert policy. Type: ThreatAlertType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -159,6 +168,9 @@ Accept wildcard characters: False ``` ### -AggregationType + +> Applicable: Security & Compliance + The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. @@ -169,7 +181,6 @@ The AggregationType parameter specifies the how the alert policy triggers alerts Type: AlertAggregationType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -179,6 +190,9 @@ Accept wildcard characters: False ``` ### -AlertBy + +> Applicable: Security & Compliance + The AlertBy parameter specifies the scope for aggregated alert policies. Valid values are determined by the ThreatType parameter value: - Activity: Valid values are User or $null (blank, which is the default value). If you don't use the value User, the scope of the alert policy is the entire organization. @@ -192,7 +206,6 @@ You can't use this parameter when the AggregationType parameter value is None (a Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -202,13 +215,15 @@ Accept wildcard characters: False ``` ### -AlertFor + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -218,13 +233,15 @@ 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 @@ -234,6 +251,9 @@ 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`. @@ -243,7 +263,6 @@ 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,13 +272,15 @@ Accept wildcard characters: False ``` ### -CorrelationPolicyId + +> Applicable: Security & Compliance + {{ Fill CorrelationPolicyId Description }} ```yaml Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -269,13 +290,15 @@ Accept wildcard characters: False ``` ### -CustomProperties + +> Applicable: Security & Compliance + {{ Fill CustomProperties Description }} ```yaml Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -285,13 +308,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Security & Compliance + The Description parameter specifies descriptive text for the alert policy. 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 @@ -301,6 +326,9 @@ Accept wildcard characters: False ``` ### -Disabled + +> Applicable: Security & Compliance + The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. @@ -310,7 +338,6 @@ The Disabled parameter enables or disables the alert policy. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -320,6 +347,9 @@ Accept wildcard characters: False ``` ### -Filter + +> Applicable: Security & Compliance + 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. @@ -378,7 +408,6 @@ Malware Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -388,13 +417,15 @@ Accept wildcard characters: False ``` ### -LogicalOperationName + +> Applicable: Security & Compliance + {{ Fill LogicalOperationName Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -404,6 +435,9 @@ Accept wildcard characters: False ``` ### -NotificationCulture + +> Applicable: Security & Compliance + The NotificationCulture parameter specifies the language or locale that's used for notifications. 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). @@ -412,7 +446,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -422,13 +455,15 @@ Accept wildcard characters: False ``` ### -NotificationEnabled + +> Applicable: Security & Compliance + {{ Fill NotificationEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -438,6 +473,9 @@ Accept wildcard characters: False ``` ### -NotifyUserOnFilterMatch + +> Applicable: Security & Compliance + The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). @@ -449,7 +487,6 @@ You can't use this parameter when the AggregationType parameter value is None (a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -459,6 +496,9 @@ Accept wildcard characters: False ``` ### -NotifyUserSuppressionExpiryDate + +> Applicable: Security & Compliance + The NotifyUserSuppressionExpiryDate parameter specifies whether to temporarily suspend notifications for the alert policy. Until the specified date-time, no notifications are sent for detected activities. 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". @@ -467,7 +507,6 @@ 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 @@ -477,6 +516,9 @@ Accept wildcard characters: False ``` ### -NotifyUserThrottleThreshold + +> Applicable: Security & Compliance + The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. @@ -486,7 +528,6 @@ The NotifyUserThrottleThreshold parameter specifies the maximum number of notifi Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -496,6 +537,9 @@ Accept wildcard characters: False ``` ### -NotifyUserThrottleWindow + +> Applicable: Security & Compliance + The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. @@ -505,7 +549,6 @@ The NotifyUserThrottleWindow parameter specifies the time interval in minutes th Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -515,6 +558,9 @@ Accept wildcard characters: False ``` ### -Operation + +> Applicable: Security & Compliance + The Operation parameter specifies the activities that are monitored by the alert policy. For the list of available activities, see the Audited activities tab at [Audited activities](https://learn.microsoft.com/purview/audit-log-activities). Although this parameter is technically capable of accepting multiple values separated by commas, multiple values don't work. @@ -525,7 +571,6 @@ You can only use this parameter when the ThreatType parameter has the value Acti Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -535,13 +580,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypes + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -551,13 +598,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypesForCounting + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypesForCounting Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -567,13 +616,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypesThreshold + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypesThreshold Description }} ```yaml Type: System.UInt64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -583,6 +634,9 @@ Accept wildcard characters: False ``` ### -Severity + +> Applicable: Security & Compliance + The Severity parameter specifies the severity of the detection. Valid values are: - Low (This is the default value) @@ -593,7 +647,6 @@ The Severity parameter specifies the severity of the detection. Valid values are Type: RuleSeverity Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -603,6 +656,9 @@ Accept wildcard characters: False ``` ### -Threshold + +> Applicable: Security & Compliance + The Threshold parameter specifies the number of detections that trigger the alert policy within the time period specified by the TimeWindow parameter. A valid value is an integer that's greater than or equal to 3. You can only use this parameter when the AggregationType parameter value is SimpleAggregation. @@ -611,7 +667,6 @@ You can only use this parameter when the AggregationType parameter value is Simp Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -621,6 +676,9 @@ Accept wildcard characters: False ``` ### -TimeWindow + +> Applicable: Security & Compliance + The TimeWindow parameter specifies the time interval in minutes for number of detections specified by the Threshold parameter. A valid value is an integer that's greater than 60 (one hour). You can only use this parameter when the AggregationType parameter value is SimpleAggregation. @@ -629,7 +687,6 @@ You can only use this parameter when the AggregationType parameter value is Simp Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -639,13 +696,15 @@ Accept wildcard characters: False ``` ### -UseCreatedDateTime + +> Applicable: Security & Compliance + {{ Fill UseCreatedDateTime Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -655,13 +714,15 @@ Accept wildcard characters: False ``` ### -VolumeThreshold + +> Applicable: Security & Compliance + {{ Fill VolumeThreshold Description }} ```yaml Type: System.UInt64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -671,13 +732,15 @@ 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/exchange/New-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md similarity index 89% rename from exchange/exchange-ps/exchange/New-PublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md index 71c11a5ab5..6fd47d78b9 100644 --- a/exchange/exchange-ps/exchange/New-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-PublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolder +schema: 2.0.0 +title: New-PublicFolder --- # New-PublicFolder @@ -68,13 +69,15 @@ This example creates the public folder Support in the North\_America hierarchy p ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name for the public folder. ```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 @@ -84,6 +87,9 @@ 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`. @@ -93,7 +99,6 @@ 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 @@ -103,6 +108,9 @@ 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. @@ -111,7 +119,6 @@ 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 @@ -121,13 +128,15 @@ Accept wildcard characters: False ``` ### -EformsLocaleId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EformsLocaleId parameter specifies the locale-specific version of the e-forms library. The valid input for the EformsLocaleId parameter is the string names listed in the Culture Name column in the Microsoft .NET Class Library class reference available at [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo). ```yaml Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -137,6 +146,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailbox parameter specifies the hierarchy public folder mailbox where you want this public folder created. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -154,7 +166,6 @@ The Mailbox parameter specifies the hierarchy public folder mailbox where you wa Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -164,13 +175,15 @@ Accept wildcard characters: False ``` ### -Path + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Path parameter specifies the location of the folder in the folder hierarchy, for example, \\Legal\\Cases. ```yaml Type: PublicFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -180,6 +193,9 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Server parameter specifies the Mailbox server where you want to create the new public folder. You can use any value that uniquely identifies the server. For example: @@ -195,7 +211,6 @@ If you don't use this parameter, the command is run on the local server if the s Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -205,13 +220,15 @@ 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/exchange/New-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md similarity index 95% rename from exchange/exchange-ps/exchange/New-PublicFolderDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md index 992f21daac..fb40c3a2da 100644 --- a/exchange/exchange-ps/exchange/New-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabase applicable: Exchange Server 2010 -title: New-PublicFolderDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabase +schema: 2.0.0 +title: New-PublicFolderDatabase --- # New-PublicFolderDatabase @@ -47,13 +48,15 @@ This example creates the public folder database PFDB01. ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies the name of the new public folder database. The name must be unique to your entire organization. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -63,6 +66,9 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2010 + The Server parameter specifies the Mailbox server where you want to create the new public folder database. You can use any value that uniquely identifies the server. For example: - Name @@ -76,7 +82,6 @@ A server can have only one public folder database. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -86,6 +91,9 @@ 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`. @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ 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 @@ -121,13 +130,15 @@ Accept wildcard characters: False ``` ### -EdbFilePath + +> Applicable: Exchange Server 2010 + The EdbFilePath parameter specifies the full path of the public folder database files. The default location is `%ExchangeInstallPath%Mailbox\\.edb` ```yaml Type: EdbFilePath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -137,13 +148,15 @@ Accept wildcard characters: False ``` ### -LogFolderPath + +> Applicable: Exchange Server 2010 + The LogFolderPath parameter specifies the folder location for log files. The default location is `%ExchangeInstallPath%Mailbox\`. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -153,13 +166,15 @@ 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/exchange/New-PublicFolderDatabaseRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md similarity index 95% rename from exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md index 332ac3deec..1803578826 100644 --- a/exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabaserepairrequest applicable: Exchange Server 2010 -title: New-PublicFolderDatabaseRepairRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfolderdatabaserepairrequest +schema: 2.0.0 +title: New-PublicFolderDatabaseRepairRequest --- # New-PublicFolderDatabaseRepairRequest @@ -55,6 +56,9 @@ This example only detects and reports on replication issues on public folder dat ## PARAMETERS ### -Database + +> Applicable: Exchange Server 2010 + The Database parameter specifies the public folder database that you want to repair. You can use any value that uniquely identifies the database. For example: - Name @@ -65,7 +69,6 @@ The Database parameter specifies the public folder database that you want to rep Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -75,13 +78,15 @@ Accept wildcard characters: False ``` ### -CorruptionType + +> Applicable: Exchange Server 2010 + The CorruptionType parameter specifies the type of corruption that you want to detect and repair. The only available value is ReplState. ```yaml Type: PublicFolderDatabaseCorruptionType[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -91,6 +96,9 @@ 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`. @@ -100,7 +108,6 @@ 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 @@ -110,13 +117,15 @@ Accept wildcard characters: False ``` ### -DetectOnly + +> Applicable: Exchange Server 2010 + The DetectOnly switch specifies that you want this command to report errors, but not fix them. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -126,13 +135,15 @@ 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 @@ -142,13 +153,15 @@ 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/exchange/New-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md index 8707577d81..7a8fea7ee7 100644 --- a/exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfoldermigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-PublicFolderMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfoldermigrationrequest +schema: 2.0.0 +title: New-PublicFolderMigrationRequest --- # New-PublicFolderMigrationRequest @@ -63,13 +64,15 @@ This example creates a public folder migration request from the Exchange 2010 so ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the public folder migration request. 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: False Position: 1 @@ -79,6 +82,9 @@ Accept wildcard characters: False ``` ### -SourceDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SourceDatabase parameter specifies the target database for the public folders. You can use any value that uniquely identifies the database. For example: - Name @@ -89,7 +95,6 @@ The SourceDatabase parameter specifies the target database for the public folder Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -99,6 +104,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -107,7 +115,6 @@ You need to use this switch if you set the LargeItemLimit parameter to a value o Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -117,6 +124,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -125,7 +135,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -135,13 +144,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BatchName parameter specifies a descriptive name for the public folder migration batch. You can use the BatchName parameter as a search string when you use the Get-PublicFolderMigrationRequest cmdlet. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -151,13 +162,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -167,6 +180,9 @@ 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`. @@ -176,7 +192,6 @@ 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 @@ -186,6 +201,9 @@ Accept wildcard characters: False ``` ### -CSVData + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CSVData parameter specifies the mapping file output generated by the PublicFoldertoMailboxMapGenerator.ps1 script. Use this parameter for local migrations. 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`). @@ -196,7 +214,6 @@ You can't use this parameter with the CSVStream parameter, but you need to use i Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -206,6 +223,9 @@ Accept wildcard characters: False ``` ### -CSVStream + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CSVStream parameter specifies the mapping file output generated by the PublicFoldertoMailboxMapGenerator.ps1 script. Use this parameter for remote migrations. You can't use this parameter with the CSVData parameter, but you need to use it if you don't use CSVData parameter. @@ -214,7 +234,6 @@ You can't use this parameter with the CSVData parameter, but you need to use it Type: Stream Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -224,13 +243,15 @@ 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 @@ -240,13 +261,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -256,6 +279,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -271,7 +297,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -281,13 +306,15 @@ Accept wildcard characters: False ``` ### -MigrationMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,6 +324,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lowest @@ -312,7 +342,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -322,6 +351,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -335,7 +367,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -345,13 +376,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SkipMerging parameter specifies whether certain stages of a public folder migration are skipped for debugging purposes. Don't use this parameter unless directed to do so by a Microsoft Customer Service and Support or specific documentation. ```yaml Type: SkippableMergeComponent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -361,13 +394,15 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MigrationEndpointIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -377,6 +412,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -385,7 +423,6 @@ If you use this switch, the request is queued, but the request won't reach the s Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -395,13 +432,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -411,13 +450,15 @@ 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 @@ -427,13 +468,15 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: RequestWorkloadType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md index 435cac68b3..0efc0a25e5 100644 --- a/exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfoldermoverequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-PublicFolderMoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-publicfoldermoverequest +schema: 2.0.0 +title: New-PublicFolderMoveRequest --- # New-PublicFolderMoveRequest @@ -80,13 +81,15 @@ This example moves all public folders from public folder mailbox Pub1 to public ## PARAMETERS ### -Folders + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability. ```yaml Type: PublicFolderIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -96,6 +99,9 @@ Accept wildcard characters: False ``` ### -TargetMailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetMailbox parameter specifies the target public folder mailbox that you want to move the public folders to. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -113,7 +119,6 @@ The TargetMailbox parameter specifies the target public folder mailbox that you Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -123,6 +128,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptLargeDataLoss switch specifies that the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -131,7 +139,6 @@ You need to use this switch if you set the LargeItemLimit parameter to a value o Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -141,6 +148,9 @@ Accept wildcard characters: False ``` ### -AllowLargeItems + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowLargeItems switch specifies that you can move large items only when they're encountered. You don't need to specify a value with this switch. Large items are email messages with a maximum of 1,023 attachments. @@ -149,7 +159,6 @@ Large items are email messages with a maximum of 1,023 attachments. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -159,6 +168,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to be completed. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means that the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so that the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and then try the request again. @@ -167,7 +179,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -177,13 +188,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has been completed before being automatically removed. The default value for this parameter is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -193,6 +206,9 @@ 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`. @@ -202,7 +218,6 @@ 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 @@ -212,6 +227,9 @@ 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. @@ -220,7 +238,6 @@ 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 @@ -230,13 +247,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -246,13 +265,15 @@ 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 don't specify a name, the default name is PublicFolderMove. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -262,6 +283,9 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Organization Description }} @@ -270,7 +294,6 @@ This parameter is available only in the cloud-based service. Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 7 @@ -280,6 +303,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lowest @@ -295,7 +321,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -305,6 +330,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -318,7 +346,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -328,6 +355,9 @@ Accept wildcard characters: False ``` ### -Suspend + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch. If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet. @@ -336,7 +366,6 @@ If you use this switch, the request is queued, but the request won't reach the s Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -346,13 +375,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -362,6 +393,9 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SuspendWhenReadyToComplete switch specifies whether to suspend the request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch. @@ -372,7 +406,6 @@ After the move is suspended, it has a status of AutoSuspended. You can then manu Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -382,13 +415,15 @@ 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 @@ -398,13 +433,15 @@ Accept wildcard characters: False ``` ### -WorkloadType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkloadType parameter is reserved for internal Microsoft use. ```yaml Type: RequestWorkloadType 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/exchange/New-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md similarity index 94% rename from exchange/exchange-ps/exchange/New-QuarantinePermissions.md rename to exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md index 2ce42db98f..5155a34c93 100644 --- a/exchange/exchange-ps/exchange/New-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-quarantinepermissions applicable: Exchange Online, Exchange Online Protection -title: New-QuarantinePermissions -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-quarantinepermissions +schema: 2.0.0 +title: New-QuarantinePermissions --- # New-QuarantinePermissions @@ -72,6 +73,9 @@ In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuaran ## PARAMETERS ### -PermissionToAllowSender + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToAllowSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. @@ -81,7 +85,6 @@ The PermissionToAllowSender parameter specifies whether users are allowed to add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -91,6 +94,9 @@ Accept wildcard characters: False ``` ### -PermissionToBlockSender + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. @@ -100,7 +106,6 @@ The PermissionToBlockSender parameter specifies whether users are allowed to add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 2 @@ -110,6 +115,9 @@ Accept wildcard characters: False ``` ### -PermissionToDelete + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. @@ -119,7 +127,6 @@ The PermissionToDelete parameter specifies whether users are allowed to delete m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 3 @@ -129,6 +136,9 @@ Accept wildcard characters: False ``` ### -PermissionToDownload + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. @@ -140,7 +150,6 @@ Currently, this value has no effect on the available actions in quarantine notif Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 4 @@ -150,6 +159,9 @@ Accept wildcard characters: False ``` ### -PermissionToPreview + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. @@ -159,7 +171,6 @@ The PermissionToPreview parameter specifies whether users are allowed to preview Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 5 @@ -169,6 +180,9 @@ Accept wildcard characters: False ``` ### -PermissionToRelease + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToRelease parameter specifies whether users are allowed to directly release affected messages from quarantine. Valid values are: - $true: Release is available in quarantine notifications for affected messages, and Release (Release email) is available for affected messages in quarantine. @@ -180,7 +194,6 @@ Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 6 @@ -190,6 +203,9 @@ Accept wildcard characters: False ``` ### -PermissionToRequestRelease + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToRequestRelease parameter specifies whether users are allowed to request messages to be released from quarantine. The request must be approved by an admin. Valid values are: - $true: Request Release is available in quarantine notifications for affected messages, and Request release is available for affected messages in quarantine. @@ -201,7 +217,6 @@ Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 7 @@ -211,6 +226,9 @@ Accept wildcard characters: False ``` ### -PermissionToViewHeader + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. @@ -222,7 +240,6 @@ Currently, this value has no effect on the available actions in quarantine notif Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 8 diff --git a/exchange/exchange-ps/exchange/New-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/New-QuarantinePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md index 1d12b70c98..647a6626cd 100644 --- a/exchange/exchange-ps/exchange/New-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-quarantinepolicy applicable: Exchange Online, Exchange Online Protection -title: New-QuarantinePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-quarantinepolicy +schema: 2.0.0 +title: New-QuarantinePolicy --- # New-QuarantinePolicy @@ -66,13 +67,15 @@ To assign Limited access permissions, use the value 27. To assign Full access pe ## PARAMETERS ### -Name + +> Applicable: Exchange Online, Exchange Online Protection + The Name parameter specifies a unique name for the quarantine 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 @@ -82,13 +85,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online, Exchange Online Protection + The AdminDisplayName parameter specifies a description for the quarantine 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 @@ -98,13 +103,15 @@ Accept wildcard characters: False ``` ### -AdminNotificationFrequencyInDays + +> 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 @@ -114,6 +121,9 @@ Accept wildcard characters: False ``` ### -AdminNotificationLanguage + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml @@ -121,7 +131,6 @@ Type: EsnLanguage Parameter Sets: (All) Aliases: Accepted values: Default, English, French, German, Italian, Japanese, Spanish, Korean, Portuguese, Russian, ChineseSimplified, ChineseTraditional, Amharic, Arabic, Bulgarian, BengaliIndia, Catalan, Czech, Cyrillic, Danish, Greek, Estonian, Basque, Persian, Finnish, Filipino, Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Icelandic, Kazakh, Kannada, Lithuanian, Latvian, Malayalam, Marathi, Malay, Dutch, NorwegianNynorsk, Norwegian, Odia, Polish, PortuguesePortugal, Romanian, Slovak, Slovenian, SerbianCyrillic, Serbian, Swedish, Swahili, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -131,13 +140,15 @@ Accept wildcard characters: False ``` ### -AdminNotificationsEnabled + +> 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 @@ -147,13 +158,15 @@ Accept wildcard characters: False ``` ### -AdminQuarantinePermissionsList + +> 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 @@ -163,13 +176,15 @@ Accept wildcard characters: False ``` ### -CustomDisclaimer + +> 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 @@ -179,13 +194,15 @@ 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 @@ -195,6 +212,9 @@ Accept wildcard characters: False ``` ### -EndUserQuarantinePermissions + +> Applicable: Exchange Online, Exchange Online Protection + **Note**: To set permissions in quarantine policies, we recommend using the EndUserQuarantinePermissionsValue parameter. The EndUserQuarantinePermissions specifies the end-user permissions for the quarantine policy by using a variable from the output of a New-QuarantinePermissions or Set-QuarantinePermissions command. @@ -205,7 +225,6 @@ For example, run the following command to store the required permissions in a va Type: QuarantinePermissions Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -215,6 +234,9 @@ Accept wildcard characters: False ``` ### -EndUserQuarantinePermissionsValue + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserQuarantinePermissionsValue parameter specifies the end-user permissions for the quarantine policy. This parameter uses a decimal value that's converted from a binary value. The binary value corresponds to the list of available permissions in a specific order. For each permission, the value 1 equals True and the value 0 equals False. The required order is described in the following list from highest (1000000 or 128) to lowest (00000001 or 1): @@ -242,7 +264,6 @@ For custom permissions, get the binary value that corresponds to the permissions Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -252,6 +273,9 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationCustomFromAddress + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserSpamNotificationCustomFromAddress specifies the email address of an existing internal sender to use as the sender for quarantine notifications. If you don't use this parameter, the default sender is quarantine@messaging.microsoft.com. @@ -260,7 +284,6 @@ If you don't use this parameter, the default sender is quarantine@messaging.micr Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -270,6 +293,9 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationFrequency + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserSpamNotificationFrequency parameter specifies how often quarantine notifications are sent to users. Valid values are: - 04:00:00 (4 hours) @@ -280,7 +306,6 @@ The EndUserSpamNotificationFrequency parameter specifies how often quarantine no Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -290,13 +315,15 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationFrequencyInDays + +> 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 @@ -306,6 +333,9 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationLanguage + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml @@ -313,7 +343,6 @@ Type: EsnLanguage Parameter Sets: (All) Aliases: Accepted values: Default, English, French, German, Italian, Japanese, Spanish, Korean, Portuguese, Russian, ChineseSimplified, ChineseTraditional, Amharic, Arabic, Bulgarian, BengaliIndia, Catalan, Czech, Cyrillic, Danish, Greek, Estonian, Basque, Persian, Finnish, Filipino, Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Icelandic, Kazakh, Kannada, Lithuanian, Latvian, Malayalam, Marathi, Malay, Dutch, NorwegianNynorsk, Norwegian, Odia, Polish, PortuguesePortugal, Romanian, Slovak, Slovenian, SerbianCyrillic, Serbian, Swedish, Swahili, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -323,6 +352,9 @@ Accept wildcard characters: False ``` ### -EsnCustomSubject + +> Applicable: Exchange Online, Exchange Online Protection + The EsnCustomSubject parameter specifies the text to use in the Subject field of quarantine notifications. You can specify multiple values separated by commas using the syntax: `('value1',''value2',...'valueN')`. For each language that you specify with the MultiLanguageSetting parameter, you need to specify unique Sender text. Be sure to align the corresponding MultiLanguageSetting, MultiLanguageCustomDisclaimer, EsnCustomSubject, and MultiLanguageSenderName parameter values in the same order. @@ -335,7 +367,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: MultiValuedProperty Parameter Sets: (All) Aliases: MultiValuedProperty -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -345,6 +376,9 @@ Accept wildcard characters: False ``` ### -ESNEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. @@ -356,7 +390,6 @@ The ESNEnabled parameter specifies whether to enable quarantine notifications (f Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -366,6 +399,9 @@ Accept wildcard characters: False ``` ### -IncludeMessagesFromBlockedSenderAddress + +> Applicable: Exchange Online, Exchange Online Protection + The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. @@ -375,7 +411,6 @@ The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -385,13 +420,15 @@ Accept wildcard characters: False ``` ### -MultiLanguageCustomDisclaimer + +> 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 @@ -401,13 +438,15 @@ Accept wildcard characters: False ``` ### -MultiLanguageSenderName + +> 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 @@ -417,13 +456,15 @@ Accept wildcard characters: False ``` ### -MultiLanguageSetting + +> 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 @@ -433,13 +474,15 @@ Accept wildcard characters: False ``` ### -OrganizationBrandingEnabled + +> 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 @@ -449,13 +492,15 @@ Accept wildcard characters: False ``` ### -QuarantineRetentionDays + +> 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 @@ -465,6 +510,9 @@ Accept wildcard characters: False ``` ### -QuarantinePolicyType + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml @@ -472,7 +520,6 @@ 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/exchange/New-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md similarity index 90% rename from exchange/exchange-ps/exchange/New-ReceiveConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md index a053087232..ac31fc54b8 100644 --- a/exchange/exchange-ps/exchange/New-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-receiveconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-ReceiveConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-receiveconnector +schema: 2.0.0 +title: New-ReceiveConnector --- # New-ReceiveConnector @@ -401,13 +402,15 @@ It accepts incoming SMTP connections only from the IP range 192.168.0.1-192.168. ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name for the Receive connector. 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 Required: True Position: 1 @@ -417,6 +420,9 @@ Accept wildcard characters: False ``` ### -Bindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax `"IPv4Address:TCPPort","IPv6Address:TCPPort"`. You can specify an IPv4 address and port, an IPv6 address and port, or both. The IP address values 0.0.0.0 or `[::]` indicate that the Receive connector uses all available local IPv4 or all IPv6 addresses. You need to specify a valid local IP address from the network adapters of the Exchange server. If you specify an invalid local IP address, the Microsoft Exchange Transport service might fail to start when the service is restarted. @@ -439,9 +445,8 @@ The values for this parameter must satisfy one of the following uniqueness requi ```yaml Type: MultiValuedProperty -Parameter Sets: Custom, Internet, Partner +Parameter Sets: Custom, Internet, Partner, Internal, Client, UsageType Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -450,20 +455,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MultiValuedProperty -Parameter Sets: Internal, Client, UsageType -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Client -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Client The Client switch specifies the Client usage type for the Receive connector. You don't need to specify a value with this switch. This usage type assigns the following default permission groups and authentication methods: @@ -479,7 +474,6 @@ You can't use this switch with any other usage type parameters (Internal, Intern Type: SwitchParameter Parameter Sets: Client Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -489,6 +483,9 @@ Accept wildcard characters: False ``` ### -Internal + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Internal switch specifies the Internal usage type for the Receive connector. You don't need to specify a value with this switch. This usage type assigns the following default permission groups and authentication methods: @@ -504,7 +501,6 @@ You can't use this switch with any other usage type parameters (Client, Internet Type: SwitchParameter Parameter Sets: Internal Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -514,6 +510,9 @@ Accept wildcard characters: False ``` ### -Internet + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Internet switch specifies the Internet usage type for the Receive connector. You don't need to specify a value with this switch. This usage type assigns the following default permission groups and authentication methods: @@ -529,7 +528,6 @@ You can't use this switch with any other usage type parameters (Client, Internal Type: SwitchParameter Parameter Sets: Internet Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -539,6 +537,9 @@ Accept wildcard characters: False ``` ### -Partner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Partner switch specifies the Partner usage type for the Receive connector. You don't need to specify a value with this switch. This usage type assigns the following default permission groups and authentication methods: @@ -554,7 +555,6 @@ You can't use this switch with any other usage type parameters (Client, Internal Type: SwitchParameter Parameter Sets: Partner Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -564,6 +564,9 @@ Accept wildcard characters: False ``` ### -RemoteIPRanges + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteIPRanges parameter specifies the remote IP addresses that the Receive connector accepts messages from. Valid values are: - Single IP address: For example, 192.168.1.1 or fe80::39bd:88f7:6969:d223%11. @@ -591,9 +594,8 @@ You can't use this parameter with the Internet usage type (the default value is ```yaml Type: MultiValuedProperty -Parameter Sets: Custom, Partner, Internal, Client +Parameter Sets: Custom, Partner, Internal, Client, Internet, UsageType Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -602,20 +604,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MultiValuedProperty -Parameter Sets: Internet, UsageType -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Usage -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Usage The Usage parameter specifies the default permission groups and authentication methods that are assigned to the Receive connector. Valid values are: - Client @@ -645,7 +637,6 @@ You can't use this parameter with any other usage type switches (Client, Interna Type: UsageType Parameter Sets: UsageType Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -655,6 +646,9 @@ Accept wildcard characters: False ``` ### -AdvertiseClientSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). @@ -664,7 +658,6 @@ The AdvertiseClientSettings parameter specifies whether the SMTP server name, po Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -674,6 +667,9 @@ Accept wildcard characters: False ``` ### -AuthMechanism + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are: - None @@ -696,7 +692,6 @@ You can specify multiple values separated by commas, but some values have depend Type: AuthMechanisms Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -706,6 +701,9 @@ Accept wildcard characters: False ``` ### -AuthTarpitInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 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. @@ -718,7 +716,6 @@ You can configure the delay for other SMTP failure responses by using the Tarpit Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -728,6 +725,9 @@ Accept wildcard characters: False ``` ### -Banner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Banner parameter specifies a custom SMTP 220 banner that's displayed to remote messaging servers that connect to the Receive connector. When you specify a value, enclose the value in quotation marks, and start the value with 220 (the default "Service ready" SMTP response code). The default value of this parameter is blank ($null), which uses the following SMTP banner: @@ -738,7 +738,6 @@ The default value of this parameter is blank ($null), which uses the following S Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -748,6 +747,9 @@ Accept wildcard characters: False ``` ### -BinaryMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. @@ -759,7 +761,6 @@ The binary MIME extension is defined in RFC 3030. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -769,6 +770,9 @@ Accept wildcard characters: False ``` ### -ChunkingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. @@ -780,7 +784,6 @@ Chunking is defined in RFC 3030. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -790,13 +793,15 @@ 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 @@ -806,6 +811,9 @@ 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`. @@ -815,7 +823,6 @@ 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 @@ -825,6 +832,9 @@ Accept wildcard characters: False ``` ### -ConnectionInactivityTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionInactivityTimeout parameter specifies the maximum amount of idle time before a connection to the Receive connector is closed. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -839,7 +849,6 @@ The value of this parameter must be less than the value of the ConnectionTimeout Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -849,6 +858,9 @@ Accept wildcard characters: False ``` ### -ConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionTimeout parameter specifies the maximum time that the connection to the Receive connector can remain open, even if the connection is actively transmitting data. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -863,7 +875,6 @@ The value of this parameter must be greater than the value of the ConnectionInac Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -873,6 +884,9 @@ Accept wildcard characters: False ``` ### -Custom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Custom switch specifies the Custom usage type for the Receive connector. You don't need to specify a value with this switch. This usage type assigns the following default permission groups and authentication methods: @@ -890,7 +904,6 @@ You can't use this switch with any other usage type parameters (Client, Internal Type: SwitchParameter Parameter Sets: Custom Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -900,6 +913,9 @@ Accept wildcard characters: False ``` ### -DefaultDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultDomain parameter specifies the default accepted domain to use for the Exchange organization. You can use any value that uniquely identifies the accepted domain. For example: - Name @@ -916,7 +932,6 @@ Although you can configure any accepted domain as the default domain, you typica Type: AcceptedDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -926,6 +941,9 @@ Accept wildcard characters: False ``` ### -DeliveryStatusNotificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: DSN is enabled and is advertised in the EHLO response. This is the default value. @@ -937,7 +955,6 @@ Delivery status notifications are defined in RFC 3461. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -947,6 +964,9 @@ 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. @@ -955,7 +975,6 @@ 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 @@ -965,6 +984,9 @@ Accept wildcard characters: False ``` ### -DomainSecureEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DomainSecureEnabled parameter specifies whether to enable or disable mutual Transport Layer Security (TLS) authentication (also known as Domain Secure) for the domains that are serviced by the Receive connector. Valid values are: - $true: Mutual TLS authentication is enabled. @@ -982,7 +1004,6 @@ Note that setting this parameter to the value $true is only part of the requirem Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -992,6 +1013,9 @@ Accept wildcard characters: False ``` ### -EightBitMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. @@ -1003,7 +1027,6 @@ The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1013,6 +1036,9 @@ Accept wildcard characters: False ``` ### -EnableAuthGSSAPI + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableAuthGSSAPI parameter enables or disables Kerberos when Integrated Windows authentication is available on the Receive connector (the AuthMechanism parameter contains the value Integrated). Valid values are: - $true: Kerberos is enabled. The Extended SMTP keyword AUTH GSSAPI NTLM is advertised in the EHLO response. Clients can use Kerberos or NTLM for Integrated Windows authentication. @@ -1024,7 +1050,6 @@ The Generic Security Services application programming interface (GSSAPI) is an I Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1034,6 +1059,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: - $true: The Receive connector is enabled. This is the default value. @@ -1043,7 +1071,6 @@ The Enabled parameter specifies whether to enable or disable the Receive connect Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1053,6 +1080,9 @@ Accept wildcard characters: False ``` ### -EnhancedStatusCodesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. @@ -1064,7 +1094,6 @@ Enhanced status codes are defined in RFC 2034. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1074,6 +1103,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is implemented on the Receive connector. Valid values are: - None: Extended Protection for Authentication isn't used. This is the default value. @@ -1086,7 +1118,6 @@ Extended Protection for Authentication enhances the protection and handling of c Type: ExtendedProtectionPolicySetting Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1096,6 +1127,9 @@ Accept wildcard characters: False ``` ### -Fqdn + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Fqdn parameter specifies the destination FQDN that's shown to connected messaging servers. This value is used in the following locations: - In the default SMTP banner of the Receive connector. @@ -1109,7 +1143,6 @@ The default value is the FQDN of theExchange server that contains the Receive co Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1119,6 +1152,9 @@ Accept wildcard characters: False ``` ### -LongAddressesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. @@ -1136,7 +1172,6 @@ You can only configure this parameter on Receive connectors in the Transport ser Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1146,6 +1181,9 @@ Accept wildcard characters: False ``` ### -MaxAcknowledgementDelay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgment until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgment anyway. @@ -1158,7 +1196,6 @@ The default value is 30 seconds. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1168,6 +1205,9 @@ Accept wildcard characters: False ``` ### -MaxHeaderSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxHeaderSize parameter specifies the maximum size of the SMTP message header before the Receive connector closes the connection. The default value is 256 kilobytes (262144 bytes). When you enter a value, qualify the value with one of the following units: @@ -1185,7 +1225,6 @@ A valid value is from 1 to 2147483647 bytes. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1195,6 +1234,9 @@ Accept wildcard characters: False ``` ### -MaxHopCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxHopCount parameter specifies the maximum number of hops that a message can take before the message is rejected by the Receive connector. The maximum number of hops is determined by the number of Received header fields that exist in a submitted message. A valid value is from 1 to 500. The default value is 30. @@ -1203,7 +1245,6 @@ A valid value is from 1 to 500. The default value is 30. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1213,6 +1254,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnection + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnection parameter specifies the maximum number of inbound connections that this Receive connector serves at the same time. A valid value is from 1 to 2147483647, or the value unlimited. The default value is 5000. @@ -1223,7 +1267,6 @@ To disable the inbound connection limit on a Receive connector, enter a value of Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1233,6 +1276,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnectionPercentagePerSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnectionPercentagePerSource parameter specifies the maximum number of connections that a Receive connector serves at the same time from a single IP address, expressed as the percentage of available remaining connections on a Receive connector. A valid value is from 1 to 100 without the percent sign (%). The default value is 2 percent. @@ -1241,7 +1287,6 @@ A valid value is from 1 to 100 without the percent sign (%). The default value i Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1251,6 +1296,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnectionPerSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnectionPerSource parameter specifies the maximum number of connections that this Receive connector serves at the same time from a single IP address. A valid value is from 1 to 10000, or the value unlimited. The default value is 20. @@ -1261,7 +1309,6 @@ To disable the inbound connection per source limit on a Receive connector, enter Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1271,6 +1318,9 @@ Accept wildcard characters: False ``` ### -MaxLocalHopCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxLocalHopCount parameter specifies the maximum number of local hops that a message can take before the message is rejected by the Receive connector. The maximum number of local hops is determined by the number of Received headers with local server addresses in a submitted message. A valid value is from 0 to 50. The default value is 8. @@ -1281,7 +1331,6 @@ When you specify the value 0, the message is never rejected based on the number Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1291,6 +1340,9 @@ Accept wildcard characters: False ``` ### -MaxLogonFailures + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxLogonFailures parameter specifies the number of logon failures that the Receive connector retries before it closes the connection. A valid value is from 0 to 10. The default value is 3. @@ -1301,7 +1353,6 @@ When you specify the value 0, the connection is never closed because of logon fa Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1311,6 +1362,9 @@ 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 through the Receive connector. The default value is 36 MB, which results in a realistic maximum message size of 25 MB. When you enter a value, qualify the value with one of the following units: @@ -1330,7 +1384,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1340,6 +1393,9 @@ Accept wildcard characters: False ``` ### -MaxProtocolErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxProtocolErrors parameter specifies the maximum number of SMTP protocol errors that the Receive connector accepts before closing the connection. A valid value is from 0 to 2147483647, or the value unlimited. The default value is 5. @@ -1350,7 +1406,6 @@ When you specify the value unlimited, a connection is never closed because of pr Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1360,6 +1415,9 @@ Accept wildcard characters: False ``` ### -MaxRecipientsPerMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxRecipientsPerMessage parameter specifies the maximum number of recipients per message that the Receive connector accepts before closing the connection. A valid value is from 1 to 512000. The default value is 200. @@ -1368,7 +1426,6 @@ A valid value is from 1 to 512000. The default value is 200. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1378,6 +1435,9 @@ Accept wildcard characters: False ``` ### -MessageRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute. A valid value is from 1 to 2147483647, or the value unlimited. @@ -1390,7 +1450,6 @@ The default value for Receive connectors on Mailbox servers is unlimited. The de Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1400,6 +1459,9 @@ Accept wildcard characters: False ``` ### -MessageRateSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are: - None: The message submission rate isn't calculated. @@ -1411,7 +1473,6 @@ The MessageRateSource parameter specifies how the message submission rate is cal Type: MessageRateSourceFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1421,6 +1482,9 @@ Accept wildcard characters: False ``` ### -OrarEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. @@ -1432,7 +1496,6 @@ If the email address specified in the ORAR information is a long X.400 email add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1442,6 +1505,9 @@ Accept wildcard characters: False ``` ### -PermissionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PermissionGroups parameter specifies the well-known security principals who are authorized to use the Receive connector, and the permissions that are assigned to them. Valid values are: - None @@ -1462,7 +1528,6 @@ For more information about the default permissions and security principals for p Type: PermissionGroups Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1472,6 +1537,9 @@ Accept wildcard characters: False ``` ### -PipeliningEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. @@ -1483,7 +1551,6 @@ Pipelining is defined in RFC 2920. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1493,6 +1560,9 @@ Accept wildcard characters: False ``` ### -ProtocolLoggingLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: - None: Protocol logging is disabled on the Receive connector. This is the default value. @@ -1504,7 +1574,6 @@ For more information about protocol logging, see [Protocol logging](https://lear Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1514,6 +1583,9 @@ Accept wildcard characters: False ``` ### -RejectReservedSecondLevelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. @@ -1523,7 +1595,6 @@ The RejectReservedSecondLevelRecipientDomains parameter specifies whether to rej Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1533,6 +1604,9 @@ Accept wildcard characters: False ``` ### -RejectReservedTopLevelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. @@ -1542,7 +1616,6 @@ The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1552,6 +1625,9 @@ Accept wildcard characters: False ``` ### -RejectSingleLabelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. @@ -1561,7 +1637,6 @@ The RejectSingleLabelRecipientDomains parameter specifies whether to reject conn Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1571,6 +1646,9 @@ Accept wildcard characters: False ``` ### -RequireEHLODomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. @@ -1580,7 +1658,6 @@ The RequireEHLODomain parameter specifies whether the client must provide a doma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1590,6 +1667,9 @@ Accept wildcard characters: False ``` ### -RequireTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. @@ -1599,7 +1679,6 @@ The RequireTLS parameter specifies whether to require TLS transmission for inbou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1609,6 +1688,9 @@ 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 @@ -1622,7 +1704,6 @@ 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 @@ -1632,13 +1713,15 @@ Accept wildcard characters: False ``` ### -ServiceDiscoveryFqdn + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN) for the Receive connector. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1648,6 +1731,9 @@ Accept wildcard characters: False ``` ### -SizeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: - Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. @@ -1660,7 +1746,6 @@ SIZE is defined in RFC 1870. Type: SizeMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1670,6 +1755,9 @@ Accept wildcard characters: False ``` ### -SuppressXAnonymousTls + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. @@ -1681,7 +1769,6 @@ The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter conta Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1691,6 +1778,9 @@ Accept wildcard characters: False ``` ### -TarpitInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 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. @@ -1703,7 +1793,6 @@ You can configure the delay for authentication failure responses by using the Au Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1713,13 +1802,15 @@ 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. A valid value for this parameter is `"X.500IssuerX.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint `, run the command `$TLSCertName = "$($TLSCert.Issuer)$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter. ```yaml Type: SmtpX509Identifier Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1729,6 +1820,9 @@ Accept wildcard characters: False ``` ### -TlsDomainCapabilities + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsDomainCapabilities parameter specifies the capabilities that the Receive connector makes available to specific hosts outside of the organization. Remote hosts are authenticated with TLS with certificate validation before these capabilities are offered. This parameter uses the following syntax: @@ -1750,7 +1844,6 @@ For example, `"contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptCloudServices Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1760,6 +1853,9 @@ Accept wildcard characters: False ``` ### -TransportRole + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created. Valid values are: - FrontendTransport: The Front End Transport service where client or external SMTP connections occur. @@ -1769,7 +1865,6 @@ The TransportRole parameter specifies the transport service on the Mailbox serve Type: ServerRole Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1779,13 +1874,15 @@ 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/exchange/New-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/New-RemoteDomain.md rename to exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md index d482738214..f948209222 100644 --- a/exchange/exchange-ps/exchange/New-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-remotedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-RemoteDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-remotedomain +schema: 2.0.0 +title: New-RemoteDomain --- # New-RemoteDomain @@ -43,13 +44,15 @@ This example creates the remote domain named Contoso for the domain contoso.com ## 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 remote domain 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -59,6 +62,9 @@ Accept wildcard characters: False ``` ### -DomainName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DomainName parameter specifies the SMTP domain that you want to establish as a remote domain. A valid value is an SMTP domain (for example, contoso.com). The maximum length is 256 characters. You can use the wildcard character (\*) to specify a domain and all subdomains (for example: \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com). @@ -67,7 +73,6 @@ You can use the wildcard character (\*) to specify a domain and all subdomains ( Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -77,6 +82,9 @@ 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,7 +94,6 @@ 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 @@ -96,6 +103,9 @@ 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,7 +116,6 @@ 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,13 +125,15 @@ 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/exchange/New-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md similarity index 88% rename from exchange/exchange-ps/exchange/New-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md index 2647a103bb..323acee73a 100644 --- a/exchange/exchange-ps/exchange/New-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-remotemailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-RemoteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-remotemailbox +schema: 2.0.0 +title: New-RemoteMailbox --- # New-RemoteMailbox @@ -194,13 +195,15 @@ As in Example 1, this example assumes that mail flow and directory synchronizati ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the on-premises mail user and the associated mailbox in the service. 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 Required: True Position: 1 @@ -210,13 +213,15 @@ Accept wildcard characters: False ``` ### -AccountDisabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AccountDisabled switch specifies whether to create the mail user in a disabled state. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: AccountDisabled Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -226,6 +231,9 @@ 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). @@ -236,7 +244,6 @@ You can't use this switch with the Room switch. Type: SwitchParameter Parameter Sets: Equipment Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -246,6 +253,9 @@ Accept wildcard characters: False ``` ### -Password + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Password parameter specifies the password used by the mail user to secure his or her account and associated mailbox in the service. You can use the following methods as a value for this parameter: @@ -256,9 +266,8 @@ You can use the following methods as a value for this parameter: ```yaml Type: SecureString -Parameter Sets: AccountDisabled, Equipment, Room, Shared +Parameter Sets: Default, AccountDisabled, Equipment, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -267,20 +276,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecureString -Parameter Sets: Default -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Room -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Room 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 the Room switch if you specified the Equipment switch. @@ -289,7 +288,6 @@ You can't use the Room switch if you specified the Equipment switch. Type: SwitchParameter Parameter Sets: Room Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -299,6 +297,9 @@ 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. @@ -309,7 +310,6 @@ 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 @@ -319,13 +319,15 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. ```yaml Type: String -Parameter Sets: AccountDisabled, Equipment, Room, Shared +Parameter Sets: Default, AccountDisabled, Equipment, Room, Shared Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -334,27 +336,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: Default -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -ACLableSyncedObjectEnabled -Required: True -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -ACLableSyncedObjectEnabled 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: False Position: Named @@ -364,6 +355,9 @@ 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: @@ -388,7 +382,6 @@ 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 @@ -398,13 +391,15 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Archive switch specifies whether to also create an archive mailbox in the service. 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 @@ -414,6 +409,9 @@ 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`. @@ -423,7 +421,6 @@ 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 @@ -433,6 +430,9 @@ 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 and the associated mailbox in the service. The display name is visible in the Exchange admin center, in address lists, and in 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. @@ -441,7 +441,6 @@ 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 Required: False Position: Named @@ -451,13 +450,15 @@ 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 @@ -467,13 +468,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FirstName parameter specifies the user's first name. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -483,6 +486,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -491,7 +497,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -501,13 +506,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Initials parameter specifies the user's middle initials. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -517,13 +524,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LastName parameter specifies the user's last name. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -533,6 +542,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 @@ -550,7 +562,6 @@ You need to use this parameter to specify at least one moderator when you set th Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -560,6 +571,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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. @@ -571,7 +585,6 @@ 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 Required: False Position: Named @@ -581,6 +594,9 @@ Accept wildcard characters: False ``` ### -OnPremisesOrganizationalUnit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OnPremisesOrganizationalUnit parameter specifies the organizational unit (OU) in the on-premises organization in which the new mailbox is added (for example, redmond.contoso.com/Users). 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: @@ -596,7 +612,6 @@ This parameter has no effect on the mailbox in the service. Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -606,13 +621,15 @@ 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 @@ -622,6 +639,9 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: - $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value. @@ -635,7 +655,6 @@ A user's experience in any of these management interfaces is still controlled by Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -645,6 +664,9 @@ 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. This address is created automatically when the service is initially configured in the format of `.mail.onmicrosoft.com`. If you've configured mail flow between the on-premises organization and the service, such as in a hybrid deployment, you don't need to specify this parameter. The remote routing address is calculated automatically and assigned to the email address policy for the on-premises organization by the Hybrid Configuration wizard. @@ -653,7 +675,6 @@ If you've configured mail flow between the on-premises organization and the serv Type: ProxyAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -663,6 +684,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. @@ -672,7 +696,6 @@ The ResetPasswordOnNextLogon parameter specifies whether the user must change th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -682,13 +705,15 @@ Accept wildcard characters: False ``` ### -SamAccountName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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). The maximum length is 20 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -698,6 +723,9 @@ Accept wildcard characters: False ``` ### -SendModerationNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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. @@ -710,7 +738,6 @@ 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 Required: False Position: Named @@ -720,13 +747,15 @@ 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/exchange/New-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md index 1f7d59a1bc..879bd8df3e 100644 --- a/exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-reportsubmissionpolicy applicable: Exchange Online -title: New-ReportSubmissionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-reportsubmissionpolicy +schema: 2.0.0 +title: New-ReportSubmissionPolicy --- # New-ReportSubmissionPolicy @@ -144,6 +145,9 @@ This example creates the report submission policy with the following values: rep ## PARAMETERS ### -DisableQuarantineReportingOption + +> Applicable: Exchange Online + The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. @@ -155,7 +159,6 @@ This parameter is meaningful only reporting in Outlook is enabled as described i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -165,13 +168,15 @@ Accept wildcard characters: False ``` ### -DisableUserSubmissionOptions + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -181,13 +186,15 @@ Accept wildcard characters: False ``` ### -EnableCustomizedMsg + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -197,6 +204,9 @@ Accept wildcard characters: False ``` ### -EnableCustomNotificationSender + +> Applicable: Exchange Online + The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. @@ -208,7 +218,6 @@ You specify the sender email address using the NotificationSenderAddress paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -218,6 +227,9 @@ Accept wildcard characters: False ``` ### -EnableOrganizationBranding + +> Applicable: Exchange Online + The EnableOrganizationBranding parameter specifies whether to show the company logo in the footer of result messages that users receive after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use the company logo in the footer text instead of the Microsoft logo. @@ -229,7 +241,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -239,6 +250,9 @@ Accept wildcard characters: False ``` ### -EnableReportToMicrosoft + +> Applicable: Exchange Online + The EnableReportToMicrosoft parameter specifies whether Microsoft integrated reporting experience is enabled or disabled. Valid values are $true or $false. The value $true for this parameter enables reporting in Outlook. The following configurations are possible: @@ -257,7 +271,6 @@ This parameter is required to create the report submission policy only if you se Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -267,6 +280,9 @@ Accept wildcard characters: False ``` ### -EnableThirdPartyAddress + +> Applicable: Exchange Online + The EnableThirdPartyAddress parameter specifies whether you're using non-Microsoft reporting tools in Outlook instead of Microsoft tools to send messages to the reporting mailbox in Exchange Online. Valid values are: - $true: Reporting in Outlook is enabled, but non-Microsoft tools in Outlook send reported messages to the reporting mailbox in Exchange Online. You also need to set the EnableReportToMicrosoft parameter value to $false. To create the policy, use the same email address in the ThirdPartyReportAddresses parameter and also in the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlets. @@ -278,7 +294,6 @@ This parameter is required to create the report submission policy only if you se Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -288,6 +303,9 @@ Accept wildcard characters: False ``` ### -EnableUserEmailNotification + +> Applicable: Exchange Online + The EnableUserEmailNotification parameter species whether users receive result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Customized admin review result messages are sent. @@ -303,7 +321,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -313,6 +330,9 @@ Accept wildcard characters: False ``` ### -JunkReviewResultMessage + +> Applicable: Exchange Online + The JunkReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as junk. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -325,7 +345,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -335,6 +354,9 @@ Accept wildcard characters: False ``` ### -NotJunkReviewResultMessage + +> Applicable: Exchange Online + The NotJunkReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as not junk. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -347,7 +369,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -357,6 +378,9 @@ Accept wildcard characters: False ``` ### -NotificationFooterMessage + +> Applicable: Exchange Online + The NotificationFooterMessage parameter specifies the custom footer text to use in email notifications after an admin reviews and marks the reported messages as junk, not junk, or phishing. If the value contains spaces, enclose the value in quotation marks. You can use the EnableOrganizationBranding parameter to include your company logo in the message footer. @@ -367,7 +391,6 @@ This parameter is meaningful only when the value of the EnableUserEmailNotificat Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -377,6 +400,9 @@ Accept wildcard characters: False ``` ### -NotificationSenderAddress + +> Applicable: Exchange Online + The NotificationSenderAddress parameter specifies the sender email address to use in result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. The email address must be in Exchange Online. This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -385,7 +411,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -395,13 +420,15 @@ Accept wildcard characters: False ``` ### -NotificationsForCleanSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -411,13 +438,15 @@ Accept wildcard characters: False ``` ### -NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -427,13 +456,15 @@ Accept wildcard characters: False ``` ### -NotificationsForSpamSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -443,13 +474,15 @@ Accept wildcard characters: False ``` ### -NotificationsForSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -459,13 +492,15 @@ Accept wildcard characters: False ``` ### -OnlyShowPhishingDisclaimer + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -475,6 +510,9 @@ Accept wildcard characters: False ``` ### -PhishingReviewResultMessage + +> Applicable: Exchange Online + The PhishingReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as phishing. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -487,7 +525,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -497,6 +534,9 @@ Accept wildcard characters: False ``` ### -PostSubmitMessage + +> Applicable: Exchange Online + The PostSubmitMessage parameter specifies the custom pop-up message text to use in Outlook notifications after users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message title using the PostSubmitMessageTitle parameter. @@ -507,7 +547,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -517,13 +556,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageEnabled + +> Applicable: Exchange Online + {{ Fill PostSubmitMessageEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -533,13 +574,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -549,13 +592,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -565,13 +610,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -581,6 +628,9 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitle + +> Applicable: Exchange Online + The PostSubmitMessage parameter parameter specifies the custom pop-up message title to use in Outlook notifications after users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message text using the PostSubmitMessage parameter. @@ -591,7 +641,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -601,13 +650,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -617,13 +668,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -633,13 +686,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -649,6 +704,9 @@ Accept wildcard characters: False ``` ### -PreSubmitMessage + +> Applicable: Exchange Online + The PreSubmitMessage parameter specifies the custom pop-up message text to use in Outlook notifications before users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message title using the PreSubmitMessageTitle parameter. @@ -659,7 +717,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -669,13 +726,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageEnabled + +> Applicable: Exchange Online + {{ Fill PreSubmitMessageEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -685,13 +744,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -701,13 +762,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -717,13 +780,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -733,6 +798,9 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitle + +> Applicable: Exchange Online + The PreSubmitMessage parameter parameter specifies the custom pop-up message title to use in Outlook notifications before users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the pop-up message text using the PreSubmitMessage parameter. @@ -743,7 +811,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -753,13 +820,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -769,13 +838,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -785,13 +856,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -801,13 +874,15 @@ Accept wildcard characters: False ``` ### -ReportChatMessageEnabled + +> Applicable: Exchange Online + {{ Fill ReportChatMessageEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -817,13 +892,15 @@ Accept wildcard characters: False ``` ### -ReportChatMessageToCustomizedAddressEnabled + +> Applicable: Exchange Online + {{ Fill ReportChatMessageToCustomizedAddressEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -833,6 +910,9 @@ Accept wildcard characters: False ``` ### -ReportJunkAddresses + +> Applicable: Exchange Online + The ReportJunkAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. This parameter is required to create the report submission policy if the ReportJunkToCustomizedAddress parameter value is $true. @@ -845,7 +925,6 @@ You also need to specify the same email address in the SentTo parameter on the N Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -855,6 +934,9 @@ Accept wildcard characters: False ``` ### -ReportJunkToCustomizedAddress + +> Applicable: Exchange Online + The ReportJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -868,7 +950,6 @@ This parameter is required to create the report submission policy if you're usin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -878,6 +959,9 @@ Accept wildcard characters: False ``` ### -ReportNotJunkAddresses + +> Applicable: Exchange Online + The ReportNotJunkAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. This parameter is required to create the report submission policy if the ReportNotJunkToCustomizedAddress parameter value is $true. @@ -890,7 +974,6 @@ You also need to specify the same email address in the SentTo parameter on the N Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -900,6 +983,9 @@ Accept wildcard characters: False ``` ### -ReportNotJunkToCustomizedAddress + +> Applicable: Exchange Online + The ReportNotJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -913,7 +999,6 @@ This parameter is required to create the report submission policy if you're usin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -923,6 +1008,9 @@ Accept wildcard characters: False ``` ### -ReportPhishAddresses + +> Applicable: Exchange Online + The ReportPhishAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. This parameter is required to create the report submission policy if the ReportPhishToCustomizedAddress parameter value is $true. @@ -935,7 +1023,6 @@ You also need to specify the same email address in the SentTo parameter on the N Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -945,6 +1032,9 @@ Accept wildcard characters: False ``` ### -ReportPhishToCustomizedAddress + +> Applicable: Exchange Online + The ReportPhishToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -958,7 +1048,6 @@ This parameter is required to create the report submission policy if you're usin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -968,6 +1057,9 @@ Accept wildcard characters: False ``` ### -ThirdPartyReportAddresses + +> Applicable: Exchange Online + Use the ThirdPartyReportAddresses parameter to specify the email address of the reporting mailbox in Exchange Online when you're using a non-Microsoft product for user submissions instead of reporting in Outlook. This parameter is required to create the report submission policy if you've disabled reporting in Outlook (`-EnableReportToMicrosoft $false`) and you're using the reporting mailbox with non-Microsoft tools (`-EnableThirdPartyAddress $true`). @@ -976,7 +1068,6 @@ This parameter is required to create the report submission policy if you've disa Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -986,13 +1077,15 @@ Accept wildcard characters: False ``` ### -UserSubmissionOptions + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1002,13 +1095,15 @@ Accept wildcard characters: False ``` ### -UserSubmissionOptionsMessage + +> 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 diff --git a/exchange/exchange-ps/exchange/New-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/New-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md index 4a81e082a0..f78757c656 100644 --- a/exchange/exchange-ps/exchange/New-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-reportsubmissionrule applicable: Exchange Online -title: New-ReportSubmissionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-reportsubmissionrule +schema: 2.0.0 +title: New-ReportSubmissionRule --- # New-ReportSubmissionRule @@ -61,13 +62,15 @@ This example creates the report submission rule. The reporting mailbox is userre ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the name of the report submission rule. When the rule is automatically created, the name of the rule is DefaultReportSubmissionRule. We recommend using this value to avoid confusion. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -77,13 +80,15 @@ Accept wildcard characters: False ``` ### -ReportSubmissionPolicy + +> Applicable: Exchange Online + The ReportSubmissionPolicy parameter specifies the report submission policy that's associated with this rule. The only available policy is named DefaultReportSubmissionPolicy. ```yaml Type: ReportSubmissionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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`. @@ -118,7 +128,6 @@ 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 @@ -128,6 +137,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the rule is enabled or disabled. Valid values are: - $true: The rule is enabled. This is the default value. @@ -139,7 +151,6 @@ After you create the rule, use the Enable-ReportSubmissionRule and Disable-Repor Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -149,6 +160,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Online + The SentTo parameter specifies the email address of the reporting mailbox in Exchange Online where user reported messages are sent. The value of this parameter is meaningful only if reporting in Outlook is enabled, and user reported messages are sent to a reporting mailbox as configured in the \*-ReportSubmissionPolicy cmdlets (either of the following scenarios): @@ -167,7 +181,6 @@ When you use this cmdlet to set the email address of the reporting mailbox, the Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -177,13 +190,15 @@ 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/exchange/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md index cacf15afbe..a1325ba36d 100644 --- a/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-retentioncompliancepolicy applicable: Security & Compliance -title: New-RetentionCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-retentioncompliancepolicy +schema: 2.0.0 +title: New-RetentionCompliancePolicy --- # New-RetentionCompliancePolicy @@ -115,13 +116,15 @@ The next step is to use the New-RetentionComplianceRule cmdlet to add a retentio ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name of the retention 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 @@ -131,6 +134,9 @@ 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 @@ -141,7 +147,6 @@ The AdaptiveScopeLocation parameter specifies the adaptive scope location to inc Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -151,6 +156,9 @@ Accept wildcard characters: False ``` ### -Applications + +> Applicable: Security & Compliance + The Applications parameter specifies the target when Microsoft 365 Groups are included in the policy (the ModernGroups parameter is set). Valid values are: - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group. @@ -162,7 +170,6 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in Type: MultiValuedProperty Parameter Sets: Default, AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -172,13 +179,15 @@ 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 @@ -188,6 +197,9 @@ 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`. @@ -197,7 +209,6 @@ 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 @@ -207,6 +218,9 @@ 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. @@ -216,7 +230,6 @@ 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 @@ -226,6 +239,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocation + +> Applicable: Security & Compliance + The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are: - A mailbox @@ -247,7 +263,6 @@ If no mailboxes are specified, then no mailboxes are placed on hold. Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -257,6 +272,9 @@ Accept wildcard characters: False ``` ### -ExchangeLocationException + +> Applicable: Security & Compliance + The ExchangeLocationException parameter specifies the mailboxes to exclude from the policy when you use the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -275,7 +293,6 @@ 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 @@ -285,6 +302,9 @@ 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. @@ -293,7 +313,6 @@ 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 @@ -303,6 +322,9 @@ Accept wildcard characters: False ``` ### -IsSimulation + +> Applicable: Security & Compliance + The IsSimulation switch specifies the policy is created in simulation mode. 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). @@ -311,7 +333,6 @@ 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 @@ -321,6 +342,9 @@ 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 @@ -339,7 +363,6 @@ 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 @@ -349,6 +372,9 @@ 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: @@ -364,7 +390,6 @@ 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 @@ -374,6 +399,9 @@ Accept wildcard characters: False ``` ### -OneDriveLocation + +> Applicable: Security & Compliance + The OneDriveLocation parameter specifies the OneDrive 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"`. @@ -382,7 +410,6 @@ 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 @@ -392,6 +419,9 @@ 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"`. @@ -400,7 +430,6 @@ 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 @@ -410,6 +439,9 @@ 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. @@ -420,7 +452,6 @@ 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 @@ -430,13 +461,15 @@ Accept wildcard characters: False ``` ### -PolicyTemplateInfo + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: PswsHashtable Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -446,6 +479,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to create a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -454,7 +490,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -464,13 +499,15 @@ Accept wildcard characters: False ``` ### -PublicFolderLocation + +> Applicable: Security & Compliance + The PublicFolderLocation parameter specifies that you want to include all public folders in the retention policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -480,6 +517,9 @@ 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. @@ -493,7 +533,6 @@ Therefore, before you lock a retention policy, it's critical that you understand Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -503,6 +542,9 @@ Accept wildcard characters: False ``` ### -RetainCloudAttachment + +> Applicable: Security & Compliance + **Note**: This parameter is currently in Preview, is not available in all organizations, and is subject to change. The RetainCloudAttachment parameter specifies that this is a cloud attachment policy. Valid values are: @@ -524,7 +566,6 @@ The RetainCloudAttachment parameter is not available on the Set-RetentionComplia Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -534,6 +575,9 @@ 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"`. @@ -544,7 +588,6 @@ SharePoint sites can't be added to the policy until they have been indexed. If n Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -554,6 +597,9 @@ 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"`. @@ -562,7 +608,6 @@ 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 @@ -572,13 +617,15 @@ Accept wildcard characters: False ``` ### -SkipPriorityCleanupConfirmation + +> Applicable: Security & Compliance + {{ Fill SkipPriorityCleanupConfirmation Description }} ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -588,6 +635,9 @@ Accept wildcard characters: False ``` ### -SkypeLocation + +> Applicable: Security & Compliance + The SkypeLocation parameter specifies the Skype for Business Online users to include in the policy. You can use any value that uniquely identifies the user. For example: @@ -603,7 +653,6 @@ 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 @@ -613,13 +662,15 @@ Accept wildcard characters: False ``` ### -SkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -629,6 +680,9 @@ Accept wildcard characters: False ``` ### -TeamsChannelLocation + +> Applicable: Security & Compliance + The TeamsChannelLocation parameter specifies the Teams to include in the policy. You can use any value that uniquely identifies the team. For example: @@ -643,7 +697,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -653,6 +706,9 @@ Accept wildcard characters: False ``` ### -TeamsChannelLocationException + +> Applicable: Security & Compliance + The TeamsChannelLocationException parameter specifies the Teams to exclude when you use the value All for the TeamsChannelLocation parameter. You can use any value that uniquely identifies the team. For example: - Name @@ -665,7 +721,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -675,6 +730,9 @@ Accept wildcard characters: False ``` ### -TeamsChatLocation + +> Applicable: Security & Compliance + The TeamsChatLocation parameter specifies the Teams users to include in the policy. You can use any value that uniquely identifies the user. For example: @@ -690,7 +748,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -700,6 +757,9 @@ Accept wildcard characters: False ``` ### -TeamsChatLocationException + +> Applicable: Security & Compliance + The TeamsChatLocationException parameter specifies the Teams users to exclude when you use the value All for the TeamsChatLocation parameter. You can use any value that uniquely identifies the user. For example: - Name @@ -713,7 +773,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -723,13 +782,15 @@ 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/exchange/New-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/New-RetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md index fa75892cc2..f4a4d4a0c0 100644 --- a/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-retentioncompliancerule applicable: Security & Compliance -title: New-RetentionComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-retentioncompliancerule +schema: 2.0.0 +title: New-RetentionComplianceRule --- # New-RetentionComplianceRule @@ -86,6 +87,9 @@ This example creates a new retention rule named SeptOneYear and adds it to the e ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies a unique name for the retention rule. If the value contains spaces, enclose the value in quotation marks. You can't use this parameter with the ApplyComplianceTag or PublishComplianceTag parameters. @@ -94,7 +98,6 @@ You can't use this parameter with the ApplyComplianceTag or PublishComplianceTag Type: String Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -104,6 +107,9 @@ Accept wildcard characters: False ``` ### -ApplyComplianceTag + +> Applicable: Security & Compliance + The ApplyComplianceTag parameter specifies the label that's applied to email messages or documents by the rule (which affects how long the content is retained). A valid value for this parameter is the name of an existing label. If the value contains spaces, enclose the value in quotation marks. You view and create labels by using the Get-ComplianceTag and New-ComplianceTag cmdlets. @@ -116,7 +122,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: ComplianceTag Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -126,13 +131,15 @@ 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 @@ -142,6 +149,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to create a rule associated with a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -150,7 +160,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -160,6 +169,9 @@ Accept wildcard characters: False ``` ### -PublishComplianceTag + +> Applicable: Security & Compliance + The PublishComplianceTag parameter specifies the label that's published for the rule, which makes the label visible to users in apps (for example, Outlook, SharePoint, and OneDrive). A valid value for this parameter is the name of an existing label. If the value contains spaces, enclose the value in quotation marks. You view and create labels by using the Get-ComplianceTag and New-ComplianceTag cmdlets. @@ -174,7 +186,6 @@ You can't use this parameter in the following scenarios: Type: String Parameter Sets: PublishComplianceTag Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -184,13 +195,15 @@ 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 @@ -200,6 +213,9 @@ 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`. @@ -209,7 +225,6 @@ 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 @@ -219,6 +234,9 @@ 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"})`. @@ -233,7 +251,6 @@ You can't use this parameter for Teams retention rules. Type: PswsHashtable[] Parameter Sets: ComplianceTag Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -243,6 +260,9 @@ 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). @@ -253,7 +273,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: ComplianceTag, Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -263,6 +282,9 @@ 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 @@ -284,7 +306,6 @@ You can't use this parameter for Teams retention rules. Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -294,6 +315,9 @@ 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 @@ -305,7 +329,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -315,13 +338,15 @@ Accept wildcard characters: False ``` ### -IRMRiskyUserProfiles + +> Applicable: Security & Compliance + {{ Fill IRMRiskyUserProfiles Description }} ```yaml Type: String Parameter Sets: ComplianceTag Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -331,13 +356,15 @@ Accept wildcard characters: False ``` ### -MachineLearningModelIDs + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: ComplianceTag Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -347,6 +374,9 @@ Accept wildcard characters: False ``` ### -RetentionComplianceAction + +> Applicable: Security & Compliance + The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - Delete @@ -359,7 +389,6 @@ If you don't use this parameter, the retention policy is created as an "UniH" po Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -369,6 +398,9 @@ 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. @@ -378,7 +410,6 @@ The RetentionDuration parameter specifies the hold duration for the retention ru Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -388,6 +419,9 @@ 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 @@ -402,7 +436,6 @@ You can't use this parameter for Teams retention rules. Type: HoldDurationHint Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -412,13 +445,15 @@ 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/exchange/New-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/New-RetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md index a6a970985e..40a4ab57f9 100644 --- a/exchange/exchange-ps/exchange/New-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-retentionpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-RetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-retentionpolicy +schema: 2.0.0 +title: New-RetentionPolicy --- # New-RetentionPolicy @@ -58,13 +59,15 @@ The second retention tag, which is named Legal, is also enclosed in quotation ma ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the policy name. ```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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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,7 +109,6 @@ 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,6 +118,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. @@ -130,7 +140,6 @@ Changes to the default retention policy that affect existing mailboxes can poten Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -140,6 +149,9 @@ Accept wildcard characters: False ``` ### -IsDefaultArbitrationMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IsDefaultArbitrationMailbox switch configures this policy as the default retention policy for arbitration mailboxes in your Exchange Online organization. You don't need to specify a value with this switch. @@ -148,7 +160,6 @@ The IsDefaultArbitrationMailbox switch configures this policy as the default ret Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -158,13 +169,15 @@ Accept wildcard characters: False ``` ### -RetentionId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionId parameter specifies the identity of the retention policy to ensure mailboxes moved from an on-premises Exchange deployment to the cloud continue to have the same retention policy applied to them. The RetentionId parameter is used in cross-premises deployments. You don't need to specify this parameter in on-premises-only deployments. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -174,13 +187,15 @@ Accept wildcard characters: False ``` ### -RetentionPolicyTagLinks + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionPolicyTagLinks parameter specifies the names of retention policy tags to be associated with this policy. ```yaml Type: RetentionPolicyTagIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -190,13 +205,15 @@ 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/exchange/New-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md similarity index 88% rename from exchange/exchange-ps/exchange/New-RetentionPolicyTag.md rename to exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md index a320464cfa..e6cd81e37e 100644 --- a/exchange/exchange-ps/exchange/New-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-retentionpolicytag applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-RetentionPolicyTag -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-retentionpolicytag +schema: 2.0.0 +title: New-RetentionPolicyTag --- # New-RetentionPolicyTag @@ -99,13 +100,15 @@ This example creates the retention tag Business Critical of type Personal. When ## 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 tag. ```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 @@ -115,6 +118,9 @@ Accept wildcard characters: False ``` ### -AddressForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -123,7 +129,6 @@ This parameter is reserved for internal Microsoft use. Type: RecipientIdParameter Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -133,13 +138,15 @@ Accept wildcard characters: False ``` ### -AgeLimitForRetention + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date the item was delivered, or the date an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. ```yaml Type: EnhancedTimeSpan Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -149,13 +156,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Comment parameter specifies a comment for the tag. ```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 @@ -165,6 +174,9 @@ 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`. @@ -174,7 +186,6 @@ 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 @@ -184,6 +195,9 @@ 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. @@ -192,7 +206,6 @@ 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,6 +215,9 @@ Accept wildcard characters: False ``` ### -IsDefaultAutoGroupPolicyTag + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -210,7 +226,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -220,6 +235,9 @@ Accept wildcard characters: False ``` ### -IsDefaultModeratedRecipientsPolicyTag + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -228,7 +246,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -238,6 +255,9 @@ Accept wildcard characters: False ``` ### -JournalingEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -246,7 +266,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -256,6 +275,9 @@ Accept wildcard characters: False ``` ### -LabelForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -264,7 +286,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -274,13 +295,15 @@ Accept wildcard characters: False ``` ### -LocalizedComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LocalizedComment parameter specifies localized comments and their languages. When the user's language setting matches a language specified for this parameter, Microsoft Outlook and Outlook on the web display the corresponding localized comment. Comments are specified in the form of ISO Language Code:Comment, for example, LocalizedComment EN-US:"This is a localized comment in U.S. English". ```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 @@ -290,13 +313,15 @@ Accept wildcard characters: False ``` ### -LocalizedRetentionPolicyTagName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LocalizedRetentionPolicyTagName parameter specifies localized tag names and their languages. When the user's language setting matches a language specified for this parameter, Outlook and Outlook on the web display the corresponding localized tag name. Names are specified in the form of ISO Language Code:Name, for example, LocalizedRetentionPolicyTagName EN-US:"Business Critical". ```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 @@ -306,6 +331,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderToUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ManagedFolderToUpgrade parameter specifies the name of a managed folder to use as a template for a retention tag. @@ -314,7 +342,6 @@ The ManagedFolderToUpgrade parameter specifies the name of a managed folder to u Type: ELCFolderIdParameter Parameter Sets: UpgradeManagedFolder Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -324,6 +351,9 @@ Accept wildcard characters: False ``` ### -MessageClass + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MessageClass parameter specifies the message type to which the tag applies. If not specified, the default value is set to \*. With the exception of a default policy tag (DPT) for voicemail, Exchange doesn't support retention tags for different message types. Only tags with a MessageClass of \* are supported, and they apply to all message types. @@ -336,7 +366,6 @@ A DPT for voice mail messages applies only to Microsoft Exchange Unified Messagi Type: String Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -346,6 +375,9 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -354,7 +386,6 @@ This parameter is reserved for internal Microsoft use. Type: JournalingFormat Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -364,13 +395,15 @@ Accept wildcard characters: False ``` ### -MustDisplayCommentEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MustDisplayCommentEnabled parameter specifies whether the comment can be hidden. 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 @@ -380,6 +413,9 @@ Accept wildcard characters: False ``` ### -RetentionAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionAction parameter specifies the action for the retention policy. Valid values are: - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. @@ -395,7 +431,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionAction Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -405,6 +440,9 @@ Accept wildcard characters: False ``` ### -RetentionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionEnabled parameter specifies whether the tag is enabled. When set to $false, the tag is disabled, and no retention action is taken on messages that have the tag applied. Messages with a disabled tag are still considered tagged, so any tags of the same type as the disabled tag in the user's retention policy aren't applied to such messages. @@ -415,7 +453,6 @@ When you set the RetentionEnabled parameter to $false, the retention period for Type: Boolean Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -425,13 +462,15 @@ Accept wildcard characters: False ``` ### -RetentionId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionId parameter specifies an alternate tag ID to make sure the retention tag found on mailbox items tagged in an on-premises deployment matches the tag when the mailbox is moved to the cloud, or mailbox items tagged in the cloud match the tag when the mailbox is moved to an on-premises Exchange server. The parameter is used in cross-premises deployments. You don't need to specify this parameter in on-premises-only deployments. ```yaml Type: Guid Parameter Sets: RetentionPolicy Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -441,13 +480,15 @@ Accept wildcard characters: False ``` ### -SystemTag + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SystemTag parameter specifies that the tag is created for internal Exchange functionality. ```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 @@ -457,6 +498,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Type parameter specifies the type of retention tag being created. Valid values include: - All @@ -487,7 +531,6 @@ To create a default policy tag (DPT), specify type All. For tags of type Recover 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 @@ -497,13 +540,15 @@ 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/exchange/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md index 37d991b855..09c3767f3f 100644 --- a/exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-roleassignmentpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-RoleAssignmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-roleassignmentpolicy +schema: 2.0.0 +title: New-RoleAssignmentPolicy --- # New-RoleAssignmentPolicy @@ -74,13 +75,15 @@ Because setting the new role assignment as default applies only to new mailboxes ## 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 new assignment policy. If the assignment policy name contains spaces, enclose the name in quotation marks ("). The maximum length of the name is 64 characters. ```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: 1 @@ -90,6 +93,9 @@ 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`. @@ -99,7 +105,6 @@ 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 @@ -109,13 +114,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Description parameter specifies the description that's displayed when the role assignment policy is viewed using the Get-RoleAssignmentPolicy cmdlet. Enclose the description 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 @@ -125,6 +132,9 @@ 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. @@ -135,7 +145,6 @@ 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 @@ -145,6 +154,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The IsDefault switch makes the assignment policy the default assignment policy. You don't need to specify a value with this switch. New mailboxes or mailboxes moved from previous versions of Exchange are assigned the default assignment policy when an explicit assignment policy isn't provided. @@ -155,7 +167,6 @@ Setting an assignment policy as default doesn't change the role assignment on ex 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 @@ -165,6 +176,9 @@ Accept wildcard characters: False ``` ### -Roles + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Roles parameter specifies the management roles to assign to the role assignment policy when it's created. If a role name contains spaces, enclose the name in quotation marks ("). If you want to assign more that one role, separate the role names with commas. For a list of built-in management roles that you can assign to a role group, see [Built-in management roles](https://learn.microsoft.com/exchange/built-in-management-roles-exchange-2013-help). @@ -173,7 +187,6 @@ For a list of built-in management roles that you can assign to a role group, see Type: RoleIdParameter[] 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 @@ -183,13 +196,15 @@ 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/exchange/New-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/New-RoleGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md index 308719a319..1ddcd9e837 100644 --- a/exchange/exchange-ps/exchange/New-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-rolegroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: New-RoleGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-rolegroup +schema: 2.0.0 +title: New-RoleGroup --- # New-RoleGroup @@ -127,6 +128,9 @@ This example removes the role assignment between the Distribution Groups managem ## PARAMETERS ### -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 new role group. The name can have a maximum of 64 characters. If the name contains spaces, enclose the name in quotation marks ("). **Note**: If you create a linked role group, we recommend that you include the name of the foreign forest in the name of the role group so that you can more easily associate the linked role group and the associated foreign forest. This is especially important if you have multiple forests. @@ -135,7 +139,6 @@ The Name parameter specifies the name of the new role group. The name can have a 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: True Position: 1 @@ -145,6 +148,9 @@ 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 fully qualified domain name (FQDN) or IP address of the domain controller in the forest where the foreign USG resides. The domain controller you specify is used to get security information for the foreign USG specified by the LinkedForeignGroup parameter. @@ -155,7 +161,6 @@ If you use the LinkedDomainController parameter, you must specify a foreign USG Type: String Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -165,6 +170,9 @@ Accept wildcard characters: False ``` ### -LinkedForeignGroup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The LinkedForeignGroup parameter specifies the name of the foreign USG you want to link this role group to. If the foreign USG name contains spaces, enclose the name in quotation marks ("). @@ -175,7 +183,6 @@ If you use the LinkedForeignGroup parameter, you must specify a domain controlle Type: UniversalSecurityGroupIdParameter Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -185,6 +192,9 @@ 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`. @@ -194,7 +204,6 @@ 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 @@ -204,6 +213,9 @@ 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 specifies the existing configuration-based management scope to associate with management role assignments created with this role group. If the management scope name contains spaces, enclose the name in quotation marks ("). Use the Get-ManagementScope cmdlet to retrieve a list of existing management scopes. @@ -212,7 +224,6 @@ The CustomConfigWriteScope parameter specifies the existing configuration-based Type: ManagementScopeIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -222,6 +233,9 @@ 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 specifies the existing recipient-based management scope to associate with management role assignments created with this role group. If the management scope name contains spaces, enclose the name in quotation marks ("). Use the Get-ManagementScope cmdlet to retrieve a list of existing management scopes. @@ -232,7 +246,6 @@ If you use the CustomRecipientWriteScope parameter, you can't use the RecipientO 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 @@ -242,13 +255,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Description parameter specifies the description that's displayed when the role group is viewed using the Get-RoleGroup cmdlet. Enclose the description 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, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -258,13 +273,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter has a maximum length of 256 characters. ```yaml 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 @@ -274,6 +291,9 @@ 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. @@ -282,7 +302,6 @@ 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 @@ -292,6 +311,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Security & Compliance, 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. @@ -302,7 +324,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -312,6 +333,9 @@ Accept wildcard characters: False ``` ### -Id + +> Applicable: Security & Compliance + This parameter is available only in Security & Compliance PowerShell. This parameter is reserved for internal Microsoft use. @@ -320,7 +344,6 @@ This parameter is reserved for internal Microsoft use. Type: Guid Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -330,6 +353,9 @@ 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 username and password that's used to access the domain controller specified by the LinkedDomainController parameter. @@ -340,7 +366,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -350,6 +375,9 @@ 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 the users or USGs who can modify the configuration of a role group or add and remove members to or from a role group. You can use the name, distinguished name (DN), or primary SMTP address of the user or USG that you want to add. If the name of the user or USG contains spaces, enclose the name in quotation marks ("). @@ -360,7 +388,6 @@ If you want to add more than one user or USG, separate them using commas. 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 @@ -370,6 +397,9 @@ Accept wildcard characters: False ``` ### -Members + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Members parameter specifies the mailboxes or mail-enabled USGs to add as a member of the role group. You can identify the user or group by the name, DN, or primary SMTP address value. You can specify multiple members separated by commas (`Value1,Value2,...ValueN`). If the value contains spaces, enclose the value in quotation marks (`"Value 1","Value 2",..."Value N"`). If you use the Members parameter, you can't use the LinkedForeignGroup, LinkedDomainController or LinkedCredential parameters. @@ -378,7 +408,6 @@ If you use the Members parameter, you can't use the LinkedForeignGroup, LinkedDo 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 @@ -388,6 +417,9 @@ Accept wildcard characters: False ``` ### -RecipientOrganizationalUnitScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RecipientOrganizationalUnitScope parameter specifies the organizational unit (OU) scope added to the role assignments created when the role group is created. If you use the RecipientOrganizationalUnitScope parameter, you can't use the CustomRecipientWriteScope parameter. To specify an OU, use the syntax: domain/ou. If the OU name contains spaces, enclose the domain and OU in quotation marks ("). @@ -396,7 +428,6 @@ The RecipientOrganizationalUnitScope parameter specifies the organizational unit Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -406,6 +437,9 @@ Accept wildcard characters: False ``` ### -Roles + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Roles parameter specifies the management roles to assign to the role group when it's created. If a role name contains spaces, enclose the name in quotation marks ("). If you want to assign more that one role, separate the role names with commas. For a list of built-in management roles that you can assign to a role group, see [Built-in management roles](https://learn.microsoft.com/exchange/built-in-management-roles-exchange-2013-help). @@ -414,7 +448,6 @@ For a list of built-in management roles that you can assign to a role group, see Type: RoleIdParameter[] 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 @@ -424,6 +457,9 @@ 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). The maximum length is 20 characters. @@ -432,7 +468,6 @@ 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 @@ -442,6 +477,9 @@ Accept wildcard characters: False ``` ### -WellKnownObject + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill WellKnownObject Description }} @@ -450,7 +488,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -460,6 +497,9 @@ 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. @@ -468,7 +508,6 @@ 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/exchange/New-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md similarity index 95% rename from exchange/exchange-ps/exchange/New-RoutingGroupConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md index 4fd4b16fbf..04bb3c7e8b 100644 --- a/exchange/exchange-ps/exchange/New-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-routinggroupconnector applicable: Exchange Server 2010 -title: New-RoutingGroupConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-routinggroupconnector +schema: 2.0.0 +title: New-RoutingGroupConnector --- # New-RoutingGroupConnector @@ -55,13 +56,15 @@ This example creates the routing group connector Interop RGC with the following ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies the name to assign to the routing group connector. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -71,13 +74,15 @@ Accept wildcard characters: False ``` ### -SourceTransportServers + +> Applicable: Exchange Server 2010 + The SourceTransportServers parameter specifies the host name or fully qualified domain name (FQDN) of the transport servers used to send messages to the target transport servers. You can specify more than one server by separating each entry with a comma. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -87,13 +92,15 @@ Accept wildcard characters: False ``` ### -TargetTransportServers + +> Applicable: Exchange Server 2010 + The TargetTransportServers parameter specifies the host name or FQDN of the transport servers that receive messages from the source transport servers. You can specify more than one server by separating each entry with a comma. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -103,13 +110,15 @@ Accept wildcard characters: False ``` ### -BiDirectional + +> Applicable: Exchange Server 2010 + The BiDirectional parameter specifies whether this is a one-way or two-way connector. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -119,6 +128,9 @@ 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`. @@ -128,7 +140,6 @@ 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,13 +149,15 @@ Accept wildcard characters: False ``` ### -Cost + +> Applicable: Exchange Server 2010 + The Cost parameter specifies a cost to the connector. Transport servers use the connector cost to determine the least cost routing path from a source server to the destination server for message delivery. The default value is 1. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -154,13 +167,15 @@ 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 @@ -170,13 +185,15 @@ Accept wildcard characters: False ``` ### -PublicFolderReferralsEnabled + +> Applicable: Exchange Server 2010 + The PublicFolderReferralsEnabled parameter specifies whether users can use this routing group connector to access a public folder replica located in the routing group of the target servers when an instance of that public folder isn't available in the same routing group as the user's mailbox. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -186,13 +203,15 @@ 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/exchange/New-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md similarity index 95% rename from exchange/exchange-ps/exchange/New-RpcClientAccess.md rename to exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md index 183a022952..b9173bfbd7 100644 --- a/exchange/exchange-ps/exchange/New-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-rpcclientaccess applicable: Exchange Server 2010 -title: New-RpcClientAccess -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-rpcclientaccess +schema: 2.0.0 +title: New-RpcClientAccess --- # New-RpcClientAccess @@ -48,6 +49,9 @@ This example creates configuration information for the Exchange RPC Client Acces ## PARAMETERS ### -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 @@ -59,7 +63,6 @@ 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: True Position: Named @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -BlockedClientVersions + +> Applicable: Exchange Server 2010 + The BlockedClientVersions parameter specifies which versions of Microsoft Outlook are restricted from connecting. The Exchange RPC Client Access service rejects Outlook connections if versions are in the range specified. This setting affects MAPI and Outlook Anywhere client connections. The value must be less than 256 characters in length. Versions should be single numbers in the format X.Y.Z where X is a major version number, Y is the minor revision number, and Z specifies the build, and ranges should be delimited by semicolons (for example, 0.0.0-5.9.9; 7.0.0-65535.65535.65535). @@ -77,7 +83,6 @@ Versions should be single numbers in the format X.Y.Z where X is a major version Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -87,6 +92,9 @@ 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`. @@ -96,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ 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 @@ -122,13 +131,15 @@ Accept wildcard characters: False ``` ### -EncryptionRequired + +> Applicable: Exchange Server 2010 + The EncryptionRequired parameter specifies whether to require Outlook connections to be encrypted. The Exchange RPC Client Access service rejects unencrypted Outlook connections if this parameter is set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -138,6 +149,9 @@ Accept wildcard characters: False ``` ### -MaximumConnections + +> Applicable: Exchange Server 2010 + The MaximumConnections parameter specifies the maximum number of concurrent connections allowed. The Exchange RPC Client Access service reads and limits connections based on this property. This parameter has a range from 1 through 65535. @@ -148,7 +162,6 @@ Although you can configure a non-default value for this parameter, changes to th Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -158,13 +171,15 @@ 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/exchange/New-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md index 7bd53126c9..4a2a857ae0 100644 --- a/exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-safeattachmentpolicy applicable: Exchange Online -title: New-SafeAttachmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-safeattachmentpolicy +schema: 2.0.0 +title: New-SafeAttachmentPolicy --- # New-SafeAttachmentPolicy @@ -61,13 +62,15 @@ This example creates a new safe attachment policy named Marketing Block Attachme ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the safe attachment 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 @@ -77,6 +80,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Online + The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. @@ -93,7 +99,6 @@ The results of all actions are available in message trace. Type: SafeAttachmentAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -103,13 +108,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -119,6 +126,9 @@ 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`. @@ -128,7 +138,6 @@ 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 @@ -138,6 +147,9 @@ Accept wildcard characters: False ``` ### -Enable + +> Applicable: Exchange Online + The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the Safe Attachment policy. @@ -149,7 +161,6 @@ To enable or disable a complete Safe Attachments policy in the Microsoft Defende Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -159,13 +170,15 @@ Accept wildcard characters: False ``` ### -MakeBuiltInProtection + +> Applicable: Exchange Online + The MakeBuiltInProtection switch is used for Built-in protection policy creation as part of [Preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies). Don't use this switch yourself. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -175,6 +188,9 @@ Accept wildcard characters: False ``` ### -QuarantineTag + +> Applicable: Exchange Online + The QuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as malware by Safe Attachments. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -191,7 +207,6 @@ 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 @@ -201,13 +216,15 @@ Accept wildcard characters: False ``` ### -RecommendedPolicyType + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -217,6 +234,9 @@ Accept wildcard characters: False ``` ### -Redirect + +> Applicable: Exchange Online + The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. @@ -226,7 +246,6 @@ The Redirect parameter specifies whether to deliver messages to an alternate ema Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -236,6 +255,9 @@ Accept wildcard characters: False ``` ### -RedirectAddress + +> Applicable: Exchange Online + The RedirectAddress parameter specifies the destination email address to deliver messages if malware is detected in an attachment. The value of this parameter is meaningful only when value of the Redirect parameter is $true and the value of the Action parameter is Allow. @@ -244,7 +266,6 @@ The value of this parameter is meaningful only when value of the Redirect parame Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -254,13 +275,15 @@ 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/exchange/New-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md similarity index 96% rename from exchange/exchange-ps/exchange/New-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md index 373513e1c0..b2d6131eb5 100644 --- a/exchange/exchange-ps/exchange/New-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-safeattachmentrule applicable: Exchange Online -title: New-SafeAttachmentRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-safeattachmentrule +schema: 2.0.0 +title: New-SafeAttachmentRule --- # New-SafeAttachmentRule @@ -64,13 +65,15 @@ This example creates a new safe attachment rule named Research Department Attach ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the safe attachment rule. 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 @@ -80,6 +83,9 @@ Accept wildcard characters: False ``` ### -SafeAttachmentPolicy + +> Applicable: Exchange Online + The SafeAttachmentPolicy parameter specifies the safe attachment policy that's associated with this safe attachment rule. The rule defines the conditions, and the policy defines the actions. You can use any value that uniquely identifies the policy. For example: @@ -94,7 +100,6 @@ You can't specify a safe attachment policy that's already associated with anothe Type: SafeAttachmentPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -104,13 +109,15 @@ 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 @@ -120,6 +127,9 @@ 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`. @@ -129,7 +139,6 @@ 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 @@ -139,6 +148,9 @@ 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. This is the default value. @@ -150,7 +162,6 @@ 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 Required: False Position: Named @@ -160,13 +171,15 @@ 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 @@ -176,6 +189,9 @@ 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 @@ -191,7 +207,6 @@ 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 @@ -201,6 +216,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + 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 @@ -218,7 +236,6 @@ 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 @@ -228,6 +245,9 @@ 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. Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: @@ -242,7 +262,6 @@ 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 Required: False Position: Named @@ -252,13 +271,15 @@ 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 @@ -268,6 +289,9 @@ 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 @@ -283,7 +307,6 @@ 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 @@ -293,6 +316,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Online + 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 @@ -310,7 +336,6 @@ 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 @@ -320,13 +345,15 @@ 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/exchange/New-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-SafeLinksPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md index 07d98d9dab..6da60515fc 100644 --- a/exchange/exchange-ps/exchange/New-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-safelinkspolicy applicable: Exchange Online -title: New-SafeLinksPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-safelinkspolicy +schema: 2.0.0 +title: New-SafeLinksPolicy --- # New-SafeLinksPolicy @@ -66,13 +67,15 @@ This example creates a new Safe Links policy named Marketing Block URL with the ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the Safe Links 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 @@ -82,13 +85,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -98,6 +103,9 @@ Accept wildcard characters: False ``` ### -AllowClickThrough + +> Applicable: Exchange Online + The AllowClickThrough parameter specifies whether users are allowed to click through to the original URL on warning pages. Valid values are: - $true: The user is allowed to click through to the original URL. @@ -109,7 +117,6 @@ In PowerShell, the default value is $false. In new Safe Links policies created i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -119,6 +126,9 @@ 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`. @@ -128,7 +138,6 @@ 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 @@ -138,13 +147,15 @@ Accept wildcard characters: False ``` ### -CustomNotificationText + +> Applicable: Exchange Online + The custom notification text specifies the customized notification text to show to users. 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 @@ -154,6 +165,9 @@ Accept wildcard characters: False ``` ### -DeliverMessageAfterScan + +> Applicable: Exchange Online + The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: - $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This is the default value. @@ -163,7 +177,6 @@ The DeliverMessageAfterScan parameter specifies whether to deliver email message Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -173,6 +186,9 @@ Accept wildcard characters: False ``` ### -DisableUrlRewrite + +> Applicable: Exchange Online + The DisableUrlRewrite parameter specifies whether to rewrite (wrap) URLs in email messages. Valid values are: - $true: URLs in messages are not rewritten, but messages are still scanned by Safe Links prior to delivery. Time of click checks on links are done using the Safe Links API in supported Outlook clients (currently, Outlook for Windows and Outlook for Mac). @@ -184,7 +200,6 @@ In PowerShell, the default value is $false. In new Safe Links policies created i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -194,6 +209,9 @@ Accept wildcard characters: False ``` ### -DoNotRewriteUrls + +> Applicable: Exchange Online + The DoNotRewriteUrls parameter specifies the URLs that are not rewritten by Safe Links scanning. The list of entries allows users who are included in the policy to access the specified URLs that would otherwise be blocked by Safe Links. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -206,7 +224,6 @@ For details about the entry syntax, see [Entry syntax for the "Do not rewrite th Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,6 +233,9 @@ Accept wildcard characters: False ``` ### -EnableForInternalSenders + +> Applicable: Exchange Online + The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: - $true: The policy is applied to internal and external senders. This is the default value. @@ -225,7 +245,6 @@ The EnableForInternalSenders parameter specifies whether the Safe Links policy i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -235,6 +254,9 @@ Accept wildcard characters: False ``` ### -EnableOrganizationBranding + +> Applicable: Exchange Online + The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. @@ -244,7 +266,6 @@ The EnableOrganizationBranding parameter specifies whether your organization's l Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -254,6 +275,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForEmail + +> Applicable: Exchange Online + The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: - $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -263,7 +287,6 @@ The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links pro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -273,6 +296,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForOffice + +> Applicable: Exchange Online + The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: - $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -284,7 +310,6 @@ Note that this protection applies to links in Office documents, not links in ema Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -294,6 +319,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForTeams + +> Applicable: Exchange Online + The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: - $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -303,7 +331,6 @@ The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -313,13 +340,15 @@ Accept wildcard characters: False ``` ### -MakeBuiltInProtection + +> Applicable: Exchange Online + The MakeBuiltInProtection switch is used for Built-in protection policy creation as part of [Preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies). Don't use this switch yourself. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -329,13 +358,15 @@ Accept wildcard characters: False ``` ### -RecommendedPolicyType + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -345,6 +376,9 @@ Accept wildcard characters: False ``` ### -ScanUrls + +> Applicable: Exchange Online + The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: - $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. @@ -354,7 +388,6 @@ The ScanUrls parameter specifies whether to enable or disable real-time scanning Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -364,6 +397,9 @@ Accept wildcard characters: False ``` ### -TrackClicks + +> Applicable: Exchange Online + The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: - $true: User clicks messages are tracked. This is the default value. @@ -373,7 +409,6 @@ The TrackClicks parameter specifies whether to track user clicks related to Safe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -383,6 +418,9 @@ Accept wildcard characters: False ``` ### -UseTranslatedNotificationText + +> Applicable: Exchange Online + The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. @@ -392,7 +430,6 @@ The UseTranslatedNotificationText specifies whether to use Microsoft Translator Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -402,13 +439,15 @@ 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/exchange/New-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/New-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md index 33a08f67c7..24e1c7304b 100644 --- a/exchange/exchange-ps/exchange/New-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-safelinksrule applicable: Exchange Online -title: New-SafeLinksRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-safelinksrule +schema: 2.0.0 +title: New-SafeLinksRule --- # New-SafeLinksRule @@ -87,13 +88,15 @@ This example is similar to Example 2, but in this example, the rule applies to r ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the Safe Links rule. 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 @@ -103,6 +106,9 @@ Accept wildcard characters: False ``` ### -SafeLinksPolicy + +> Applicable: Exchange Online + The SafeLinksPolicy parameter specifies the Safe Links policy that's associated with this Safe Links rule. The rule defines the conditions and the policy defines the actions. You can use any value that uniquely identifies the policy. For example: @@ -117,7 +123,6 @@ You can't specify a Safe Links policy that's already associated with another Saf Type: SafeLinksPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -127,13 +132,15 @@ 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 @@ -143,6 +150,9 @@ 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`. @@ -152,7 +162,6 @@ 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 @@ -162,6 +171,9 @@ 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. This is the default value. @@ -173,7 +185,6 @@ 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 Required: False Position: Named @@ -183,13 +194,15 @@ 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 @@ -199,6 +212,9 @@ 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 @@ -214,7 +230,6 @@ 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 @@ -224,6 +239,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + 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 @@ -241,7 +259,6 @@ 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 @@ -251,6 +268,9 @@ 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. Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: @@ -265,7 +285,6 @@ 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 Required: False Position: Named @@ -275,13 +294,15 @@ 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 @@ -291,6 +312,9 @@ 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 @@ -306,7 +330,6 @@ 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 @@ -316,6 +339,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Online + 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 @@ -333,7 +359,6 @@ 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 @@ -343,13 +368,15 @@ 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/exchange/New-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md similarity index 90% rename from exchange/exchange-ps/exchange/New-SearchDocumentFormat.md rename to exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md index 2f54d72235..78f87c1c45 100644 --- a/exchange/exchange-ps/exchange/New-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-searchdocumentformat applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SearchDocumentFormat -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-searchdocumentformat +schema: 2.0.0 +title: New-SearchDocumentFormat --- # New-SearchDocumentFormat @@ -46,13 +47,15 @@ This example creates a new search document format with an extension of .sct and ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter uniquely identifies the new search document format. For example, an identity of "PropSCT" might specify a proprietary document format which is supported by a custom IFilter. The Identity parameter must be unique within the search document formats. ```yaml Type: SearchDocumentFormatId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -62,13 +65,15 @@ Accept wildcard characters: False ``` ### -Extension + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Extension parameter specifies the file type to be processed by the filter and is designated by the common file extension associated with the file type. Examples include .MP3, .JPG and .PNG. Note the leading period. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -78,13 +83,15 @@ Accept wildcard characters: False ``` ### -MimeType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MimeType parameter specifies the MIME type of the format. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -94,13 +101,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name specifies a friendly name for the format, but does not need to be unique. For example, you might have several different formats (supported by custom IFilters) that are used to index output from a proprietary system called "My Business Output". You could use the Name parameter to create a category of formats called "My Business Output Formats" and uniquely identify each format within that group using the Identity parameter. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -110,6 +119,9 @@ 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`. @@ -119,7 +131,6 @@ 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 @@ -129,6 +140,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the new format is enabled at creation. Valid input for this parameter is $true or $false. The default is $true. @@ -137,7 +151,6 @@ Valid input for this parameter is $true or $false. The default is $true. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,6 +160,9 @@ 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 @@ -160,7 +176,6 @@ 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 @@ -170,13 +185,15 @@ 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/exchange/New-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md index dcdcdca10f..abec057e67 100644 --- a/exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-secopsoverridepolicy applicable: Exchange Online -title: New-SecOpsOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-secopsoverridepolicy +schema: 2.0.0 +title: New-SecOpsOverridePolicy --- # New-SecOpsOverridePolicy @@ -46,13 +47,15 @@ This example creates the SecOps mailbox override policy with the specified setti ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name will be SecOpsOverridePolicy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -62,6 +65,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Online + The SentTo parameter specifies the email address of the SecOps mailbox. Groups are not allowed. You can specify multiple email addresses separated by commas. @@ -70,7 +76,6 @@ You can specify multiple email addresses separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -80,13 +85,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -96,6 +103,9 @@ 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`. @@ -105,7 +115,6 @@ 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 @@ -115,13 +124,15 @@ 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 @@ -131,6 +142,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the policy is enabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -140,7 +154,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -150,6 +163,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -158,7 +174,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -168,13 +183,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/New-SendConnector.md rename to exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md index 0b08ca8a40..a71f217356 100644 --- a/exchange/exchange-ps/exchange/New-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-sendconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SendConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-sendconnector +schema: 2.0.0 +title: New-SendConnector --- # New-SendConnector @@ -137,13 +138,15 @@ To assign a specific authentication credential for the Send connector, you must ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a descriptive name for 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: 1 @@ -153,6 +156,9 @@ 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 Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. - AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed. @@ -179,7 +185,6 @@ Although you can configure non-SMTP address spaces on a Send connector in the Tr Type: MultiValuedProperty Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -189,6 +194,9 @@ Accept wildcard characters: False ``` ### -AuthenticationCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthenticationCredential parameter specifies the username and password that's required to use the connector. 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). @@ -197,7 +205,6 @@ 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 @@ -207,6 +214,9 @@ Accept wildcard characters: False ``` ### -CloudServicesMailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **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. @@ -220,7 +230,6 @@ Valid values are: Type: Boolean Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -230,13 +239,15 @@ 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 @@ -246,6 +257,9 @@ 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`. @@ -255,7 +269,6 @@ 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 @@ -265,6 +278,9 @@ Accept wildcard characters: False ``` ### -ConnectionInactivityTimeOut + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionInactivityTimeOut parameter specifies the maximum time an idle connection can remain open. The default value is ten 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. @@ -275,7 +291,6 @@ For example, to specify fifteen minutes, set it to 00:15:00. The valid input ran Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -285,6 +300,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are: - Default: The connector isn't used to send messages to Microsoft 365. This is the default value. @@ -294,7 +312,6 @@ The ConnectorType parameter specifies whether the connector is used in hybrid de Type: TenantConnectorType Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -304,6 +321,9 @@ Accept wildcard characters: False ``` ### -Custom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Custom switch specifies the Custom usage type. You don't need to specify a value with this switch. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Custom switch, you can't use any of the following parameters: @@ -319,7 +339,6 @@ For more information about Send connector usage types, permissions, and authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -329,13 +348,15 @@ Accept wildcard characters: False ``` ### -DNSRoutingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DNSRoutingEnabled parameter specifies whether the Send connector uses Domain Name System (DNS) to route mail. Valid values for this parameter are $true or $false. The default value is $true. If you specify a SmartHosts parameter, the DNSRoutingEnabled parameter must be $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 @@ -345,6 +366,9 @@ 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. @@ -353,7 +377,6 @@ 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 @@ -363,6 +386,9 @@ Accept wildcard characters: False ``` ### -DomainSecureEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DomainSecureEnabled parameter enables mutual Transport Layer Security (TLS) authentication for the domains serviced by the Send connector when set to $true. Mutual TLS authentication functions correctly only if the following conditions are met: - DomainSecureEnabled is set to $true. @@ -382,7 +408,6 @@ The default value is $true for a default Send connector defined on an Edge serve Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -392,13 +417,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether to enable the Send connector to process email messages. Valid values are $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 @@ -408,6 +435,9 @@ Accept wildcard characters: False ``` ### -ErrorPolicies + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ErrorPolicies parameter specifies how communication errors are treated. Possible values are the following: - Default: A non-delivery report (NDR) is generated for communication errors. @@ -423,7 +453,6 @@ Specify a value other than Default for this parameter only if this Send connecto Type: ErrorPolicies Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -433,6 +462,9 @@ 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. @@ -441,7 +473,6 @@ 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 @@ -451,13 +482,15 @@ Accept wildcard characters: False ``` ### -ForceHELO + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceHELO parameter specifies whether HELO is sent instead of the default EHLO. Valid values are $true or $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 Required: False Position: Named @@ -467,6 +500,9 @@ Accept wildcard characters: False ``` ### -Fqdn + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Fqdn parameter specifies the FQDN used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this parameter is displayed to connected messaging servers whenever a source server name is required, as in the following examples: - In the EHLO/HELO command when the Send connector communicates with the next hop messaging server @@ -479,7 +515,6 @@ The default value of the Fqdn parameter is $null. This means the default FQDN va Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -489,13 +524,15 @@ Accept wildcard characters: False ``` ### -FrontendProxyEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true. ```yaml Type: Boolean Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -505,13 +542,15 @@ Accept wildcard characters: False ``` ### -IgnoreSTARTTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IgnoreSTARTTLS parameter specifies whether to ignore the StartTLS option offered by a remote sending server. This parameter is used with remote domains. This parameter must be set to $false if the RequireTLS parameter is set to $true. Valid values for this parameter are $true or $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 @@ -521,6 +560,9 @@ Accept wildcard characters: False ``` ### -Internal + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Internal switch specifies the Internal usage type. You don't need to specify a value with this switch. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Internal switch, you can't use any of the following parameters: @@ -536,7 +578,6 @@ For more information about Send connector usage types, permissions, and authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -546,6 +587,9 @@ Accept wildcard characters: False ``` ### -Internet + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Internet switch specifies the Internet usage type. You don't need to specify a value with this switch. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Internet switch, you can't use any of the following parameters: @@ -561,7 +605,6 @@ For more information about Send connector usage types, permissions, and authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -571,6 +614,9 @@ Accept wildcard characters: False ``` ### -IsCoexistenceConnector + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IsCoexistenceConnector parameter specifies whether this Send connector is used for secure mail flow between your on-premises deployment and your Microsoft 365 organization. The default value is $false. @@ -579,7 +625,6 @@ The IsCoexistenceConnector parameter specifies whether this Send connector is us Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -589,13 +634,15 @@ 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 with the Transport service. 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 only be used by Transport service on Mailbox servers in the same Active Directory site. The default value is $false. ```yaml Type: Boolean Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -605,6 +652,9 @@ Accept wildcard characters: False ``` ### -LinkedReceiveConnector + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The LinkedReceiveConnector parameter specifies whether to force all messages received by the specified Receive connector out through this Send connector. The value of LinkedReceivedConnector can use any of the following identifiers to specify the Receive connector: @@ -626,7 +676,6 @@ When you use the LinkedReceiveConnector parameter, you can't use the AddressSpac Type: ReceiveConnectorIdParameter Parameter Sets: LinkedReceiveConnector Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -636,6 +685,9 @@ 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 can pass through a connector. The default value is 25 MB. When you enter a value, qualify the value with one of the following units: @@ -654,7 +706,6 @@ Values entered in bytes are rounded up to nearest kilobyte. The valid input rang Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -664,6 +715,9 @@ Accept wildcard characters: False ``` ### -Partner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Partner switch specifies the Partner usage type. You don't need to specify a value with this switch. The usage type specifies the permissions and authentication methods assigned to the Send connector. If you use the Partner switch, you can't use any of the following parameters: @@ -679,7 +733,6 @@ For more information about Send connector usage types, permissions, and authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -689,13 +742,15 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Port parameter specifies the port number for smart host forwarding, if you specify a value in the SmartHosts parameter. The valid input range is an integer from 0 through 65535. The default value is 25. In most organizations, the port number is set to 25. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -705,13 +760,15 @@ Accept wildcard characters: False ``` ### -ProtocolLoggingLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLoggingLevel parameter specifies whether to enable protocol logging. Verbose enables protocol logging. None disables protocol logging. The location of the Send connector protocol logs for all Send connectors configured in the Transport service on a Mailbox server or on an Edge server is specified with the SendProtocolLogPath parameter of the Set-TransportService cmdlet. ```yaml Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -721,13 +778,15 @@ Accept wildcard characters: False ``` ### -RequireOorg + +> 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 @@ -737,13 +796,15 @@ Accept wildcard characters: False ``` ### -RequireTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireTLS parameter specifies whether all messages sent through this connector must be transmitted using TLS. 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 @@ -753,13 +814,15 @@ Accept wildcard characters: False ``` ### -SmartHostAuthMechanism + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmartHostAuthMechanism parameter specifies the smart host authentication mechanism to use for authentication with a remote server. Use this parameter only when a smart host is configured and the DNSRoutingEnabled parameter is set to $false. Valid values are None, BasicAuth, BasicAuthRequireTLS, ExchangeServer, and ExternalAuthoritative. All values are mutually exclusive. If you select BasicAuth or BasicAuthRequireTLS, you must use the AuthenticationCredential parameter to specify the authentication credential. ```yaml Type: AuthMechanisms Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -769,6 +832,9 @@ Accept wildcard characters: False ``` ### -SmartHosts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmartHosts parameter specifies the smart hosts the Send connector uses to route mail. This parameter is required if you set the DNSRoutingEnabled parameter to $false and it must be specified on the same command line. The SmartHosts parameter takes one or more FQDNs, such as server.contoso.com, or one or more IP addresses, or a combination of both FQDNs and IP addresses. If you enter an IP address, you must enter the IP address as a literal. For example, 10.10.1.1. The smart host identity can be the FQDN of a smart-host server, a mail exchanger (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart host server. 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"`. @@ -777,7 +843,6 @@ 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 @@ -787,13 +852,15 @@ Accept wildcard characters: False ``` ### -SmtpMaxMessagesPerConnection + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmtpMaxMessagesPerConnection parameter specifies the maximum number of messages the server can send per connection. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -803,13 +870,15 @@ Accept wildcard characters: False ``` ### -SourceIPAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SourceIPAddress parameter specifies the local IP address to use as the endpoint for an SMTP connection to a remote messaging server. The default IP address is 0.0.0.0. This value means that the server can use any available local IP address. This parameter is valid only for Send connectors configured on an Edge server. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -819,6 +888,9 @@ 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 can use this Send connector. This parameter isn't valid for Send connectors configured on an Edge server. 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"`. @@ -827,7 +899,6 @@ 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 @@ -837,6 +908,9 @@ Accept wildcard characters: False ``` ### -TlsAuthLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsAuthLevel parameter specifies the TLS authentication level that is used for outbound TLS connections established by this Send connector. Valid values are: - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. @@ -849,7 +923,6 @@ You can't specify a value for this parameter if the IgnoreSTARTTLS parameter is Type: TlsAuthLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -859,13 +932,15 @@ 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. A valid value for this parameter is `"X.500IssuerX.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint `, run the command `$TLSCertName = "$($TLSCert.Issuer)$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter. ```yaml Type: SmtpX509Identifier Parameter Sets: AddressSpaces Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -875,6 +950,9 @@ Accept wildcard characters: False ``` ### -TlsDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsDomain parameter specifies the domain name that the Send connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. This parameter is used only if the TlsAuthLevel parameter is set to DomainValidation. @@ -888,7 +966,6 @@ A value for this parameter is required if: Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -898,6 +975,9 @@ Accept wildcard characters: False ``` ### -Usage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Usage parameter specifies the default permissions and authentication methods assigned to the Send connector. The valid values are as follows: Custom, Internal, Internet, or Partner. The default is Custom. If you use the Usage parameter, you can't use any of the following parameters: @@ -913,7 +993,6 @@ For more information about Send connector usage types, permissions, and authenti Type: UsageType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -923,13 +1002,15 @@ Accept wildcard characters: False ``` ### -UseExternalDNSServersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseExternalDNSServersEnabled parameter specifies whether this Send connector uses the external DNS list specified by the ExternalDNSServers parameter of the Set-TransportService cmdlet. 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 @@ -939,13 +1020,15 @@ 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/exchange/New-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md similarity index 91% rename from exchange/exchange-ps/exchange/New-ServicePrincipal.md rename to exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md index 6e59edbe3e..16c9845bdd 100644 --- a/exchange/exchange-ps/exchange/New-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-serviceprincipal applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: New-ServicePrincipal -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-serviceprincipal +schema: 2.0.0 +title: New-ServicePrincipal --- # New-ServicePrincipal @@ -49,6 +50,9 @@ This example create a new service principal in Exchange Online with the specifie ## PARAMETERS ### -AppId + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The AppId parameter specifies the unique AppId GUID value for the service principal. For example, ca73fffa-cedb-4b84-860f-d7fb8aa8a6c1. A valid value for this parameter is available in the following locations: @@ -60,7 +64,6 @@ A valid value for this parameter is available in the following locations: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -ObjectId + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ObjectId parameter specifies the unique ObjectId GUID value for the service principal. For example, 7c7599b2-23af-45e3-99ff-0025d148e929. A valid value for this parameter is available in the following locations: @@ -81,7 +87,6 @@ A valid value for this parameter is available in the following locations: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -91,13 +96,15 @@ Accept wildcard characters: False ``` ### -ServiceId + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + This parameter is being deprecated. Use the ObjectId parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -107,6 +114,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -116,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The DisplayName parameter specifies the friendly name of the service principal. If the name contains spaces, enclose the name in quotation marks ("). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -142,13 +153,15 @@ 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 @@ -158,13 +171,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/New-SettingOverride.md rename to exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md index 6ffa158c1c..e72e27c9ab 100644 --- a/exchange/exchange-ps/exchange/New-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-settingoverride applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SettingOverride -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-settingoverride +schema: 2.0.0 +title: New-SettingOverride --- # New-SettingOverride @@ -62,13 +63,15 @@ For more information, see the topic [Change the offline address book generation ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the setting override. 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 @@ -78,6 +81,9 @@ Accept wildcard characters: False ``` ### -Component + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Component parameter specifies the component that the setting override is applied to. For example: - TimeBasedAssistants @@ -87,7 +93,6 @@ The Component parameter specifies the component that the setting override is app Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -97,6 +102,9 @@ Accept wildcard characters: False ``` ### -Parameters + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Parameters parameter specifies one or more parameters for the override that are available for the combination of the Component and Section parameter values. This parameter uses the syntax: `@("Parameter1=Value1","Parameter2=Value2"...)`. For example: - `@("Enabled=true")` @@ -106,7 +114,6 @@ The Parameters parameter specifies one or more parameters for the override that Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -116,13 +123,15 @@ Accept wildcard characters: False ``` ### -Reason + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Reason parameter specifies why you are creating the setting override. 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: Named @@ -132,13 +141,15 @@ Accept wildcard characters: False ``` ### -Section + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Section parameter specifies the name of the section for which the override is created. The available values for this parameter depend on the value of the Component parameter. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -148,6 +159,9 @@ 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`. @@ -157,7 +171,6 @@ 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 @@ -167,13 +180,15 @@ 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 @@ -183,6 +198,9 @@ 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. @@ -191,7 +209,6 @@ 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 @@ -201,6 +218,9 @@ Accept wildcard characters: False ``` ### -MaxVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxVersion parameter specifies the latest version of Exchange 2016 that this override applies to (up to and including the specified value). Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42. @@ -211,7 +231,6 @@ The default value is blank ($null), which means the override applies to all vers Type: Version Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -221,6 +240,9 @@ Accept wildcard characters: False ``` ### -MinVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MinVersion parameter specifies the earliest version of Exchange 2016 that this override applies to (up to and including the specified value). Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42. @@ -231,7 +253,6 @@ The default value is blank ($null), which means the override applies to all vers Type: Version Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,6 +262,9 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter specifies the name of the Exchange 2016 server where you want the override applied. You can specify a single Exchange 2016 server name, or an array of Exchange 2016 server name wildcards. For example, if you have three Exchange 2016 servers named Exchange01, Exchange02 and Exchange03, specify the value Exchange\* to apply the override to all of them. If you don't use this parameter to specify a server, the override applies to all Exchange 2016 servers in the Active Directory forest. @@ -249,7 +273,6 @@ If you don't use this parameter to specify a server, the override applies to all Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -259,13 +282,15 @@ 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/exchange/New-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/New-SharingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md index c955830dfd..d872da4d8c 100644 --- a/exchange/exchange-ps/exchange/New-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-sharingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-SharingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-sharingpolicy +schema: 2.0.0 +title: New-SharingPolicy --- # New-SharingPolicy @@ -54,13 +55,15 @@ This example creates a default sharing policy, which is applied to all mailboxes ## 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 new sharing 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,6 +73,9 @@ Accept wildcard characters: False ``` ### -Domains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Domains parameter specifies the domains and the associated sharing options for those domains in the sharing policy. Values for this parameter use the basic syntax: `'Domain: SharingPolicyAction'`. You can use the following values for `Domain`: @@ -91,7 +97,6 @@ You can specify multiple `'Domain: SharingPolicyAction'` values separated by com 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 @@ -101,6 +106,9 @@ 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`. @@ -110,7 +118,6 @@ 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 @@ -120,6 +127,9 @@ Accept wildcard characters: False ``` ### -Default + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch. If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled. @@ -128,7 +138,6 @@ If no sharing policy has been applied to a mailbox, the default policy is automa 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 @@ -138,6 +147,9 @@ 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. @@ -146,7 +158,6 @@ 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,6 +167,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether to enable the new sharing policy. Valid input for this parameter is $true or $false. The default is $true. When the sharing policy is disabled, users who are provisioned to use this policy continue to share information until the sharing policy assistant runs and removes the permissions on the shared folder. The frequency with which the sharing policy assistant runs is assigned in the Set-MailboxServer cmdlet using the SharingPolicySchedule parameter. @@ -164,7 +178,6 @@ When the sharing policy is disabled, users who are provisioned to use this polic 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 @@ -174,13 +187,15 @@ 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/exchange/New-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md similarity index 88% rename from exchange/exchange-ps/exchange/New-SiteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md index 21fd001892..cc4fb83d1a 100644 --- a/exchange/exchange-ps/exchange/New-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-sitemailbox applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SiteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-sitemailbox +schema: 2.0.0 +title: New-SiteMailbox --- # New-SiteMailbox @@ -51,13 +52,15 @@ You can't run this cmdlet from the Exchange Management Shell. Use SharePoint to ## PARAMETERS ### -DisplayName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DisplayName parameter specifies the display name that displays in the user's global address list and on SharePoint. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -67,13 +70,15 @@ Accept wildcard characters: False ``` ### -SharePointUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SharePointUrl parameter specifies the SharePoint URL where the site mailbox is hosted, for example, "https://myserver/teams/edu". ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -83,13 +88,15 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Alias parameter specifies the alias of the site mailbox. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -99,6 +106,9 @@ 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`. @@ -108,7 +118,6 @@ 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 @@ -118,6 +127,9 @@ Accept wildcard characters: False ``` ### -Database + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Database parameter specifies the mailbox database that holds the mailbox data for the site mailbox. You can use any value that uniquely identifies the database. For example: - Name @@ -128,7 +140,6 @@ The Database parameter specifies the mailbox database that holds the mailbox dat Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,13 +149,15 @@ 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 @@ -154,6 +167,9 @@ 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. This switch tests that site mailbox provisioning is working independently of the SharePoint deployment. We recommend that you never use this switch for production site mailboxes. @@ -162,7 +178,6 @@ This switch tests that site mailbox provisioning is working independently of the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,13 +187,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the site mailbox. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,13 +205,15 @@ Accept wildcard characters: False ``` ### -OrganizationalUnit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OrganizationalUnit parameter specifies the organizational unit in which the site mailbox resides. ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -204,13 +223,15 @@ Accept wildcard characters: False ``` ### -OverrideRecipientQuotas + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -220,13 +241,15 @@ 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/exchange/New-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md index 2766674f44..946583da41 100644 --- a/exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-sitemailboxprovisioningpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SiteMailboxProvisioningPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-sitemailboxprovisioningpolicy +schema: 2.0.0 +title: New-SiteMailboxProvisioningPolicy --- # New-SiteMailboxProvisioningPolicy @@ -71,13 +72,15 @@ This example creates the default provisioning policy named SM\_DefaultPolicy and ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the site mailbox provisioning 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 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -87,6 +90,9 @@ Accept wildcard characters: False ``` ### -AliasPrefix + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are: - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified. @@ -96,7 +102,6 @@ The AliasPrefix parameter specifies the custom text prefix to add to the aliases Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -106,6 +111,9 @@ 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`. @@ -115,7 +123,6 @@ 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 @@ -125,6 +132,9 @@ Accept wildcard characters: False ``` ### -DefaultAliasPrefixEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are: - $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). @@ -136,7 +146,6 @@ The value of this parameter is related to the value of the AliasPrefix parameter Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,13 +155,15 @@ 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 @@ -162,6 +173,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsDefault switch specifies that the site mailbox provisioning policy is the default policy. You don't need to specify a value with this switch. You can have multiple policies, but only the default policy is followed when users create site mailboxes. @@ -170,7 +184,6 @@ You can have multiple policies, but only the default policy is followed when use Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -180,6 +193,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -200,7 +216,6 @@ The default value is 49 GB. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -210,6 +225,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the site mailbox. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -227,7 +245,6 @@ A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the val Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -237,6 +254,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -257,7 +277,6 @@ The default value is 50 GB. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -267,13 +286,15 @@ 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/exchange/New-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewPolicyV2.md similarity index 93% rename from exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md rename to exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewPolicyV2.md index ed8687d950..86c093f393 100644 --- a/exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewPolicyV2.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-supervisoryreviewpolicyv2 applicable: Security & Compliance -title: New-SupervisoryReviewPolicyV2 -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-supervisoryreviewpolicyv2 +schema: 2.0.0 +title: New-SupervisoryReviewPolicyV2 --- # New-SupervisoryReviewPolicyV2 @@ -48,13 +49,15 @@ This example creates a new supervisory review policy named EU Brokers Policy. ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the supervisory review policy. The name can't exceed 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 @@ -64,13 +67,15 @@ Accept wildcard characters: False ``` ### -Reviewers + +> Applicable: Security & Compliance + The Reviewers parameter specifies the SMTP addresses of the reviewers for the supervisory review policy. You can specify multiple email addresses separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -80,13 +85,15 @@ 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 @@ -96,6 +103,9 @@ 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`. @@ -105,7 +115,6 @@ 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,13 +124,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Security & Compliance + {{ Fill Enabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -131,6 +142,9 @@ 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. @@ -139,7 +153,6 @@ 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 @@ -149,13 +162,15 @@ Accept wildcard characters: False ``` ### -PolicyRBACScopes + +> Applicable: Security & Compliance + {{ Fill PolicyRBACScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -165,13 +180,15 @@ Accept wildcard characters: False ``` ### -PreservationPeriodInDays + +> Applicable: Security & Compliance + {{ Fill PreservationPeriodInDays Description }} ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -181,13 +198,15 @@ Accept wildcard characters: False ``` ### -UserReportingWorkloads + +> Applicable: Security & Compliance + {{ Fill UserReportingWorkloads Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -197,13 +216,15 @@ 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/exchange/New-SupervisoryReviewRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewRule.md similarity index 92% rename from exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewRule.md index c4b9d1a57f..266df6ec91 100644 --- a/exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SupervisoryReviewRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-supervisoryreviewrule applicable: Security & Compliance -title: New-SupervisoryReviewRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-supervisoryreviewrule +schema: 2.0.0 +title: New-SupervisoryReviewRule --- # New-SupervisoryReviewRule @@ -67,13 +68,15 @@ This example creates a new supervisory review rule named EU Brokers Rule with th ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies the unique name for the supervisory review rule. The name can't exceed 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 @@ -83,6 +86,9 @@ Accept wildcard characters: False ``` ### -Policy + +> Applicable: Security & Compliance + The Policy parameter specifies the supervisory review policy that's assigned to the rule. You can use any value that uniquely identifies the policy. For example: - Name @@ -93,7 +99,6 @@ The Policy parameter specifies the supervisory review policy that's assigned to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -103,13 +108,15 @@ Accept wildcard characters: False ``` ### -AdvancedRule + +> Applicable: Security & Compliance + {{ Fill AdvancedRule Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -119,13 +126,15 @@ Accept wildcard characters: False ``` ### -CcsiDataModelOperator + +> Applicable: Security & Compliance + {{ Fill CcsiDataModelOperator Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -135,6 +144,9 @@ Accept wildcard characters: False ``` ### -Condition + +> Applicable: Security & Compliance + The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax: - User or group communications to supervise: `"((Reviewee:) -OR (Reviewee:)...)"`. Exceptions use the syntax `"(NOT((Reviewee:) -OR (Reviewee:)...))"`. @@ -151,7 +163,6 @@ The Condition parameter specifies the conditions and exceptions for the rule. Th Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -161,6 +172,9 @@ 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`. @@ -170,7 +184,6 @@ 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 @@ -180,13 +193,15 @@ Accept wildcard characters: False ``` ### -ContentContainsSensitiveInformation + +> Applicable: Security & Compliance + {{ Fill ContentContainsSensitiveInformation Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -196,13 +211,15 @@ Accept wildcard characters: False ``` ### -ContentMatchesDataModel + +> Applicable: Security & Compliance + {{ Fill ContentMatchesDataModel Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -212,13 +229,15 @@ Accept wildcard characters: False ``` ### -ContentSources + +> Applicable: Security & Compliance + {{ Fill ContentSources Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -228,13 +247,15 @@ Accept wildcard characters: False ``` ### -DayXInsights + +> Applicable: Security & Compliance + {{ Fill DayXInsights Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -244,13 +265,15 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom + +> Applicable: Security & Compliance + {{ Fill ExceptIfFrom Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -260,13 +283,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfRecipientDomainIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -276,13 +301,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRevieweeIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfRevieweeIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -292,13 +319,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfSenderDomainIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -308,13 +337,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Security & Compliance + {{ Fill ExceptIfSentTo Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -324,13 +355,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords + +> Applicable: Security & Compliance + {{ Fill ExceptIfSubjectOrBodyContainsWords Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -340,13 +373,15 @@ Accept wildcard characters: False ``` ### -From + +> Applicable: Security & Compliance + {{ Fill From Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -356,13 +391,15 @@ Accept wildcard characters: False ``` ### -IncludeAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill IncludeAdaptiveScopes Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -372,13 +409,15 @@ Accept wildcard characters: False ``` ### -InPurviewFilter + +> Applicable: Security & Compliance + {{ Fill InPurviewFilter Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -388,13 +427,15 @@ Accept wildcard characters: False ``` ### -Ocr + +> Applicable: Security & Compliance + {{ Fill Ocr Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -404,13 +445,15 @@ Accept wildcard characters: False ``` ### -PolicyRBACScopes + +> Applicable: Security & Compliance + {{ Fill PolicyRBACScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -420,13 +463,15 @@ Accept wildcard characters: False ``` ### -SamplingRate + +> Applicable: Security & Compliance + The SamplingRate parameter specifies the percentage of communications for review. If you want reviewers to review all detected items, use the value 100. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -436,13 +481,15 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Security & Compliance + {{ Fill SentTo Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -452,13 +499,15 @@ 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/exchange/New-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md similarity index 91% rename from exchange/exchange-ps/exchange/New-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md index 6aa53c55aa..8a94e9b228 100644 --- a/exchange/exchange-ps/exchange/New-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-sweeprule applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-SweepRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-sweeprule +schema: 2.0.0 +title: New-SweepRule --- # New-SweepRule @@ -66,13 +67,15 @@ This example creates a new Sweep rule named "From Jeff" in Felipe Apodaca's mail ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the Sweep rule. 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: True Position: 1 @@ -82,6 +85,9 @@ Accept wildcard characters: False ``` ### -Provider + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Provider parameter specifies the provider for the Sweep rule. If the value contains spaces, enclose the value in quotation marks. For Sweep rules that you create in Outlook on the web, the default value is Exchange16. @@ -90,7 +96,6 @@ For Sweep rules that you create in Outlook on the web, the default value is Exch Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -100,6 +105,9 @@ 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`. @@ -109,7 +117,6 @@ 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 @@ -119,6 +126,9 @@ Accept wildcard characters: False ``` ### -DestinationFolder + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The DestinationFolder parameter specifies an action for the Sweep rule that moves messages to the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: @@ -140,7 +150,6 @@ Example values for this parameter are `john@contoso.com:\Unimportant` or `John:\ Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -150,6 +159,9 @@ 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. @@ -158,7 +170,6 @@ 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 @@ -168,6 +179,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether the Sweep rule is enabled or disabled. Valid values are: - $true: The rule is enabled. This is the default value. @@ -179,7 +193,6 @@ After you create the rule, you can enable or disable it by using the Enable-Swee Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -189,6 +202,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFlagged + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExceptIfFlagged parameter specifies an exception for the Sweep rule that looks messages with a message flag applied. Valid values are: @@ -214,7 +230,6 @@ The typical message flag values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -224,6 +239,9 @@ Accept wildcard characters: False ``` ### -ExceptIfPinned + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PinMessage parameter specifies an exception for the Sweep rule that looks for pinned messages. Valid values are: @@ -235,7 +253,6 @@ The PinMessage parameter specifies an exception for the Sweep rule that looks fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -245,6 +262,9 @@ Accept wildcard characters: False ``` ### -KeepForDays + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The KeepForDays parameter specifies an action for the Sweep rule that specifies the number of days to keep messages that match the conditions of the rule. After the number of days have passed, the messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder). You can't use this parameter with the KeepLatest parameter and the Sweep rule must contain a KeepForDays or KeepLatest parameter value. @@ -253,7 +273,6 @@ You can't use this parameter with the KeepLatest parameter and the Sweep rule mu Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -263,6 +282,9 @@ Accept wildcard characters: False ``` ### -KeepLatest + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The KeepLatest parameter specifies an action for the Sweep rule that specifies the number of messages to keep that match the conditions of the rule. After the number of messages is exceeded, the oldest messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder). You can't use this parameter with the KeepForDays parameter and the Sweep rule must contain a KeepForDays or KeepLatest parameter value. @@ -271,7 +293,6 @@ You can't use this parameter with the KeepForDays parameter and the Sweep rule m Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -281,6 +302,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailbox parameter specifies the mailbox where you want to create the Sweep rule. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -298,7 +322,6 @@ The Mailbox parameter specifies the mailbox where you want to create the Sweep r Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -308,6 +331,9 @@ Accept wildcard characters: False ``` ### -Sender + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Sender parameter specifies a condition for the Sweep rule that looks for the specified sender in messages. For internal senders, you can use any value that uniquely identifies the sender. For example: - Name @@ -323,7 +349,6 @@ For external senders, use their email address. Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -333,6 +358,9 @@ Accept wildcard characters: False ``` ### -SourceFolder + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceFolder parameter specifies a condition for the Sweep rule that looks for messages in the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: @@ -354,7 +382,6 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -364,6 +391,9 @@ Accept wildcard characters: False ``` ### -SystemCategory + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SystemCategory parameter specifies a condition for the sweep rule that looks for messages with the specified system category. System categories are available to all mailboxes in the organization. Valid values are: - NotDefined @@ -395,7 +425,6 @@ The SystemCategory parameter specifies a condition for the sweep rule that looks Type: SystemCategoryType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -405,13 +434,15 @@ 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/exchange/New-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md index 8084e8b744..2f76a37518 100644 --- a/exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-syncmailpublicfolder applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: New-SyncMailPublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-syncmailpublicfolder +schema: 2.0.0 +title: New-SyncMailPublicFolder --- # New-SyncMailPublicFolder @@ -76,6 +77,9 @@ This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Syn ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the unique name of the mail-enabled public folder. 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. @@ -84,7 +88,6 @@ 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 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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: @@ -118,7 +124,6 @@ The Alias parameter never generates or updates the primary email address of a ma Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -128,13 +133,15 @@ Accept wildcard characters: False ``` ### -EntryId + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 Required: True Position: Named @@ -144,6 +151,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -165,7 +175,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: DeliveryRecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -175,6 +184,9 @@ 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`. @@ -184,7 +196,6 @@ 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 @@ -194,6 +205,9 @@ Accept wildcard characters: False ``` ### -Contacts + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Contacts parameter specifies the contacts for the public folder. Contacts are persons about whom you can save several types of information, such as addresses, telephone numbers, and web page URLs. Valid values for this parameter are recipients in your organization. You can use any value that uniquely identifies the recipient. For example: @@ -211,7 +225,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -221,13 +234,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -237,13 +252,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -253,13 +270,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -269,13 +288,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -285,13 +306,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -301,13 +324,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -317,13 +342,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -333,13 +360,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -349,13 +378,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -365,13 +396,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -381,13 +414,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -397,13 +432,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -413,13 +450,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -429,13 +468,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -445,13 +486,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Required: False Position: Named @@ -461,6 +504,9 @@ Accept wildcard characters: False ``` ### -DeliverToMailboxAndForward + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress parameter. Valid values are: - $true: Messages are delivered to this mail-enabled public folder and forwarded to the specified recipient or email address. @@ -472,7 +518,6 @@ The default value is $false. This parameter is meaningful only if you configure Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -482,6 +527,9 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The DisplayName parameter specifies the display name of the mail-enabled public folder. The display name is visible in the Exchange admin center, in address lists, and in 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. @@ -490,7 +538,6 @@ 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 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -500,6 +547,9 @@ 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. @@ -508,7 +558,6 @@ 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 @@ -518,6 +567,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -539,7 +591,6 @@ To specify the primary SMTP email address, you can use any of the following meth Type: ProxyAddress[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -549,13 +600,15 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalEmailAddress parameter specifies an email address outside the organization. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -565,6 +618,9 @@ Accept wildcard characters: False ``` ### -ForwardingAddress + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForwardingAddress parameter specifies a forwarding address for messages that are sent to this mail-enabled public folder. A valid value for this parameter is a recipient in your organization. You can use any value that uniquely identifies the recipient. For example: - Name @@ -585,7 +641,6 @@ The default value is blank ($null), which means no forwarding recipient is confi Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -595,6 +650,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail-enabled public folder. Although messages send on behalf of the public folder clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the public folder, not the sender. The sender you specify for this parameter must be a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -614,7 +672,6 @@ By default, this parameter is blank, which means no one else has permission to s Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -624,13 +681,15 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The HiddenFromAddressListsEnabled switch specifies that this recipient is not visible in address lists. 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 @@ -640,6 +699,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail-enabled public folder. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -659,7 +721,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -669,6 +730,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail-enabled public folder. When you enter a value, qualify the value with one of the following units: @@ -688,7 +752,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -698,13 +761,15 @@ Accept wildcard characters: False ``` ### -OnPremisesObjectId + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The OnPremisesObjectId parameter specifies the GUID of the on-premises mail-enabled public folder that's used to create the mail-enabled public folder object in Exchange Online. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -714,13 +779,15 @@ Accept wildcard characters: False ``` ### -OverrideRecipientQuotas + +> 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: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -730,6 +797,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -751,7 +821,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: DeliveryRecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -761,6 +830,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -770,7 +842,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -780,13 +851,15 @@ 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 @@ -796,6 +869,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -807,7 +883,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director Type: SmtpAddress 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/exchange/New-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md similarity index 93% rename from exchange/exchange-ps/exchange/New-SystemMessage.md rename to exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md index 05d97b7970..bee811829f 100644 --- a/exchange/exchange-ps/exchange/New-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-systemmessage applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-SystemMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-systemmessage +schema: 2.0.0 +title: New-SystemMessage --- # New-SystemMessage @@ -62,6 +63,9 @@ This example creates a custom English quota message for mailboxes that exceed th ## PARAMETERS ### -DsnCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DsnCode parameter specifies the enhanced status code for the custom system message. Valid values are 4.x.y or 5.x.y where x and y are one to three digit numbers. You can specify a default code that's included with Exchange, or you can specify a custom code. @@ -76,7 +80,6 @@ You can't use this parameter with the QuotaMessageType parameter. Type: EnhancedStatusCode Parameter Sets: Dsn Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -86,6 +89,9 @@ Accept wildcard characters: False ``` ### -Internal + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Internal parameter specifies whether the system message is displayed to internal or external users. Valid values are: - $true: The NDR is displayed to internal senders. @@ -99,7 +105,6 @@ You can't use this parameter with the QuotaMessageType parameter. Type: Boolean Parameter Sets: Dsn Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -109,6 +114,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Language parameter specifies the language of the message (for example, en for English or ja for Japanese). For the list of supported language codes, see [Supported languages for NDRs](https://learn.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). You need to use this parameter with the DsnCode or QuotaMessageType parameters. @@ -117,7 +125,6 @@ You need to use this parameter with the DsnCode or QuotaMessageType parameters. Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -127,6 +134,9 @@ Accept wildcard characters: False ``` ### -QuotaMessageType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QuotaMessageType parameter specifies the quota for the custom system message. Valid values are: Mailbox size quotas: @@ -171,7 +181,6 @@ You can't use this parameter with the DsnCode or Internal parameters. Type: QuotaMessageType Parameter Sets: Quota Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -181,6 +190,9 @@ Accept wildcard characters: False ``` ### -Text + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Text parameter specifies the text in the custom system message. The text should explain why the system message was sent, and any actions that the user should take. You need to use this parameter with the DsnCode or QuotaMessageType parameters. @@ -210,7 +222,6 @@ Here's an example value for this parameter that uses HTML tags and special chara Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -220,6 +231,9 @@ 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`. @@ -229,7 +243,6 @@ 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 @@ -239,6 +252,9 @@ 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. @@ -247,7 +263,6 @@ 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 @@ -257,13 +272,15 @@ 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/exchange/New-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md index 18775fc30b..d0fbdf857f 100644 --- a/exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-teamsprotectionpolicy applicable: Exchange Online -title: New-TeamsProtectionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-teamsprotectionpolicy +schema: 2.0.0 +title: New-TeamsProtectionPolicy --- # New-TeamsProtectionPolicy @@ -48,13 +49,15 @@ This example creates the Teams protection policy with the default values. ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the unique name of the Teams protection policy. If the value contains spaces, enclose the value in quotation marks. The default name of the Teams protection policy in an organization is Teams Protection Policy. We recommend using this value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -64,6 +67,12 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: Exchange Online + + +> 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,8 +82,6 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Online -Applicable: Exchange Online Required: False Position: Named @@ -84,6 +91,9 @@ Accept wildcard characters: False ``` ### -HighConfidencePhishQuarantineTag + +> Applicable: Exchange Online + The HighConfidencePhishQuarantineTag parameter specifies the quarantine policy that's used for messages that are quarantined as high confidence phishing by ZAP for Teams. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -98,7 +108,6 @@ If you don't use this parameter, the default quarantine policy that's used is na Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -108,6 +117,9 @@ Accept wildcard characters: False ``` ### -MalwareQuarantineTag + +> Applicable: Exchange Online + The MalwareQuarantineTag parameter specifies the quarantine policy that's used for messages that are quarantined as malware by ZAP for Teams. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -122,7 +134,6 @@ If you don't use this parameter, the default quarantine policy that's used is na Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -132,13 +143,15 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -148,13 +161,15 @@ 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 @@ -164,6 +179,9 @@ Accept wildcard characters: False ``` ### -ZapEnabled + +> Applicable: Exchange Online + The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are: - $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value. @@ -173,7 +191,6 @@ The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md index b2a9f0c731..da1023d2ca 100644 --- a/exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-teamsprotectionpolicyrule applicable: Exchange Online -title: New-TeamsProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-teamsprotectionpolicyrule +schema: 2.0.0 +title: New-TeamsProtectionPolicyRule --- # New-TeamsProtectionPolicyRule @@ -58,13 +59,15 @@ This example creates the Teams protection policy rule with members of the group ## PARAMETERS ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the unique name of the Teams protection policy rule. If the value contains spaces, enclose the value in quotation marks. The default name of the Teams protection policy rule in an organization is Teams Protection Policy Rule. We recommend using this value. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -74,13 +77,15 @@ Accept wildcard characters: False ``` ### -TeamsProtectionPolicy + +> Applicable: Exchange Online + The TeamsProtectionPolicy parameter specifies the Teams protection policy that's associated with this rule. The only available policy is named Teams Protection Policy. ```yaml Type: TeamsProtectionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ 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`. @@ -115,7 +125,6 @@ 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 @@ -125,13 +134,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -141,13 +152,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Online + The ExceptIfRecipientDomainIs parameter specifies an exception to ZAP for Teams protection that looks for recipients of Teams messages 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 @@ -157,6 +170,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Online + The ExceptIfSentTo parameter specifies an exception to ZAP for Teams protection that looks for recipients of Teams messages. You can use any value that uniquely identifies the recipient. For example: - Name @@ -172,7 +188,6 @@ 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 @@ -182,6 +197,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + The ExceptIfSentToMemberOf parameter specifies an exception to ZAP for Teams protection that looks for Teams messages sent to members of distribution groups or mail-enabled security groups. You can use any value that uniquely identifies the group. For example: - Name @@ -199,7 +217,6 @@ If you remove the group after you create the rule, no exception is made for Team Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -209,13 +226,15 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -225,13 +244,15 @@ 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/exchange/New-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md similarity index 92% rename from exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md rename to exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md index bd3cf8d4ad..fab10b4e31 100644 --- a/exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-tenantallowblocklistitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: New-TenantAllowBlockListItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-tenantallowblocklistitems +schema: 2.0.0 +title: New-TenantAllowBlockListItems --- # New-TenantAllowBlockListItems @@ -86,6 +87,9 @@ For URLs identified as malware or high-confidence phishing, you need to submit t ## PARAMETERS ### -Entries + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Entries parameter specifies the values that you want to add to the Tenant Allow/Block List based on the ListType parameter value: - FileHash: Use the SHA256 hash value of the file. You can find the SHA256 hash value by running the following command in PowerShell: `Get-FileHash -Path "\" -Algorithm SHA256`. An example value is `768a813668695ef2483b2bde7cf5d1b2db0423a0d3e63e498f3ab6f2eb13ea3`. @@ -117,7 +121,6 @@ In most cases, you can't modify the sender, URL, file, or IP address values afte Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -127,6 +130,9 @@ Accept wildcard characters: False ``` ### -ExpirationDate + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ExpirationDate parameter set the expiration date of the entry in Coordinated Universal Time (UTC). To specify a date/time value for this parameter, use either of the following options: @@ -140,7 +146,6 @@ You can't use this parameter with the NoExpiration or RemoveAfter parameters. Type: DateTime Parameter Sets: Expiration Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -150,6 +155,9 @@ Accept wildcard characters: False ``` ### -ListType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListType parameter specifies the type of entry to add. Valid values are: - FileHash @@ -161,7 +169,6 @@ The ListType parameter specifies the type of entry to add. Valid values are: Type: ListType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -171,6 +178,9 @@ Accept wildcard characters: False ``` ### -NoExpiration + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The NoExpiration switch specifies that the entry should never expire. You don't need to specify a value with this switch. This switch is available to use in the following scenarios: @@ -185,7 +195,6 @@ You can't use this switch with the ExpirationDate or RemoveAfter parameter. Type: SwitchParameter Parameter Sets: NoExpiration Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -195,6 +204,9 @@ Accept wildcard characters: False ``` ### -Allow + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Allow switch specifies that you're creating an allow entry. You don't need to specify a value with this switch. You can't use this switch with the Block switch. @@ -207,7 +219,6 @@ You can also use allow entries for non-Microsoft phishing simulation URLs with n Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -217,6 +228,9 @@ Accept wildcard characters: False ``` ### -Block + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Allow switch specifies that you're creating a block entry. You don't need to specify a value with this switch. You can't use this switch with the Allow switch. @@ -225,7 +239,6 @@ You can't use this switch with the Allow switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -235,6 +248,9 @@ Accept wildcard characters: False ``` ### -ListSubType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListSubType parameter specifies the subtype for this entry. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). @@ -244,7 +260,6 @@ The ListSubType parameter specifies the subtype for this entry. Valid values are Type: ListSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -254,13 +269,15 @@ Accept wildcard characters: False ``` ### -LogExtraDetails + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill LogExtraDetails Description }} ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -270,13 +287,15 @@ Accept wildcard characters: False ``` ### -Notes + +> Applicable: Exchange Online, Security & Compliance, 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 Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -286,6 +305,9 @@ Accept wildcard characters: False ``` ### -RemoveAfter + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The RemoveAfter parameter enables the **Remove on** \> **45 days after last used date** feature for an allow entry. The LastUsedDate property is populated when the bad entity in the allow entry is encountered by the filtering system during mail flow or time of click. The allow entry is kept for 45 days after the filtering system determines that the entity is clean. The only valid value for this parameter is 45. @@ -298,7 +320,6 @@ You can't use this parameter with the ExpirationDate or NoExpirationDate paramet Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -308,6 +329,9 @@ 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. @@ -316,7 +340,6 @@ 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 @@ -326,13 +349,15 @@ Accept wildcard characters: False ``` ### -SubmissionID + +> 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 diff --git a/exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md similarity index 90% rename from exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md rename to exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md index 48976dd565..886afbc790 100644 --- a/exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-tenantallowblocklistspoofitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: New-TenantAllowBlockListSpoofItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-tenantallowblocklistspoofitems +schema: 2.0.0 +title: New-TenantAllowBlockListSpoofItems --- # New-TenantAllowBlockListSpoofItems @@ -44,13 +45,15 @@ This example creates an allow entry for the sender bob@contoso.com from the sour ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Identity parameter uses the value Default. ```yaml Type: HostedConnectionFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 0 @@ -60,6 +63,9 @@ Accept wildcard characters: False ``` ### -SendingInfrastructure + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The SendingInfrastructure parameter specifies the source of the messages sent by the spoofed sender that's defined in the SpoofedUser parameter. Valid values are: - An email domain (for example contoso.com). The domain is found in the reverse DNS lookup (PTR record) of the source email server's IP address. @@ -70,7 +76,6 @@ The SendingInfrastructure parameter specifies the source of the messages sent by Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -80,6 +85,9 @@ Accept wildcard characters: True ``` ### -SpoofedUser + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The SpoofedUser parameter specifies the email address or domain for the spoofed sender entry. - For domains outside your organization (cross-org), use the domain of the email address that appears in the From field of the message. @@ -91,7 +99,6 @@ For spoofed senders, the maximum number of entries is 1024. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -101,6 +108,9 @@ Accept wildcard characters: True ``` ### -SpoofType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The SpoofType parameter specifies whether this is an internal or external spoofed sender entry. Valid values are: - External @@ -110,7 +120,6 @@ The SpoofType parameter specifies whether this is an internal or external spoofe Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -120,6 +129,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Action parameter specifies whether is an allowed or blocked spoofed sender entry. Valid values are: - Allow @@ -129,7 +141,6 @@ The Action parameter specifies whether is an allowed or blocked spoofed sender e Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -139,6 +150,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -148,7 +162,6 @@ 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 @@ -158,13 +171,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/New-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md similarity index 87% rename from exchange/exchange-ps/exchange/New-ThrottlingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md index 4b540a9784..ab43f9ad8c 100644 --- a/exchange/exchange-ps/exchange/New-ThrottlingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-throttlingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-ThrottlingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-throttlingpolicy +schema: 2.0.0 +title: New-ThrottlingPolicy --- # New-ThrottlingPolicy @@ -233,13 +234,15 @@ This example creates a throttling policy that restricts a user to be able to onl ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy`. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -249,13 +252,15 @@ Accept wildcard characters: False ``` ### -AnonymousCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousCutoffBalance parameter specifies the resource consumption limits for an anonymous user before the user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -265,13 +270,15 @@ Accept wildcard characters: False ``` ### -AnonymousMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousMaxBurst parameter specifies the amount of time that an anonymous user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -281,13 +288,15 @@ Accept wildcard characters: False ``` ### -AnonymousMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousMaxConcurrency parameter specifies how many anonymous connections can be made to a user's calendar data at the same time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If anonymous users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The AnonymousMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 1. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,6 +306,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInAD parameter specifies the percentage of a minute that anonymous users can spend executing LDAP requests (PercentTimeInAD) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -305,7 +317,6 @@ The AnonymousPercentTimeInAD parameter specifies the percentage of a minute that Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -315,6 +326,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInCAS parameter specifies the percentage of a minute that anonymous users can spend executing CAS code (PercentTimeInCAS) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -323,7 +337,6 @@ The AnonymousPercentTimeInCAS parameter specifies the percentage of a minute tha Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -333,6 +346,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInMailboxRPC parameter specifies the percentage of a minute that anonymous users can spend executing mailbox RPC requests (PercentTimeInMailboxRPC) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -341,7 +357,6 @@ The AnonymousPercentTimeInMailboxRPC parameter specifies the percentage of a min Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -351,13 +366,15 @@ Accept wildcard characters: False ``` ### -AnonymousRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousRechargeRate parameter specifies the rate at which an anonymous user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -367,13 +384,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -383,13 +402,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -399,13 +420,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -415,13 +438,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -431,13 +456,15 @@ Accept wildcard characters: False ``` ### -ComplianceMaxExpansionDGRecipients + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ComplianceMaxExpansionDGRecipients parameter specifies the maximum number of recipients to expand in distribution groups when a discovery search is looking for a specified recipient. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -447,13 +474,15 @@ Accept wildcard characters: False ``` ### -ComplianceMaxExpansionNestedDGs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ComplianceMaxExpansionNestedDGs parameter specifies the maximum number of nested distribution groups to expand when a discovery search is looking for a specified recipient. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -463,6 +492,9 @@ 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,7 +504,6 @@ 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 @@ -482,13 +513,15 @@ Accept wildcard characters: False ``` ### -ConsensusCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -498,13 +531,15 @@ Accept wildcard characters: False ``` ### -ConsensusMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -514,13 +549,15 @@ Accept wildcard characters: False ``` ### -ConsensusMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -530,13 +567,15 @@ Accept wildcard characters: False ``` ### -ConsensusRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -546,13 +585,15 @@ Accept wildcard characters: False ``` ### -CpaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaCutoffBalance parameter specifies the resource consumption limits for a cross-premises user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -562,13 +603,15 @@ Accept wildcard characters: False ``` ### -CpaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaMaxBurst parameter specifies the amount of time that a cross-premises user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -578,13 +621,15 @@ Accept wildcard characters: False ``` ### -CPAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaMaxConcurrency parameter specifies how many concurrent connections a cross-premises user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The CpaMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -594,13 +639,15 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + The CPAPercentTimeInCAS parameter specifies the percentage of a minute that a cross-premises user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -610,6 +657,9 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CPAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that a cross-premises user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -618,7 +668,6 @@ The CPAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -628,13 +677,15 @@ Accept wildcard characters: False ``` ### -CpaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaRechargeRate parameter specifies the rate at which a cross premises user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -644,6 +695,9 @@ Accept wildcard characters: False ``` ### -CPUStartPercent + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CPUStartPercent parameter specifies the per-process CPU percentage at which users governed by this policy begin to be backed off. Valid values are from 0 through 100. Use $null to turn off CPU percentage-based throttling for this policy. @@ -652,7 +706,6 @@ The CPUStartPercent parameter specifies the per-process CPU percentage at which Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -662,13 +715,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. To modify the discovery throttling parameters, create a new policy and name it "DiscoveryThrottlingPolicy". ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -678,13 +733,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxKeywords parameter specifies the maximum number of keywords that a user can include in a discovery search. For more information, see [Search-Mailbox](https://learn.microsoft.com/powershell/module/exchange/search-mailbox). ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -694,13 +751,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywordsPerPage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxKeywordsPerPage parameter specifies the number of keywords for which to show statistics on a single page in the EAC. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -710,13 +769,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxMailboxes parameter specifies the maximum number of source mailboxes that a user can include in a discovery search. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -726,13 +787,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxPreviewSearchMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxPreviewSearchMailboxes parameter specifies the maximum number of mailboxes that a user can include in eDiscovery Search Preview. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -742,13 +805,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxRefinerResults + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't used and will be removed. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -758,13 +823,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxSearchQueueDepth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxSearchQueueDepth parameter specifies the maximum number of concurrent discovery search threads that can be active at the same time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -774,13 +841,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxStatsSearchMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxStatsSearchMailboxes parameter specifies the maximum number of mailboxes that a user can search in an In-Place eDiscovery search without being able to view the statistics. When the number of mailboxes configured with the DiscoveryMaxStatsSearchMailboxes parameter is exceeded, the user must copy the search results to a discovery mailbox to view the statistics for the discovery search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -790,13 +859,15 @@ Accept wildcard characters: False ``` ### -DiscoveryPreviewSearchResultsPageSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryPreviewSearchResultsPageSize parameter specifies the number of messages displayed on a single page in eDiscovery Search Preview. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -806,13 +877,15 @@ Accept wildcard characters: False ``` ### -DiscoverySearchTimeoutPeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -822,6 +895,9 @@ 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. @@ -830,7 +906,6 @@ 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 @@ -840,13 +915,15 @@ Accept wildcard characters: False ``` ### -EasCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasCutoffBalance parameter specifies the resource consumption limits for an Exchange ActiveSync user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -856,13 +933,15 @@ Accept wildcard characters: False ``` ### -EasMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxBurst parameter specifies the amount of time that an Exchange ActiveSync user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -872,13 +951,15 @@ Accept wildcard characters: False ``` ### -EASMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxConcurrency parameter specifies how many concurrent connections an Exchange ActiveSync user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EasMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -888,13 +969,15 @@ Accept wildcard characters: False ``` ### -EASMaxDeviceDeletesPerMonth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxDeviceDeletesPerMonth parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can delete per month. By default, each user can delete a maximum of 20 partnerships per calendar month. When the limit is reached, the partnership deletion attempt fails and an error message is displayed to the user. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -904,13 +987,15 @@ Accept wildcard characters: False ``` ### -EASMaxDevices + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxDevices parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can have at one time. By default, each user can create 100 Exchange ActiveSync partnerships with their Exchange account. After users exceed the limit, they must delete one of their existing partnerships before they can create any more new partnerships. An email error message describing the limitation is sent to the user when the limit is exceeded. Additionally, an event is logged in the Application log when a user exceeds the limit. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -920,13 +1005,15 @@ Accept wildcard characters: False ``` ### -EasMaxInactivityForDeviceCleanup + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -936,6 +1023,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInAD parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -944,7 +1034,6 @@ The EASPercentTimeInAD parameter specifies the percentage of a minute that an Ex Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -954,6 +1043,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInCAS parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -962,7 +1054,6 @@ The EASPercentTimeInCAS parameter specifies the percentage of a minute that an E Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -972,6 +1063,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -980,7 +1074,6 @@ The EASPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -990,13 +1083,15 @@ Accept wildcard characters: False ``` ### -EasRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasRechargeRate parameter specifies the rate at which an Exchange ActiveSync user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1006,13 +1101,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1022,13 +1119,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1038,13 +1137,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1054,13 +1155,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1070,13 +1173,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1086,13 +1191,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1102,13 +1209,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1118,13 +1227,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1134,13 +1245,15 @@ Accept wildcard characters: False ``` ### -EwsCostThreshold + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The EwsCostThreshold parameter specifies the cost threshold for Exchange Web Services users. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1150,13 +1263,15 @@ Accept wildcard characters: False ``` ### -EwsCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsCutoffBalance parameter specifies the resource consumption limits for an Exchange Web Services user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1166,13 +1281,15 @@ Accept wildcard characters: False ``` ### -EwsMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxBurst parameter specifies the amount of time that an Exchange Web Services user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1182,6 +1299,9 @@ Accept wildcard characters: False ``` ### -EWSFastSearchTimeoutInSeconds + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSFastSearchTimeoutInSeconds parameter specifies the amount of time that searches made using Exchange Web Services continue before they time out. If the search takes more than the time indicated by the policy value, the search stops and an error is returned. The default value of this setting is 60 seconds. @@ -1190,7 +1310,6 @@ The EWSFastSearchTimeoutInSeconds parameter specifies the amount of time that se Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1200,6 +1319,9 @@ Accept wildcard characters: False ``` ### -EWSFindCountLimit + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSFindCountLimit parameter specifies the maximum result size of FindItem or FindFolder calls that can exist in memory on the Client Access server at the same time for this user in this current process. If an attempt is made to find more items or folders than your policy limit allows, an error is returned. However, the limit isn't strictly enforced if the call is made within the context of an indexed page view. Specifically, in this scenario, the search results are truncated to include the number of items and folders that fit within the policy limit. You can then continue paging into your results set via further FindItem or FindFolder calls. @@ -1208,7 +1330,6 @@ The EWSFindCountLimit parameter specifies the maximum result size of FindItem or Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1218,13 +1339,15 @@ Accept wildcard characters: False ``` ### -EWSMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxConcurrency parameter specifies how many concurrent connections an Exchange Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EwsMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1234,13 +1357,15 @@ Accept wildcard characters: False ``` ### -EWSMaxSubscriptions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxSubscriptions parameter specifies the maximum number of active push and pull subscriptions that an Exchange Web Services user can have on a specified Exchange server at the same time. If a user tries to create more subscriptions than the configured maximum, the subscription fails, and an event is logged in Event Viewer. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1250,6 +1375,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInAD parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1258,7 +1386,6 @@ The EWSPercentTimeInAD parameter specifies the percentage of a minute that an Ex Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1268,6 +1395,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInCAS parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1276,7 +1406,6 @@ The EWSPercentTimeInCAS parameter specifies the percentage of a minute that an E Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1286,6 +1415,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1294,7 +1426,6 @@ The EWSPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1304,13 +1435,15 @@ Accept wildcard characters: False ``` ### -EwsRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsRechargeRate parameter specifies the rate at which an Exchange Web Services user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1320,6 +1453,9 @@ Accept wildcard characters: False ``` ### -ExchangeMaxCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExchangeMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is slowed down. The value specified by this parameter should be less than the value specified by the PowerShellMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. We recommend that you set values for both parameters at the same time. @@ -1328,7 +1464,6 @@ The time period used for this limit is specified by the PowerShellMaxCmdletsTime Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1338,13 +1473,15 @@ Accept wildcard characters: False ``` ### -ForwardeeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForwardeeLimit parameter specifies the limits for the number of recipients that can be configured in Inbox Rules when using the forward or redirect action. This parameter doesn't limit the number of messages that can be forwarded or redirected to the recipients that are configured. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1354,13 +1491,15 @@ Accept wildcard characters: False ``` ### -ImapCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapCutoffBalance parameter specifies the resource consumption limits for an IMAP user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1370,13 +1509,15 @@ Accept wildcard characters: False ``` ### -ImapMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapMaxBurst parameter specifies the amount of time that an IMAP user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1386,13 +1527,15 @@ Accept wildcard characters: False ``` ### -IMAPMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapMaxConcurrency parameter specifies how many concurrent connections an IMAP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The ImapMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1402,6 +1545,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInAD parameter specifies the percentage of a minute that an IMAP user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1410,7 +1556,6 @@ The IMAPPercentTimeInAD parameter specifies the percentage of a minute that an I Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1420,6 +1565,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInCAS parameter specifies the percentage of a minute that an IMAP user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1428,7 +1576,6 @@ The IMAPPercentTimeInCAS parameter specifies the percentage of a minute that an Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1438,6 +1585,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an IMAP user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1446,7 +1596,6 @@ The IMAPPercentTimeInMailboxRPC parameter specifies the percentage of a minute t Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1456,13 +1605,15 @@ Accept wildcard characters: False ``` ### -ImapRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapRechargeRate parameter specifies the rate at which the IMAP user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1472,6 +1623,9 @@ Accept wildcard characters: False ``` ### -IsServiceAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsServiceAccount switch specifies that the user accounts associated with this policy are moderated by per-user thresholds and the health of system resources (for example, overall CPU usage). You don't need to specify a value with this switch. You might want to use this switch if you intend to associate this policy with user accounts that require higher throttling limits (for example, service accounts that perform IMAP mailbox migrations or nightly Windows PowerShell tasks). @@ -1482,7 +1636,6 @@ By using this switch, work done by these accounts is moderated by the higher use Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1492,13 +1645,15 @@ Accept wildcard characters: False ``` ### -MessageRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateLimit parameter specifies the number of messages per minute that can be submitted to transport by POP3 or IMAP4 clients that use SMTP. Clients receive a transient error if they submit messages at a rate that exceeds the value of this parameter. Exchange attempts to connect and send the messages at a later time. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1508,13 +1663,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1524,13 +1681,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1540,13 +1699,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1556,13 +1717,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSocketConnectionsPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1572,13 +1735,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSocketConnectionsPerUser + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1588,13 +1753,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSubscriptions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1604,13 +1771,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1620,13 +1789,15 @@ Accept wildcard characters: False ``` ### -OwaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1636,13 +1807,15 @@ Accept wildcard characters: False ``` ### -OwaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaMaxBurst parameter specifies the amount of time that an Outlook on the web user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1652,6 +1825,9 @@ Accept wildcard characters: False ``` ### -OWAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. A valid value for this parameter is an integer from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), use the value $null. @@ -1662,7 +1838,6 @@ A valid value for this parameter is an integer from 0 through 2147483647 inclusi Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1672,6 +1847,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInAD parameter specifies the percentage of a minute that an Outlook Web App user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1680,7 +1858,6 @@ The OWAPercentTimeInAD parameter specifies the percentage of a minute that an Ou Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1690,6 +1867,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInCAS parameter specifies the percentage of a minute that an Outlook Web App user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1698,7 +1878,6 @@ The OWAPercentTimeInCAS parameter specifies the percentage of a minute that an O Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1708,6 +1887,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Outlook Web App user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1716,7 +1898,6 @@ The OWAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1726,13 +1907,15 @@ Accept wildcard characters: False ``` ### -OwaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaRechargeRate parameter specifies the rate at which an Outlook on the web user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1742,13 +1925,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web voice user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1758,13 +1943,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceMaxBurst parameter specifies the amount of time that an Outlook on the web voice user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1774,13 +1961,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web voice user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The OwaVoiceMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1790,13 +1979,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceRechargeRate parameter specifies the rate at which an Outlook on the web voice user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1806,13 +1997,15 @@ Accept wildcard characters: False ``` ### -PopCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1822,13 +2015,15 @@ Accept wildcard characters: False ``` ### -PopMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1838,13 +2033,15 @@ Accept wildcard characters: False ``` ### -POPMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopMaxConcurrency parameter specifies how many concurrent connections a POP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PopMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 20. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1854,6 +2051,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInAD parameter specifies the percentage of a minute a POP user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1862,7 +2062,6 @@ The POPPercentTimeInAD parameter specifies the percentage of a minute a POP user Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1872,6 +2071,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInCAS parameter specifies the percentage of a minute a POP user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1880,7 +2082,6 @@ The POPPercentTimeInCAS parameter specifies the percentage of a minute a POP use Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1890,6 +2091,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInMailboxRPC parameter specifies the percentage of a minute a POP user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1898,7 +2102,6 @@ The POPPercentTimeInMailboxRPC parameter specifies the percentage of a minute a Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1908,13 +2111,15 @@ Accept wildcard characters: False ``` ### -PopRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1924,13 +2129,15 @@ Accept wildcard characters: False ``` ### -PowerShellCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1940,13 +2147,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1956,13 +2165,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdletQueueDepth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1972,13 +2183,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is stopped. The value specified by this parameter should be more than the value specified by the ExchangeMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. Both values should be set at the same time. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1988,13 +2201,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdletsTimePeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine whether the number of cmdlets being executed exceeds the limits specified by the PowerShellMaxCmdlets and ExchangeMaxCmdlets parameters. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2004,6 +2219,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxConcurrency parameter specifies different information depending on context: - In the context of remote PowerShell, the PowerShellMaxConcurrency parameter specifies the maximum number of remote PowerShell sessions that a remote PowerShell user can have open at the same time. @@ -2015,7 +2233,6 @@ This parameter value doesn't necessarily correlate to the number of browsers ope Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2025,6 +2242,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxDestructiveCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive: - Disable-Mailbox @@ -2043,7 +2263,6 @@ The time period used for this limit is specified by the PowerShellMaxDestructive Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2053,13 +2272,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxDestructiveCmdletsTimePeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxDestructiveCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many destructive cmdlets can be run. You set a value for this parameter when you set the PowerShellMaxDestructiveCmdlets parameter. Both values should be set at the same time. For more information, see the description for the PowerShellMaxDestructiveCmdlets parameter. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2069,13 +2290,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxOperations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2085,13 +2308,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxRunspaces + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a user is allowed to have. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2101,13 +2326,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxRunspacesTimePeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxRunspacesTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many Windows PowerShell sessions can be run. You set this value when you set the PowerShellMaxRunspaces parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2117,6 +2344,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxTenantConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxTenantConcurrency parameter limits the number of concurrent Windows PowerShell connections per tenant organization. By default, the limit for concurrent Windows PowerShell connections per tenant organization is set to 9. If users in a tenant organization try to make more concurrent requests than the limit set by the PowerShellMaxTenantConcurrency parameter, the new connection attempt fails. However, the existing connections remain valid. This limit is enforced even if a single user hasn't exceeded the per-user limit set by the PowerShellMaxConcurrency parameter. The PowerShellMaxTenantConcurrency parameter has a valid range from 0 through 100 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. This property can only be set for the default throttling policy. @@ -2125,7 +2355,6 @@ This property can only be set for the default throttling policy. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2135,13 +2364,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxTenantRunspaces + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxTenantRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a tenant is allowed to have. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2151,13 +2382,15 @@ Accept wildcard characters: False ``` ### -PowerShellRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2167,6 +2400,9 @@ Accept wildcard characters: False ``` ### -PswsMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxConcurrency parameter specifies how many concurrent connections a Windows PowerShell Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PswsMaxConcurrency parameter has a default value of 18. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. @@ -2175,7 +2411,6 @@ The PswsMaxConcurrency parameter has a default value of 18. To indicate that the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2185,13 +2420,15 @@ Accept wildcard characters: False ``` ### -PswsMaxRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxRequest parameter specifies how many requests a Windows PowerShell Web Services user can have against an Exchange server at one time. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2201,13 +2438,15 @@ Accept wildcard characters: False ``` ### -PswsMaxRequestTimePeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxRequestTimePeriod parameter specifies the period of time, in seconds, that the throttling policy uses to determine how many requests can be run. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2217,13 +2456,15 @@ Accept wildcard characters: False ``` ### -PushNotificationCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2233,13 +2474,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2249,13 +2492,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxBurstPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2265,13 +2510,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2281,13 +2528,15 @@ Accept wildcard characters: False ``` ### -PushNotificationRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2297,13 +2546,15 @@ Accept wildcard characters: False ``` ### -PushNotificationRechargeRatePerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2313,13 +2564,15 @@ Accept wildcard characters: False ``` ### -PushNotificationSamplingPeriodPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2329,13 +2582,15 @@ Accept wildcard characters: False ``` ### -RcaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2345,13 +2600,15 @@ Accept wildcard characters: False ``` ### -RcaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2361,6 +2618,9 @@ Accept wildcard characters: False ``` ### -RCAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaMaxConcurrency parameter specifies how many concurrent connections an RPC Client Access user can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if the user goes offline). If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. A valid value is an integer from 0 through 4294967295, or the value unlimited. The default value is 40. @@ -2371,7 +2631,6 @@ To indicate that the number of concurrent connections should be unthrottled (no Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2381,6 +2640,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInAD parameter specifies the percentage of a minute that an Outlook user can spend executing directory requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2389,7 +2651,6 @@ The RCAPercentTimeInAD parameter specifies the percentage of a minute that an Ou Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2399,6 +2660,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInCAS parameter specifies the percentage of a minute that an Outlook user can spend executing CAS mailbox requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2407,7 +2671,6 @@ The RCAPercentTimeInCAS parameter specifies the percentage of a minute that an O Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2417,6 +2680,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an RPC Client Access user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2425,7 +2691,6 @@ The RCAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2435,13 +2700,15 @@ Accept wildcard characters: False ``` ### -RcaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaRechargeRate parameter specifies the rate at which the budget for the user is charged (how much the budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2451,13 +2718,15 @@ Accept wildcard characters: False ``` ### -RcaSharedCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedCutoffBalance parameter specifies the resource consumption limits for all users before they're completely blocked from performing operations on a specific component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2467,13 +2736,15 @@ Accept wildcard characters: False ``` ### -RcaSharedMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaShardMaxBurst parameter specifies the amount of time that all users can consume elevated amounts of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2483,6 +2754,9 @@ Accept wildcard characters: False ``` ### -RcaSharedMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedMaxConcurrency parameter specifies how many concurrent connections all RPC Client Access users can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if users go offline). If there are more concurrent requests than the policy allows, new connection attempts fail. However, the existing connections remain valid. The default value is unlimited, which means the limit is controlled individually for each user by the RcaMaxConcurrency parameter. @@ -2491,7 +2765,6 @@ The default value is unlimited, which means the limit is controlled individually Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2501,13 +2774,15 @@ Accept wildcard characters: False ``` ### -RcaSharedRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedRechargeRate parameter specifies the rate at which the budget for all users is charged (how much the budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2517,13 +2792,15 @@ Accept wildcard characters: False ``` ### -RecipientRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientRateLimit parameter specifies the limits on the number of recipients that a user can address in a 24-hour period. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2533,13 +2810,15 @@ Accept wildcard characters: False ``` ### -SchedulesCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2549,13 +2828,15 @@ Accept wildcard characters: False ``` ### -SchedulesMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2565,13 +2846,15 @@ Accept wildcard characters: False ``` ### -SchedulesMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2581,13 +2864,15 @@ Accept wildcard characters: False ``` ### -SchedulesRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2597,13 +2882,15 @@ Accept wildcard characters: False ``` ### -SuiteCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2613,13 +2900,15 @@ Accept wildcard characters: False ``` ### -SuiteMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2629,13 +2918,15 @@ Accept wildcard characters: False ``` ### -SuiteMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2645,13 +2936,15 @@ Accept wildcard characters: False ``` ### -SuiteRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2661,6 +2954,9 @@ 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. - Regular: Specifies a custom policy that applies to specific users. @@ -2673,7 +2969,6 @@ For more information about throttling policy scopes, see [User workload manageme Type: ThrottlingPolicyScopeType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2683,13 +2978,15 @@ 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/exchange/New-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md similarity index 88% rename from exchange/exchange-ps/exchange/New-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md index c737eb0d8d..5f375fb422 100644 --- a/exchange/exchange-ps/exchange/New-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-transportrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: New-TransportRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-transportrule +schema: 2.0.0 +title: New-TransportRule --- # New-TransportRule @@ -231,13 +232,15 @@ This example creates a rule with the following settings: ## 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 rule. 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, Exchange Online Protection Required: True Position: 1 @@ -247,6 +250,9 @@ Accept wildcard characters: False ``` ### -ActivationDate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/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". @@ -255,7 +261,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -265,6 +270,9 @@ Accept wildcard characters: False ``` ### -ADComparisonAttribute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -307,7 +315,6 @@ If you don't use the ADComparisonOperator parameter, the default comparison oper Type: ADAttribute 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 @@ -317,6 +324,9 @@ Accept wildcard characters: False ``` ### -ADComparisonOperator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -330,7 +340,6 @@ The ADComparisonOperator parameter specifies the comparison operator for the ADC Type: Evaluation 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 @@ -340,6 +349,9 @@ Accept wildcard characters: False ``` ### -AddManagerAsRecipientType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -357,7 +369,6 @@ This action only works if the sender's Manager attribute is defined. Type: AddedRecipientType 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 @@ -367,6 +378,9 @@ Accept wildcard characters: False ``` ### -AddToRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -386,7 +400,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -396,6 +409,9 @@ Accept wildcard characters: False ``` ### -AnyOfCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -419,7 +435,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -429,6 +444,9 @@ Accept wildcard characters: False ``` ### -AnyOfCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -452,7 +470,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -462,6 +479,9 @@ Accept wildcard characters: False ``` ### -AnyOfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -476,7 +496,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: Word[] 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 @@ -486,6 +505,9 @@ Accept wildcard characters: False ``` ### -AnyOfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -500,7 +522,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: Pattern[] 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 @@ -510,6 +531,9 @@ Accept wildcard characters: False ``` ### -AnyOfToCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -533,7 +557,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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,6 +566,9 @@ Accept wildcard characters: False ``` ### -AnyOfToCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -566,7 +592,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -576,6 +601,9 @@ Accept wildcard characters: False ``` ### -AnyOfToHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -599,7 +627,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -609,6 +636,9 @@ Accept wildcard characters: False ``` ### -AnyOfToHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -632,7 +662,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -642,6 +671,9 @@ Accept wildcard characters: False ``` ### -ApplyClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -654,7 +686,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -664,6 +695,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerFallbackAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -687,7 +721,6 @@ If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the Type: DisclaimerFallbackAction 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 @@ -697,6 +730,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -712,7 +748,6 @@ If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the Type: DisclaimerLocation 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 @@ -722,6 +757,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -762,7 +800,6 @@ You use the ApplyHtmlDisclaimerLocation parameter to specify where to insert the Type: DisclaimerText 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 @@ -772,6 +809,9 @@ Accept wildcard characters: False ``` ### -ApplyOME + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -785,7 +825,6 @@ The ApplyOME parameter specifies an action that encrypts messages and their atta Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -795,6 +834,9 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionCustomizationTemplate + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -805,7 +847,6 @@ The ApplyRightsProtectionCustomizationTemplate parameter specifies an action tha Type: OMEConfigurationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -815,6 +856,9 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionTemplate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -831,7 +875,6 @@ For more information, see [Transport protection rules](https://learn.microsoft.c 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: Named @@ -841,6 +884,9 @@ Accept wildcard characters: False ``` ### -AttachmentContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -853,7 +899,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] 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 @@ -863,6 +908,9 @@ Accept wildcard characters: False ``` ### -AttachmentExtensionMatchesWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -875,7 +923,6 @@ The AttachmentExtensionMatchesWords parameter specifies a condition that looks f Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -885,6 +932,9 @@ Accept wildcard characters: False ``` ### -AttachmentHasExecutableContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -900,7 +950,6 @@ The system inspects the file properties rather than relying on the file's extens 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 @@ -910,6 +959,9 @@ Accept wildcard characters: False ``` ### -AttachmentIsPasswordProtected + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -923,7 +975,6 @@ The AttachmentIsPasswordProtected parameter specifies a condition that looks for 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 @@ -933,6 +984,9 @@ Accept wildcard characters: False ``` ### -AttachmentIsUnsupported + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -952,7 +1006,6 @@ In Exchange 2010, to extend the list of supported file types, see [Register Filt 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 @@ -962,6 +1015,9 @@ Accept wildcard characters: False ``` ### -AttachmentMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -976,7 +1032,6 @@ Only the first 150 kilobytes (KB) of the attachment is scanned when trying to ma Type: Pattern[] 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 @@ -986,6 +1041,9 @@ Accept wildcard characters: False ``` ### -AttachmentNameMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -996,7 +1054,6 @@ The AttachmentNameMatchesPatterns parameter specifies a condition that looks for Type: Pattern[] 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 @@ -1006,6 +1063,9 @@ Accept wildcard characters: False ``` ### -AttachmentProcessingLimitExceeded + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1021,7 +1081,6 @@ You use this condition to create rules that work together with other attachment 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 @@ -1031,6 +1090,9 @@ Accept wildcard characters: False ``` ### -AttachmentPropertyContainsWords + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1060,7 +1122,6 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1070,6 +1131,9 @@ Accept wildcard characters: False ``` ### -AttachmentSizeOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -1092,7 +1156,6 @@ The embedded images are treated as attachments (for example, messages with a pic Type: ByteQuantifiedSize 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 @@ -1102,6 +1165,9 @@ Accept wildcard characters: False ``` ### -BetweenMemberOf1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1121,7 +1187,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1131,6 +1196,9 @@ Accept wildcard characters: False ``` ### -BetweenMemberOf2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1150,7 +1218,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1160,6 +1227,9 @@ Accept wildcard characters: False ``` ### -BlindCopyTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1179,7 +1249,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1189,13 +1258,15 @@ Accept wildcard characters: False ``` ### -Comments + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Comments parameter specifies optional descriptive text for the rule (for example, what the rule is used for, or how it has changed over time). The length of the comment can't exceed 1024 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, Exchange Online Protection Required: False Position: Named @@ -1205,6 +1276,9 @@ 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`. @@ -1214,7 +1288,6 @@ 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 @@ -1224,6 +1297,9 @@ Accept wildcard characters: False ``` ### -ContentCharacterSetContainsWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1236,7 +1312,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1246,6 +1321,9 @@ Accept wildcard characters: False ``` ### -CopyTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1265,7 +1343,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1275,6 +1352,9 @@ Accept wildcard characters: False ``` ### -DeleteMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1288,7 +1368,6 @@ The DeleteMessage parameter specifies an action that silently drops messages wit 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 @@ -1298,6 +1377,9 @@ Accept wildcard characters: False ``` ### -Disconnect + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -1311,7 +1393,6 @@ The Disconnect parameter specifies an action that ends the SMTP connection betwe 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 @@ -1321,6 +1402,9 @@ 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 specifies the data loss prevention (DLP) policy that's associated with the rule. Each DLP policy is enforced using a set of mail flow rules (transport rules). To learn more about DLP, see [Data loss prevention in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/data-loss-prevention). @@ -1329,7 +1413,6 @@ The DlpPolicy parameter specifies the data loss prevention (DLP) policy that's a Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1339,6 +1422,9 @@ 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. @@ -1349,7 +1435,6 @@ 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 @@ -1359,6 +1444,9 @@ 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 the new rule is created as enabled or disabled. Valid values are: - $true: The new rule is enabled. This is the default value. @@ -1370,7 +1458,6 @@ To enable or disable a rule after you create it, use the Enable-TransportRule an 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 @@ -1380,6 +1467,9 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonAttribute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1422,7 +1512,6 @@ If you don't use the ExceptIfADComparisonOperator parameter, the default compari Type: ADAttribute 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 @@ -1432,6 +1521,9 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonOperator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1445,7 +1537,6 @@ The ExceptIfADComparisonOperator parameter specifies the comparison operator for Type: Evaluation 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 @@ -1455,6 +1546,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1478,7 +1572,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1488,6 +1581,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1511,7 +1607,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1521,6 +1616,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1535,7 +1633,6 @@ A match for this exception prevents the rule action from being applied to all re Type: Word[] 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 @@ -1545,6 +1642,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1559,7 +1659,6 @@ A match for this exception prevents the rule action from being applied to all re Type: Pattern[] 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 @@ -1569,6 +1668,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1592,7 +1694,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1602,6 +1703,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1625,7 +1729,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1635,6 +1738,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1658,7 +1764,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1668,6 +1773,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1691,7 +1799,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1701,6 +1808,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1713,7 +1823,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] 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 @@ -1723,6 +1832,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentExtensionMatchesWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1735,7 +1847,6 @@ The ExceptIfAttachmentExtensionMatchesWords parameter specifies an exception tha Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1745,6 +1856,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentHasExecutableContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1760,7 +1874,6 @@ The system inspects the file properties rather than relying on the file extensio 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 @@ -1770,6 +1883,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsPasswordProtected + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1783,7 +1899,6 @@ The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that 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 @@ -1793,6 +1908,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsUnsupported + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1812,7 +1930,6 @@ In Exchange 2010, to extend the list of supported file types, see [Register Filt 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 @@ -1822,6 +1939,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1836,7 +1956,6 @@ Only the first 150 KB of the attachment is scanned when trying to match a text p Type: Pattern[] 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 @@ -1846,6 +1965,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentNameMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1856,7 +1978,6 @@ The ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that Type: Pattern[] 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 @@ -1866,6 +1987,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentProcessingLimitExceeded + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1881,7 +2005,6 @@ You use this exception to create rules that work together with other attachment 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 @@ -1891,6 +2014,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentPropertyContainsWords + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1920,7 +2046,6 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1930,6 +2055,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentSizeOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1950,7 +2078,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize 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 @@ -1960,6 +2087,9 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1979,7 +2109,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1989,6 +2118,9 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2008,7 +2140,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -2018,6 +2149,9 @@ Accept wildcard characters: False ``` ### -ExceptIfContentCharacterSetContainsWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2030,7 +2164,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2040,6 +2173,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2061,7 +2197,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -2071,6 +2206,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2083,7 +2221,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] 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 @@ -2093,6 +2230,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2107,7 +2247,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Pattern[] 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 @@ -2117,6 +2256,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2138,7 +2280,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -2148,6 +2289,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2161,7 +2305,6 @@ The ExceptIfFromScope parameter specifies an exception that looks for the locati Type: FromUserScope 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 @@ -2171,6 +2314,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2187,7 +2333,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -2197,6 +2342,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasNoClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2210,7 +2358,6 @@ The ExceptIfHasNoClassification parameter specifies an exception that looks for 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 @@ -2220,6 +2367,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasSenderOverride + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. @@ -2235,7 +2385,6 @@ The ExceptIfHasSenderOverride parameter specifies an exception that looks for me 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 @@ -2245,6 +2394,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2255,7 +2407,6 @@ The ExceptIfHeaderContainsMessageHeader parameter specifies the name of header f Type: HeaderName 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 @@ -2265,6 +2416,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2279,7 +2433,6 @@ You specify the header field to search by using the ExceptIfHeaderContainsMessag Type: Word[] 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 @@ -2289,6 +2442,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2299,7 +2455,6 @@ The ExceptIfHeaderMatchesMessageHeader parameter specifies the name of header fi Type: HeaderName 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 @@ -2309,6 +2464,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2321,7 +2479,6 @@ You specify the header field to search by using the ExceptIfHeaderMatchesMessage Type: Pattern[] 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 @@ -2331,6 +2488,9 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2352,7 +2512,6 @@ You specify if you want to look for these users as managers of senders or recipi Type: RecipientIdParameter[] 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 @@ -2362,6 +2521,9 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerForEvaluatedUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2377,7 +2539,6 @@ You specify the users to look for by using the ExceptIfManagerAddresses paramete Type: EvaluatedUser 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 @@ -2387,6 +2548,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageContainsDataClassifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. @@ -2403,7 +2567,6 @@ For a list of sensitive information types available, see [Sensitive information Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2413,6 +2576,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageSizeOver + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2433,7 +2599,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2443,6 +2608,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageTypeMatches + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2463,7 +2631,6 @@ The ExceptIfMessageTypeMatches parameter specifies an exception that looks for m Type: MessageType 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 @@ -2473,6 +2640,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2519,7 +2689,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -2529,6 +2698,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2573,7 +2745,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -2583,6 +2754,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2593,7 +2767,6 @@ The ExceptIfRecipientAddressContainsWords parameter specifies an exception that Type: Word[] 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 @@ -2603,6 +2776,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2615,7 +2791,6 @@ This parameter works when the recipient is an individual user. This parameter do Type: Pattern[] 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 @@ -2625,6 +2800,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2637,7 +2815,6 @@ This exception matches domains and subdomains. For example, "contoso.com" matche Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2647,6 +2824,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientInSenderList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2655,7 +2835,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2665,6 +2844,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSCLOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2680,7 +2862,6 @@ The rule looks for messages with an SCL value that's greater than or equal to th Type: SclValue 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 @@ -2690,6 +2871,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2736,7 +2920,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -2746,6 +2929,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2790,7 +2976,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -2800,6 +2985,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2814,7 +3002,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2824,6 +3011,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderInRecipientList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2832,7 +3022,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2842,6 +3031,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderIpRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2860,7 +3052,6 @@ In Exchange Online, the IP address that's used during evaluation of this excepti 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 @@ -2870,6 +3061,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderManagementRelationship + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2883,7 +3077,6 @@ The ExceptIfSenderManagementRelationship parameter specifies an exception that l Type: ManagementRelationship 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 @@ -2893,6 +3086,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2912,7 +3108,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -2922,6 +3117,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. 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: @@ -2939,7 +3137,6 @@ If you remove the group after you create the rule, no exception is made for mess Type: RecipientIdParameter[] 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 @@ -2949,6 +3146,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2964,7 +3164,6 @@ The ExceptIfSentToScope parameter specifies an exception that looks for the loca Type: ToUserScope 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 @@ -2974,6 +3173,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2988,7 +3190,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -2998,6 +3199,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -3008,7 +3212,6 @@ The ExceptIfSubjectMatchesPatterns parameter specifies an exception that looks f Type: Pattern[] 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 @@ -3018,6 +3221,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -3032,7 +3238,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -3042,6 +3247,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -3052,7 +3260,6 @@ The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception that l Type: Pattern[] 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 @@ -3062,6 +3269,9 @@ Accept wildcard characters: False ``` ### -ExceptIfWithImportance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -3076,7 +3286,6 @@ The ExceptIfWithImportance parameter specifies an exception that looks for messa Type: Importance 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 @@ -3086,6 +3295,9 @@ Accept wildcard characters: False ``` ### -ExpiryDate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time. @@ -3096,7 +3308,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -3106,6 +3317,9 @@ Accept wildcard characters: False ``` ### -From + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3127,7 +3341,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -3137,6 +3350,9 @@ Accept wildcard characters: False ``` ### -FromAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3149,7 +3365,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] 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 @@ -3159,6 +3374,9 @@ Accept wildcard characters: False ``` ### -FromAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3173,7 +3391,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Pattern[] 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 @@ -3183,6 +3400,9 @@ Accept wildcard characters: False ``` ### -FromMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3204,7 +3424,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -3214,6 +3433,9 @@ Accept wildcard characters: False ``` ### -FromScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3227,7 +3449,6 @@ The FromScope parameter specifies a condition that looks for the location of mes Type: FromUserScope 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 @@ -3237,6 +3458,9 @@ Accept wildcard characters: False ``` ### -GenerateIncidentReport + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3256,7 +3480,6 @@ The GenerateIncidentReport parameter specifies where to send the incident report Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3266,6 +3489,9 @@ Accept wildcard characters: False ``` ### -GenerateNotification + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3287,7 +3513,6 @@ The maximum number of characters is 5120. Type: DisclaimerText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3297,6 +3522,9 @@ Accept wildcard characters: False ``` ### -HasClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3313,7 +3541,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -3323,6 +3550,9 @@ Accept wildcard characters: False ``` ### -HasNoClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3336,7 +3566,6 @@ The HasNoClassification parameter specifies a condition that looks for messages 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 @@ -3346,6 +3575,9 @@ Accept wildcard characters: False ``` ### -HasSenderOverride + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. @@ -3361,7 +3593,6 @@ The HasSenderOverride parameter specifies a condition that looks for messages wh 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 @@ -3371,6 +3602,9 @@ Accept wildcard characters: False ``` ### -HeaderContainsMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3381,7 +3615,6 @@ The HeaderContainsMessageHeader parameter specifies the name of header field in Type: HeaderName 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 @@ -3391,6 +3624,9 @@ Accept wildcard characters: False ``` ### -HeaderContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3405,7 +3641,6 @@ You specify the header field to search by using the HeaderContainsMessageHeader Type: Word[] 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 @@ -3415,6 +3650,9 @@ Accept wildcard characters: False ``` ### -HeaderMatchesMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3425,7 +3663,6 @@ The HeaderMatchesMessageHeader parameter specifies the name of header field in t Type: HeaderName 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 @@ -3435,6 +3672,9 @@ Accept wildcard characters: False ``` ### -HeaderMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3447,7 +3687,6 @@ You specify the header field to search by using the HeaderMatchesMessageHeader p Type: Pattern[] 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 @@ -3457,6 +3696,9 @@ Accept wildcard characters: False ``` ### -IncidentReportContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3484,7 +3726,6 @@ You use this parameter with the GenerateIncidentReport parameter. Type: IncidentReportContent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3494,6 +3735,9 @@ Accept wildcard characters: False ``` ### -IncidentReportOriginalMail + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. @@ -3511,7 +3755,6 @@ The IncidentReportOriginalMail parameter specifies whether to include the origin Type: IncidentReportOriginalMail Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -3521,6 +3764,9 @@ Accept wildcard characters: False ``` ### -LogEventText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -3539,7 +3785,6 @@ The entry contains the following information: Type: EventLogText 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 @@ -3549,6 +3794,9 @@ Accept wildcard characters: False ``` ### -ManagerAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3570,7 +3818,6 @@ You specify if you want to look for these users as managers of senders or recipi Type: RecipientIdParameter[] 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 @@ -3580,6 +3827,9 @@ Accept wildcard characters: False ``` ### -ManagerForEvaluatedUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3595,7 +3845,6 @@ You specify the users to look for by using the ManagerAddresses parameter. Type: EvaluatedUser 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 @@ -3605,6 +3854,9 @@ Accept wildcard characters: False ``` ### -MessageContainsDataClassifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. @@ -3623,7 +3875,6 @@ You can specify the notification options by using the NotifySender parameter. Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3633,6 +3884,9 @@ Accept wildcard characters: False ``` ### -MessageSizeOver + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3653,7 +3907,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3663,6 +3916,9 @@ Accept wildcard characters: False ``` ### -MessageTypeMatches + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3683,7 +3939,6 @@ The MessageTypeMatches parameter specifies a condition that looks for messages o Type: MessageType 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 @@ -3693,6 +3948,9 @@ 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. Valid values are: - Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs. @@ -3703,7 +3961,6 @@ The Mode parameter specifies how the rule operates. Valid values are: 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 @@ -3713,6 +3970,9 @@ Accept wildcard characters: False ``` ### -ModerateMessageByManager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3728,7 +3988,6 @@ This action only works if the sender's Manager attribute is defined. 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 @@ -3738,6 +3997,9 @@ Accept wildcard characters: False ``` ### -ModerateMessageByUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3759,7 +4021,6 @@ You can't use a distribution group as a moderator. Type: RecipientIdParameter[] 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 @@ -3769,6 +4030,9 @@ Accept wildcard characters: False ``` ### -NotifySender + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -3793,7 +4057,6 @@ This action is applicable to messages sent by internal users only. External send Type: NotifySenderType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3803,6 +4066,9 @@ Accept wildcard characters: False ``` ### -PrependSubject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -3815,7 +4081,6 @@ Consider ending the value for this parameter with a colon (:) and a space, or at Type: SubjectPrefix 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 @@ -3825,6 +4090,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, 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: @@ -3839,7 +4107,6 @@ 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3849,6 +4116,9 @@ Accept wildcard characters: False ``` ### -Quarantine + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Edge Transport servers. @@ -3864,7 +4134,6 @@ If this action is in a rule that's not the last rule in the list, rule evaluatio 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 @@ -3874,6 +4143,9 @@ Accept wildcard characters: False ``` ### -RecipientADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3920,7 +4192,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -3930,6 +4201,9 @@ Accept wildcard characters: False ``` ### -RecipientADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3974,7 +4248,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -3984,6 +4257,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3994,7 +4270,6 @@ The RecipientAddressContainsWords parameter specifies a condition that looks for Type: Word[] 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 @@ -4004,6 +4279,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4016,7 +4294,6 @@ This parameter works when the recipient is an individual user. This parameter do Type: Pattern[] 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 @@ -4026,6 +4303,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressType + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are: @@ -4037,7 +4317,6 @@ The RecipientAddressType parameter specifies how conditions and exceptions check Type: RecipientAddressType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4047,6 +4326,9 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4059,7 +4341,6 @@ This condition matches domains and subdomains. For example, "contoso.com" matche Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4069,6 +4350,9 @@ Accept wildcard characters: False ``` ### -RecipientInSenderList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -4077,7 +4361,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4087,6 +4370,9 @@ Accept wildcard characters: False ``` ### -RedirectMessageTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4106,7 +4392,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -4116,6 +4401,9 @@ Accept wildcard characters: False ``` ### -RejectMessageEnhancedStatusCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4132,7 +4420,6 @@ To further customize the NDR (for example, multiple languages), you need to crea Type: RejectEnhancedStatus 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 @@ -4142,6 +4429,9 @@ Accept wildcard characters: False ``` ### -RejectMessageReasonText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4162,7 +4452,6 @@ To further customize the NDR (for example, multiple languages), you need to crea Type: RejectText 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 @@ -4172,6 +4461,9 @@ Accept wildcard characters: False ``` ### -RemoveHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4182,7 +4474,6 @@ The RemoveHeader parameter specifies an action that removes a header field from Type: HeaderName 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 @@ -4192,6 +4483,9 @@ Accept wildcard characters: False ``` ### -RemoveOME + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4205,7 +4499,6 @@ The RemoveOME parameter specifies an action that removes the previous version of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4215,6 +4508,9 @@ Accept wildcard characters: False ``` ### -RemoveOMEv2 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4228,7 +4524,6 @@ The RemoveOMEv2 parameter specifies an action that removes Microsoft Purview Mes Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4238,6 +4533,9 @@ Accept wildcard characters: False ``` ### -RemoveRMSAttachmentEncryption + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4253,7 +4551,6 @@ The RemoveRMSAttachmentEncryption parameter specifies an action that removes Mic Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4263,6 +4560,9 @@ Accept wildcard characters: False ``` ### -RouteMessageOutboundConnector + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4277,7 +4577,6 @@ The RouteMessageOutboundConnector parameter specifies an action that routes mess Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4287,6 +4586,9 @@ Accept wildcard characters: False ``` ### -RouteMessageOutboundRequireTls + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4300,7 +4602,6 @@ The RouteMessageOutboundRequireTls parameter specifies an action that uses Trans 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 @@ -4310,6 +4611,9 @@ Accept wildcard characters: False ``` ### -RuleErrorAction + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are: - Ignore: The message is sent anyway. This is the default value. @@ -4319,7 +4623,6 @@ The RuleErrorAction parameter specifies what to do if rule processing can't be c Type: RuleErrorAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4329,6 +4632,9 @@ Accept wildcard characters: False ``` ### -RuleSubType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RuleSubType parameter specifies the rule type. Valid values are: - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. @@ -4338,7 +4644,6 @@ The RuleSubType parameter specifies the rule type. Valid values are: Type: RuleSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4348,6 +4653,9 @@ Accept wildcard characters: False ``` ### -SCLOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4363,7 +4671,6 @@ The rule looks for messages with an SCL value that's greater than or equal to th Type: SclValue 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 @@ -4373,6 +4680,9 @@ Accept wildcard characters: False ``` ### -SenderADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4419,7 +4729,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -4429,6 +4738,9 @@ Accept wildcard characters: False ``` ### -SenderADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4473,7 +4785,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -4483,6 +4794,9 @@ Accept wildcard characters: False ``` ### -SenderAddressLocation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). @@ -4501,7 +4815,6 @@ Message envelope searching is available only for the following conditions and ex Type: SenderAddressLocation Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4511,6 +4824,9 @@ Accept wildcard characters: False ``` ### -SenderDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4525,7 +4841,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4535,6 +4850,9 @@ Accept wildcard characters: False ``` ### -SenderInRecipientList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -4543,7 +4861,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4553,6 +4870,9 @@ Accept wildcard characters: False ``` ### -SenderIpRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4571,7 +4891,6 @@ In Exchange Online, the IP address that's used during evaluation of this conditi 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 @@ -4581,6 +4900,9 @@ Accept wildcard characters: False ``` ### -SenderManagementRelationship + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4594,7 +4916,6 @@ The SenderManagementRelationship parameter specifies a condition that looks for Type: ManagementRelationship 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 @@ -4604,6 +4925,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4623,7 +4947,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -4633,6 +4956,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4654,7 +4980,6 @@ If you remove the group after you create the rule, no action is taken on message Type: RecipientIdParameter[] 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 @@ -4664,6 +4989,9 @@ Accept wildcard characters: False ``` ### -SentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4679,7 +5007,6 @@ The SentToScope parameter specifies a condition that looks for the location of r Type: ToUserScope 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 @@ -4689,6 +5016,9 @@ Accept wildcard characters: False ``` ### -SetAuditSeverity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4704,7 +5034,6 @@ The SetAuditSeverity parameter specifies an action that sets the severity level 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 @@ -4714,6 +5043,9 @@ Accept wildcard characters: False ``` ### -SetHeaderName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4724,7 +5056,6 @@ The SetHeaderName parameter specifies an action that adds or modifies a header f Type: HeaderName 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 @@ -4734,6 +5065,9 @@ Accept wildcard characters: False ``` ### -SetHeaderValue + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4744,7 +5078,6 @@ The SetHeaderValue parameter specifies an action that adds or modifies a header Type: HeaderValue 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 @@ -4754,6 +5087,9 @@ Accept wildcard characters: False ``` ### -SetSCL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4767,7 +5103,6 @@ The SetSCL parameter specifies an action that adds or modifies the SCL value of Type: SclValue 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 @@ -4777,6 +5112,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectStatusCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -4789,7 +5127,6 @@ You can use this parameter with the SmtpRejectMessageRejectText parameter. If yo Type: RejectStatusCode 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 @@ -4799,6 +5136,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -4811,7 +5151,6 @@ You can use this parameter with the SmtpRejectMessageRejectStatusCode parameter. Type: RejectText 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 @@ -4821,6 +5160,9 @@ Accept wildcard characters: False ``` ### -StopRuleProcessing + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4834,7 +5176,6 @@ The StopRuleProcessing parameter specifies an action that stops processing more 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 @@ -4844,6 +5185,9 @@ Accept wildcard characters: False ``` ### -SubjectContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4858,7 +5202,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -4868,6 +5211,9 @@ Accept wildcard characters: False ``` ### -SubjectMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4878,7 +5224,6 @@ The SubjectMatchesPatterns parameter specifies a condition that looks for text p Type: Pattern[] 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 @@ -4888,6 +5233,9 @@ Accept wildcard characters: False ``` ### -SubjectOrBodyContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4902,7 +5250,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -4912,6 +5259,9 @@ Accept wildcard characters: False ``` ### -SubjectOrBodyMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4922,7 +5272,6 @@ The SubjectOrBodyMatchesPatterns parameter specifies a condition that looks for Type: Pattern[] 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 @@ -4932,6 +5281,9 @@ Accept wildcard characters: False ``` ### -UseLegacyRegex + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UseLegacyRegex parameter specifies whether the rule uses regular expression syntax that's compatible with Exchange Server 2010. Valid values are: - $true: Regular expression syntax that's compatible with Exchange 2010. @@ -4941,7 +5293,6 @@ The UseLegacyRegex parameter specifies whether the rule uses regular expression 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 @@ -4951,13 +5302,15 @@ 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 @@ -4967,6 +5320,9 @@ Accept wildcard characters: False ``` ### -WithImportance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4981,7 +5337,6 @@ The WithImportance parameter specifies a condition that looks for messages with Type: Importance 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/exchange/New-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md similarity index 90% rename from exchange/exchange-ps/exchange/New-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md index 7f9922c4c4..7e89a7e869 100644 --- a/exchange/exchange-ps/exchange/New-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-umautoattendant applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: New-UMAutoAttendant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-umautoattendant +schema: 2.0.0 +title: New-UMAutoAttendant --- # New-UMAutoAttendant @@ -58,13 +59,15 @@ This example creates the speech-enabled UM auto attendant MyUMAutoAttendant usin ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the UM auto attendant. The display name for the UM auto attendant can contain as many as 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -74,13 +77,15 @@ Accept wildcard characters: False ``` ### -UMDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMDialPlan parameter specifies the UM dial plan identifier for the UM dial plan to be associated with this UM auto attendant. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -90,6 +95,9 @@ 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`. @@ -99,7 +107,6 @@ 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 @@ -109,13 +116,15 @@ 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,13 +134,15 @@ Accept wildcard characters: False ``` ### -DTMFFallbackAutoAttendant + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DTMFFallbackAutoAttendant parameter specifies a secondary UM auto attendant. A secondary UM auto attendant can be used only if the SpeechEnabled parameter is set to $true. ```yaml Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -141,13 +152,15 @@ Accept wildcard characters: False ``` ### -PilotIdentifierList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PilotIdentifierList parameter specifies a list of one or more pilot numbers. Pilot numbers route incoming calls to Mailbox servers. The calls are then answered by the UM auto attendant. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -157,13 +170,15 @@ Accept wildcard characters: False ``` ### -SpeechEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SpeechEnabled parameter specifies whether the UM auto attendant is speech-enabled. The default value is $true. If this parameter is omitted, or if the value is $false, the UM auto attendant isn't speech-enabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -173,6 +188,9 @@ Accept wildcard characters: False ``` ### -Status + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Status parameter specifies whether the UM auto attendant being created will be enabled. Valid values are: - Enabled @@ -182,7 +200,6 @@ The Status parameter specifies whether the UM auto attendant being created will Type: StatusEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -192,13 +209,15 @@ 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/exchange/New-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md similarity index 94% rename from exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md index 4fa9e1f46e..a4df1bf108 100644 --- a/exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-umcallansweringrule applicable: Exchange Server 2013, Exchange Server 2016 -title: New-UMCallAnsweringRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-umcallansweringrule +schema: 2.0.0 +title: New-UMCallAnsweringRule --- # New-UMCallAnsweringRule @@ -120,13 +121,15 @@ This example creates the call answering rule MyCallAnsweringRule in the mailbox ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the name of the Unified Messaging (UM) call answering rule or Call Answering Rule ID being modified. The call answering ID or name must be unique per the user's UM-enabled mailbox. The name or ID for the call answering rule can contain up to 255 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -136,13 +139,15 @@ Accept wildcard characters: False ``` ### -CallerIds + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CallerIds parameter specifies an entry for the "If the Caller is" condition. Each entry for this parameter can contain a phone number, an Active Directory contact, a personal contact, or the personal Contacts folder. The parameter can contain 50 phone numbers or contact entries and no more than one entry for specifying the default Contacts folder. If the CallerIds parameter doesn't contain a condition, the condition isn't set and is ignored. The default value is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -152,13 +157,15 @@ Accept wildcard characters: False ``` ### -CallersCanInterruptGreeting + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CallersCanInterruptGreeting parameter specifies whether a caller can interrupt the voice mail greeting while it's being played. The default is $null. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -168,13 +175,15 @@ Accept wildcard characters: False ``` ### -CheckAutomaticReplies + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CheckAutomaticReplies parameter specifies an entry for the "If My Automatic Replies are Enabled" condition. The default is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -184,6 +193,9 @@ 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`. @@ -193,7 +205,6 @@ 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 @@ -203,13 +214,15 @@ 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 @@ -219,13 +232,15 @@ Accept wildcard characters: False ``` ### -ExtensionsDialed + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The ExtensionsDialed parameter specifies an entry for the "If the Caller Dials" condition. Each entry must be unique per call answering rule. Each extension must correspond to existing extension numbers assigned to UM-enabled users. The default is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -235,13 +250,15 @@ Accept wildcard characters: False ``` ### -KeyMappings + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The KeyMappings parameter specifies a key mapping entry for a call answering rule. The key mappings are those menu options offered to callers if the call answering rule is set to $true. You can configure a maximum of 10 entries. None of the defined key mappings can overlap. The default is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -251,6 +268,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Mailbox parameter specifies the UM-enabled mailbox where the call answering rule is created. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -270,7 +290,6 @@ 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 @@ -280,13 +299,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Priority parameter specifies the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -296,6 +317,9 @@ Accept wildcard characters: False ``` ### -ScheduleStatus + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The ScheduleStatus parameter specifies an entry for the "If my Schedule show that I am" condition. Users can specify their free/busy status to be checked. This parameter can be set from 0 through 15 and is interpreted as a 4-bit mask that represents the calendar status including Free, Tentative, Busy, and Out of Office. The following settings can be used to set the schedule status: - None = 0x0 @@ -310,7 +334,6 @@ The default setting is $null. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -320,13 +343,15 @@ Accept wildcard characters: False ``` ### -TimeOfDay + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The TimeOfDay parameter specifies an entry for the "If the Call Arrives During" condition for the call answering rule. You can specify working hours, non-working hours, or custom hours. The default is $null. ```yaml Type: TimeOfDay Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -336,13 +361,15 @@ 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/exchange/New-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md similarity index 90% rename from exchange/exchange-ps/exchange/New-UMDialPlan.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md index 5b47dbb7ad..7608e3ce1d 100644 --- a/exchange/exchange-ps/exchange/New-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-umdialplan applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: New-UMDialPlan -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-umdialplan +schema: 2.0.0 +title: New-UMDialPlan --- # New-UMDialPlan @@ -69,13 +70,15 @@ This example creates the unsecured UM dial plan MyUMDialPlan that supports E.164 ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name of the UM dial plan. This description is presented to the administrator when a user is enabled for Unified Messaging. The UM dial plan name field can contain as many as 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -85,13 +88,15 @@ Accept wildcard characters: False ``` ### -CountryOrRegionCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CountryOrRegionCode parameter specifies the country or region code that precedes a telephone number used to place calls from other countries or regions to the country or region in which the UM dial plan is located. For example, 1 is the code used for North America and 44 is the code used for the United Kingdom. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -101,13 +106,15 @@ Accept wildcard characters: False ``` ### -NumberOfDigitsInExtension + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The NumberOfDigitsInExtension parameter specifies the fixed number of digits in an extension number. The range for this parameter is from 1 through 20 digits. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -117,13 +124,15 @@ Accept wildcard characters: False ``` ### -AccessTelephoneNumbers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AccessTelephoneNumbers parameter specifies the telephone number or numbers used for subscriber access. These numbers are sometimes referred to as pilot or pilot ID numbers. The telephone number is limited to 32 characters. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -133,6 +142,9 @@ 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`. @@ -142,7 +154,6 @@ 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 @@ -152,13 +163,15 @@ Accept wildcard characters: False ``` ### -DefaultLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DefaultLanguage parameter specifies the default language of the system. This default language is selected from the list of available languages. If there are no other UM language packs installed, the default value is en-US. ```yaml Type: UMLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -168,13 +181,15 @@ 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 @@ -184,13 +199,15 @@ Accept wildcard characters: False ``` ### -FaxEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The FaxEnabled parameter specifies whether the Mailbox servers associated with the dial plan answer and process incoming fax calls. The default is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -200,13 +217,15 @@ Accept wildcard characters: False ``` ### -GenerateUMMailboxPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The GenerateUMMailboxPolicy parameter specifies whether a default UM mailbox policy is created when the UM dial plan is created. The default setting is to create a UM mailbox when the UM dial plan is created. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -216,13 +235,15 @@ Accept wildcard characters: False ``` ### -URIType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The URIType parameter specifies the URI type to be sent and received with SIP messages from the Private Branch eXchange (PBX). ```yaml Type: UMURIType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -232,13 +253,15 @@ Accept wildcard characters: False ``` ### -VoIPSecurity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoIPSecurity parameter specifies whether the signaling channel is encrypted using mutual Transport Layer Security (TLS). The default setting is Unsecured. ```yaml Type: UMVoIPSecurityType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -248,13 +271,15 @@ 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/exchange/New-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md similarity index 90% rename from exchange/exchange-ps/exchange/New-UMHuntGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md index c471f60d1e..55bd7feae5 100644 --- a/exchange/exchange-ps/exchange/New-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-umhuntgroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: New-UMHuntGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-umhuntgroup +schema: 2.0.0 +title: New-UMHuntGroup --- # New-UMHuntGroup @@ -55,13 +56,15 @@ This example creates the UM hunt group MyUMHuntGroup that has multiple pilot ide ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the UM hunt group name used for display purposes. This string can contain as many as 64 characters and it must be unique. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -71,13 +74,15 @@ Accept wildcard characters: False ``` ### -UMDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMDialPlan parameter specifies the UM dial plan used with the UM hunt group. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -87,13 +92,15 @@ Accept wildcard characters: False ``` ### -UMIPGateway + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMIPGateway parameter specifies the UM IP gateway to be associated with the UM hunt group. ```yaml Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -103,6 +110,9 @@ 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`. @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ 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 @@ -138,13 +149,15 @@ Accept wildcard characters: False ``` ### -PilotIdentifier + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PilotIdentifier parameter specifies the number string used to uniquely identify the pilot access number for the specified IP gateway. This number must match the subscriber access number configured in 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 @@ -154,13 +167,15 @@ 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/exchange/New-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md similarity index 92% rename from exchange/exchange-ps/exchange/New-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md index 3e03d94273..85525ffe10 100644 --- a/exchange/exchange-ps/exchange/New-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-umipgateway applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: New-UMIPGateway -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-umipgateway +schema: 2.0.0 +title: New-UMIPGateway --- # New-UMIPGateway @@ -63,13 +64,15 @@ This example creates the UM IP gateway MyUMIPGateway that enables a Mailbox serv ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the UM IP gateway. The name for the new UM IP gateway can contain up to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -79,13 +82,15 @@ Accept wildcard characters: False ``` ### -Address + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Address parameter specifies the IP address configured on the IP gateway or SIP-enabled IP PBX. ```yaml Type: UMSmartHost Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -95,6 +100,9 @@ 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`. @@ -104,7 +112,6 @@ 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,6 +121,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + 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,7 +132,6 @@ 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 Required: False Position: Named @@ -132,6 +141,9 @@ Accept wildcard characters: False ``` ### -IPAddressFamily + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are: - IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value. @@ -142,7 +154,6 @@ The IPAddressFamily parameter specifies whether the UM IP gateway will use Inter Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -152,13 +163,15 @@ Accept wildcard characters: False ``` ### -UMDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMDialPlan parameter specifies the UM dial plan to be associated with the UM IP gateway. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -168,13 +181,15 @@ 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/exchange/New-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/New-UMMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md index 3ab4d1f26f..510056d606 100644 --- a/exchange/exchange-ps/exchange/New-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-ummailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: New-UMMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-ummailboxpolicy +schema: 2.0.0 +title: New-UMMailboxPolicy --- # New-UMMailboxPolicy @@ -47,13 +48,15 @@ This example creates the UM mailbox policy MyUMMailboxPolicy associated with the ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the UM mailbox policy. The name for the UM mailbox policy can contain as many as 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,13 +66,15 @@ Accept wildcard characters: False ``` ### -UMDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMDialPlan parameter specifies the identifier for the UM dial plan to be associated with the UM mailbox policy. This parameter is the directory object ID for the UM dial plan. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -79,6 +84,9 @@ 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`. @@ -88,7 +96,6 @@ 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,13 +105,15 @@ 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 @@ -114,13 +123,15 @@ 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/exchange/New-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md index 2196b0f833..c8feaad795 100644 --- a/exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-unifiedauditlogretentionpolicy applicable: Security & Compliance -title: New-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-unifiedauditlogretentionpolicy +schema: 2.0.0 +title: New-UnifiedAuditLogRetentionPolicy --- # New-UnifiedAuditLogRetentionPolicy @@ -55,13 +56,15 @@ This example creates an audit log retention policy that retains all audit logs f ## PARAMETERS ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies a unique name for the audit log retention 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 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Security & Compliance + The Priority parameter specifies a priority value for the policy that determines the order of policy processing. A higher integer value indicates a lower priority. The value 1 is the highest priority, and the value 10000 is the lowest priority. No two policies can have the same priority value. This parameter is required when you create an audit log retention policy, and you must use a unique priority value. @@ -81,7 +87,6 @@ Any custom audit log retention policy that you create will take precedence over Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -91,6 +96,9 @@ Accept wildcard characters: False ``` ### -RetentionDuration + +> Applicable: Security & Compliance + The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: - ThreeMonths @@ -104,7 +112,6 @@ Type: UnifiedAuditLogRetentionDuration Parameter Sets: (All) Aliases: Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears -Applicable: Security & Compliance Required: True Position: Named @@ -114,6 +121,9 @@ 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`. @@ -123,7 +133,6 @@ 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 @@ -133,13 +142,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Security & Compliance + The Description parameter specifies a description for the audit log retention 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: Security & Compliance Required: False Position: Named @@ -149,6 +160,9 @@ Accept wildcard characters: False ``` ### -Operations + +> Applicable: Security & Compliance + The Operations parameter specifies the audit log operations that are retained by 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"`. @@ -159,7 +173,6 @@ If you use this parameter, you must also use the RecordTypes parameter to specif Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -169,6 +182,9 @@ Accept wildcard characters: False ``` ### -RecordTypes + +> Applicable: Security & Compliance + The RecordTypes parameter specifies the audit logs of a specific record type that are retained by 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). You can specify multiple values separated by commas. If you specify more than one value, you can't use the Operations parameter. @@ -177,7 +193,6 @@ You can specify multiple values separated by commas. If you specify more than on Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -187,6 +202,9 @@ Accept wildcard characters: False ``` ### -UserIds + +> Applicable: Security & Compliance + The UserIds parameter specifies the audit logs that are retained by the policy based on the ID of the user who performed the action. 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"`. @@ -195,7 +213,6 @@ 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 @@ -205,13 +222,15 @@ 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/exchange/New-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/New-UnifiedGroup.md rename to exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md index 7490a242d1..ccd41353d3 100644 --- a/exchange/exchange-ps/exchange/New-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-unifiedgroup applicable: Exchange Online, Exchange Online Protection -title: New-UnifiedGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-unifiedgroup +schema: 2.0.0 +title: New-UnifiedGroup --- # New-UnifiedGroup @@ -140,6 +141,9 @@ This example creates a new Microsoft 365 Group named Engineering Department. ## PARAMETERS ### -DisplayName + +> Applicable: Exchange Online, Exchange Online Protection + The DisplayName parameter specifies the name of the Microsoft 365 Group. The display name is visible in the Exchange admin center, address lists, and Outlook. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). For Microsoft 365 Groups, the DisplayName value is used in the unique Name property. However, because the DisplayName value doesn't need to be unique, the DisplayName value is appended with an underscore character (\_) and a short GUID value when it's used for the Name property. @@ -148,7 +152,6 @@ For Microsoft 365 Groups, the DisplayName value is used in the unique Name prope Type: String Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -158,6 +161,9 @@ Accept wildcard characters: False ``` ### -DlIdentity + +> Applicable: Exchange Online, Exchange Online Protection + The DlIdentity parameter specifies the distribution group (also known as a distribution list or DL) that you want to migrate to a Microsoft 365 Group. The distribution group must be a universal distribution group (the RecipientTypeDetails property value is MailUniversalDistributionGroup). You can use any value that uniquely identifies the distribution group. For example: - Name @@ -177,7 +183,6 @@ Microsoft 365 Groups don't have ReportToManager and ReportToOriginator parameter Type: DistributionGroupIdParameter Parameter Sets: DlMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -187,6 +192,9 @@ Accept wildcard characters: False ``` ### -AccessType + +> Applicable: Exchange Online, Exchange Online Protection + The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Valid values are: - Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This is the default value. @@ -200,7 +208,6 @@ You can change the privacy type at any point in the lifecycle of the group. Type: ModernGroupTypeInfo Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -210,6 +217,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Online, Exchange Online Protection + The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the Microsoft 365 Group. 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: @@ -229,7 +239,6 @@ The Alias value is appended with the ExternalDirectoryObjectId property value an Type: String Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -239,6 +248,9 @@ Accept wildcard characters: False ``` ### -AlwaysSubscribeMembersToCalendarEvents + +> Applicable: Exchange Online, Exchange Online Protection + The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group. - If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents. @@ -252,7 +264,6 @@ The AutoSubscribeNewMembers switch overrides this switch. Type: SwitchParameter Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -262,6 +273,9 @@ Accept wildcard characters: False ``` ### -AutoSubscribeNewMembers + +> Applicable: Exchange Online, Exchange Online Protection + The AutoSubscribeNewMembers switch specifies whether to automatically subscribe new members that are added to the Microsoft 365 Group to conversations and calendar events. You don't need to specify a value with this switch. You need to use this switch with the SubscriptionEnabled switch. @@ -270,7 +284,6 @@ You need to use this switch with the SubscriptionEnabled switch. Type: SwitchParameter Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -280,13 +293,15 @@ Accept wildcard characters: False ``` ### -Classification + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -296,6 +311,9 @@ 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`. @@ -305,7 +323,6 @@ 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 @@ -315,6 +332,9 @@ Accept wildcard characters: False ``` ### -ConvertClosedDlToPrivateGroup + +> Applicable: Exchange Online, Exchange Online Protection + The ConvertClosedDlToPrivateGroup switch specifies whether to migrate the closed distribution group to a private Microsoft 365 Group. You don't need to specify a value with this switch. By default, this switch is always applied when migrating closed distribution groups, and is no longer required. @@ -327,7 +347,6 @@ You can only use this switch with the DlIdentity parameter. Type: SwitchParameter Parameter Sets: DlMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -337,6 +356,9 @@ Accept wildcard characters: False ``` ### -DataEncryptionPolicy + +> Applicable: Exchange Online, Exchange Online Protection + The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the Microsoft 365 Group. You can use any value that uniquely identifies the policy. For example: - Name @@ -347,7 +369,6 @@ The DataEncryptionPolicy parameter specifies the data encryption policy that's a Type: DataEncryptionPolicyIdParameter Parameter Sets: Identity, SegmentationOption, ProvisioningOptions Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -357,6 +378,9 @@ Accept wildcard characters: False ``` ### -DeleteDlAfterMigration + +> Applicable: Exchange Online, Exchange Online Protection + The DeleteDlAfterMigration switch specifies whether to delete the distribution group after it's migrated to a Microsoft 365 Group. You don't need to specify a value with this switch. You can only use this switch with the DlIdentity parameter. @@ -365,7 +389,6 @@ You can only use this switch with the DlIdentity parameter. Type: SwitchParameter Parameter Sets: DlMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -375,6 +398,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the Microsoft 365 Group, including the primary SMTP address. In cloud-based organizations, the primary SMTP address and other proxy addresses for Microsoft 365 Groups are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the Microsoft 365 Group. Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -395,7 +421,6 @@ To specify the primary SMTP email address, you can use any of the following meth Type: ProxyAddressCollection Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -405,13 +430,15 @@ Accept wildcard characters: False ``` ### -ExecutingUser + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -421,6 +448,9 @@ Accept wildcard characters: False ``` ### -ExoErrorAsWarning + +> Applicable: Exchange Online, Exchange Online Protection + The ExoErrorAsWarning switch specifies that Exchange Online errors that you encounter while creating the Microsoft 365 Group are treated as warnings, not errors. You don't need to specify a value with this switch. Creating Microsoft 365 Groups involves background operations in Microsoft Entra ID and Exchange Online. Errors that you might encounter in Exchange Online don't prevent the creation of the group (and therefore aren't really errors), because the group object in Microsoft Entra ID is synchronized back to Exchange Online. @@ -429,7 +459,6 @@ Creating Microsoft 365 Groups involves background operations in Microsoft Entra Type: SwitchParameter Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -439,6 +468,9 @@ Accept wildcard characters: False ``` ### -HiddenGroupMembershipEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The HiddenGroupMembershipEnabled switch specifies whether to hide the members of the Microsoft 365 Group from users who aren't members of the group. You don't need to specify a value with this switch. You can use this setting to help comply with regulations that require you to hide group membership from outsiders (for example, a Microsoft 365 Group that represents students enrolled in a class). @@ -449,7 +481,6 @@ You can use this setting to help comply with regulations that require you to hid Type: SwitchParameter Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -459,13 +490,15 @@ Accept wildcard characters: False ``` ### -IsMemberAllowedToEditContent + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill IsMemberAllowedToEditContent Description }} ```yaml Type: System.Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -475,6 +508,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Online, Exchange Online Protection + The Language parameter specifies the language preference for the Microsoft 365 Group. 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). @@ -483,7 +519,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -493,13 +528,15 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online, Exchange Online Protection + The MailboxRegion parameter specifies the preferred data location (PDL) for the Microsoft 365 Group in multi-geo environments. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -509,13 +546,15 @@ Accept wildcard characters: False ``` ### -ManagedBy + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -525,6 +564,9 @@ Accept wildcard characters: False ``` ### -Members + +> Applicable: Exchange Online, Exchange Online Protection + The Members parameter specifies the recipients (mail-enabled objects) that are members of the Microsoft 365 Group. You can use any value that uniquely identifies the recipient. For example: - Name @@ -540,7 +582,6 @@ 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 @@ -550,6 +591,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online, Exchange Online Protection + This parameter has been deprecated and is no longer used. Previously, if you specified a value for this parameter, a random GUID value was added and used as the Name property value for the Microsoft 365 Group (`Name_`). Now, the value of the Name property is populated by the Alias parameter value and the ExternalDirectoryObjectId property value (`_`). @@ -558,7 +602,6 @@ Previously, if you specified a value for this parameter, a random GUID value was Type: String Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -568,13 +611,15 @@ Accept wildcard characters: False ``` ### -Notes + +> Applicable: Exchange Online, Exchange Online Protection + The Notes parameter specifies the description of the Microsoft 365 Group. If the value contains spaces, enclose the value in quotation marks. ```yaml Type: String Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -584,6 +629,9 @@ Accept wildcard characters: False ``` ### -Owner + +> Applicable: Exchange Online, Exchange Online Protection + The Owner parameter specifies the for the Microsoft 365 Group. An owner is a group member who has certain privileges, such as the ability to edit group properties. The owner you specify for this parameter must be a mailbox or mail user (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the owner. For example: @@ -599,7 +647,6 @@ The owner you specify for this parameter must be a mailbox or mail user (a mail- Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -609,13 +656,15 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Online, Exchange Online Protection + The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. ```yaml Type: SmtpAddress Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -625,6 +674,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: 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. @@ -634,7 +686,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes Type: Boolean Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -644,6 +695,9 @@ Accept wildcard characters: False ``` ### -SensitivityLabelId + +> Applicable: Exchange Online, Exchange Online Protection + The SensitivityLabelId parameter specifies the GUID value of the sensitivity label that's assigned to the Microsoft 365 Group. **Note**: In the output of the Get-UnifiedGroup cmdlet, this property is named SensitivityLabel, not SensitivityLabelId. @@ -652,7 +706,6 @@ The SensitivityLabelId parameter specifies the GUID value of the sensitivity lab Type: System.Guid Parameter Sets: Identity, SegmentationOption, ProvisioningOptions Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -662,13 +715,15 @@ Accept wildcard characters: False ``` ### -SubscriptionEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The SubscriptionEnabled switch specifies whether subscriptions to conversations and calendar events are enabled for the Microsoft 365 Group. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -678,13 +733,15 @@ Accept wildcard characters: False ``` ### -SuppressWarmupMessage + +> Applicable: Exchange Online, Exchange Online Protection + This parameter has been deprecated and is no longer used. ```yaml Type: SwitchParameter Parameter Sets: Identity, ProvisioningOptions, SegmentationOption Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -694,13 +751,15 @@ 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/exchange/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md similarity index 87% rename from exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md index f99ae64e15..952971cc09 100644 --- a/exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-webservicesvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-WebServicesVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-webservicesvirtualdirectory +schema: 2.0.0 +title: New-WebServicesVirtualDirectory --- # New-WebServicesVirtualDirectory @@ -66,13 +67,15 @@ This example creates a virtual directory under the non-default website www.conto ## 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 @@ -82,13 +85,15 @@ 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 @@ -98,13 +103,15 @@ Accept wildcard characters: False ``` ### -AppPoolIdForManagement + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AppPoolIdForManagement parameter specifies the pool of programs that manages the virtual directory. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -114,6 +121,9 @@ 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. @@ -123,7 +133,6 @@ 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 @@ -133,6 +142,9 @@ 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`. @@ -142,7 +154,6 @@ 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 @@ -152,6 +163,9 @@ 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. @@ -161,7 +175,6 @@ 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 @@ -171,13 +184,15 @@ 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 @@ -187,6 +202,9 @@ 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. @@ -199,7 +217,6 @@ 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 @@ -209,6 +226,9 @@ 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. @@ -218,7 +238,6 @@ 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 @@ -228,6 +247,9 @@ 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,7 +262,6 @@ 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 @@ -250,6 +271,9 @@ 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. @@ -258,7 +282,6 @@ This setting is important when Secure Sockets Layer (SSL) is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -268,6 +291,9 @@ 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. @@ -276,7 +302,6 @@ 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 @@ -286,6 +311,9 @@ Accept wildcard characters: False ``` ### -GzipLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. @@ -297,7 +325,6 @@ The GzipLevel parameter sets the Gzip configuration for the Exchange Web Service Type: GzipLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -307,6 +334,9 @@ Accept wildcard characters: False ``` ### -InternalNLBBypassUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalNLBBypassUrl parameter specifies the URL of the Exchange server that has the Client Access server role installed, regardless of whether it's behind a Network Load Balancing (NLB) array or not. When you set the InternalUrl parameter to the URL of the NLB array, you should set the InternalNLBBypassUrl parameter to the URL of the Client Access server itself. @@ -315,7 +345,6 @@ When you set the InternalUrl parameter to the URL of the NLB array, you should s Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -325,6 +354,9 @@ 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. @@ -333,7 +365,6 @@ This setting is important when SSL is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -343,13 +374,15 @@ Accept wildcard characters: False ``` ### -MRSProxyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Mailbox server. MRSProxy is a service that runs on Mailbox servers in a remote forest and helps to proxy a mailbox move. For more information, see [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -359,6 +392,9 @@ Accept wildcard characters: False ``` ### -MRSProxyMaxConnections + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). @@ -367,7 +403,6 @@ The MRSProxyMaxConnections parameter specifies the maximum number of simultaneou Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -377,6 +412,9 @@ 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. @@ -386,7 +424,6 @@ 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 @@ -396,13 +433,15 @@ Accept wildcard characters: False ``` ### -Path + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Path parameter sets the path of the virtual directory in the metabase. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -412,6 +451,9 @@ 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. @@ -423,7 +465,6 @@ 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 @@ -433,6 +474,9 @@ 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 @@ -444,7 +488,6 @@ 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 @@ -454,13 +497,15 @@ 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 website under which to create the virtual directory. This parameter shouldn't be used when you're creating a 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 @@ -470,13 +515,15 @@ 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 @@ -486,6 +533,9 @@ 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. @@ -495,7 +545,6 @@ 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 @@ -505,6 +554,9 @@ 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. @@ -514,7 +566,6 @@ 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/exchange/New-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md similarity index 91% rename from exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md rename to exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md index c18e6668eb..41ae4d24bf 100644 --- a/exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/new-x400authoritativedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: New-X400AuthoritativeDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/new-x400authoritativedomain +schema: 2.0.0 +title: New-X400AuthoritativeDomain --- # New-X400AuthoritativeDomain @@ -85,13 +86,15 @@ This example creates an external relay domain for the X.400 namespace Europe org ## PARAMETERS ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name for the X.400 authoritative domain. 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 Required: True Position: 1 @@ -101,6 +104,9 @@ Accept wildcard characters: False ``` ### -X400DomainName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X400DomainName parameter specifies the X.400 namespace, which can only include the X.400 organizational components. Specifically, only the following attribute types are supported: - C (Country) @@ -118,7 +124,6 @@ Separate the address attributes with semicolons and enclose the entire address i Type: X400Domain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -128,6 +133,9 @@ 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`. @@ -137,7 +145,6 @@ 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 @@ -147,6 +154,9 @@ 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,7 +165,6 @@ 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 @@ -165,13 +174,15 @@ 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 @@ -181,13 +192,15 @@ Accept wildcard characters: False ``` ### -X400ExternalRelay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X400ExternalRelay parameter specifies authoritative domain an external relay domain. If you set the X400ExternalRelay parameter to $true, Microsoft Exchange routes email to the external address and doesn't treat resolution failures to this subdomain as an error. ```yaml 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/exchange/Preview-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md similarity index 92% rename from exchange/exchange-ps/exchange/Preview-QuarantineMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md index 655b0da6f5..89f11cefda 100644 --- a/exchange/exchange-ps/exchange/Preview-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/preview-quarantinemessage applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Preview-QuarantineMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/preview-quarantinemessage +schema: 2.0.0 +title: Preview-QuarantineMessage --- # Preview-QuarantineMessage @@ -49,6 +50,9 @@ This example previews the quarantined message that has the specified Identity va ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Identity parameter specifies the quarantined message that you want to preview. 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. @@ -57,7 +61,6 @@ 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 @@ -67,6 +70,9 @@ 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 @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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/exchange/Redirect-Message.md b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md similarity index 93% rename from exchange/exchange-ps/exchange/Redirect-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md index 1a0354a5bc..b3da933b3e 100644 --- a/exchange/exchange-ps/exchange/Redirect-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/redirect-message applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Redirect-Message -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/redirect-message +schema: 2.0.0 +title: Redirect-Message --- # Redirect-Message @@ -48,6 +49,9 @@ This example drains the active messages from the delivery queues on the Mailbox ## PARAMETERS ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter specifies the source Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example: - Name @@ -59,7 +63,6 @@ The Server parameter specifies the source Exchange server where you want to run Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -69,13 +72,15 @@ Accept wildcard characters: False ``` ### -Target + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Target parameter specifies the target Mailbox server where you want to transfer the messages from the drained delivery queues. Enter the server name as a fully qualified domain name (FQDN). ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -85,6 +90,9 @@ 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`. @@ -94,7 +102,6 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Release-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md similarity index 89% rename from exchange/exchange-ps/exchange/Release-QuarantineMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md index 17f3d5590b..2ea8da2115 100644 --- a/exchange/exchange-ps/exchange/Release-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/release-quarantinemessage applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Release-QuarantineMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/release-quarantinemessage +schema: 2.0.0 +title: Release-QuarantineMessage --- # Release-QuarantineMessage @@ -114,6 +115,9 @@ This example releases a file that was quarantined as part of Safe Attachments fo ## 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`. 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. @@ -122,9 +126,8 @@ When you use this parameter, the Identity parameter is required, but the value i ```yaml Type: QuarantineMessageIdentity[] -Parameter Sets: Identities +Parameter Sets: Identities, OrgReleaseToAll, OrgReleaseToUser Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -133,29 +136,18 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: QuarantineMessageIdentity[] -Parameter Sets: OrgReleaseToAll, OrgReleaseToUser -Aliases: -Applicable: Exchange Online, Exchange Online Protection +### -Identity -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -### -Identity The Identity parameter specifies the quarantined message that you want to release. 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, OrgReleaseToAll, OrgReleaseToUser +Parameter Sets: Identities, OrgReleaseToAll, OrgReleaseToUser, IdentityOnly Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -164,20 +156,10 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: QuarantineMessageIdentity -Parameter Sets: IdentityOnly -Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection +### -ReleaseToAll -Required: True -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection -### -ReleaseToAll The ReleaseToAll switch releases the quarantined message to all original recipients. You don't need to specify a value with this switch. This switch is required for the quarantine type SPOMalware. @@ -190,7 +172,6 @@ You can't use the ReleaseToAll switch and the User parameter in the same command Type: SwitchParameter Parameter Sets: OrgReleaseToAll Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -200,6 +181,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The User parameter specifies the email address of the user to whom you want to release the quarantined message. You can specify multiple email addresses separated by commas. You can use this parameter to release the message to recipients of the original message, or to any other email addresses in the organization. @@ -210,7 +194,6 @@ If you previously used the ReleaseToAll switch to release the quarantined messag Type: String[] Parameter Sets: OrgReleaseToUser Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -220,6 +203,9 @@ Accept wildcard characters: False ``` ### -ActionType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ActionType parameter specifies the release action type. Valid values are: - Deny @@ -230,7 +216,6 @@ The ActionType parameter specifies the release action type. Valid values are: Type: ReleaseActionType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -240,6 +225,9 @@ Accept wildcard characters: False ``` ### -AllowSender + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The AllowSender switch specifies that all future messages from the sender won't be quarantined. You don't need to specify a value with this switch. If the message was quarantined because of a transport rule or blocked sender, messages from the sender can still be blocked in the future. @@ -248,7 +236,6 @@ If the message was quarantined because of a transport rule or blocked sender, me Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -258,6 +245,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -267,7 +257,6 @@ 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 @@ -277,6 +266,9 @@ 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 @@ -288,7 +280,6 @@ 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 @@ -298,6 +289,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. Use this switch whenever you attempt to re-release previously released messages from quarantine. @@ -306,7 +300,6 @@ Use this switch whenever you attempt to re-release previously released messages Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -316,6 +309,9 @@ Accept wildcard characters: False ``` ### -ReportFalsePositive + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ReportFalsePositive switch specifies whether to report the message as a false positive to Microsoft (good message marked as bad). You don't need to specify a value with this switch. This switch is available only for quarantined spam messages. @@ -324,7 +320,6 @@ This switch is available only for quarantined spam messages. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -334,6 +329,9 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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. The WhatIf switch doesn't work in Security & Compliance PowerShell. @@ -342,7 +340,6 @@ The WhatIf switch doesn't work in Security & Compliance PowerShell. 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/exchange/Remove-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md similarity index 84% rename from exchange/exchange-ps/exchange/Remove-ADPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md index 13ca24fb1e..d660d06056 100644 --- a/exchange/exchange-ps/exchange/Remove-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-adpermission applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ADPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-adpermission +schema: 2.0.0 +title: Remove-ADPermission --- # Remove-ADPermission @@ -86,15 +87,17 @@ This example removes the ability for anonymous users to send messages through th ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the object from which the permission should be removed. 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 +Parameter Sets: AccessRights, Owner, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -103,27 +106,16 @@ Accept pipeline input: True Accept wildcard characters: False ``` -```yaml -Type: ADRawEntryIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Instance -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -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 @@ -133,6 +125,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The User parameter specifies whose permissions are being removed from the Active Directory object. You can specify the following types of users or groups: - Mailbox users @@ -159,9 +154,8 @@ Otherwise, you can use any value that uniquely identifies the user or group. For ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -170,20 +164,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -AccessRights -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -AccessRights The AccessRights parameter specifies the rights that you want to remove from the user on the Active Directory object. Valid values include: - CreateChild @@ -212,7 +196,6 @@ You can specify multiple values separated by commas. Type: ActiveDirectoryRights[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -222,6 +205,9 @@ 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 removed from. The ChildObjectTypes parameter can only be used if the AccessRights parameter is set to CreateChild or DeleteChild. @@ -230,7 +216,6 @@ The ChildObjectTypes parameter can only be used if the AccessRights parameter is Type: ADSchemaObjectIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -240,6 +225,9 @@ 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`. @@ -249,7 +237,6 @@ 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 @@ -259,13 +246,15 @@ 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 removing are Deny permissions. 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 @@ -275,6 +264,9 @@ 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. @@ -283,7 +275,6 @@ 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 @@ -293,13 +284,15 @@ 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 to remove. ```yaml Type: ExtendedRightIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -309,6 +302,9 @@ 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 @@ -321,7 +317,6 @@ The InheritanceType parameter specifies how permissions are inherited. Valid val Type: ActiveDirectorySecurityInheritance Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -331,13 +326,15 @@ 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: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -347,6 +344,9 @@ 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. @@ -355,7 +355,6 @@ The Properties parameter can only be used if the AccessRights parameter is set t Type: ADSchemaObjectIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -365,13 +364,15 @@ 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/exchange/Remove-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md index 47ada3944f..ff5535af77 100644 --- a/exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-atpprotectionpolicyrule applicable: Exchange Online -title: Remove-ATPProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-atpprotectionpolicyrule +schema: 2.0.0 +title: Remove-ATPProtectionPolicyRule --- # Remove-ATPProtectionPolicyRule @@ -46,6 +47,9 @@ This example removes the existing rule for Defender for Office 365 protections i ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -77,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Remove-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md index 5339aa412e..5457e69552 100644 --- a/exchange/exchange-ps/exchange/Remove-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-accepteddomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AcceptedDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-accepteddomain +schema: 2.0.0 +title: Remove-AcceptedDomain --- # Remove-AcceptedDomain @@ -43,13 +44,15 @@ This example removes the accepted domain Contoso. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the accepted domain you want to remove. Enter either the GUID or the name of the remote domain. ```yaml Type: AcceptedDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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,7 +94,6 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md index 5ec58a6bb4..e63c3e3748 100644 --- a/exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdevice applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-ActiveSyncDevice -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdevice +schema: 2.0.0 +title: Remove-ActiveSyncDevice --- # Remove-ActiveSyncDevice @@ -61,13 +62,15 @@ This example removes the mobile device partnership for the device named Tablet\_ ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter uniquely identifies the specific device partnership to be removed. ```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 @@ -77,6 +80,9 @@ 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,7 +92,6 @@ 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 @@ -96,6 +101,9 @@ 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,7 +112,6 @@ 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,13 +121,15 @@ 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/exchange/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md index 5e56ff683d..91d4977b72 100644 --- a/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdeviceaccessrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-ActiveSyncDeviceAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdeviceaccessrule +schema: 2.0.0 +title: Remove-ActiveSyncDeviceAccessRule --- # Remove-ActiveSyncDeviceAccessRule @@ -52,13 +53,15 @@ This example removes all device access rules that have a name that starts with C ## 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 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: True Position: 1 @@ -68,6 +71,9 @@ 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`. @@ -77,7 +83,6 @@ 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,6 +92,9 @@ 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,7 +103,6 @@ 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,13 +112,15 @@ 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/exchange/Remove-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md index fee0ac4e53..7a2bbc5747 100644 --- a/exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdeviceclass applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ActiveSyncDeviceClass -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncdeviceclass +schema: 2.0.0 +title: Remove-ActiveSyncDeviceClass --- # Remove-ActiveSyncDeviceClass @@ -45,13 +46,15 @@ This example retrieves the list of devices connecting to Microsoft Exchange and ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the group of devices on which to scope the task. ```yaml Type: ActiveSyncDeviceClassIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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,13 +103,15 @@ 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/exchange/Remove-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md index faa170542f..3bd0f48e17 100644 --- a/exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncmailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-ActiveSyncMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncmailboxpolicy +schema: 2.0.0 +title: Remove-ActiveSyncMailboxPolicy --- # Remove-ActiveSyncMailboxPolicy @@ -55,6 +56,9 @@ This example removes the mobile device mailbox policy named Management and bypas ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mobile device mailbox policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the mobile device mailbox policy that you want Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -75,6 +78,9 @@ 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`. @@ -84,7 +90,6 @@ 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 @@ -94,6 +99,9 @@ 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,7 +110,6 @@ 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,6 +119,9 @@ 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. @@ -120,7 +130,6 @@ 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 Required: False Position: Named @@ -130,13 +139,15 @@ 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/exchange/Remove-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md index a45a5a2bd8..aff2abee24 100644 --- a/exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ActiveSyncVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-activesyncvirtualdirectory +schema: 2.0.0 +title: Remove-ActiveSyncVirtualDirectory --- # Remove-ActiveSyncVirtualDirectory @@ -59,6 +60,9 @@ This example removes a custom Exchange ActiveSync virtual directory from the ser ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the Exchange ActiveSync virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -71,7 +75,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,6 +84,9 @@ 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`. @@ -90,7 +96,6 @@ 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 @@ -100,13 +105,15 @@ 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,13 +123,15 @@ 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/exchange/Remove-AdaptiveScope.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AdaptiveScope.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-AdaptiveScope.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AdaptiveScope.md index 6716aabc5e..933ea4e7f3 100644 --- a/exchange/exchange-ps/exchange/Remove-AdaptiveScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AdaptiveScope.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-adaptivescope applicable: Security & Compliance -title: Remove-AdaptiveScope -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-adaptivescope +schema: 2.0.0 +title: Remove-AdaptiveScope --- # Remove-AdaptiveScope @@ -43,6 +44,9 @@ This example removes the adaptive scope named Project X. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the adaptive scope that you want to remove. You can use any value that uniquely identifies the adaptive scope. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the adaptive scope that you want to remove. You Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the adaptive scope. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md index f2bac7b9a2..4bc4052972 100644 --- a/exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-addressbookpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-AddressBookPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-addressbookpolicy +schema: 2.0.0 +title: Remove-AddressBookPolicy --- # Remove-AddressBookPolicy @@ -49,13 +50,15 @@ This example deletes the address book policy Murchison's Class. ## 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 that you want to remove. ```yaml Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md index a77eb38489..21b6c2bf2e 100644 --- a/exchange/exchange-ps/exchange/Remove-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-addresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-AddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-addresslist +schema: 2.0.0 +title: Remove-AddressList --- # Remove-AddressList @@ -51,6 +52,9 @@ This example removes the address list named AddressList1 and all of its child ad ## 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 remove. You can use any value that uniquely identifies the address list. For example: - Name @@ -64,7 +68,6 @@ If the address list has child address lists that you also want to remove, you ne Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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,7 +109,6 @@ 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,6 +118,9 @@ Accept wildcard characters: False ``` ### -Recursive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recursive switch specifies whether to remove all child address lists. You don't need to specify a value for this switch. If you don't use this switch, and the address list has child address lists, the command will fail. @@ -119,7 +129,6 @@ If you don't use this switch, and the address list has child address lists, 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 @@ -129,13 +138,15 @@ 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/exchange/Remove-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md index 8eb9950d2e..dda4541b6a 100644 --- a/exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-addressrewriteentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AddressRewriteEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-addressrewriteentry +schema: 2.0.0 +title: Remove-AddressRewriteEntry --- # Remove-AddressRewriteEntry @@ -54,13 +55,15 @@ This example removes all address rewrite entries that include contoso.com in the ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the address rewrite entry you want to remove. 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: True Position: 1 @@ -70,6 +73,9 @@ 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,7 +85,6 @@ 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,6 +94,9 @@ 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,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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/exchange/Remove-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md index 6bff81fad7..78d43a6137 100644 --- a/exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-antiphishpolicy applicable: Exchange Online, Exchange Online Protection -title: Remove-AntiPhishPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-antiphishpolicy +schema: 2.0.0 +title: Remove-AntiPhishPolicy --- # Remove-AntiPhishPolicy @@ -43,6 +44,9 @@ This example removes the antiphish policy named Quarantine Policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the antiphish policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the antiphish policy that you want to remove. Y Type: AntiPhishPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -90,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md index 77562bbd26..1d0e5e6eb2 100644 --- a/exchange/exchange-ps/exchange/Remove-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-antiphishrule applicable: Exchange Online, Exchange Online Protection -title: Remove-AntiPhishRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-antiphishrule +schema: 2.0.0 +title: Remove-AntiPhishRule --- # Remove-AntiPhishRule @@ -42,6 +43,9 @@ This examples removes the antiphish rule named Research Department Phishing Rule ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the antiphish rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the antiphish rule that you want to remove. You Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-App.md b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-App.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-App.md index c24c1658e5..8c0a55cea5 100644 --- a/exchange/exchange-ps/exchange/Remove-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-app applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-App -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-app +schema: 2.0.0 +title: Remove-App --- # Remove-App @@ -49,13 +50,15 @@ This example removes the Finance Test app installed for user Tony. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the AppID (GUID value) of the app that you want to remove. 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: True Position: 1 @@ -65,6 +68,9 @@ Accept wildcard characters: False ``` ### -AppType + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AppType Description }} @@ -73,7 +79,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -83,6 +88,9 @@ 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`. @@ -92,7 +100,6 @@ 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,6 +109,9 @@ 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. @@ -110,7 +120,6 @@ 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 @@ -120,6 +129,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailbox parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -137,7 +149,6 @@ The Mailbox parameter specifies the mailbox that you want to modify. You can use Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -147,6 +158,9 @@ 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. You don't need to specify a value with this switch. This switch is required if the targeted app is installed for the organization. @@ -155,7 +169,6 @@ This switch is required if the targeted app is installed for the organization. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -165,13 +178,15 @@ Accept wildcard characters: False ``` ### -PrivateCatalog + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrivateCatalog switch specifies that the app you want to remove 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 @@ -181,13 +196,15 @@ 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/exchange/Remove-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionCompliancePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionCompliancePolicy.md index c470a3f9f2..aca121c1a2 100644 --- a/exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-appretentioncompliancepolicy applicable: Security & Compliance -title: Remove-AppRetentionCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-appretentioncompliancepolicy +schema: 2.0.0 +title: Remove-AppRetentionCompliancePolicy --- # Remove-AppRetentionCompliancePolicy @@ -43,6 +44,9 @@ This example removes the app retention compliance policy named Contoso Viva Enga ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the app retention compliance policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the app retention compliance policy that you wa Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionComplianceRule.md index 724cda7063..0b9a8bb859 100644 --- a/exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AppRetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-appretentioncompliancerule applicable: Security & Compliance -title: Remove-AppRetentionComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-appretentioncompliancerule +schema: 2.0.0 +title: Remove-AppRetentionComplianceRule --- # Remove-AppRetentionComplianceRule @@ -43,6 +44,9 @@ This example removes the app retention compliance policy rule Contoso Viva Engag ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the app retention compliance rule that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the app retention compliance rule that you want Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the rule. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md index 9b1bae6a1a..c5b4421902 100644 --- a/exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-applicationaccesspolicy applicable: Exchange Online, Exchange Online Protection -title: Remove-ApplicationAccessPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-applicationaccesspolicy +schema: 2.0.0 +title: Remove-ApplicationAccessPolicy --- # Remove-ApplicationAccessPolicy @@ -42,13 +43,15 @@ This example removes the specified policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the application access policy that you want to remove. 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 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Remove-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md index a166c59fe8..e3608c13b0 100644 --- a/exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-attachmentfilterentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AttachmentFilterEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-attachmentfilterentry +schema: 2.0.0 +title: Remove-AttachmentFilterEntry --- # Remove-AttachmentFilterEntry @@ -52,6 +53,9 @@ This example removes the attachment filter entry that filters attachments that h ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the type of attachment that this filter entry removes. The Identity parameter accepts values in the format Type:Name, where Type is one of the following two values: - ContentType: This value matches the attachment filter entry against the MIME content type. @@ -63,7 +67,6 @@ In Type:Name, Name can be either the file name of the attachment filter entry to Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,6 +97,9 @@ 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. @@ -100,7 +108,6 @@ 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 @@ -110,13 +117,15 @@ 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/exchange/Remove-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AuthRedirect.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md index 5472c1ac64..2cb9339dcb 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-authredirect applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AuthRedirect -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-authredirect +schema: 2.0.0 +title: Remove-AuthRedirect --- # Remove-AuthRedirect @@ -50,13 +51,15 @@ This example removes all existing OAuth redirection objects from your organizati ## 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 remove. The object name uses the syntax `AuthRedirect-Bearer-GUID`. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect. ```yaml Type: AuthRedirectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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 @@ -101,13 +108,15 @@ 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/exchange/Remove-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-AuthServer.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md index 826c25a07f..76288e4fa3 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-authserver applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AuthServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-authserver +schema: 2.0.0 +title: Remove-AuthServer --- # Remove-AuthServer @@ -43,6 +44,9 @@ This example removes the authorization server named AMC. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the authorization server object that you want to remove. You can use any value that uniquely identifies the authorization server. For example: - Name @@ -53,7 +57,6 @@ 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 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index 7881265a05..9e29dc960a 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-authenticationpolicy applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-AuthenticationPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-authenticationpolicy +schema: 2.0.0 +title: Remove-AuthenticationPolicy --- # Remove-AuthenticationPolicy @@ -51,6 +52,9 @@ In Exchange Online, this example enables legacy Exchange tokens to be issued to ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + The Identity parameter specifies the authentication policy you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the authentication policy you want to remove. Y Type: AuthPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -AllowLegacyExchangeTokens + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AllowLegacyExchangeTokens switch enables legacy Exchange tokens to be issued to Outlook add-ins for your organization. You don't need to specify a value with this switch. @@ -90,7 +96,6 @@ This switch applies to the entire organization. The Identity parameter is requir Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -100,6 +105,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> 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`. @@ -109,7 +117,6 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -119,6 +126,9 @@ Accept wildcard characters: False ``` ### -TenantId + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill TenantId Description }} @@ -127,7 +137,6 @@ 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 @@ -137,13 +146,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> 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: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelPolicy.md index d6b2940550..81ef790987 100644 --- a/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-autosensitivitylabelpolicy applicable: Security & Compliance -title: Remove-AutoSensitivityLabelPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-autosensitivitylabelpolicy +schema: 2.0.0 +title: Remove-AutoSensitivityLabelPolicy --- # Remove-AutoSensitivityLabelPolicy @@ -42,6 +43,9 @@ This example removes the policy named Marketing Group. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the auto-labeling policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the auto-labeling policy that you want to remov Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelRule.md index f779597117..7016a2ac07 100644 --- a/exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutoSensitivityLabelRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-autosensitivitylabelrule applicable: Security & Compliance -title: Remove-AutoSensitivityLabelRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-autosensitivitylabelrule +schema: 2.0.0 +title: Remove-AutoSensitivityLabelRule --- # Remove-AutoSensitivityLabelRule @@ -42,6 +43,9 @@ This example removes the rule named Social Security Rule. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the auto-labeling policy rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the auto-labeling policy rule that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md index 948dcc21f7..9fe4188fd7 100644 --- a/exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-autodiscovervirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-AutodiscoverVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-autodiscovervirtualdirectory +schema: 2.0.0 +title: Remove-AutodiscoverVirtualDirectory --- # Remove-AutodiscoverVirtualDirectory @@ -43,6 +44,9 @@ This example removes the Autodiscover virtual directory from the site autodiscov ## 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 remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -55,7 +59,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md index 97bf6ead5a..9f6f30bccf 100644 --- a/exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityaddressspace applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-AvailabilityAddressSpace -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityaddressspace +schema: 2.0.0 +title: Remove-AvailabilityAddressSpace --- # Remove-AvailabilityAddressSpace @@ -52,6 +53,9 @@ This example immediately removes the availability address space object named Con ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the availability address that you want to remove. You can use any value that uniquely identifies the object. For example: - Name @@ -62,7 +66,6 @@ The Identity parameter specifies the availability address that you want to remov Type: AvailabilityAddressSpaceIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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,7 +107,6 @@ 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,13 +116,15 @@ 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/exchange/Remove-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md index f51da6fded..2285d9f8c8 100644 --- a/exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityconfig applicable: Exchange Online -title: Remove-AvailabilityConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityconfig +schema: 2.0.0 +title: Remove-AvailabilityConfig --- # Remove-AvailabilityConfig @@ -42,13 +43,15 @@ This example removes the existing availability configuration. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the availability configuration that you want to remove. You don't need to use this parameter, because there's only one availability configuration object named Availability Configuration in any organization. ```yaml Type: AvailabilityConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 1 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Remove-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md index 8e66eefd7a..bea03d8ffd 100644 --- a/exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityreportoutage applicable: Exchange Server 2010 -title: Remove-AvailabilityReportOutage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-availabilityreportoutage +schema: 2.0.0 +title: Remove-AvailabilityReportOutage --- # Remove-AvailabilityReportOutage @@ -45,13 +46,15 @@ This example removes a manually injected site-scoped outage for a specified day. ## 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 @@ -61,13 +64,15 @@ 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 @@ -77,6 +82,9 @@ 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`. @@ -86,7 +94,6 @@ 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 @@ -96,6 +103,9 @@ 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. @@ -104,7 +114,6 @@ 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 @@ -114,13 +123,15 @@ 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 @@ -130,13 +141,15 @@ 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 @@ -146,13 +159,15 @@ 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/exchange/Remove-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-BlockedConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md index 6520e630b3..9c30aa00e0 100644 --- a/exchange/exchange-ps/exchange/Remove-BlockedConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-blockedconnector applicable: Exchange Online, Exchange Online Protection -title: Remove-BlockedConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-blockedconnector +schema: 2.0.0 +title: Remove-BlockedConnector --- # Remove-BlockedConnector @@ -39,13 +40,15 @@ This unblocks the specified blocked connector. ## PARAMETERS ### -ConnectorId + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorId parameter specifies the blocked connector that you want to unblock. The value is a GUID (for example, 159eb7c4-75d7-43e2-95fe-ced44b3e0a56). You can find this value from the output of the Get-BlockedConnector command. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -55,13 +58,15 @@ Accept wildcard characters: False ``` ### -Reason + +> Applicable: Exchange Online, Exchange Online Protection + The Reason parameter specifies comments about why you're unblocking the blocked connector. 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 diff --git a/exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md index ce007bf146..f0d6df6ea5 100644 --- a/exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-blockedsenderaddress applicable: Exchange Online, Exchange Online Protection -title: Remove-BlockedSenderAddress -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-blockedsenderaddress +schema: 2.0.0 +title: Remove-BlockedSenderAddress --- # Remove-BlockedSenderAddress @@ -43,13 +44,15 @@ This example unblocks the user julia@contoso.com. ## PARAMETERS ### -SenderAddress + +> Applicable: Exchange Online, Exchange Online Protection + The SenderAddress parameter specifies the email address of the user that you want to unblock. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -59,13 +62,15 @@ Accept wildcard characters: False ``` ### -Reason + +> Applicable: Exchange Online, Exchange Online Protection + The Reason parameter specifies the reason the user was blocked (the Reason property value). 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 diff --git a/exchange/exchange-ps/exchange/Remove-CalendarEvents.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-CalendarEvents.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md index c199b24fec..fadf359348 100644 --- a/exchange/exchange-ps/exchange/Remove-CalendarEvents.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-calendarevents applicable: Exchange Server 2019, Exchange Online -title: Remove-CalendarEvents -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-calendarevents +schema: 2.0.0 +title: Remove-CalendarEvents --- # Remove-CalendarEvents @@ -62,6 +63,9 @@ This example previews the meetings that would be cancelled in Jacob Berger's cal ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2019, Exchange Online + The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -79,7 +83,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -89,6 +92,9 @@ Accept wildcard characters: False ``` ### -QueryWindowInDays + +> Applicable: Exchange Server 2019, Exchange Online + The QueryWindowInDays parameter specifies the number of days after the QueryStartDate parameter value to look for meetings that you want to cancel. If an instance of a recurring meeting occurs during the specified time period, the entire series is cancelled (not just the instances during the time period). @@ -99,7 +105,6 @@ If an instance of a recurring meeting occurs during the specified time period, t Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: True Position: Named @@ -109,6 +114,9 @@ Accept wildcard characters: False ``` ### -CancelOrganizedMeetings + +> Applicable: Exchange Server 2019, Exchange Online + The CancelOrganizedMeetings switch specifies whether to cancel meetings in the mailbox. You don't need to specify a value with this switch. To cancel meetings in the mailbox, you need to use this switch. @@ -117,7 +125,6 @@ To cancel meetings in the mailbox, you need to use this switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: False Position: Named @@ -127,6 +134,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -136,7 +146,6 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2019, Exchange Online Required: False Position: Named @@ -146,6 +155,9 @@ Accept wildcard characters: False ``` ### -PreviewOnly + +> Applicable: Exchange Server 2019, Exchange Online + The PreviewOnly switch specifies whether to preview the results of the command without actually cancelling any meetings. You don't need to specify a value with this switch. You use this switch with the Verbose switch. @@ -154,7 +166,6 @@ You use this switch with the Verbose switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: False Position: Named @@ -164,6 +175,9 @@ Accept wildcard characters: False ``` ### -QueryStartDate + +> Applicable: Exchange Server 2019, Exchange Online + The QueryStartDate parameter specifies the start date to look for meetings that you want to cancel. 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". @@ -176,7 +190,6 @@ You use the QueryWindowInDays parameter to specify the end date. Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: False Position: Named @@ -186,6 +199,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -194,7 +210,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -204,13 +219,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: 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 2019, Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldPolicy.md index 0a3fbdb087..e3638b382f 100644 --- a/exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-caseholdpolicy applicable: Security & Compliance -title: Remove-CaseHoldPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-caseholdpolicy +schema: 2.0.0 +title: Remove-CaseHoldPolicy --- # Remove-CaseHoldPolicy @@ -45,6 +46,9 @@ This example removes the case hold policy named "Regulation 123 Compliance". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the case hold policy to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the case hold policy to remove. You can use any Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -65,6 +68,9 @@ 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,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-CaseHoldRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldRule.md index cb7f9417bd..e0f96c91f0 100644 --- a/exchange/exchange-ps/exchange/Remove-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CaseHoldRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-caseholdrule applicable: Security & Compliance -title: Remove-CaseHoldRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-caseholdrule +schema: 2.0.0 +title: Remove-CaseHoldRule --- # Remove-CaseHoldRule @@ -45,6 +46,9 @@ This example removes the case hold rule named "One Year Standard". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the case hold rule to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the case hold rule to remove. You can use any v Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -65,6 +68,9 @@ 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,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the rule. 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md index 9e0c0ef4af..5ee367f66b 100644 --- a/exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-classificationrulecollection applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-ClassificationRuleCollection -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-classificationrulecollection +schema: 2.0.0 +title: Remove-ClassificationRuleCollection --- # Remove-ClassificationRuleCollection @@ -45,13 +46,15 @@ This example removes the classification rule collection named External Classific ## 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 remove. 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: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ClientAccessArray.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md index 24930a04a7..85528f0cdb 100644 --- a/exchange/exchange-ps/exchange/Remove-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-clientaccessarray applicable: Exchange Server 2010 -title: Remove-ClientAccessArray -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-clientaccessarray +schema: 2.0.0 +title: Remove-ClientAccessArray --- # Remove-ClientAccessArray @@ -43,6 +44,9 @@ This example removes the existing Client Access array with the FQDN value casarr ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the Client Access array that you want to remove. You can use these values: - Name (if the value doesn't contain spaces) @@ -55,7 +59,6 @@ The Identity parameter specifies the Client Access array that you want to remove Type: ClientAccessArrayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ClientAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md index df3b17ddf9..cbca9aa176 100644 --- a/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-clientaccessrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-ClientAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-clientaccessrule +schema: 2.0.0 +title: Remove-ClientAccessRule --- # Remove-ClientAccessRule @@ -48,6 +49,9 @@ This example removes the existing client access rule named "Block Connections fr ## 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 remove. You can use any value that uniquely identifies the client access rule. For example: - Name @@ -58,7 +62,6 @@ The Identity parameter specifies the client access rule that you want to remove. Type: ClientAccessRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -68,6 +71,9 @@ 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`. @@ -77,7 +83,6 @@ 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 @@ -87,6 +92,9 @@ 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. @@ -95,7 +103,6 @@ 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,13 +112,15 @@ 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/exchange/Remove-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCase.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-ComplianceCase.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCase.md index a636d54a72..b0b6e7f7db 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancecase applicable: Security & Compliance -title: Remove-ComplianceCase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancecase +schema: 2.0.0 +title: Remove-ComplianceCase --- # Remove-ComplianceCase @@ -43,6 +44,9 @@ This example removes the compliance case named Case 5150 ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the compliance case that you want to remove. You can use any value that uniquely identifies the case. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the compliance case that you want to remove. Yo Type: ComplianceCaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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 @@ -97,13 +104,15 @@ 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/exchange/Remove-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCaseMember.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCaseMember.md index 2a22dd2318..14a1b2c628 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceCaseMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancecasemember applicable: Security & Compliance -title: Remove-ComplianceCaseMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancecasemember +schema: 2.0.0 +title: Remove-ComplianceCaseMember --- # Remove-ComplianceCaseMember @@ -42,6 +43,9 @@ This example removes Jan Dryml from the eDiscovery case named Case OU812. ## 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. @@ -50,7 +54,6 @@ To see the available eDiscovery cases, use the Get-ComplianceCase cmdlet. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -60,6 +63,9 @@ Accept wildcard characters: False ``` ### -Member + +> Applicable: Security & Compliance + The Member parameter specifies the user that you want to remove from the eDiscovery case. You can use any value that uniquely identifies the user. For example: - Name @@ -71,7 +77,6 @@ The Member parameter specifies the user that you want to remove from the eDiscov Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -81,6 +86,9 @@ 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`. @@ -90,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md index fdca44b480..f51564eba1 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-complianceretentioneventtype applicable: Security & Compliance -title: Remove-ComplianceRetentionEventType -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-complianceretentioneventtype +schema: 2.0.0 +title: Remove-ComplianceRetentionEventType --- # Remove-ComplianceRetentionEventType @@ -43,6 +44,9 @@ This example remove the retention event type name Fabrikam Project ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention event type that you want to remove. You can use any value that uniquely identifies the retention event type. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the retention event type that you want to remov Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the retention event type. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md index 92fdcfc7a7..b5b6d80f34 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesearch applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Remove-ComplianceSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesearch +schema: 2.0.0 +title: Remove-ComplianceSearch --- # Remove-ComplianceSearch @@ -46,6 +47,9 @@ This example removes 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 remove. You can use any value that uniquely identifies the compliance search. For example: @@ -59,7 +63,6 @@ You can find these values by running the command Get-ComplianceSearch | Format-T Type: ComplianceSearchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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. @@ -96,7 +104,6 @@ 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/exchange/Remove-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearchAction.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearchAction.md index 8140168e36..2a0bd47957 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearchAction.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesearchaction applicable: Security & Compliance -title: Remove-ComplianceSearchAction -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesearchaction +schema: 2.0.0 +title: Remove-ComplianceSearchAction --- # Remove-ComplianceSearchAction @@ -42,6 +43,9 @@ This example removes the compliance search action named `Case 1234_Preview`. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the compliance search action that you want to remove. 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"`. @@ -51,7 +55,6 @@ The Identity parameter specifies the compliance search action that you want to r Type: ComplianceSearchActionIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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,13 +85,15 @@ 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/exchange/Remove-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md index 8b38b2ba8a..ad4929bded 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesecurityfilter applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Remove-ComplianceSecurityFilter -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancesecurityfilter +schema: 2.0.0 +title: Remove-ComplianceSecurityFilter --- # Remove-ComplianceSecurityFilter @@ -42,13 +43,15 @@ This example removes the compliance security filter named HR Filter. ## PARAMETERS ### -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 remove. 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 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Remove-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceTag.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-ComplianceTag.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceTag.md index 46c293ddf7..65d8ada32f 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceTag.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancetag applicable: Security & Compliance -title: Remove-ComplianceTag -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-compliancetag +schema: 2.0.0 +title: Remove-ComplianceTag --- # Remove-ComplianceTag @@ -44,6 +45,9 @@ This example removes the label named HR Content. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the label that you want to remove. You can use any value that uniquely identifies the tag. For example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the label that you want to remove. You can use Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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,13 +88,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the label. 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 @@ -99,13 +106,15 @@ 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 @@ -115,13 +124,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Security & Compliance + The WhatIf switch causes the command to simulate its results. By using this switch, you can view what changes would occur without having to commit those changes. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md index 88836574db..62a8323508 100644 --- a/exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-contentfilterphrase applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ContentFilterPhrase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-contentfilterphrase +schema: 2.0.0 +title: Remove-ContentFilterPhrase --- # Remove-ContentFilterPhrase @@ -53,6 +54,9 @@ This example removes the custom phrase Free credit report from the list of phras ## 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 remove. You must enclose the value of the Identity parameter in quotation marks ("). For this command, the Identity parameter performs the same actions as the Phrase parameter. The Identity and Phrase parameters are interchangeable. You can't use the Phrase parameter if the Identity parameter is used. @@ -61,7 +65,6 @@ For this command, the Identity parameter performs the same actions as the Phrase Type: ContentFilterPhraseIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -71,6 +74,9 @@ 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,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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 remove. You must enclose the value of the Phrase parameter in quotation marks ("). For this command, the Phrase parameter performs the same actions as the Identity parameter. The Phrase and Identity parameters are interchangeable. You can't use the Identity parameter if the Phrase parameter is used. @@ -116,7 +126,6 @@ For this command, the Phrase parameter performs the same actions as the Identity Type: ContentFilterPhraseIdParameter Parameter Sets: Phrase Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -126,13 +135,15 @@ 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/exchange/Remove-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-DataClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md index c89fd96ca0..4d24401f84 100644 --- a/exchange/exchange-ps/exchange/Remove-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dataclassification applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-DataClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dataclassification +schema: 2.0.0 +title: Remove-DataClassification --- # Remove-DataClassification @@ -47,6 +48,9 @@ This example removes the data classification rule named "Contoso Confidential". ## PARAMETERS ### -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 remove. You can use any value that uniquely identifies the data classification rule. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the data classification rule that you want to r Type: DataClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md index 2311d1505f..7f1a55f10e 100644 --- a/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-DatabaseAvailabilityGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroup +schema: 2.0.0 +title: Remove-DatabaseAvailabilityGroup --- # Remove-DatabaseAvailabilityGroup @@ -43,13 +44,15 @@ This example, deletes 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 be removed. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,13 +83,15 @@ 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 @@ -94,13 +101,15 @@ 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/exchange/Remove-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md index 2a130fd882..d6358cdd96 100644 --- a/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroupnetwork applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-DatabaseAvailabilityGroupNetwork -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroupnetwork +schema: 2.0.0 +title: Remove-DatabaseAvailabilityGroupNetwork --- # Remove-DatabaseAvailabilityGroupNetwork @@ -43,13 +44,15 @@ This example removes the DAG network DAGNetwork04 from 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 network being removed. ```yaml Type: DatabaseAvailabilityGroupNetworkIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,13 +83,15 @@ 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 @@ -94,13 +101,15 @@ 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/exchange/Remove-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md index dfb283d873..ecca706c27 100644 --- a/exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroupserver applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-DatabaseAvailabilityGroupServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-databaseavailabilitygroupserver +schema: 2.0.0 +title: Remove-DatabaseAvailabilityGroupServer --- # Remove-DatabaseAvailabilityGroupServer @@ -52,13 +53,15 @@ This example removes the configuration settings for the Mailbox server MBX4 from ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the DAG from which you're removing the server. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ 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 remove from the DAG. You can use any value that uniquely identifies the server. For example: - Name @@ -79,7 +85,6 @@ The MailboxServer parameter specifies the Mailbox server to remove from the DAG. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 2 @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConfigurationOnly switch remove the Mailbox server from the DAG object in Active Directory. You don't need to specify a value with this switch. If the Mailbox server is offline but the DAG has quorum, the Mailbox server is evicted from the DAG's cluster and removed from the DAG object in Active Directory. @@ -99,7 +107,6 @@ You should use this switch only if the Mailbox server has been lost and can no l Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -109,6 +116,9 @@ 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`. @@ -118,7 +128,6 @@ 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 @@ -128,13 +137,15 @@ 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 @@ -144,13 +155,15 @@ 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 removing members from 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 @@ -160,13 +173,15 @@ 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/exchange/Remove-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md index ff7ae195fd..ca8f2c7702 100644 --- a/exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-deliveryagentconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-DeliveryAgentConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-deliveryagentconnector +schema: 2.0.0 +title: Remove-DeliveryAgentConnector --- # Remove-DeliveryAgentConnector @@ -45,13 +46,15 @@ This example removes the delivery agent connector named Contoso Delivery Agent C ## 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: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessPolicy.md index 12423d67fd..fe478249fe 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconditionalaccesspolicy applicable: Security & Compliance -title: Remove-DeviceConditionalAccessPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconditionalaccesspolicy +schema: 2.0.0 +title: Remove-DeviceConditionalAccessPolicy --- # Remove-DeviceConditionalAccessPolicy @@ -51,6 +52,9 @@ This example removes the mobile device conditional access policy named Human Res ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device conditional access policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the mobile device conditional access policy tha Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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/exchange/Remove-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessRule.md index 08e72f3b32..84de737627 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConditionalAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconditionalaccessrule applicable: Security & Compliance -title: Remove-DeviceConditionalAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconditionalaccessrule +schema: 2.0.0 +title: Remove-DeviceConditionalAccessRule --- # Remove-DeviceConditionalAccessRule @@ -51,13 +52,15 @@ This example removes the mobile device conditional access rule named Secure Emai ## PARAMETERS ### -Identity + +> Applicable: 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}`. You can find the name value by running the command: Get-DeviceConditionalAccessRule | Format-List Name. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ 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/exchange/Remove-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationPolicy.md index 913547d5a2..b64e13266a 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconfigurationpolicy applicable: Security & Compliance -title: Remove-DeviceConfigurationPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconfigurationpolicy +schema: 2.0.0 +title: Remove-DeviceConfigurationPolicy --- # Remove-DeviceConfigurationPolicy @@ -51,6 +52,9 @@ This example removes the mobile device configuration policy named Engineering Gr ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device configuration policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the mobile device configuration policy that you Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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/exchange/Remove-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationRule.md index d3ab49229c..f7f2bf1a7d 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceConfigurationRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconfigurationrule applicable: Security & Compliance -title: Remove-DeviceConfigurationRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-deviceconfigurationrule +schema: 2.0.0 +title: Remove-DeviceConfigurationRule --- # Remove-DeviceConfigurationRule @@ -51,13 +52,15 @@ This example removes the mobile device configuration rule named Legal Team{58b50 ## PARAMETERS ### -Identity + +> Applicable: 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}`. You can find the name values by running the command: Get-DeviceConfigurationRule | Format-List Name. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ 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/exchange/Remove-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantPolicy.md index 919b43271d..ef5069d0ed 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-devicetenantpolicy applicable: Security & Compliance -title: Remove-DeviceTenantPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-devicetenantpolicy +schema: 2.0.0 +title: Remove-DeviceTenantPolicy --- # Remove-DeviceTenantPolicy @@ -50,13 +51,15 @@ This example removes your organization's mobile device tenant policy. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the mobile device tenant policy that you want to remove, but there's only one in your organization. The name of the policy is a GUID value. For example, a6958701-c82c-4064-ac11-64e40e7f4032. You can find this value by running the command: `Get-DeviceTenantPolicy | Format-List Name`. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Remove-DeviceTenantRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantRule.md index 0fe5232d12..9700d4dacf 100644 --- a/exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeviceTenantRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-devicetenantrule applicable: Security & Compliance -title: Remove-DeviceTenantRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-devicetenantrule +schema: 2.0.0 +title: Remove-DeviceTenantRule --- # Remove-DeviceTenantRule @@ -51,13 +52,15 @@ This example removes the mobile device tenant rule from your organization. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the mobile device tenant rule that you want to remove, but there's only one in your organization. The name of the rule is a GUID. For example, 7577c5f3-05a4-4f55-a0a3-82aab5e98c84. You can find the name value by running the command `Get-DeviceTenantRule | Format-List Name`. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ 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/exchange/Remove-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md similarity index 88% rename from exchange/exchange-ps/exchange/Remove-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md index b35ddb9a2a..7062678e01 100644 --- a/exchange/exchange-ps/exchange/Remove-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-distributiongroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-DistributionGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-distributiongroup +schema: 2.0.0 +title: Remove-DistributionGroup --- # Remove-DistributionGroup @@ -45,6 +46,9 @@ This example removes the distribution group named Temporary 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 distribution group or mail-enabled security group that you want to remove. You can use any value that uniquely identifies the group. For example: - Name @@ -58,7 +62,6 @@ 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, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -68,6 +71,9 @@ 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: @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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,7 +126,6 @@ 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 @@ -126,6 +135,9 @@ 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. @@ -139,7 +151,6 @@ 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 @@ -149,13 +160,15 @@ 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/exchange/Remove-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md similarity index 88% rename from exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md index 0f323c30da..8c025231b8 100644 --- a/exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-distributiongroupmember applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-DistributionGroupMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-distributiongroupmember +schema: 2.0.0 +title: Remove-DistributionGroupMember --- # Remove-DistributionGroupMember @@ -47,6 +48,9 @@ This example removes Jan Dryml from the distribution group named Technical Suppo ## 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 modify. You can use any value that uniquely identifies the group. For example: - Name @@ -60,7 +64,6 @@ 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, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -70,6 +73,9 @@ 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: @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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`. @@ -100,7 +108,6 @@ 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,6 +117,9 @@ 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. @@ -118,7 +128,6 @@ 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,6 +137,9 @@ 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 remove from the group. You can use any value that uniquely identifies the recipient. For example: - Name @@ -141,7 +153,6 @@ The Member parameter specifies the recipient that you want to remove from the gr 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 @@ -151,13 +162,15 @@ 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/exchange/Remove-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpCompliancePolicy.md index 86f93677d8..bfc6077491 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpcompliancepolicy applicable: Security & Compliance -title: Remove-DlpCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpcompliancepolicy +schema: 2.0.0 +title: Remove-DlpCompliancePolicy --- # Remove-DlpCompliancePolicy @@ -49,6 +50,9 @@ This example removes a DLP policy specified by its name. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the DLP policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -60,7 +64,6 @@ The Identity parameter specifies the DLP policy that you want to remove. You can Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -70,6 +73,9 @@ 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`. @@ -79,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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/exchange/Remove-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpComplianceRule.md index cbbfa8b856..0e3c4cb796 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpcompliancerule applicable: Security & Compliance -title: Remove-DlpComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpcompliancerule +schema: 2.0.0 +title: Remove-DlpComplianceRule --- # Remove-DlpComplianceRule @@ -42,6 +43,9 @@ This example removes the DLP rule named "PII SS# Custom". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the DLP rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the DLP rule that you want to remove. You can u Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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/exchange/Remove-DlpEdmSchema.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpEdmSchema.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpEdmSchema.md index f32281feb1..d918f01cb3 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpEdmSchema.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpedmschema applicable: Security & Compliance -title: Remove-DlpEdmSchema -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpedmschema +schema: 2.0.0 +title: Remove-DlpEdmSchema --- # Remove-DlpEdmSchema @@ -42,6 +43,9 @@ This example removes the DLP EDM schema named Schema for Patient Records. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the DLP EDM schema that you want to remove. You can use any value that uniquely identifies the schema. For example: - Name @@ -51,7 +55,6 @@ The Identity parameter specifies the DLP EDM schema that you want to remove. You Type: EdmStorageIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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,13 +85,15 @@ 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/exchange/Remove-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpKeywordDictionary.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpKeywordDictionary.md index 9497d5484f..aaaa6614ac 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpKeywordDictionary.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpkeyworddictionary applicable: Security & Compliance -title: Remove-DlpKeywordDictionary -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpkeyworddictionary +schema: 2.0.0 +title: Remove-DlpKeywordDictionary --- # Remove-DlpKeywordDictionary @@ -49,13 +50,15 @@ This example removes all the DLP keyword dictionaries with a Confirm on each rem ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the DLP keyword dictionary that you want to remove. If the value contains spaces, enclose the value in quotation marks. ```yaml Type: SensitiveInformationTypeIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -65,6 +68,9 @@ 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,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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/exchange/Remove-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-DlpPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md index e7591b41e1..5efaf5eed3 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlppolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-DlpPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlppolicy +schema: 2.0.0 +title: Remove-DlpPolicy --- # Remove-DlpPolicy @@ -45,6 +46,9 @@ This example removes the existing DLP policy named Contoso PII. ## 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 remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the DLP policy that you want to remove. You can Type: DlpPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md index 6ec3166bac..f0f8b5e4f0 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlppolicytemplate applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-DlpPolicyTemplate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlppolicytemplate +schema: 2.0.0 +title: Remove-DlpPolicyTemplate --- # Remove-DlpPolicyTemplate @@ -43,13 +44,15 @@ This example removes the DLP policy template named External DLP Policy Template. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the DLP policy template you want to remove. 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 Required: False Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,13 +83,15 @@ 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 @@ -94,13 +101,15 @@ 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/exchange/Remove-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationType.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationType.md index 248e930c45..47afe158d0 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationType.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpsensitiveinformationtype applicable: Security & Compliance -title: Remove-DlpSensitiveInformationType -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpsensitiveinformationtype +schema: 2.0.0 +title: Remove-DlpSensitiveInformationType --- # Remove-DlpSensitiveInformationType @@ -46,6 +47,9 @@ This example removes the sensitive information type rule named "Contoso Confiden ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the sensitive information type rule that you want to remove. You can use any value that uniquely identifies the sensitive information type rule. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the sensitive information type rule that you wa Type: DataClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationTypeRulePackage.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationTypeRulePackage.md index 33e6cf6253..48f4e4ada4 100644 --- a/exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpSensitiveInformationTypeRulePackage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpsensitiveinformationtyperulepackage applicable: Security & Compliance -title: Remove-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dlpsensitiveinformationtyperulepackage +schema: 2.0.0 +title: Remove-DlpSensitiveInformationTypeRulePackage --- # Remove-DlpSensitiveInformationTypeRulePackage @@ -46,6 +47,9 @@ This example removes the non-Microsoft sensitive information type rule package n ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the sensitive information type rule package that you want to remove. You can use any value that uniquely identifies the rule package. For example: - RuleCollectionName @@ -56,7 +60,6 @@ The Identity parameter specifies the sensitive information type rule package tha Type: SensitiveInformationTypeRuleCollectionIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Remove-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md index 3c76cd90a3..b2ca6334c2 100644 --- a/exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-dynamicdistributiongroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-DynamicDistributionGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-dynamicdistributiongroup +schema: 2.0.0 +title: Remove-DynamicDistributionGroup --- # Remove-DynamicDistributionGroup @@ -44,6 +45,9 @@ This example deletes the dynamic distribution group named Test Users. ## 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 remove. You can use any value that uniquely identifies the dynamic distribution group. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the dynamic distribution group that you want to Type: DynamicGroupIdParameter 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 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Remove-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md index 9aeaf4a0cd..2b2abe8932 100644 --- a/exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-eopprotectionpolicyrule applicable: Exchange Online, Exchange Online Protection -title: Remove-EOPProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-eopprotectionpolicyrule +schema: 2.0.0 +title: Remove-EOPProtectionPolicyRule --- # Remove-EOPProtectionPolicyRule @@ -46,6 +47,9 @@ This example removes the existing rule for EOP protections in the Standard prese ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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/exchange/Remove-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md index 07f4762142..223a071c0b 100644 --- a/exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ecpvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-EcpVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ecpvirtualdirectory +schema: 2.0.0 +title: Remove-EcpVirtualDirectory --- # Remove-EcpVirtualDirectory @@ -45,6 +46,9 @@ This example removes the ECP virtual directory named ecp located on the default ## 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 remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -59,7 +63,6 @@ Remote removal of an ECP virtual directory isn't supported. You need run this co Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Remove-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-EdgeSubscription.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md index e792a7e0b9..83423a19d8 100644 --- a/exchange/exchange-ps/exchange/Remove-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-edgesubscription applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-EdgeSubscription -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-edgesubscription +schema: 2.0.0 +title: Remove-EdgeSubscription --- # Remove-EdgeSubscription @@ -51,13 +52,15 @@ This example removes Edge Subscription for the Edge Transport server named Edge1 ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the Edge Transport server for which you want to remove Edge Subscription. The identity is expressed as the host name of the Edge Transport server. ```yaml Type: TransportServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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. @@ -94,7 +102,6 @@ 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,6 +111,9 @@ 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. If you don't use this switch, the command will inform you that the removal of the replicated recipient data from AD LDS can take a long time and will give you the option to cancel the operation. @@ -112,7 +122,6 @@ If you don't use this switch, the command will inform you that the removal of th Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -122,13 +131,15 @@ 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/exchange/Remove-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md index 8389a40fd5..18af557dd5 100644 --- a/exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-emailaddresspolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-EmailAddressPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-emailaddresspolicy +schema: 2.0.0 +title: Remove-EmailAddressPolicy --- # Remove-EmailAddressPolicy @@ -43,6 +44,9 @@ This example removes the email address policy named Southwest Executives. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the email address policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the email address policy that you want to remov Type: EmailAddressPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md index e6a35f7f1c..c2e3d4daec 100644 --- a/exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-exchangecertificate applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ExchangeCertificate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-exchangecertificate +schema: 2.0.0 +title: Remove-ExchangeCertificate --- # Remove-ExchangeCertificate @@ -67,6 +68,9 @@ This example uses the same settings, but removes the certificate from the server ## 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 remove. 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. @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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 remove. Valid values are: - `ServerNameOrFQDN\Thumbprint` @@ -100,7 +106,6 @@ 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 @@ -110,6 +115,9 @@ 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`. @@ -119,7 +127,6 @@ 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 @@ -129,6 +136,9 @@ 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. @@ -137,7 +147,6 @@ 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 @@ -147,6 +156,9 @@ 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 @@ -162,7 +174,6 @@ 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 @@ -172,13 +183,15 @@ 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/exchange/Remove-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md index d6d761dd66..1775b0617f 100644 --- a/exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-exophishsimoverriderule applicable: Exchange Online -title: Remove-ExoPhishSimOverrideRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-exophishsimoverriderule +schema: 2.0.0 +title: Remove-ExoPhishSimOverrideRule --- # Remove-ExoPhishSimOverrideRule @@ -50,6 +51,9 @@ This example removes the specified phishing simulation override rule. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the phishing simulation override rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -63,7 +67,6 @@ Use the Get-ExoPhishSimOverrideRule cmdlet to find the values. The rule name syn Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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,13 +97,15 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Remove-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md index 4b7747e02b..c360b14ce6 100644 --- a/exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-exosecopsoverriderule applicable: Exchange Online -title: Remove-ExoSecOpsOverrideRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-exosecopsoverriderule +schema: 2.0.0 +title: Remove-ExoSecOpsOverrideRule --- # Remove-ExoSecOpsOverrideRule @@ -50,6 +51,9 @@ This example removes the specified SecOps mailbox override rule. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the SecOps override rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -63,7 +67,6 @@ Use the Get-ExoSecOpsMailboxRule cmdlet to find these values. The name of the ru Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -73,13 +76,15 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/Remove-FeatureConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FeatureConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FeatureConfiguration.md index d6b0f82b35..c8f19b3b14 100644 --- a/exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FeatureConfiguration.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-featureconfiguration -applicable: Security & Compliance -title: Remove-FeatureConfiguration schema: 2.0.0 +title: Remove-FeatureConfiguration --- # Remove-FeatureConfiguration @@ -45,6 +47,9 @@ This example removes the specified feature configuration. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity policy specifies the feature configuration that you want to remove. You can use any value that uniquely identifies the configuration. For example: - Name @@ -55,7 +60,6 @@ The Identity policy specifies the feature configuration that you want to remove. Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -65,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -84,13 +90,15 @@ 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/exchange/Remove-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-FederatedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md index c0cbc63696..ccac9d0e60 100644 --- a/exchange/exchange-ps/exchange/Remove-FederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-federateddomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-FederatedDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-federateddomain +schema: 2.0.0 +title: Remove-FederatedDomain --- # Remove-FederatedDomain @@ -50,13 +51,15 @@ This example removes the federated domain contoso.co.uk from the federated organ ## 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 @@ -66,13 +69,15 @@ Accept wildcard characters: False ``` ### -DomainName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DomainName parameter specifies the federated domain name to be removed from the federated organization identifier. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,13 +108,15 @@ 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 @@ -117,6 +126,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Force switch specifies whether to suppress warning or confirmation messages when removing a federated domain. You don't need to specify a value with this switch. You can use this switch when the removal of the federated domain from the cloud fails, but the configuration of this domain as a federated domain in Exchange should be removed regardless. @@ -125,7 +137,6 @@ You can use this switch when the removal of the federated domain from the cloud Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -135,13 +146,15 @@ 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/exchange/Remove-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-FederationTrust.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md index 86132d007a..c819ee6890 100644 --- a/exchange/exchange-ps/exchange/Remove-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-federationtrust applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-FederationTrust -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-federationtrust +schema: 2.0.0 +title: Remove-FederationTrust --- # Remove-FederationTrust @@ -45,13 +46,15 @@ This example removes the federation trust Microsoft Federation Gateway. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the federation trust being removed. ```yaml Type: FederationTrustIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertyAuthority.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyAuthority.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyAuthority.md index 6de6ae8679..455e4fd253 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyAuthority.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertyauthority -applicable: Security & Compliance -title: Remove-FilePlanPropertyAuthority schema: 2.0.0 +title: Remove-FilePlanPropertyAuthority --- # Remove-FilePlanPropertyAuthority @@ -40,6 +42,9 @@ This example removes the custom file plan property authority named Contoso Autho ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property authority that you want to remove. You can use any value that uniquely identifies the authority. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property authority that yo Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property authority. 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertyCategory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCategory.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCategory.md index e5e7d1c7fa..1ce0f2a592 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertycategory -applicable: Security & Compliance -title: Remove-FilePlanPropertyCategory schema: 2.0.0 +title: Remove-FilePlanPropertyCategory --- # Remove-FilePlanPropertyCategory @@ -40,6 +42,9 @@ This example removes the custom file plan property category named Contoso Catego ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property category that you want to remove. You can use any value that uniquely identifies the category. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property category that you Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property category. 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertyCitation.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCitation.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCitation.md index 70c1f29a20..a5cfe9c2b1 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyCitation.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertycitation -applicable: Security & Compliance -title: Remove-FilePlanPropertyCitation schema: 2.0.0 +title: Remove-FilePlanPropertyCitation --- # Remove-FilePlanPropertyCitation @@ -40,6 +42,9 @@ This example removes the custom file plan property citation named Contoso Citati ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property citation that you want to remove. You can use any value that uniquely identifies the citation. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property citation that you Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property citation. 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertyDepartment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyDepartment.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyDepartment.md index 630bbe64a4..2dc26d1278 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyDepartment.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertydepartment -applicable: Security & Compliance -title: Remove-FilePlanPropertyDepartment schema: 2.0.0 +title: Remove-FilePlanPropertyDepartment --- # Remove-FilePlanPropertyDepartment @@ -40,6 +42,9 @@ This example removes the custom file plan property department named Contoso HR. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property department that you want to remove. You can use any value that uniquely identifies the department. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property department that y Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property department. 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyReferenceId.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyReferenceId.md index 7548cc4cf3..e550f7042e 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertyReferenceId.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertyreferenceid -applicable: Security & Compliance -title: Remove-FilePlanPropertyReferenceId schema: 2.0.0 +title: Remove-FilePlanPropertyReferenceId --- # Remove-FilePlanPropertyReferenceId @@ -40,6 +42,9 @@ This example removes the custom file plan property reference ID named Contoso-00 ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property reference ID that you want to remove. You can use any value that uniquely identifies the reference ID. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property reference ID that Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property reference ID. 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,13 +103,15 @@ 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/exchange/Remove-FilePlanPropertySubCategory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertySubCategory.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertySubCategory.md index 5e45a1faf5..37de0684a6 100644 --- a/exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FilePlanPropertySubCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/remove-fileplanpropertysubcategory -applicable: Security & Compliance -title: Remove-FilePlanPropertySubCategory schema: 2.0.0 +title: Remove-FilePlanPropertySubCategory --- # Remove-FilePlanPropertySubCategory @@ -40,6 +42,9 @@ This example removes the custom file plan property subcategory named US Tax. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property subcategory that you want to movidy. You can use any value that uniquely identifies the subcategory. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property subcategory that Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the file plan property subcategory. 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,13 +103,15 @@ 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/exchange/Remove-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ForeignConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md index d43ea4b717..fd23b0fcaf 100644 --- a/exchange/exchange-ps/exchange/Remove-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-foreignconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ForeignConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-foreignconnector +schema: 2.0.0 +title: Remove-ForeignConnector --- # Remove-ForeignConnector @@ -47,13 +48,15 @@ This example deletes the Foreign connector named Fax Connector. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the GUID or connector name of a specific Foreign connector. You can also include the server name by using the format ServerName\\ConnectorName. ```yaml Type: ForeignConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-GlobalAddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md index 2307a60bef..de0d258249 100644 --- a/exchange/exchange-ps/exchange/Remove-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-globaladdresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-GlobalAddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-globaladdresslist +schema: 2.0.0 +title: Remove-GlobalAddressList --- # Remove-GlobalAddressList @@ -45,6 +46,9 @@ This example removes the GAL named OldGAL. ## 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 remove. You can use any value that uniquely identifies the GAL. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the global address list that you want to remove Type: GlobalAddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md index 6bdf488dfa..5f8c0c1a2b 100644 --- a/exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-globalmonitoringoverride applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-GlobalMonitoringOverride -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-globalmonitoringoverride +schema: 2.0.0 +title: Remove-GlobalMonitoringOverride --- # Remove-GlobalMonitoringOverride @@ -52,13 +53,15 @@ This example removes a global monitoring override of the ExtensionAttributes pro ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the monitoring item that was overridden. The value is in the form of HealthSet\\MonitoringItem or HealthSet\\MonitoringItem\\TargetResource. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ Accept wildcard characters: False ``` ### -ItemType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ItemType parameter specifies the item type that you want to remove. It can be any of the following values: - Probe @@ -78,7 +84,6 @@ The ItemType parameter specifies the item type that you want to remove. It can b Type: MonitoringItemTypeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -88,13 +93,15 @@ Accept wildcard characters: False ``` ### -PropertyName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PropertyName parameter specifies the property for the override you want to remove. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -104,13 +111,15 @@ 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: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,6 +129,9 @@ 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`. @@ -129,7 +141,6 @@ 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 @@ -139,6 +150,9 @@ 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. @@ -147,7 +161,6 @@ 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 @@ -157,13 +170,15 @@ 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 @@ -173,13 +188,15 @@ 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/exchange/Remove-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md index f4e942a974..9d5a10b0ad 100644 --- a/exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-holdcompliancepolicy applicable: Security & Compliance -title: Remove-HoldCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-holdcompliancepolicy +schema: 2.0.0 +title: Remove-HoldCompliancePolicy --- # Remove-HoldCompliancePolicy @@ -47,6 +48,9 @@ This example removes the preservation policy named "Regulation 123 Compliance". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the preservation policy to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the preservation policy to remove. You can use Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md index 5b0fea9c47..5e03e66eb9 100644 --- a/exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-holdcompliancerule applicable: Security & Compliance -title: Remove-HoldComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-holdcompliancerule +schema: 2.0.0 +title: Remove-HoldComplianceRule --- # Remove-HoldComplianceRule @@ -47,6 +48,9 @@ This example removes the preservation rule named "One Year Standard". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the preservation rule to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the preservation rule to remove. You can use an Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the rule. 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md index b94bb23bff..6be99f973b 100644 --- a/exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedcontentfilterpolicy applicable: Exchange Online, Exchange Online Protection -title: Remove-HostedContentFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedcontentfilterpolicy +schema: 2.0.0 +title: Remove-HostedContentFilterPolicy --- # Remove-HostedContentFilterPolicy @@ -44,6 +45,9 @@ This example removes the spam filter policy named Contoso Content Filter Policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the spam filter policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the spam filter policy that you want to remove. Type: HostedContentFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Remove-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md index 473b44deb4..791b82185b 100644 --- a/exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedcontentfilterrule applicable: Exchange Online, Exchange Online Protection -title: Remove-HostedContentFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedcontentfilterrule +schema: 2.0.0 +title: Remove-HostedContentFilterRule --- # Remove-HostedContentFilterRule @@ -42,6 +43,9 @@ This example removes the 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 remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the spam filter rule that you want to remove. Y Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md index 20e3e3eb7f..3f66f6de2c 100644 --- a/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedoutboundspamfilterpolicy applicable: Exchange Online, Exchange Online Protection -title: Remove-HostedOutboundSpamFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedoutboundspamfilterpolicy +schema: 2.0.0 +title: Remove-HostedOutboundSpamFilterPolicy --- # Remove-HostedOutboundSpamFilterPolicy @@ -43,6 +44,9 @@ This example removes the outbound spam filter policy named Contoso Executives. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the outbound spam filter policy you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the outbound spam filter policy you want to rem Type: HostedOutboundSpamFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -63,6 +66,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -71,7 +77,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md index cc89753dc3..da32ee8776 100644 --- a/exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedoutboundspamfilterrule applicable: Exchange Online, Exchange Online Protection -title: Remove-HostedOutboundSpamFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-hostedoutboundspamfilterrule +schema: 2.0.0 +title: Remove-HostedOutboundSpamFilterRule --- # Remove-HostedOutboundSpamFilterRule @@ -42,6 +43,9 @@ This example removes the outbound spam filter rule named Contoso Executives. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the outbound spam filter rule that you want to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-HybridConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md index ed6b8d990c..8ccc607ff7 100644 --- a/exchange/exchange-ps/exchange/Remove-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-hybridconfiguration applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-HybridConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-hybridconfiguration +schema: 2.0.0 +title: Remove-HybridConfiguration --- # Remove-HybridConfiguration @@ -44,6 +45,9 @@ This example removes the HybridConfiguration object for the hybrid deployment. ## PARAMETERS ### -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`. @@ -53,7 +57,6 @@ 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 @@ -63,6 +66,9 @@ 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. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md index 07022d05d8..315371856f 100644 --- a/exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipallowlistentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-IPAllowListEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipallowlistentry +schema: 2.0.0 +title: Remove-IPAllowListEntry --- # Remove-IPAllowListEntry @@ -50,13 +51,15 @@ This example removes the IP address range 192.168.0.0/24 from the IP Allow list. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the integer value of the IP Allow list entry that you want to remove. When you add an entry to the IP Allow list, the Identity value is automatically assigned. To find the Identity value of an IP Allow list entry, use the Get-IPAllowListEntry cmdlet. ```yaml Type: IPListEntryIdentity Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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 @@ -100,7 +108,6 @@ 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 @@ -110,13 +117,15 @@ 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/exchange/Remove-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md index 530652a8e2..d2afccf56c 100644 --- a/exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipallowlistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-IPAllowListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipallowlistprovider +schema: 2.0.0 +title: Remove-IPAllowListProvider --- # Remove-IPAllowListProvider @@ -43,6 +44,9 @@ This example removes the IP Allow list provider named Contoso.com. ## 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 remove. You can use any value that uniquely identifies the IP Allow list provider. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the IP Allow list provider that you want to rem Type: IPAllowListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md index 81f9179a23..9b3d6c977d 100644 --- a/exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipblocklistentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-IPBlockListEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipblocklistentry +schema: 2.0.0 +title: Remove-IPBlockListEntry --- # Remove-IPBlocklistEntry @@ -50,13 +51,15 @@ This example removes the IP address range 192.168.0.0/24 from the IP Block list. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the integer value of the IP Block list entry that you want to remove. When you add an entry to the IP Block list, the Identity value is automatically assigned. To find the Identity value of an IP Block list entry, use the Get-IPBlockListEntry cmdlet. ```yaml Type: IPListEntryIdentity Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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 @@ -100,7 +108,6 @@ You can't use this command 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 @@ -110,13 +117,15 @@ 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/exchange/Remove-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md index 27e5a41a87..ec85e6e507 100644 --- a/exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipblocklistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-IPBlockListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ipblocklistprovider +schema: 2.0.0 +title: Remove-IPBlockListProvider --- # Remove-IPBlockListProvider @@ -43,6 +44,9 @@ This example removes the IP Block list provider named Contoso.com. ## 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 remove. You can use any value that uniquely identifies the IP Block list provider. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the IP Block list provider that you want to rem Type: IPBlockListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-InboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md index 643afa3df0..8b8c53d141 100644 --- a/exchange/exchange-ps/exchange/Remove-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-inboundconnector applicable: Exchange Online, Exchange Online Protection -title: Remove-InboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-inboundconnector +schema: 2.0.0 +title: Remove-InboundConnector --- # Remove-InboundConnector @@ -44,13 +45,15 @@ This example deletes the Inbound connector named Contoso Inbound Connector. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the Inbound connector you want to remove. ```yaml Type: InboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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/exchange/Remove-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Remove-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md index 78a9af6e7b..9ba47a81e6 100644 --- a/exchange/exchange-ps/exchange/Remove-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-inboxrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-InboxRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-inboxrule +schema: 2.0.0 +title: Remove-InboxRule --- # Remove-InboxRule @@ -55,6 +56,9 @@ This example removes all Inbox rules from the mailbox Joe@Contoso.com. ## 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 remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -66,7 +70,6 @@ The Identity parameter specifies the Inbox rule that you want to remove. 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 @@ -76,13 +79,15 @@ 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 @@ -92,6 +97,9 @@ 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`. @@ -101,7 +109,6 @@ 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,6 +118,9 @@ 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,7 +129,6 @@ 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 @@ -129,6 +138,9 @@ 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. @@ -137,7 +149,6 @@ 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 @@ -147,6 +158,9 @@ 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 @@ -164,7 +178,6 @@ 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 @@ -174,13 +187,15 @@ 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/exchange/Remove-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InformationBarrierPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-InformationBarrierPolicy.md index daac4a22b1..2cd5f18558 100644 --- a/exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InformationBarrierPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-informationbarrierpolicy applicable: Security & Compliance -title: Remove-InformationBarrierPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-informationbarrierpolicy +schema: 2.0.0 +title: Remove-InformationBarrierPolicy --- # Remove-InformationBarrierPolicy @@ -45,6 +46,9 @@ This example removes the information barrier policy named HR-Sales. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the information barrier policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the information barrier policy that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -65,6 +68,9 @@ 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,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the information barrier policy. 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md index 6f4cb23daa..3673d5874a 100644 --- a/exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-intraorganizationconnector applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-IntraOrganizationConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-intraorganizationconnector +schema: 2.0.0 +title: Remove-IntraOrganizationConnector --- # Remove-IntraOrganizationConnector @@ -47,6 +48,9 @@ This example removes the existing Intra-Organization connector named "Contoso On ## 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 remove. You can use any value that uniquely identifies the connector. For example: - Name @@ -57,7 +61,6 @@ 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: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Remove-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md index da555a20f0..7f24293c06 100644 --- a/exchange/exchange-ps/exchange/Remove-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-journalrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-JournalRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-journalrule +schema: 2.0.0 +title: Remove-JournalRule --- # Remove-JournalRule @@ -45,13 +46,15 @@ This example removes the journal rule Brokerage Communications that's no longer ## 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 remove. Enter either 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: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-Label.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Label.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-Label.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-Label.md index 7b1812a00e..c060dcd219 100644 --- a/exchange/exchange-ps/exchange/Remove-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Label.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-label applicable: Security & Compliance -title: Remove-Label -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-label +schema: 2.0.0 +title: Remove-Label --- # Remove-Label @@ -42,6 +43,9 @@ This example removes the sensitivity label named Marketing Group. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the sensitivity label that you want to remove. You can use any value that uniquely identifies the label. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the sensitivity label that you want to remove. Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Security & Compliance + The WhatIf switch causes the command to simulate its results. By using this switch, you can view what changes would occur without having to commit those changes. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-LabelPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-LabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-LabelPolicy.md index 2289247216..da5a898604 100644 --- a/exchange/exchange-ps/exchange/Remove-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-LabelPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-labelpolicy applicable: Security & Compliance -title: Remove-LabelPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-labelpolicy +schema: 2.0.0 +title: Remove-LabelPolicy --- # Remove-LabelPolicy @@ -42,6 +43,9 @@ This example removes the policy named Marketing Group. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the policy that you want to remove. You can use Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md similarity index 88% rename from exchange/exchange-ps/exchange/Remove-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md index 8a14dbb711..0da976b23c 100644 --- a/exchange/exchange-ps/exchange/Remove-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailcontact applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-MailContact -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailcontact +schema: 2.0.0 +title: Remove-MailContact --- # Remove-MailContact @@ -44,6 +45,9 @@ This example removes the mail contact named John. ## 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 remove. You can use any value that uniquely identifies the mail contact. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the mail contact that you want to remove. You c Type: MailContactIdParameter 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 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Remove-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md index 022d16da1d..427012c234 100644 --- a/exchange/exchange-ps/exchange/Remove-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailuser applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-MailUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailuser +schema: 2.0.0 +title: Remove-MailUser --- # Remove-MailUser @@ -46,6 +47,9 @@ This example removes the mail user named Ed Meadows. ## 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 remove. You can use any value that uniquely identifies the mail user. For example: - Name @@ -59,7 +63,6 @@ The Identity parameter specifies the mail user that you want to remove. You can Type: MailUserIdParameter 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 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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,7 +104,6 @@ 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 @@ -106,6 +113,9 @@ 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. @@ -119,7 +129,6 @@ 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 @@ -129,6 +138,9 @@ 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. @@ -141,7 +153,6 @@ 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 @@ -151,6 +162,9 @@ Accept wildcard characters: False ``` ### -PermanentlyDelete + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PermanentlyDelete switch immediately and permanently deletes (purges) the mail user, which prevents you from recovering or restoring the mail user. You don't need to specify a value with this switch. @@ -164,7 +178,6 @@ The PermanentlyDelete switch immediately and permanently deletes (purges) the ma Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -174,13 +187,15 @@ 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/exchange/Remove-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md index 27447b1e7a..635e59bb67 100644 --- a/exchange/exchange-ps/exchange/Remove-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-Mailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailbox +schema: 2.0.0 +title: Remove-Mailbox --- # Remove-Mailbox @@ -117,6 +118,9 @@ In Exchange Online, this example removes the specified soft-deleted mailbox. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter identifies the mailbox that you want to remove. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -136,7 +140,6 @@ You can't use this parameter with the Database parameter. Type: MailboxIdParameter Parameter Sets: Identity, Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -146,6 +149,9 @@ 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 mailbox that you want to remove. You can use any value that uniquely identifies the database. For example: @@ -162,7 +168,6 @@ If you've disconnected a mailbox from its associated user and want to remove the Type: DatabaseIdParameter Parameter Sets: StoreMailboxIdentity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -172,6 +177,9 @@ Accept wildcard characters: False ``` ### -StoreMailboxIdentity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The StoreMailboxIdentity parameter specifies the mailbox that you want to remove. When you use this parameter, you identify the mailbox by its MailboxGUID value. You can find the GUID value by using the Get-Mailbox or Get-MailboxStatistics cmdlets. @@ -184,7 +192,6 @@ If you've disconnected a mailbox from its associated user and want to remove the Type: StoreMailboxIdParameter Parameter Sets: StoreMailboxIdentity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -194,6 +201,9 @@ 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 remove arbitration mailboxes. You don't need to specify a value with this switch. @@ -206,7 +216,6 @@ To remove arbitration mailboxes that are used to store audit log settings or dat Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -216,6 +225,9 @@ 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 remove audit log mailboxes. You don't need to specify a value with this switch. @@ -228,7 +240,6 @@ To remove other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,6 +249,9 @@ 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 remove auxiliary audit log mailboxes. You don't need to specify a value with this switch. @@ -250,7 +264,6 @@ To remove other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,6 +273,9 @@ 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`. @@ -269,7 +285,6 @@ 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 @@ -279,6 +294,9 @@ 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,7 +305,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,6 +314,9 @@ 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. @@ -305,7 +325,6 @@ 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 @@ -315,6 +334,9 @@ 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. @@ -328,7 +350,6 @@ This switch enables the command to access Active Directory objects that aren't c Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -338,6 +359,9 @@ 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. @@ -350,7 +374,6 @@ After you disable or remove a mailbox, you can't include it in a discovery searc Type: SwitchParameter Parameter Sets: Identity, StoreMailboxIdentity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -360,13 +383,15 @@ Accept wildcard characters: False ``` ### -Migration + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Migration switch is required to remove migration mailboxes. 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 @@ -376,6 +401,9 @@ Accept wildcard characters: False ``` ### -Permanent + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Permanent parameter specifies whether to permanently delete the mailbox from the mailbox database. Valid values are: @@ -387,7 +415,6 @@ The Permanent parameter specifies whether to permanently delete the mailbox from Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -397,6 +424,9 @@ Accept wildcard characters: False ``` ### -PermanentlyDelete + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PermanentlyDelete switch immediately and permanently deletes (purges) the mailbox, which prevents you from recovering or restoring the mailbox. You don't need to specify a value with this switch. @@ -410,7 +440,6 @@ The PermanentlyDelete switch immediately and permanently deletes (purges) the ma Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -420,6 +449,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolder switch is required to remove public folder mailboxes. 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. @@ -428,7 +460,6 @@ 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 @@ -438,6 +469,9 @@ Accept wildcard characters: False ``` ### -RemoveArbitrationMailboxWithOABsAllowed + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveArbitrationMailboxWithOABsAllowed switch specifies whether to bypass the checks for offline address books (OABs) within the specified arbitration mailbox that is being removed. You don't need to specify a value with this switch. @@ -448,7 +482,6 @@ When you use this switch, the arbitration mailbox is removed even if OABs are pr Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -458,6 +491,9 @@ Accept wildcard characters: False ``` ### -RemoveCNFPublicFolderMailboxPermanently + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RemoveCNFPublicFolderMailboxPermanently Description }} @@ -466,7 +502,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -476,6 +511,9 @@ Accept wildcard characters: False ``` ### -RemoveLastArbitrationMailboxAllowed + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveLastArbitrationMailboxAllowed switch specifies whether to remove the specified mailbox, even if it's the last arbitration mailbox in the organization. You don't need to specify a value with this switch. @@ -486,7 +524,6 @@ If you remove the last arbitration mailbox in the organization, you can't have u Type: SwitchParameter Parameter Sets: StoreMailboxIdentity, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -496,6 +533,9 @@ 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. @@ -504,7 +544,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Identity, StoreMailboxIdentity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -514,13 +553,15 @@ 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/exchange/Remove-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md index 3e424e0421..39680fc175 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxdatabase applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MailboxDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxdatabase +schema: 2.0.0 +title: Remove-MailboxDatabase --- # Remove-MailboxDatabase @@ -47,6 +48,9 @@ This example removes the mailbox database MailboxDatabase01. ## 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 remove. You can use any value that uniquely identifies the database. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the mailbox database that you want to remove. Y Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md index 6fd45481ac..f33c89eef1 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxdatabasecopy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MailboxDatabaseCopy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxdatabasecopy +schema: 2.0.0 +title: Remove-MailboxDatabaseCopy --- # Remove-MailboxDatabaseCopy @@ -52,13 +53,15 @@ This example removes a copy of mailbox database DB1 from the Mailbox server MBX3 ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the mailbox database whose copy is being removed. When using this parameter, specify a format of DatabaseName\\ServerName. ```yaml Type: DatabaseCopyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ 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,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,13 +110,15 @@ 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/exchange/Remove-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md index 6f850b68be..b4afc8fab5 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxexportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MailboxExportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxexportrequest +schema: 2.0.0 +title: Remove-MailboxExportRequest --- # Remove-MailboxExportRequest @@ -76,6 +77,9 @@ This example cancels the export request by using the RequestGuid parameter for a ## 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). Use the following syntax: `Alias\Name`. You can't use this parameter with the RequestGuid parameter. @@ -84,7 +88,6 @@ You can't use this parameter with the RequestGuid parameter. Type: MailboxExportRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -94,13 +97,15 @@ 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: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -110,6 +115,9 @@ Accept wildcard characters: False ``` ### -RequestQueue + +> Applicable: Exchange Server 2010, 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 @@ -122,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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,7 +151,6 @@ 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 @@ -151,13 +160,15 @@ 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,6 +178,9 @@ 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. @@ -175,7 +189,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -185,13 +198,15 @@ 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/exchange/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md index 3dccb1d13c..c6582b3cd2 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxFolderPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission +schema: 2.0.0 +title: Remove-MailboxFolderPermission --- # Remove-MailboxFolderPermission @@ -73,6 +74,9 @@ This example will clear any corrupted delegate information from Kim's mailbox. ## 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 `Mailbox:\Folder`. For the value of Mailbox, you can use any value that uniquely identifies the mailbox. For example: - Name @@ -92,7 +96,6 @@ Example values for the Identity parameter are `john@contoso.com:\Calendar` or `J 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 @@ -102,6 +105,9 @@ 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 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: @@ -122,7 +128,6 @@ Otherwise, you can use any value that uniquely identifies the user or group. For Type: MailboxFolderUserIdParameter Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -132,6 +137,9 @@ 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`. @@ -141,7 +149,6 @@ 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 @@ -151,6 +158,9 @@ 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. @@ -159,7 +169,6 @@ 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 @@ -169,6 +178,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online + 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. @@ -179,7 +191,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity, ResetDelegateUserCollection Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -189,6 +200,9 @@ Accept wildcard characters: False ``` ### -ResetDelegateUserCollection + +> Applicable: Exchange Server 2019, Exchange Online + The ResetDelegateUserCollection switch forces the removal of the LocalFreeBusy or the PR_FREEBUSY_ENTRYIDs files in case of corruption. You don't need to specify a value with this switch. Use this switch if you encounter problems trying add, change, or remove delegate permissions. Using this switch deletes those files and downgrades any existing delegates to Editor permissions. You'll need to grant delegate permissions again using `-SharingPermissionFlag Delegate`. @@ -199,7 +213,6 @@ When you use this switch, the value of Identity should be the user's primary cal Type: SwitchParameter Parameter Sets: ResetDelegateUserCollection Aliases: -Applicable: Exchange Server 2019, Exchange Online Required: False Position: Named @@ -209,6 +222,9 @@ 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 notification to the user when you remove their calendar permissions. Valid values are: @@ -222,7 +238,6 @@ This parameter only applies to calendar folders. Type: Boolean Parameter Sets: Identity, ResetDelegateUserCollection Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -232,13 +247,15 @@ 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/exchange/Remove-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md similarity index 97% rename from exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md index 688966ba55..1bc24ca8cf 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxirmaccess applicable: Exchange Online -title: Remove-MailboxIRMAccess -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxirmaccess +schema: 2.0.0 +title: Remove-MailboxIRMAccess --- # Remove-MailboxIRMAccess @@ -43,6 +44,9 @@ This example removes the restriction from IRM-protected messages in Lynette's ma ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example - Name @@ -60,7 +64,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Online + **Note**: Delegates that you specify with this parameter must already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-recipients). The User parameter specifies the delegate who is no longer blocked from reading IRM-protected messages in the mailbox. The delegate must be a user mailbox or a mail user. You can use any value that uniquely identifies the delegate. For example: @@ -89,7 +95,6 @@ The User parameter specifies the delegate who is no longer blocked from reading Type: SecurityPrincipalIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md index e4a36d24de..db3d8a3342 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboximportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxImportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboximportrequest +schema: 2.0.0 +title: Remove-MailboxImportRequest --- # Remove-MailboxImportRequest @@ -78,6 +79,9 @@ This example removes all completed import requests. ## 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 created the request using the Name parameter, use the following syntax: `Alias\Name`. You can't use this parameter with the RequestGuid parameter. @@ -86,7 +90,6 @@ You can't use this parameter with the RequestGuid parameter. Type: MailboxImportRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -96,6 +99,9 @@ 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. @@ -106,7 +112,6 @@ You can't use this parameter with the Identity parameter. Type: Guid Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -116,6 +121,9 @@ 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. 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: @@ -130,7 +138,6 @@ 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 @@ -140,6 +147,9 @@ 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`. @@ -149,7 +159,6 @@ 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 @@ -159,6 +168,9 @@ 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. @@ -167,7 +179,6 @@ 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 @@ -177,6 +188,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -185,7 +199,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -195,13 +208,15 @@ 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/exchange/Remove-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md similarity index 85% rename from exchange/exchange-ps/exchange/Remove-MailboxPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md index b6e76be563..8671a91f7b 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxpermission applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxpermission +schema: 2.0.0 +title: Remove-MailboxPermission --- # Remove-MailboxPermission @@ -107,6 +108,9 @@ In Exchange Online, this example excludes the HR Project mailbox from auto-mappi ## 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 removing permissions. You can use any value that uniquely identifies the mailbox: For example: - Name @@ -124,7 +128,6 @@ The Identity parameter specifies the mailbox where you are removing permissions. Type: MailboxIdParameter Parameter Sets: AccessRights, Owner, ClearAutoMapping, ResetDefault Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -134,6 +137,9 @@ 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 permission that you want to remove from the user on the mailbox. Valid values are: - FullAccess @@ -148,9 +154,8 @@ You can specify multiple values separated by commas. ```yaml Type: MailboxRights[] -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -159,33 +164,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MailboxRights[] -Parameter Sets: Instance -Aliases: -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 -``` - -```yaml -Type: MailboxIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Instance -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Instance This parameter is available only in on-premises Exchange. 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. @@ -194,7 +176,6 @@ The Instance parameter enables you to pass an entire object to the command to be Type: MailboxAcePresentationObject Parameter Sets: Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -204,6 +185,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The User parameter specifies whose permissions are being removed from the specified mailbox. You can specify the following types of users or groups (security principals) for this parameter: - Mailbox users @@ -230,9 +214,8 @@ Otherwise, you can use any value that uniquely identifies the user or group. For ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: AccessRights +Parameter Sets: AccessRights, Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -241,20 +224,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -ClearAutoMapping -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -### -ClearAutoMapping This parameter is functional only in the cloud-based service. The ClearAutoMapping parameter excludes the mailbox from the auto-mapping feature in Microsoft Outlook. You don't need to specify a value with this switch. @@ -269,7 +242,6 @@ You can't use this switch with the User or AccessRights parameters. Type: SwitchParameter Parameter Sets: ClearAutoMapping Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -279,6 +251,9 @@ Accept wildcard characters: False ``` ### -ResetDefault + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The ResetDefault switch resets the default security descriptor of the mailbox. You don't need to specify a value with this switch. @@ -297,7 +272,6 @@ You can't use this switch with the User for AccessRights parameters. Type: SwitchParameter Parameter Sets: Instance Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -307,6 +281,9 @@ Accept wildcard characters: False ``` ### -BypassMasterAccountSid + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BypassMasterAccountSid switch suppresses the following error: `Can't remove the access control entry on the object "User" for the user account because the ACE doesn't exist on the object.` You don't need to specify a value with this switch. @@ -317,7 +294,6 @@ Typically, you only need to use this switch in Office 365 Dedicated or ITAR lega Type: SwitchParameter Parameter Sets: AccessRights, Owner, ClearAutoMapping Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -327,6 +303,9 @@ 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`. @@ -336,7 +315,6 @@ 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 @@ -346,13 +324,15 @@ 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 removing 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 @@ -362,6 +342,9 @@ 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. @@ -370,7 +353,6 @@ 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 @@ -380,6 +362,9 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The GroupMailbox switch is required to remove permissions from a Microsoft 365 Group mailbox. You don't need to specify a value with this switch. @@ -388,7 +373,6 @@ The GroupMailbox switch is required to remove permissions from a Microsoft 365 G Type: SwitchParameter Parameter Sets: AccessRights, Owner, Instance Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -398,6 +382,9 @@ 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: @@ -409,7 +396,6 @@ 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 @@ -419,6 +405,9 @@ Accept wildcard characters: False ``` ### -InheritanceType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InheritanceType parameter specifies whether permissions are inherited to folders within the mailbox. Valid values are: - None @@ -431,7 +420,6 @@ The InheritanceType parameter specifies whether permissions are inherited to fol 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 @@ -441,6 +429,9 @@ Accept wildcard characters: False ``` ### -SoftDeletedMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SoftDeletedMailbox switch is required to remove permissions from a soft-deleted mailbox. You don't need to specify a value with this switch. @@ -451,7 +442,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: AccessRights Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -461,13 +451,15 @@ 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/exchange/Remove-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-MailboxRepairRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md index c9037afa2f..effbe16ccd 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxRepairRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxrepairrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MailboxRepairRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxrepairrequest +schema: 2.0.0 +title: Remove-MailboxRepairRequest --- # Remove-MailboxRepairRequest @@ -63,13 +64,15 @@ This example deletes a specific mailbox repair request by specifying the unique ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox repair request to remove. 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`. Use the Get-MailboxRepairRequest cmdlet to find the identity of a mailbox repair request. ```yaml Type: StoreIntegrityCheckJobIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -79,6 +82,9 @@ 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`. @@ -88,7 +94,6 @@ 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 @@ -98,13 +103,15 @@ 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 @@ -114,13 +121,15 @@ 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/exchange/Remove-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md index 96cc00e783..c8de9a96cf 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxrestorerequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxRestoreRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxrestorerequest +schema: 2.0.0 +title: Remove-MailboxRestoreRequest --- # Remove-MailboxRestoreRequest @@ -72,6 +73,9 @@ This example cancels the restore request by using the RequestGuid parameter 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 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 a default name MailboxRestore. Exchange generates up to 10 names, starting with MailboxRestore and then MailboxRestoreX (where X = 1-9). @@ -80,7 +84,6 @@ If you didn't specify a name for the restore request when it was created, Exchan Type: MailboxRestoreRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -90,6 +93,9 @@ 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. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter. @@ -100,7 +106,6 @@ You can't use this parameter with the Identity parameter. Type: Guid Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -110,6 +115,9 @@ 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. The RequestQueue parameter specifies the target mailbox database on which the mailbox or archive of the request resides. You can use any value that uniquely identifies the database. For example: @@ -124,7 +132,6 @@ You must use this parameter with the RequestGuid parameter. You can't use this p Type: DatabaseIdParameter Parameter Sets: MigrationRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -134,6 +141,9 @@ 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`. @@ -143,7 +153,6 @@ 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 @@ -153,6 +162,9 @@ 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. @@ -161,7 +173,6 @@ 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 @@ -171,6 +182,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -179,7 +193,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -189,13 +202,15 @@ 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/exchange/Remove-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md index eca5f3db04..296a81e978 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxsearch +schema: 2.0.0 +title: Remove-MailboxSearch --- # Remove-MailboxSearch @@ -47,13 +48,15 @@ This example removes the mailbox search 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 mailbox search. ```yaml Type: SearchObjectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md index 723d1efc08..5975a843ab 100644 --- a/exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxuserconfiguration applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MailboxUserConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mailboxuserconfiguration +schema: 2.0.0 +title: Remove-MailboxUserConfiguration --- # Remove-MailboxUserConfiguration @@ -43,6 +44,9 @@ This example removes the specified user configuration item from the mailbox juli ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the user configuration item that you want to remove. 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. @@ -52,7 +56,6 @@ The Identity parameter specifies the user configuration item that you want to re Type: MailboxUserConfigurationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -62,6 +65,9 @@ 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 remove. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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. @@ -116,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ 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/exchange/Remove-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md index a5c3c84db4..8bbc2309ef 100644 --- a/exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-malwarefilterpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-MalwareFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-malwarefilterpolicy +schema: 2.0.0 +title: Remove-MalwareFilterPolicy --- # Remove-MalwareFilterPolicy @@ -46,13 +47,15 @@ This example removes the malware filter policy named Contoso Malware Filter Poli ## 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 you want to remove. 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: True Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,6 +86,9 @@ 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. @@ -89,7 +97,6 @@ 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,6 +106,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. @@ -109,7 +119,6 @@ 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 @@ -119,13 +128,15 @@ 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/exchange/Remove-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md index 4171ff3c01..9d7ea34104 100644 --- a/exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-malwarefilterrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-MalwareFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-malwarefilterrule +schema: 2.0.0 +title: Remove-MalwareFilterRule --- # Remove-MalwareFilterRule @@ -43,13 +44,15 @@ This example removes the 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 remove. 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 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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. @@ -86,7 +94,6 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Remove-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md index 3ec37d8684..cc9fe30c66 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedcontentsettings applicable: Exchange Server 2010 -title: Remove-ManagedContentSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedcontentsettings +schema: 2.0.0 +title: Remove-ManagedContentSettings --- # Remove-ManagedContentSettings @@ -45,13 +46,15 @@ This example deletes the managed content settings MyManagedContentSettings. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed content settings. ```yaml Type: ELCContentSettingsIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Remove-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ManagedFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md index 7b68957f99..55af6eccad 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfolder applicable: Exchange Server 2010 -title: Remove-ManagedFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfolder +schema: 2.0.0 +title: Remove-ManagedFolder --- # Remove-ManagedFolder @@ -45,13 +46,15 @@ This example removes the managed folder MyManagedFolder. ## 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: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Remove-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md index 4cd1f7a86c..1ea46129a2 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfoldermailboxpolicy applicable: Exchange Server 2010 -title: Remove-ManagedFolderMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managedfoldermailboxpolicy +schema: 2.0.0 +title: Remove-ManagedFolderMailboxPolicy --- # Remove-ManagedFolderMailboxPolicy @@ -46,13 +47,15 @@ This example removes the managed folder mailbox policy My Managed Folder Mailbox ## 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: True Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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 @@ -97,6 +104,9 @@ 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. This switch hides the confirmation prompt when the managed folder mailbox policy that's being removed is assigned to a mailbox user. @@ -105,7 +115,6 @@ This switch hides the confirmation prompt when the managed folder mailbox policy Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -115,13 +124,15 @@ 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/exchange/Remove-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-ManagementRole.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md index 60ed3913e0..18789756df 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagementRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementrole applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-ManagementRole -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementrole +schema: 2.0.0 +title: Remove-ManagementRole --- # Remove-ManagementRole @@ -73,13 +74,15 @@ For more information about unscoped top-level management roles, see [Understandi ## 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 custom role to remove. If the name of the role contains spaces, enclose the name in quotation marks ("). ```yaml Type: RoleIdParameter 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 @@ -89,6 +92,9 @@ 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`. @@ -98,7 +104,6 @@ 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 @@ -108,6 +113,9 @@ 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,7 +124,6 @@ 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 @@ -126,6 +133,9 @@ 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. @@ -136,7 +146,6 @@ 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 @@ -146,6 +155,9 @@ Accept wildcard characters: False ``` ### -Recurse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Recurse switch removes the specified role and all child roles of the specified role. You don't need to specify a value with this switch. We recommend that you test the command with the WhatIf switch to confirm that the results will be correct. @@ -154,7 +166,6 @@ We recommend that you test the command with the WhatIf switch to confirm that 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 @@ -164,6 +175,9 @@ 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). @@ -176,7 +190,6 @@ Unscoped top-level management roles can only contain custom scripts or non-Excha Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -186,13 +199,15 @@ 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/exchange/Remove-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md index 7540ec48ac..c21462879c 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementroleassignment applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-ManagementRoleAssignment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementroleassignment +schema: 2.0.0 +title: Remove-ManagementRoleAssignment --- # Remove-ManagementRoleAssignment @@ -55,13 +56,15 @@ After the list of role assignments to be removed is confirmed, remove the WhatIf ## 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 remove. If the role assignment name contains spaces, enclose the name in quotation marks ("). ```yaml Type: RoleAssignmentIdParameter 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,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,6 +115,9 @@ 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. @@ -118,7 +128,6 @@ 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 @@ -128,13 +137,15 @@ 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/exchange/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md index a6d8a1d54c..8f25d36f2e 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementroleentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-ManagementRoleEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementroleentry +schema: 2.0.0 +title: Remove-ManagementRoleEntry --- # Remove-ManagementRoleEntry @@ -59,6 +60,9 @@ This example forces you to acknowledge the command before proceeding (we didn'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 role entry that you want to remove. 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). @@ -69,7 +73,6 @@ 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 @@ -79,6 +82,9 @@ 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,7 +94,6 @@ 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 @@ -98,6 +103,9 @@ 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,7 +114,6 @@ 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,6 +123,9 @@ 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. @@ -126,7 +136,6 @@ 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 @@ -136,13 +145,15 @@ 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/exchange/Remove-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-ManagementScope.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md index ec73842594..4ea0bc7ef1 100644 --- a/exchange/exchange-ps/exchange/Remove-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementscope applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-ManagementScope -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-managementscope +schema: 2.0.0 +title: Remove-ManagementScope --- # Remove-ManagementScope @@ -55,13 +56,15 @@ After you verify that the scopes to be removed are correct, run the command agai ## 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 scope to remove. You can't remove a scope if it's in use by a management role assignment. ```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: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,6 +115,9 @@ 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. @@ -118,7 +128,6 @@ 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 @@ -128,13 +137,15 @@ 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/exchange/Remove-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md index 936faaf305..4087ea4258 100644 --- a/exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mapivirtualdirectory applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-MapiVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mapivirtualdirectory +schema: 2.0.0 +title: Remove-MapiVirtualDirectory --- # Remove-MapiVirtualDirectory @@ -43,6 +44,9 @@ This example removes the MAPI virtual directory from the local server named Cont ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the MAPI virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -55,7 +59,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-Message.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-Message.md index ecf08727f1..88b8ab33a8 100644 --- a/exchange/exchange-ps/exchange/Remove-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-message applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-Message -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-message +schema: 2.0.0 +title: Remove-Message --- # Remove-Message @@ -58,13 +59,15 @@ This example removes all messages that meet the following criteria without gener ## 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: True Position: 1 @@ -74,6 +77,9 @@ 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 ("). @@ -82,7 +88,6 @@ 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: True Position: Named @@ -92,6 +97,9 @@ 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`. @@ -101,7 +109,6 @@ 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 @@ -111,6 +118,9 @@ 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 @@ -126,7 +136,6 @@ 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 @@ -136,13 +145,15 @@ 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 @@ -152,13 +163,15 @@ Accept wildcard characters: False ``` ### -WithNDR + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WithNDR parameter specifies whether a non-delivery report (NDR) is returned to the sender of a message. The default value is $true. This parameter can be used with both the Identity parameter and Filter parameter sets. ```yaml 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/exchange/Remove-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-MessageClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md index 430c30d775..81c906652b 100644 --- a/exchange/exchange-ps/exchange/Remove-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-messageclassification applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MessageClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-messageclassification +schema: 2.0.0 +title: Remove-MessageClassification --- # Remove-MessageClassification @@ -43,6 +44,9 @@ This example removes the message classification named "My Message Classification ## 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 remove. You can use any value that uniquely identifies the message classification. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the message classification that you want to rem Type: MessageClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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 @@ -130,4 +139,6 @@ To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Ty ### Output types To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data. +## NOTES + ## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Remove-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md index 7a3f08fc37..f5a49960ba 100644 --- a/exchange/exchange-ps/exchange/Remove-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationbatch applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MigrationBatch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationbatch +schema: 2.0.0 +title: Remove-MigrationBatch --- # Remove-MigrationBatch @@ -56,13 +57,15 @@ This example removes the corrupted migration batch LocalMove1. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter identifies the migration batch that you want to remove. The value for this parameter is the name that was specified when the migration batch was created. ```yaml Type: MigrationBatchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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. @@ -99,7 +107,6 @@ 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,6 +116,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. @@ -121,7 +131,6 @@ If you use this switch to remove a corrupted migration batch, the individual use Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,6 +140,9 @@ 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. @@ -139,7 +151,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -149,13 +160,15 @@ 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/exchange/Remove-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md index 9484d7d7e2..0bcc18131c 100644 --- a/exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationendpoint applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MigrationEndpoint -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationendpoint +schema: 2.0.0 +title: Remove-MigrationEndpoint --- # Remove-MigrationEndpoint @@ -48,13 +49,15 @@ This example removes the migration endpoint CrossForestME01. ## 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 remove. ```yaml Type: MigrationEndpointIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ 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. @@ -109,7 +119,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -119,13 +128,15 @@ 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/exchange/Remove-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MigrationUser.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md index 61036e2269..96f1332d5d 100644 --- a/exchange/exchange-ps/exchange/Remove-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationuser applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MigrationUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-migrationuser +schema: 2.0.0 +title: Remove-MigrationUser --- # Remove-MigrationUser @@ -45,13 +46,15 @@ This example removes the migration user Tony Smith from a migration batch. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the user that you want to remove from the migration batch. ```yaml Type: MigrationUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,6 +105,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. @@ -108,7 +118,6 @@ Use this switch to work around user or data corruption issues. Specific checks a Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,6 +127,9 @@ 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. @@ -126,7 +138,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -136,13 +147,15 @@ 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/exchange/Remove-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-MobileDevice.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md index dc6843cec8..92d8875224 100644 --- a/exchange/exchange-ps/exchange/Remove-MobileDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mobiledevice applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MobileDevice -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mobiledevice +schema: 2.0.0 +title: Remove-MobileDevice --- # Remove-MobileDevice @@ -52,6 +53,9 @@ This example removes the mobile device partnership for the specified device and ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mobile device partnership that you want to remove. You can use the following values that uniquely identifies the mobile device: - Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`) @@ -62,7 +66,6 @@ The Identity parameter specifies the mobile device partnership that you want to Type: MobileDeviceIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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. @@ -99,7 +107,6 @@ 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,13 +116,15 @@ 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/exchange/Remove-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md index 24f850cef1..15c2a34c39 100644 --- a/exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-mobiledevicemailboxpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MobileDeviceMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-mobiledevicemailboxpolicy +schema: 2.0.0 +title: Remove-MobileDeviceMailboxPolicy --- # Remove-MobileDeviceMailboxPolicy @@ -60,6 +61,9 @@ This example removes the mobile device mailbox policy named Management and bypas ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mobile device mailbox policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -70,7 +74,6 @@ The Identity parameter specifies the mobile device mailbox policy that you want Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -80,6 +83,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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. @@ -107,7 +115,6 @@ 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 @@ -117,6 +124,9 @@ 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. @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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/exchange/Remove-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md index ff8f5e3203..30b16ff6fe 100644 --- a/exchange/exchange-ps/exchange/Remove-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-moverequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-MoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-moverequest +schema: 2.0.0 +title: Remove-MoveRequest --- # Remove-MoveRequest @@ -71,6 +72,9 @@ The MailboxGuid and MoveRequestQueue parameters are for debugging purposes only. ## 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 the following values: - GUID @@ -87,7 +91,6 @@ You can't use this parameter with the MailboxGuid or MoveRequestQueue parameters Type: MoveRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -97,6 +100,9 @@ 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 the mailbox for which you want to remove the move request. If you specify the MailboxGuid parameter, you must also specify the MoveRequestQueue parameter. @@ -107,7 +113,6 @@ You can't use this parameter with the Identity parameter. Type: Guid Parameter Sets: MigrationMoveRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -117,6 +122,9 @@ 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. The MoveRequestQueue parameter specifies the database on which the move request is queued. You can use any value that uniquely identifies the database. For example: @@ -131,7 +139,6 @@ You can't use this parameter with the Identity parameter. Type: DatabaseIdParameter Parameter Sets: MigrationMoveRequestQueue Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -141,6 +148,9 @@ 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`. @@ -150,7 +160,6 @@ 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 @@ -160,6 +169,9 @@ 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. @@ -168,7 +180,6 @@ 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,6 +189,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -186,7 +200,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -196,6 +209,9 @@ Accept wildcard characters: False ``` ### -ProxyToMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ProxyToMailbox parameter specifies the move destination by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example: @@ -215,7 +231,6 @@ The ProxyToMailbox parameter specifies the move destination by the location of t Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -225,13 +240,15 @@ 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/exchange/Remove-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-OMEConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md index 20d726ee54..5a9ca319f2 100644 --- a/exchange/exchange-ps/exchange/Remove-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-omeconfiguration applicable: Exchange Online -title: Remove-OMEConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-omeconfiguration +schema: 2.0.0 +title: Remove-OMEConfiguration --- # Remove-OMEConfiguration @@ -42,13 +43,15 @@ This example removes the custom OME configuration named Contoso Marketing. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the custom OME configuration that you want to remove. You can use the Get-OMEConfiguration cmdlet to see the available values. If the value contains spaces, enclose the value in quotation marks ```yaml Type: OMEConfigurationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Remove-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md index 24791b7b37..e83bc90bb4 100644 --- a/exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-oabvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-OabVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-oabvirtualdirectory +schema: 2.0.0 +title: Remove-OabVirtualDirectory --- # Remove-OabVirtualDirectory @@ -53,6 +54,9 @@ This example removes the default OAB virtual directory from Server1. ## 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 remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -65,7 +69,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -75,6 +78,9 @@ 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,7 +90,6 @@ 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,13 +99,15 @@ 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 @@ -110,6 +117,9 @@ 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. @@ -118,7 +128,6 @@ 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 @@ -128,13 +137,15 @@ 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/exchange/Remove-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md index b9d780e4f5..b3fc9276bb 100644 --- a/exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-offlineaddressbook applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-OfflineAddressBook -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-offlineaddressbook +schema: 2.0.0 +title: Remove-OfflineAddressBook --- # Remove-OfflineAddressBook @@ -48,6 +49,9 @@ This example removes the OAB named Contoso Executives. ## 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 remove. You can use any value that uniquely identifies the OAB. For example: - Name or \\Name @@ -58,7 +62,6 @@ The Identity parameter specifies the OAB that you want to remove. You can use an Type: OfflineAddressBookIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -68,6 +71,9 @@ 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`. @@ -77,7 +83,6 @@ 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,6 +92,9 @@ 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,7 +103,6 @@ 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,6 +112,9 @@ 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. @@ -113,7 +123,6 @@ 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 Required: False Position: Named @@ -123,13 +132,15 @@ 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/exchange/Remove-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md index a6196d357b..892aab9345 100644 --- a/exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-onpremisesorganization applicable: Exchange Online -title: Remove-OnPremisesOrganization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-onpremisesorganization +schema: 2.0.0 +title: Remove-OnPremisesOrganization --- # Remove-OnPremisesOrganization @@ -44,6 +45,9 @@ This example removes the ExchangeMail OnPremisesOrganization object in a Microso ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the identity of the on-premises organization object. You can use the following values: - Canonical name @@ -54,7 +58,6 @@ The Identity parameter specifies the identity of the on-premises organization ob Type: OnPremisesOrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -64,6 +67,9 @@ 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,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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/exchange/Remove-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md index 0598e9d220..429cf72374 100644 --- a/exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-organizationrelationship applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-OrganizationRelationship -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-organizationrelationship +schema: 2.0.0 +title: Remove-OrganizationRelationship --- # Remove-OrganizationRelationship @@ -45,6 +46,9 @@ This example removes the organization relationship Contoso using the Identity pa ## 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 organization relationship that you want to remove. You can use one of the following values: - Canonical name @@ -55,7 +59,6 @@ The Identity parameter specifies the identity of the organization relationship t 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: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-OrganizationSegment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationSegment.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-OrganizationSegment.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationSegment.md index 0d1f0c04fb..6ce544bd5d 100644 --- a/exchange/exchange-ps/exchange/Remove-OrganizationSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationSegment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-organizationsegment applicable: Security & Compliance -title: Remove-OrganizationSegment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-organizationsegment +schema: 2.0.0 +title: Remove-OrganizationSegment --- # Remove-OrganizationSegment @@ -42,6 +43,9 @@ This example removes the organization segment named Engineering Group. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the organization segment that you want to remove. You can use any value that uniquely identifies the segment. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the organization segment that you want to remov Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 0 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Remove-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-OutboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md index 7cfabaff38..c74dd91287 100644 --- a/exchange/exchange-ps/exchange/Remove-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-outboundconnector applicable: Exchange Online, Exchange Online Protection -title: Remove-OutboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-outboundconnector +schema: 2.0.0 +title: Remove-OutboundConnector --- # Remove-OutboundConnector @@ -44,13 +45,15 @@ This example deletes the Outbound connector named Contoso Outbound Connector. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the connector you want to remove. ```yaml Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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/exchange/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md index 2fd3e45e05..b2fe260409 100644 --- a/exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-outlookprotectionrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-OutlookProtectionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-outlookprotectionrule +schema: 2.0.0 +title: Remove-OutlookProtectionRule --- # Remove-OutlookProtectionRule @@ -54,13 +55,15 @@ This example removes all Outlook protection rules from the organization. ## 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 Outlook protection rule that you want to remove. ```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 @@ -70,6 +73,9 @@ 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,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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. @@ -97,7 +105,6 @@ 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,13 +114,15 @@ 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/exchange/Remove-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-OutlookProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md index 1d6410cdd9..3eb2bda149 100644 --- a/exchange/exchange-ps/exchange/Remove-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-outlookprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-OutlookProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-outlookprovider +schema: 2.0.0 +title: Remove-OutlookProvider --- # Remove-OutlookProvider @@ -45,13 +46,15 @@ This example deletes the AutoDiscoverConfig object named Test Object from Active ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the AutoDiscoverConfig object to remove from Active Directory. ```yaml Type: OutlookProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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,13 +103,15 @@ 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/exchange/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md index b9f7e4ee5e..385986ab04 100644 --- a/exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-owamailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-OwaMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-owamailboxpolicy +schema: 2.0.0 +title: Remove-OwaMailboxPolicy --- # Remove-OwaMailboxPolicy @@ -60,6 +61,9 @@ This example removes the mailbox policy named Corporate for the tenant Contoso i ## 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 remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -70,7 +74,6 @@ The Identity parameter specifies the mailbox policy that you want to remove. You Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -80,6 +83,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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,7 +115,6 @@ 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,6 +124,9 @@ 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. @@ -125,7 +135,6 @@ 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 Required: False Position: Named @@ -135,13 +144,15 @@ 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/exchange/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md index f97d5d7436..8287b68ab2 100644 --- a/exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-owavirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-OwaVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-owavirtualdirectory +schema: 2.0.0 +title: Remove-OwaVirtualDirectory --- # Remove-OwaVirtualDirectory @@ -50,6 +51,9 @@ This example removes the specified Outlook on the web virtual directory from the ## 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 remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -62,7 +66,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,13 +96,15 @@ 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,13 +114,15 @@ 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/exchange/Remove-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-PartnerApplication.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md index 2eb9caf5e4..c9446c8fec 100644 --- a/exchange/exchange-ps/exchange/Remove-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-partnerapplication applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PartnerApplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-partnerapplication +schema: 2.0.0 +title: Remove-PartnerApplication --- # Remove-PartnerApplication @@ -47,13 +48,15 @@ This command removes the HRApp partner application. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the identity of the partner application. ```yaml Type: PartnerApplicationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md index 9cece99ddf..589aa3887d 100644 --- a/exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-phishsimoverridepolicy applicable: Exchange Online -title: Remove-PhishSimOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-phishsimoverridepolicy +schema: 2.0.0 +title: Remove-PhishSimOverridePolicy --- # Remove-PhishSimOverridePolicy @@ -44,6 +45,9 @@ This example removes the phishing simulation override policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the phishing simulation override policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -57,7 +61,6 @@ Use the Get-PhishSimOverridePolicy cmdlet to find the values. The only available Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Exchange Online + The ForceDeletion switch forces the removal of the 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 @@ -118,6 +127,9 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + In Exchange Online 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. The WhatIf switch doesn't work in Security & Compliance PowerShell. @@ -126,7 +138,6 @@ The WhatIf switch doesn't work in Security & Compliance PowerShell. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md index 45d9e9b72c..f8247d8d28 100644 --- a/exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-policytipconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PolicyTipConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-policytipconfig +schema: 2.0.0 +title: Remove-PolicyTipConfig --- # Remove-PolicyTipConfig @@ -50,6 +51,9 @@ This example removes all the custom Russian Policy Tips. ## 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 remove. 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. @@ -61,7 +65,6 @@ The Identity parameter specifies the custom Policy Tip you want to remove. You c Type: PolicyTipConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -71,6 +74,9 @@ 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,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md index 56801944fd..58f393099e 100644 --- a/exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-powershellvirtualdirectory applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-PowerShellVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-powershellvirtualdirectory +schema: 2.0.0 +title: Remove-PowerShellVirtualDirectory --- # Remove-PowerShellVirtualDirectory @@ -47,6 +48,9 @@ Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confi ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the PowerShell virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -59,7 +63,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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/exchange/Remove-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ProtectionAlert.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-ProtectionAlert.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ProtectionAlert.md index f4edc74c13..f8d481171c 100644 --- a/exchange/exchange-ps/exchange/Remove-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ProtectionAlert.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-protectionalert applicable: Security & Compliance -title: Remove-ProtectionAlert -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-protectionalert +schema: 2.0.0 +title: Remove-ProtectionAlert --- # Remove-ProtectionAlert @@ -43,6 +44,9 @@ This example removes the specified alert policy. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the alert policy that you want to remove. You can use any value that uniquely identifies the alert policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the alert policy that you want to remove. You c Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the alert policy. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-PublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md index 036d6a15da..378194818a 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolder +schema: 2.0.0 +title: Remove-PublicFolder --- # Remove-PublicFolder @@ -55,13 +56,15 @@ This example deletes the public folder Directory Folder and all its child public ## 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 remove. A valid value uses the syntax: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`. ```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 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,6 +115,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Mailbox Description }} @@ -116,7 +126,6 @@ This parameter is available only in the cloud-based service. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -126,6 +135,9 @@ 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 all subfolders of the specified folder should also be removed. You don't need to specify a value with this switch. If you don't use this switch and the public folder has subfolders, the command doesn't run and an error message is returned. @@ -134,7 +146,6 @@ If you don't use this switch and the public folder has subfolders, the command d 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 @@ -144,6 +155,9 @@ 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: @@ -159,7 +173,6 @@ 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 @@ -169,13 +182,15 @@ 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/exchange/Remove-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md index b1b0afb2e2..11a16b886c 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderadministrativepermission applicable: Exchange Server 2010 -title: Remove-PublicFolderAdministrativePermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderadministrativepermission +schema: 2.0.0 +title: Remove-PublicFolderAdministrativePermission --- # Remove-PublicFolderAdministrativePermission @@ -61,6 +62,9 @@ This example removes the ViewInformationStore permission from the user Chris on ## 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. @@ -69,7 +73,6 @@ You can omit the parameter label so that only the public folder name or GUID is Type: PublicFolderIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -79,6 +82,9 @@ Accept wildcard characters: False ``` ### -AccessRights + +> Applicable: Exchange Server 2010 + The AccessRights parameter specifies the rights being removed. Valid values include: - None The administrator doesn't have any rights to modify public folder attributes. @@ -96,9 +102,8 @@ You can specify multiple values separated by commas. ```yaml Type: MultiValuedProperty -Parameter Sets: Identity +Parameter Sets: Identity, Instance Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -107,40 +112,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: MultiValuedProperty -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -```yaml -Type: PublicFolderIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 +### -Instance -Required: False -Position: 1 -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -Instance The Instance parameter specifies whether to pass an entire object to the command to be processed. It is 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,6 +131,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Server 2010 + The User parameter specifies whose admin permissions are being removed from the specified public folder. You can specify the following types of users or groups (security principals) for this parameter: - Mailbox users @@ -171,9 +155,8 @@ You can use any value that uniquely identifies the user or group. For example: ```yaml Type: SecurityPrincipalIdParameter -Parameter Sets: Identity +Parameter Sets: Identity, Instance Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -182,20 +165,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SecurityPrincipalIdParameter -Parameter Sets: Instance -Aliases: -Applicable: Exchange Server 2010 +### -Confirm -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -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`. @@ -205,7 +178,6 @@ 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 @@ -215,13 +187,15 @@ Accept wildcard characters: False ``` ### -Deny + +> Applicable: Exchange Server 2010 + The Deny switch specifies that the permissions you're removing are Deny permissions. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -231,13 +205,15 @@ 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 @@ -247,6 +223,9 @@ Accept wildcard characters: False ``` ### -InheritanceType + +> Applicable: Exchange Server 2010 + The InheritanceType parameter specifies the type of inheritance. Valid values are: - None @@ -259,7 +238,6 @@ The InheritanceType parameter specifies the type of inheritance. Valid values ar Type: ActiveDirectorySecurityInheritance Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -269,6 +247,9 @@ 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 @@ -282,7 +263,6 @@ 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 @@ -292,13 +272,15 @@ 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/exchange/Remove-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md index 726354e79b..67002589cb 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderclientpermission applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PublicFolderClientPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderclientpermission +schema: 2.0.0 +title: Remove-PublicFolderClientPermission --- # Remove-PublicFolderClientPermission @@ -51,6 +52,9 @@ This example removes permission for the user Chris to the public folder My Publi ## 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 by using the format \\TopLevelPublicFolder\\PublicFolder. You can omit the parameter label so that only the public folder name or GUID is supplied. @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -AccessRights + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AccessRights parameter specifies the rights that you want to remove from the user on the public folder. @@ -104,7 +110,6 @@ In addition to the access rights, you can create rights based upon roles, which Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -114,6 +119,9 @@ 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 whose permissions are being removed. For the best results, we recommend using the following values: @@ -125,7 +133,6 @@ 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 @@ -135,6 +142,9 @@ 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`. @@ -144,7 +154,6 @@ 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 @@ -154,6 +163,9 @@ 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. @@ -162,7 +174,6 @@ 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 @@ -172,6 +183,9 @@ 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: @@ -187,7 +201,6 @@ 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 @@ -197,13 +210,15 @@ 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/exchange/Remove-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md index 1da34f3a54..9177abfcda 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderdatabase applicable: Exchange Server 2010 -title: Remove-PublicFolderDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfolderdatabase +schema: 2.0.0 +title: Remove-PublicFolderDatabase --- # Remove-PublicFolderDatabase @@ -46,6 +47,9 @@ This example removes the database Public Folder Database after all the prerequis ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the public folder database that you want to remove. You can use any value that uniquely identifies the database. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the public folder database that you want to rem Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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 @@ -101,13 +108,15 @@ Accept wildcard characters: False ``` ### -RemoveLastAllowed + +> Applicable: Exchange Server 2010 + The RemoveLastAllowed switch allows the removal of the last public folder database in the organization. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -117,13 +126,15 @@ 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/exchange/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md index 647e00554d..ceadbd4b8b 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermailboxmigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PublicFolderMailboxMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermailboxmigrationrequest +schema: 2.0.0 +title: Remove-PublicFolderMailboxMigrationRequest --- # Remove-PublicFolderMailboxMigrationRequest @@ -68,6 +69,9 @@ 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 remove. This value uses the syntax `\PublicFolderMailboxMigration` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`). You can't use this parameter with the RequestGuid or RequestQueue parameters. @@ -76,7 +80,6 @@ You can't use this parameter with the RequestGuid or RequestQueue parameters. Type: PublicFolderMailboxMigrationRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -86,6 +89,9 @@ 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. To find the RequestGuid value, use the Get-PublicFolderMailboxMigrationRequest cmdlet. @@ -96,7 +102,6 @@ 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: True Position: Named @@ -106,6 +111,9 @@ 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: @@ -120,7 +128,6 @@ 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 @@ -130,6 +137,9 @@ 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,7 +149,6 @@ 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,6 +158,9 @@ 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. @@ -157,7 +169,6 @@ 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 @@ -167,6 +178,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -175,7 +189,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -185,13 +198,15 @@ 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/exchange/Remove-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md index c85f9d9a62..6cc233c520 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-PublicFolderMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermigrationrequest +schema: 2.0.0 +title: Remove-PublicFolderMigrationRequest --- # Remove-PublicFolderMigrationRequest @@ -67,6 +68,9 @@ The RequestGuid and RequestQueue parameters are for debugging purposes only. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the migration request that you want to remove. You can use the following values: - Name @@ -78,7 +82,6 @@ You can't use this parameter with the RequestGuid or RequestQueue parameters. Type: PublicFolderMigrationRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -88,6 +91,9 @@ Accept wildcard characters: False ``` ### -RequestGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequestGuid parameter identifies the migration request to remove by its RequestGUID value. This parameter also requires the RequestQueue parameter. You can't use this parameter with the Identity parameter. @@ -96,7 +102,6 @@ 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: True Position: Named @@ -106,6 +111,9 @@ Accept wildcard characters: False ``` ### -RequestQueue + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequestQueue parameter identifies the migration request by the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example: - Name @@ -120,7 +128,6 @@ 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 @@ -130,6 +137,9 @@ 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`. @@ -139,7 +149,6 @@ 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 @@ -149,13 +158,15 @@ 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 @@ -165,6 +176,9 @@ 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. @@ -173,7 +187,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -183,13 +196,15 @@ 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/exchange/Remove-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md index b32e757add..9fd7a8d071 100644 --- a/exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermoverequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-PublicFolderMoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-publicfoldermoverequest +schema: 2.0.0 +title: Remove-PublicFolderMoveRequest --- # Remove-PublicFolderMoveRequest @@ -65,6 +66,9 @@ The RequestGuid and RequestQueue parameters are for debugging purposes only. ## 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 is \\PublicFolderMove. You can't use this parameter with the RequestGuid or RequestQueue parameter. @@ -73,7 +77,6 @@ You can't use this parameter with the RequestGuid or RequestQueue parameter. Type: PublicFolderMoveRequestIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -83,6 +86,9 @@ 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. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter. You can't use this parameter with the Identity parameter. @@ -91,7 +97,6 @@ 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, Exchange Online Required: True Position: Named @@ -101,6 +106,9 @@ 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 @@ -113,7 +121,6 @@ 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 @@ -123,6 +130,9 @@ 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`. @@ -132,7 +142,6 @@ 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 @@ -142,6 +151,9 @@ 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. @@ -150,7 +162,6 @@ 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 @@ -160,6 +171,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -168,7 +182,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -178,13 +191,15 @@ 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/exchange/Remove-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md index 6c828f12bb..708f9a50d2 100644 --- a/exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-quarantinepolicy applicable: Exchange Online, Exchange Online Protection -title: Remove-QuarantinePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-quarantinepolicy +schema: 2.0.0 +title: Remove-QuarantinePolicy --- # Remove-QuarantinePolicy @@ -43,6 +44,9 @@ This example removes the quarantine policy named Contoso Engineering. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the quarantine policy you want to remove. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the quarantine policy you want to remove. You c Type: QuarantineTagIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -63,13 +66,15 @@ 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 diff --git a/exchange/exchange-ps/exchange/Remove-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ReceiveConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md index 16d1194f04..6890db609f 100644 --- a/exchange/exchange-ps/exchange/Remove-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-receiveconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ReceiveConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-receiveconnector +schema: 2.0.0 +title: Remove-ReceiveConnector --- # Remove-ReceiveConnector @@ -45,6 +46,9 @@ This example removes the Receive connector named Contoso.com Receive Connector. ## 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 remove. You can use any value that uniquely identifies the Receive connector. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the Receive connector that you want to remove. Type: ReceiveConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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 @@ -103,13 +110,15 @@ 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/exchange/Remove-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-RecipientPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md index 2b1a383994..7f1bbfe8de 100644 --- a/exchange/exchange-ps/exchange/Remove-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-recipientpermission applicable: Exchange Online -title: Remove-RecipientPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-recipientpermission +schema: 2.0.0 +title: Remove-RecipientPermission --- # Remove-RecipientPermission @@ -49,6 +50,9 @@ This example removes the SendAs permission from the user Ayla Kol for the mailbo ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the target recipient. The user or group specified by the Trustee parameter can no longer operate on this recipient. You can specify any type of recipient, for example: @@ -72,7 +76,6 @@ 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 @@ -82,13 +85,15 @@ Accept wildcard characters: False ``` ### -AccessRights + +> Applicable: Exchange Online + The AccessRights parameter specifies the permission that you want to remove from 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,6 +103,9 @@ Accept wildcard characters: False ``` ### -Trustee + +> Applicable: Exchange Online + The Trustee parameter specifies whose Send As permissions are being removing from the specified target recipient. You can specify the following types of users or groups (security principals) for this parameter: - Mailbox users @@ -121,7 +129,6 @@ 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 @@ -131,6 +138,9 @@ 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`. @@ -140,7 +150,6 @@ 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 @@ -150,13 +159,15 @@ Accept wildcard characters: False ``` ### -Deny + +> Applicable: Exchange Online + {{ Fill Deny Description }} ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -166,13 +177,15 @@ Accept wildcard characters: False ``` ### -MultiTrustees + +> Applicable: Exchange Online + {{ Fill MultiTrustees Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -182,13 +195,15 @@ Accept wildcard characters: False ``` ### -SkipDomainValidationForMailContact + +> Applicable: Exchange Online + The SkipDomainValidationForMailContact switch skips the check that confirms the proxy addresses of the external contact specified by the Identity parameter are in an accepted domain of the organization. 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 @@ -198,13 +213,15 @@ Accept wildcard characters: False ``` ### -SkipDomainValidationForMailUser + +> Applicable: Exchange Online + The SkipDomainValidationForMailUser switch skips the check that confirms the proxy addresses of the mail user specified by the Identity parameter are in an accepted domain of the organization. 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 @@ -214,13 +231,15 @@ Accept wildcard characters: False ``` ### -SkipDomainValidationForSharedMailbox + +> Applicable: Exchange Online + The SkipDomainValidationForSharedMailbox switch skips the check that confirms the proxy addresses of the shared mailbox specified by the Identity parameter are in an accepted domain of the organization. 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,13 +249,15 @@ 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/exchange/Remove-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-RemoteDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md index bc7601b802..e0738ffc12 100644 --- a/exchange/exchange-ps/exchange/Remove-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-remotedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-RemoteDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-remotedomain +schema: 2.0.0 +title: Remove-RemoteDomain --- # Remove-RemoteDomain @@ -43,6 +44,9 @@ This example removes the remote domain object named Contoso. ## 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 remove. You can use any value that uniquely identifies the remote domain. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the remote domain that you want to remove. You Type: RemoteDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md index 1795e792f9..cb85d44b48 100644 --- a/exchange/exchange-ps/exchange/Remove-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-remotemailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-RemoteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-remotemailbox +schema: 2.0.0 +title: Remove-RemoteMailbox --- # Remove-RemoteMailbox @@ -49,6 +50,9 @@ This example removes the on-premises mail-enabled user Kim Akers and the associa ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter identifies the mail-enabled user and the associated mailbox in the service that you want to remove. You can use one of the following values: - ADObjectID @@ -64,7 +68,6 @@ The Identity parameter identifies the mail-enabled user and the associated mailb Type: RemoteMailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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: @@ -120,7 +130,6 @@ 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 @@ -130,6 +139,9 @@ 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 removes the instance of the remote object in the on-premises organization, and the request to remove the mailbox is synchronized to the cloud. The Microsoft Entra object is removed, but if the mailbox is on hold, the mailbox is converted into an inactive mailbox and remains on hold. @@ -138,7 +150,6 @@ This switch removes the instance of the remote object in the on-premises organiz Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -148,13 +159,15 @@ 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/exchange/Remove-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md index bdcd81de21..91b998c527 100644 --- a/exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-reportsubmissionpolicy applicable: Exchange Online -title: Remove-ReportSubmissionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-reportsubmissionpolicy +schema: 2.0.0 +title: Remove-ReportSubmissionPolicy --- # Remove-ReportSubmissionPolicy @@ -41,13 +42,15 @@ This example removes the report submission policy from your organization. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the report submission policy that you want to remove. The only available policy is named DefaultReportSubmissionPolicy. ```yaml Type: ReportSubmissionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 diff --git a/exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md index 7c7b4a7d97..df57c8a7c7 100644 --- a/exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-reportsubmissionrule applicable: Exchange Online -title: Remove-ReportSubmissionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-reportsubmissionrule +schema: 2.0.0 +title: Remove-ReportSubmissionRule --- # Remove-ReportSubmissionRule @@ -44,13 +45,15 @@ This example removes the report submission rule from your organization. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the report submission rule that you want to remove. The default rule is named DefaultReportSubmissionRule. ```yaml Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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/exchange/Remove-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-ResubmitRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md index 6b01e58449..b16c839f65 100644 --- a/exchange/exchange-ps/exchange/Remove-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-resubmitrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ResubmitRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-resubmitrequest +schema: 2.0.0 +title: Remove-ResubmitRequest --- # Remove-ResubmitRequest @@ -50,13 +51,15 @@ This example removes all resubmit requests. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the resubmit request you want to remove. 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: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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 @@ -98,7 +106,6 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Remove-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionCompliancePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RetentionCompliancePolicy.md index e4883a0012..a8797cb36c 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentioncompliancepolicy applicable: Security & Compliance -title: Remove-RetentionCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentioncompliancepolicy +schema: 2.0.0 +title: Remove-RetentionCompliancePolicy --- # Remove-RetentionCompliancePolicy @@ -44,6 +45,9 @@ This example removes the retention policy named "Regulation 123 Compliance". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the retention policy that you want to remove. Y Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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,13 +88,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -99,6 +106,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to remove a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -107,7 +117,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -117,13 +126,15 @@ 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/exchange/Remove-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RetentionComplianceRule.md index f3478c2835..c8831d7ba0 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentioncompliancerule applicable: Security & Compliance -title: Remove-RetentionComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentioncompliancerule +schema: 2.0.0 +title: Remove-RetentionComplianceRule --- # Remove-RetentionComplianceRule @@ -46,6 +47,9 @@ This example removes the retention rule named "One Year Standard". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention rule to remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the retention rule to remove. You can use any v Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the rule. 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 @@ -101,6 +108,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to remove the rule associated with a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -109,7 +119,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -119,13 +128,15 @@ 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/exchange/Remove-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-RetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md index 3606e9995c..068e599c7b 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentionpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-RetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentionpolicy +schema: 2.0.0 +title: Remove-RetentionPolicy --- # Remove-RetentionPolicy @@ -62,13 +63,15 @@ This example removes the retention policy Business Critical, which is assigned t ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the retention 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: True Position: 1 @@ -78,6 +81,9 @@ 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`. @@ -87,7 +93,6 @@ 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,6 +102,9 @@ 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,7 +113,6 @@ 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,6 +122,9 @@ 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. Use this switch to hide the confirmation prompt when you remove a retention policy that's assigned to users. Removing a policy that's assigned to users results in those users not having any retention policy. @@ -123,7 +133,6 @@ Use this switch to hide the confirmation prompt when you remove a retention poli 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 @@ -133,13 +142,15 @@ 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/exchange/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md index 03f3e9a59f..82cafae0b4 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentionpolicytag applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-RetentionPolicyTag -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-retentionpolicytag +schema: 2.0.0 +title: Remove-RetentionPolicyTag --- # Remove-RetentionPolicyTag @@ -49,13 +50,15 @@ This example removes the retention tag Finance-DeletedItems. ## 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 retention policy tag. ```yaml Type: RetentionPolicyTagIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md index 30fc9c2297..aea96ec2c6 100644 --- a/exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-roleassignmentpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-RoleAssignmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-roleassignmentpolicy +schema: 2.0.0 +title: Remove-RoleAssignmentPolicy --- # Remove-RoleAssignmentPolicy @@ -67,13 +68,15 @@ For more information about the Where cmdlet and pipelining, see [Working with co ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the assignment policy to remove. If the assignment policy name has 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 Required: True Position: 1 @@ -83,6 +86,9 @@ 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`. @@ -92,7 +98,6 @@ 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 @@ -102,6 +107,9 @@ 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,7 +120,6 @@ 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 @@ -122,13 +129,15 @@ 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/exchange/Remove-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-RoleGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md index ed3cddf995..b529cb66a6 100644 --- a/exchange/exchange-ps/exchange/Remove-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-rolegroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: Remove-RoleGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-rolegroup +schema: 2.0.0 +title: Remove-RoleGroup --- # Remove-RoleGroup @@ -60,13 +61,15 @@ This example removes the Vancouver Recipient Administrators role group. Because ## 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 remove. 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 @@ -76,6 +79,9 @@ 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: @@ -87,7 +93,6 @@ 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 @@ -97,6 +102,9 @@ 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`. @@ -106,7 +114,6 @@ 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 @@ -116,6 +123,9 @@ 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,7 +134,6 @@ 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 @@ -134,6 +143,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Security & Compliance, 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. @@ -144,7 +156,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -154,6 +165,9 @@ 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. @@ -162,7 +176,6 @@ 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/exchange/Remove-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-RoleGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md index 34807f1679..8a647594dc 100644 --- a/exchange/exchange-ps/exchange/Remove-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-rolegroupmember applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: Remove-RoleGroupMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-rolegroupmember +schema: 2.0.0 +title: Remove-RoleGroupMember --- # Remove-RoleGroupMember @@ -73,13 +74,15 @@ This example removes the Training Assistants USG from the Training Administrator ## 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 that you want to remove a member from. 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 @@ -89,6 +92,9 @@ 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 to remove from the role group. You can specify the following types of users or groups (security principals) for this parameter: - Mailbox users @@ -113,7 +119,6 @@ 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 @@ -123,6 +128,9 @@ 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: @@ -134,7 +142,6 @@ 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 @@ -144,6 +151,9 @@ 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`. @@ -153,7 +163,6 @@ 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 @@ -163,6 +172,9 @@ 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. @@ -171,7 +183,6 @@ 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,6 +192,9 @@ 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. @@ -189,7 +203,6 @@ 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/exchange/Remove-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md index e34b39e341..3e461fed0d 100644 --- a/exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-routinggroupconnector applicable: Exchange Server 2010 -title: Remove-RoutingGroupConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-routinggroupconnector +schema: 2.0.0 +title: Remove-RoutingGroupConnector --- # Remove-RoutingGroupConnector @@ -47,13 +48,15 @@ This example removes the routing group connector Ex2010 to Ex2003 RGC. ## 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. ```yaml Type: RoutingGroupConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-RpcClientAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md index 869e6560c5..abc3471f5b 100644 --- a/exchange/exchange-ps/exchange/Remove-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-rpcclientaccess applicable: Exchange Server 2010 -title: Remove-RpcClientAccess -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-rpcclientaccess +schema: 2.0.0 +title: Remove-RpcClientAccess --- # Remove-RPCClientAccess @@ -45,6 +46,9 @@ This example removes the configuration information for the Exchange RPC Client A ## PARAMETERS ### -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 @@ -56,7 +60,6 @@ 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: True Position: Named @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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 @@ -101,13 +108,15 @@ 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/exchange/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md index 857607a82b..ad4b27f524 100644 --- a/exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-safeattachmentpolicy applicable: Exchange Online -title: Remove-SafeAttachmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-safeattachmentpolicy +schema: 2.0.0 +title: Remove-SafeAttachmentPolicy --- # Remove-SafeAttachmentPolicy @@ -45,6 +46,9 @@ This example removes the safe attachment policy named Block Attachments Policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the safe attachment policy that you want to remove. You can use any value that uniquely identifies the policy. For example: @@ -57,7 +61,6 @@ You can use any value that uniquely identifies the policy. For example: Type: SafeAttachmentPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -94,7 +102,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -104,13 +111,15 @@ 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/exchange/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md index e442e79efb..5beda7272f 100644 --- a/exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-safeattachmentrule applicable: Exchange Online -title: Remove-SafeAttachmentRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-safeattachmentrule +schema: 2.0.0 +title: Remove-SafeAttachmentRule --- # Remove-SafeAttachmentRule @@ -44,6 +45,9 @@ This examples removes the safe attachment rule named Research Department Attachm ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the safe attachment rule that you want to remove. You can use any value that uniquely identifies the rule. For example: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md index 287856fcc5..b3b3a6aa6c 100644 --- a/exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-safelinkspolicy applicable: Exchange Online -title: Remove-SafeLinksPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-safelinkspolicy +schema: 2.0.0 +title: Remove-SafeLinksPolicy --- # Remove-SafeLinksPolicy @@ -47,6 +48,9 @@ This example remove the Safe Links policy named Engineering Department URL Polic ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Safe Links policy that you want to remove. You can use any value that uniquely identifies the policy. For example: @@ -59,7 +63,6 @@ You can use any value that uniquely identifies the policy. For example: Type: SafeLinksPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -96,7 +104,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -106,13 +113,15 @@ 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/exchange/Remove-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md index 472e9e9324..24a110e8c1 100644 --- a/exchange/exchange-ps/exchange/Remove-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-safelinksrule applicable: Exchange Online -title: Remove-SafeLinksRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-safelinksrule +schema: 2.0.0 +title: Remove-SafeLinksRule --- # Remove-SafeLinksRule @@ -44,6 +45,9 @@ This examples removes the Safe Links rule named Research Department URL Rule. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Safe Links rule that you want to remove. You can use any value that uniquely identifies the rule. For example: @@ -56,7 +60,6 @@ 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 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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/exchange/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md index b15bec5d2b..1429e28a23 100644 --- a/exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-searchdocumentformat applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SearchDocumentFormat -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-searchdocumentformat +schema: 2.0.0 +title: Remove-SearchDocumentFormat --- # Remove-SearchDocumentFormat @@ -45,13 +46,15 @@ This example removes the search document format with an identity equal to "sct". ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter uniquely identifies the format to be removed. You can use the Get-SearchDocumentFormat cmdlet to view the identities of the installed formats. ```yaml Type: SearchDocumentFormatId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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 @@ -93,7 +101,6 @@ 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 @@ -103,13 +110,15 @@ 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/exchange/Remove-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md index 6974d66c3b..00b99cbd59 100644 --- a/exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-secopsoverridepolicy applicable: Exchange Online -title: Remove-SecOpsOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-secopsoverridepolicy +schema: 2.0.0 +title: Remove-SecOpsOverridePolicy --- # Remove-SecOpsOverridePolicy @@ -44,6 +45,9 @@ This example removes the SecOps mailbox override policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the SecOps override policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the SecOps override policy that you want to rem Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Exchange Online + The ForceDeletion switch forces the removal of the SecOps override 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 @@ -116,13 +125,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-SendConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md index e1ce45ac63..22844699fe 100644 --- a/exchange/exchange-ps/exchange/Remove-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-sendconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SendConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-sendconnector +schema: 2.0.0 +title: Remove-SendConnector --- # Remove-SendConnector @@ -47,13 +48,15 @@ This example deletes the Send connector named Contoso.com Send Connector. ## 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: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md index dff6213508..46cde67721 100644 --- a/exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-servermonitoringoverride applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ServerMonitoringOverride -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-servermonitoringoverride +schema: 2.0.0 +title: Remove-ServerMonitoringOverride --- # Remove-ServerMonitoringOverride @@ -49,13 +50,15 @@ This example removes a server monitoring override of the ExtensionAttributes pro ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the monitoring item that was overridden. The value is in the form of HealthSet\\MonitoringItem or HealthSet\\MonitoringItem\\TargetResource. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -65,6 +68,9 @@ Accept wildcard characters: False ``` ### -ItemType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ItemType parameter specifies the item type of the override that you want to remove. It can be any of the following values: - Probe @@ -75,7 +81,6 @@ The ItemType parameter specifies the item type of the override that you want to Type: MonitoringItemTypeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -85,13 +90,15 @@ Accept wildcard characters: False ``` ### -PropertyName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PropertyName parameter specifies the property for the override you want to remove. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -101,6 +108,9 @@ 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 override that you want to remove. You can use any value that uniquely identifies the server. For example: - Name @@ -112,7 +122,6 @@ The Server parameter specifies the Exchange server that contains the override th Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -122,6 +131,9 @@ 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`. @@ -131,7 +143,6 @@ 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 @@ -141,13 +152,15 @@ 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/exchange/Remove-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-ServicePrincipal.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md index 855f9df7b6..b79d03fb3c 100644 --- a/exchange/exchange-ps/exchange/Remove-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-serviceprincipal applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Remove-ServicePrincipal -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-serviceprincipal +schema: 2.0.0 +title: Remove-ServicePrincipal --- # Remove-ServicePrincipal @@ -42,6 +43,9 @@ This example removes the specified service principal. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Identity parameter specifies the service principal that you want to remove. You can use any value that uniquely identifies the service principal. For example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the service principal that you want to remove. Type: ServicePrincipalIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 0 @@ -64,6 +67,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Remove-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-SettingOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md index c3488fbb4e..7c374c9462 100644 --- a/exchange/exchange-ps/exchange/Remove-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-settingoverride applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SettingOverride -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-settingoverride +schema: 2.0.0 +title: Remove-SettingOverride --- # Remove-SettingOverride @@ -47,6 +48,9 @@ This example removes the setting override named IM Server Integration. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the setting override that you want to remove. You can use any value that uniquely identifies the override. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the setting override that you want to remove. Y Type: SettingOverrideIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-SharingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md index ac9dbb8159..5a0ce3eecf 100644 --- a/exchange/exchange-ps/exchange/Remove-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-sharingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-SharingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-sharingpolicy +schema: 2.0.0 +title: Remove-SharingPolicy --- # Remove-SharingPolicy @@ -50,6 +51,9 @@ This example removes the sharing policy Contoso and suppresses the confirmation ## 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 sharing policy that you want to remove. You can use one of the following values: - ADObjectID @@ -61,7 +65,6 @@ The Identity parameter specifies the identity of the sharing policy that you wan Type: SharingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,13 +115,15 @@ 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/exchange/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md index 3b226be32b..c8ee197cd6 100644 --- a/exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-sitemailboxprovisioningpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SiteMailboxProvisioningPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-sitemailboxprovisioningpolicy +schema: 2.0.0 +title: Remove-SiteMailboxProvisioningPolicy --- # Remove-SiteMailboxProvisioningPolicy @@ -47,6 +48,9 @@ This example deletes the site mailbox policy named Default that was created when ## 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 remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -57,7 +61,6 @@ 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: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Remove-StoreMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-StoreMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md index 4faccccab2..f1f1cb5bac 100644 --- a/exchange/exchange-ps/exchange/Remove-StoreMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-storemailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-StoreMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-storemailbox +schema: 2.0.0 +title: Remove-StoreMailbox --- # Remove-StoreMailbox @@ -64,6 +65,9 @@ This example permanently purges all soft-deleted mailboxes from mailbox database ## PARAMETERS ### -Database + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Database parameter specifies the mailbox database that contains the mailbox to remove. You can use any value that uniquely identifies the database. For example: - Name @@ -74,7 +78,6 @@ The Database parameter specifies the mailbox database that contains the mailbox Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -84,6 +87,9 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the mailbox that you want to remove. Use the mailbox GUID as the value for this parameter. Run the following command to obtain the mailbox GUID and other information for all mailboxes in your organization: Get-MailboxDatabase | Get-MailboxStatistics | Format-List DisplayName,MailboxGuid,Database,DisconnectReason,DisconnectDate. @@ -92,7 +98,6 @@ Run the following command to obtain the mailbox GUID and other information for a Type: StoreMailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -102,6 +107,9 @@ Accept wildcard characters: False ``` ### -MailboxState + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxState parameter specifies the mailbox state on the source mailbox database. This parameter accepts the following values: - Disabled @@ -111,7 +119,6 @@ The MailboxState parameter specifies the mailbox state on the source mailbox dat Type: MailboxStateParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -121,6 +128,9 @@ 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,7 +140,6 @@ 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 @@ -140,13 +149,15 @@ 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/exchange/Remove-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SupervisoryReviewPolicyV2.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SupervisoryReviewPolicyV2.md index 1bbb2eaf31..4f96b51338 100644 --- a/exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SupervisoryReviewPolicyV2.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-supervisoryreviewpolicyv2 applicable: Security & Compliance -title: Remove-SupervisoryReviewPolicyV2 -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-supervisoryreviewpolicyv2 +schema: 2.0.0 +title: Remove-SupervisoryReviewPolicyV2 --- # Remove-SupervisoryReviewPolicyV2 @@ -43,6 +44,9 @@ This example removes the supervisory review policy named EU Brokers Policy. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the supervisory review policy that you want to remove. You can use any value that uniquely identifies the policy. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the supervisory review policy that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md index 5a20fe05fc..2ff0ec8e46 100644 --- a/exchange/exchange-ps/exchange/Remove-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-sweeprule applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-SweepRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-sweeprule +schema: 2.0.0 +title: Remove-SweepRule --- # Remove-SweepRule @@ -51,6 +52,9 @@ This example removes 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 remove. You can use any value that uniquely identifies the rule. For example: - RuleId property (for example, x2hlsdpGmUifjFgxxGIOJw==). @@ -61,7 +65,6 @@ The Identity parameter specifies the Sweep rule that you want to remove. You can Type: SweepRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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 remove. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -125,7 +135,6 @@ The Mailbox parameter specifies the mailbox that contains the rule you want to r Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -135,13 +144,15 @@ 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/exchange/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md index b48470c51b..0152794350 100644 --- a/exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-syncmailpublicfolder applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Remove-SyncMailPublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-syncmailpublicfolder +schema: 2.0.0 +title: Remove-SyncMailPublicFolder --- # Remove-SyncMailPublicFolder @@ -45,6 +46,9 @@ This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run thi ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mail-enabled public folder object that you want to remove from Exchange Online. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the mail-enabled public folder object that you Type: MailPublicFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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 @@ -103,13 +110,15 @@ 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/exchange/Remove-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md similarity index 95% rename from exchange/exchange-ps/exchange/Remove-SystemMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md index c61753f2b5..ab15db4962 100644 --- a/exchange/exchange-ps/exchange/Remove-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-systemmessage applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-SystemMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-systemmessage +schema: 2.0.0 +title: Remove-SystemMessage --- # Remove-SystemMessage @@ -52,6 +53,9 @@ This example removes the specified custom quota message (combination of language ## 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 remove. You can use any value that uniquely identifies the system message. For example: - Identity @@ -107,7 +111,6 @@ Maximum number of levels (depth) in a mailbox folder: Type: SystemMessageIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -117,6 +120,9 @@ 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`. @@ -126,7 +132,6 @@ 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 @@ -136,6 +141,9 @@ 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. @@ -144,7 +152,6 @@ 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 @@ -154,13 +161,15 @@ 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/exchange/Remove-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-TenantAllowBlockListItems.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md index 5a329a28e1..7267267e21 100644 --- a/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-tenantallowblocklistitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Remove-TenantAllowBlockListItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-tenantallowblocklistitems +schema: 2.0.0 +title: Remove-TenantAllowBlockListItems --- # Remove-TenantAllowBlockListItems @@ -58,6 +59,9 @@ This example removes the URL allow entry for the specified non-Microsoft phishin ## PARAMETERS ### -Entries + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Entries parameter specifies the entries that you want to remove based on the ListType parameter value. Valid values are: - FileHash: The exact SHA256 file hash value. @@ -75,7 +79,6 @@ You can't use this parameter with the Ids parameter. Type: String[] Parameter Sets: Entries Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -85,6 +88,9 @@ Accept wildcard characters: False ``` ### -Ids + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Ids parameter specifies the entries that you want to remove. This value is shown in the Identity property in the output of the Get-TenantAllowBlockListItems cmdlet. An example value for this parameter is `RgAAAAAI8gSyI_NmQqzeh-HXJBywBwCqfQNJY8hBTbdlKFkv6BcUAAAl_QCZAACqfQNJY8hBTbdlKFkv6BcUAAAl_oSPAAAA0`. @@ -95,7 +101,6 @@ You can't use this parameter with the Entries parameter. Type: String[] Parameter Sets: Ids Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -105,6 +110,9 @@ Accept wildcard characters: False ``` ### -ListType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListType parameter specifies the type of entry that you want to remove. Valid values are: - FileHash @@ -116,7 +124,6 @@ The ListType parameter specifies the type of entry that you want to remove. Vali Type: ListType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -126,6 +133,9 @@ Accept wildcard characters: False ``` ### -ListSubType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListSubType specifies further specifies the type of entry that you want to remove. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. @@ -135,7 +145,6 @@ The ListSubType specifies further specifies the type of entry that you want to r Type: ListSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -145,6 +154,9 @@ 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. @@ -153,7 +165,6 @@ 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/exchange/Remove-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md index dffc5da8d0..735995ab90 100644 --- a/exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-tenantallowblocklistspoofitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Remove-TenantAllowBlockListSpoofItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-tenantallowblocklistspoofitems +schema: 2.0.0 +title: Remove-TenantAllowBlockListSpoofItems --- # Remove-TenantAllowBlockListSpoofItems @@ -44,13 +45,15 @@ This example removes the specified spoofed sender. You get the Ids parameter val ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + Use the value `domain.com\Default` for this parameter. The spoofed sender that you want to remove is really identified by the Ids parameter. ```yaml Type: HostedConnectionFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 0 @@ -60,13 +63,15 @@ Accept wildcard characters: False ``` ### -Ids + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Ids parameter specifies the spoof pair that you want to remove. A valid value for this parameter is the Identity property value from the output of the Get-TenantAllowBlockListSpoofItems cmdlet. You can specify multiple values separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -76,6 +81,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -85,7 +93,6 @@ 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 @@ -95,13 +102,15 @@ 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/exchange/Remove-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md index 98949a3787..2f79236426 100644 --- a/exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-throttlingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-ThrottlingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-throttlingpolicy +schema: 2.0.0 +title: Remove-ThrottlingPolicy --- # Remove-ThrottlingPolicy @@ -63,13 +64,15 @@ You can't remove a policy that's associated with any users. This example reassig ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter identifies the throttling policy you want to remove. Use the name that matches the name of the policy in Active Directory. ```yaml Type: ThrottlingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -79,6 +82,9 @@ 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,7 +94,6 @@ 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,6 +103,9 @@ 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,7 +114,6 @@ 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,6 +123,9 @@ 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. @@ -124,7 +134,6 @@ 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 @@ -134,13 +143,15 @@ 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/exchange/Remove-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md similarity index 89% rename from exchange/exchange-ps/exchange/Remove-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md index 110d9f1322..d9614fda00 100644 --- a/exchange/exchange-ps/exchange/Remove-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-transportrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Remove-TransportRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-transportrule +schema: 2.0.0 +title: Remove-TransportRule --- # Remove-TransportRule @@ -47,6 +48,9 @@ This example removes the rule named "Redirect messages from kim@contoso.com to l ## 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 remove. You can use any value that uniquely identifies the rule. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the rule that you want to remove. 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 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +104,6 @@ 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,13 +113,15 @@ 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/exchange/Remove-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md index 902c636055..2824355637 100644 --- a/exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-umautoattendant applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Remove-UMAutoAttendant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-umautoattendant +schema: 2.0.0 +title: Remove-UMAutoAttendant --- # Remove-UMAutoAttendant @@ -47,13 +48,15 @@ This example deletes 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 deleted. 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: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md index 85003d4509..4818c6698d 100644 --- a/exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-umcallansweringrule applicable: Exchange Server 2013, Exchange Server 2016 -title: Remove-UMCallAnsweringRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-umcallansweringrule +schema: 2.0.0 +title: Remove-UMCallAnsweringRule --- # Remove-UMCallAnsweringRule @@ -55,13 +56,15 @@ This example removes the call answering rule MyUMCallAnsweringRule from the mail ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for a call answering rule being removed. ```yaml Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,6 +113,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Mailbox parameter specifies the UM-enabled mailbox where the call answering rule is changed. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -125,7 +135,6 @@ 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 @@ -135,13 +144,15 @@ 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/exchange/Remove-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-UMDialPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md index 15968a4562..3ce7b61407 100644 --- a/exchange/exchange-ps/exchange/Remove-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-umdialplan applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Remove-UMDialPlan -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-umdialplan +schema: 2.0.0 +title: Remove-UMDialPlan --- # Remove-UMDialPlan @@ -47,13 +48,15 @@ This example deletes the existing UM dial plan MyUMDialPlan. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM dial plan being deleted. This is the directory object ID for the UM dial plan. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-UMHuntGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md index 0923af3a69..c15b1b186d 100644 --- a/exchange/exchange-ps/exchange/Remove-UMHuntGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-umhuntgroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Remove-UMHuntGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-umhuntgroup +schema: 2.0.0 +title: Remove-UMHuntGroup --- # Remove-UMHuntGroup @@ -47,13 +48,15 @@ This example deletes the UM hunt group MyUMHuntGroup. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM hunt group being deleted. This is the directory object ID for the UM hunt group object. ```yaml Type: UMHuntGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md index e19873e3a1..203e9b6e23 100644 --- a/exchange/exchange-ps/exchange/Remove-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-umipgateway applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Remove-UMIPGateway -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-umipgateway +schema: 2.0.0 +title: Remove-UMIPGateway --- # Remove-UMIPGateway @@ -49,13 +50,15 @@ This example deletes 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 deleted. ```yaml Type: UMIPGatewayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Remove-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md index 56d19d3378..607006795d 100644 --- a/exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ummailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Remove-UMMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ummailboxpolicy +schema: 2.0.0 +title: Remove-UMMailboxPolicy --- # Remove-UMMailboxPolicy @@ -47,13 +48,15 @@ This example deletes the UM mailbox policy MyUMMailboxPolicy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM mailbox policy being deleted. This parameter 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: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Remove-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedAuditLogRetentionPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedAuditLogRetentionPolicy.md index ed810f1d9c..5b3ac6528c 100644 --- a/exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedAuditLogRetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedauditlogretentionpolicy applicable: Security & Compliance -title: Remove-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedauditlogretentionpolicy +schema: 2.0.0 +title: Remove-UnifiedAuditLogRetentionPolicy --- # Remove-UnifiedAuditLogRetentionPolicy @@ -46,6 +47,9 @@ This example deletes the audit log retention policy named "SearchQueryPerformed ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the audit log retention policy that you want to delete. You can use any value that uniquely identifies the policy. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the audit log retention policy that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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 @@ -85,13 +90,15 @@ 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,13 +108,15 @@ Accept wildcard characters: False ``` ### -ForceDeletion + +> Applicable: Security & Compliance + The ForceDeletion switch forces the removal of the policy. 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 @@ -117,13 +126,15 @@ 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/exchange/Remove-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/Remove-UnifiedGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md index 8c186032fb..5badcba7ec 100644 --- a/exchange/exchange-ps/exchange/Remove-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedgroup applicable: Exchange Online, Exchange Online Protection -title: Remove-UnifiedGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedgroup +schema: 2.0.0 +title: Remove-UnifiedGroup --- # Remove-UnifiedGroup @@ -47,6 +48,9 @@ This example removes the Microsoft 365 Group named Research Department. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the Microsoft 365 Group that you want to remove. You can use any value that uniquely identifies the Microsoft 365 Group. For example: - Name @@ -60,7 +64,6 @@ The Identity parameter specifies the Microsoft 365 Group that you want to remove Type: UnifiedGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -70,6 +73,9 @@ 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,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -97,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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/exchange/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md similarity index 94% rename from exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md index f6ae947e09..6f9314fc19 100644 --- a/exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedgrouplinks applicable: Exchange Online, Exchange Online Protection -title: Remove-UnifiedGroupLinks -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-unifiedgrouplinks +schema: 2.0.0 +title: Remove-UnifiedGroupLinks --- # Remove-UnifiedGroupLinks @@ -47,6 +48,9 @@ This example removes members `laura@contoso.com` and `julia@contoso.com` from th ## 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 @@ -60,7 +64,6 @@ 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 @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -Links + +> Applicable: Exchange Online, Exchange Online Protection + The Links parameter specifies the recipients to remove from the Microsoft 365 Group. You specify whether these recipients were members, owners, or subscribers by using the LinkType parameter. You can use any value that uniquely identifies the recipient. For example: @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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 remove. Valid values are: - Members: Participate in conversations, create Teams channels, collaborate on files, and edit the connected SharePoint site. @@ -111,7 +119,6 @@ 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 @@ -121,6 +128,9 @@ 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`. @@ -130,7 +140,6 @@ 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,13 +149,15 @@ 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/exchange/Remove-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md similarity index 92% rename from exchange/exchange-ps/exchange/Remove-UserPhoto.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md index fa074e42db..b8b326398b 100644 --- a/exchange/exchange-ps/exchange/Remove-UserPhoto.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-userphoto applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-UserPhoto -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-userphoto +schema: 2.0.0 +title: Remove-UserPhoto --- # Remove-UserPhoto @@ -65,6 +66,9 @@ This example deletes the photo associated with Ann Beebe's user account. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: - Name @@ -82,7 +86,6 @@ The Identity parameter specifies the identity of the user. You can use any value Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -92,6 +95,9 @@ Accept wildcard characters: False ``` ### -ClearMailboxPhotoRecord + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ClearMailboxPhoto switch specifies that a deleted mailbox photo is considered blank instead of deleted. You don't need to specify a value with this switch. By default, when a user deletes their mailbox photo, a flag is set on the mailbox that causes subsequent photo requests to: @@ -105,7 +111,6 @@ Using this switch allows photo requests to search Active Directory for a photo. Type: SwitchParameter Parameter Sets: ClearMailboxPhoto Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -115,6 +120,9 @@ 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`. @@ -124,7 +132,6 @@ 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 @@ -134,13 +141,15 @@ 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 @@ -150,13 +159,15 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ClearMailboxPhoto Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -166,6 +177,9 @@ 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: @@ -177,7 +191,6 @@ 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 @@ -187,13 +200,15 @@ 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: ClearMailboxPhoto Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -203,13 +218,15 @@ 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/exchange/Remove-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-VivaModuleFeaturePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md index e263889a41..9caff52514 100644 --- a/exchange/exchange-ps/exchange/Remove-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-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/remove-vivamodulefeaturepolicy applicable: Exchange Online -title: Remove-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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-vivamodulefeaturepolicy +schema: 2.0.0 +title: Remove-VivaModuleFeaturePolicy --- # Remove-VivaModuleFeaturePolicy @@ -56,6 +56,9 @@ This example deletes the specified policy for the Reflection feature in Viva Ins ## PARAMETERS ### -FeatureId + +> Applicable: Exchange Online + The FeatureId parameter specifies the feature in the Viva module that you want to remove the policy from. 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. @@ -64,7 +67,6 @@ 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 @@ -74,13 +76,15 @@ Accept wildcard characters: False ``` ### -ModuleId + +> Applicable: Exchange Online + The ModuleId parameter specifies the Viva module of the feature that you want to remove the policy from. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -90,6 +94,9 @@ Accept wildcard characters: False ``` ### -PolicyId + +> Applicable: Exchange Online + The PolicyId parameter specifies the policy for the feature in the Viva module that you want to remove. To view details about the added policies for a feature in a Viva module, refer to the Get-VivaModuleFeaturePolicy cmdlet. The details provided by the Get-VivaModuleFeaturePolicy cmdlet include the policy identifier. @@ -98,7 +105,6 @@ To view details about the added policies for a feature in a Viva module, refer t Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -108,6 +114,9 @@ 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`. @@ -117,7 +126,6 @@ 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 @@ -127,13 +135,15 @@ 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 @@ -143,13 +153,15 @@ 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/exchange/Remove-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaOrgInsightsDelegatedRole.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-VivaOrgInsightsDelegatedRole.md index 037e2a9216..5602ecfe9d 100644 --- a/exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaOrgInsightsDelegatedRole.md @@ -1,12 +1,12 @@ --- +author: chrisda external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement +Locale: en-US +Module Name: ExchangePowerShell +ms.author: chrisda online version: https://learn.microsoft.com/powershell/module/exchange/remove-vivaorginsightsdelegatedrole -title: Remove-VivaOrgInsightsDelegatedRole schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: +title: Remove-VivaOrgInsightsDelegatedRole --- # Remove-VivaOrgInsightsDelegatedRole @@ -49,6 +49,9 @@ This example removes the organization insights viewing capability of the specifi ## 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. @@ -57,7 +60,6 @@ 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,6 +69,9 @@ 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. @@ -75,7 +80,6 @@ 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 @@ -85,13 +89,15 @@ 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/exchange/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md similarity index 90% rename from exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md index f4f42ba089..fe93da947f 100644 --- a/exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-webservicesvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-WebServicesVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-webservicesvirtualdirectory +schema: 2.0.0 +title: Remove-WebServicesVirtualDirectory --- # Remove-WebServicesVirtualDirectory @@ -46,6 +47,9 @@ This example removes the Exchange Web Services virtual directory named Sales fro ## 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 remove. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -58,7 +62,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ 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,7 +83,6 @@ 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 @@ -87,13 +92,15 @@ 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 @@ -103,6 +110,9 @@ 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. @@ -111,7 +121,6 @@ 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 @@ -121,13 +130,15 @@ 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/exchange/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md similarity index 91% rename from exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md index f6c5c5dddd..bf80af9efa 100644 --- a/exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-x400authoritativedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Remove-X400AuthoritativeDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-x400authoritativedomain +schema: 2.0.0 +title: Remove-X400AuthoritativeDomain --- # Remove-X400AuthoritativeDomain @@ -43,13 +44,15 @@ This example removes the X.400 authoritative domain object for the X.400 authori ## 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 X.400 authoritative domain. ```yaml Type: X400AuthoritativeDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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 @@ -78,6 +83,9 @@ 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,7 +94,6 @@ 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 @@ -96,13 +103,15 @@ 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/exchange/Remove-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/ExchangePowerShell/Remove-eDiscoveryCaseAdmin.md similarity index 96% rename from exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md rename to exchange/exchange-ps/ExchangePowerShell/Remove-eDiscoveryCaseAdmin.md index 828137cfb4..7cd34f3080 100644 --- a/exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-eDiscoveryCaseAdmin.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/remove-ediscoverycaseadmin applicable: Security & Compliance -title: Remove-eDiscoveryCaseAdmin -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/remove-ediscoverycaseadmin +schema: 2.0.0 +title: Remove-eDiscoveryCaseAdmin --- # Remove-eDiscoveryCaseAdmin @@ -46,6 +47,9 @@ This example removes an eDiscovery Administrator. ## PARAMETERS ### -User + +> Applicable: Security & Compliance + The User parameter specifies the user that you want to remove from the list of eDiscovery Administrators. You can use any value that uniquely identifies the user. For example: - Name @@ -57,7 +61,6 @@ The User parameter specifies the user that you want to remove from the list of e Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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,13 +91,15 @@ 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/exchange/Reset-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md similarity index 92% rename from exchange/exchange-ps/exchange/Reset-ProvisioningCache.md rename to exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md index 0c541d75c8..e5d12eb3ce 100644 --- a/exchange/exchange-ps/exchange/Reset-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/reset-provisioningcache applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Reset-ProvisioningCache -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/reset-provisioningcache +schema: 2.0.0 +title: Reset-ProvisioningCache --- # Reset-ProvisioningCache @@ -67,13 +68,15 @@ This example runs in a multi-tenant deployment by a data center administrator to ## 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 @@ -83,6 +86,9 @@ 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 @@ -96,7 +102,6 @@ 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 @@ -106,13 +111,15 @@ Accept wildcard characters: False ``` ### -GlobalCache + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GlobalCache switch clears all cache keys. 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,6 +129,9 @@ 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. @@ -130,7 +140,6 @@ 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 @@ -140,6 +149,9 @@ 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`. @@ -149,7 +161,6 @@ 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 @@ -159,13 +170,15 @@ Accept wildcard characters: False ``` ### -CurrentOrganization + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CurrentOrganization switch resets the provision cache for the 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 @@ -175,13 +188,15 @@ 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 @@ -191,13 +206,15 @@ 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/exchange/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md similarity index 90% rename from exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md index e7ed934cf1..2f2150bf9f 100644 --- a/exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/restore-databaseavailabilitygroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Restore-DatabaseAvailabilityGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/restore-databaseavailabilitygroup +schema: 2.0.0 +title: Restore-DatabaseAvailabilityGroup --- # Restore-DatabaseAvailabilityGroup @@ -65,13 +66,15 @@ This example activates member servers in the DAG DAG1 for the Active Directory s ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the DAG being manipulated. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,13 +84,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectorySite + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectorySite parameter specifies the site containing the DAG members to be restored. ```yaml Type: AdSiteIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -97,13 +102,15 @@ Accept wildcard characters: False ``` ### -AlternateWitnessDirectory + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AlternateWitnessDirectory parameter specifies the name of an alternate directory used to store witness data. The specified directory must not be in use by any other DAGs or used for any other purpose. This value can be populated ahead by using the Set-DatabaseAvailabilityGroup cmdlet. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -113,13 +120,15 @@ Accept wildcard characters: False ``` ### -AlternateWitnessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AlternateWitnessServer parameter specifies the name of a new witness server for the DAG as part of a site activation process. This value can be populated ahead by using the Set-DatabaseAvailabilityGroup cmdlet. ```yaml Type: FileShareWitnessServerName Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -129,6 +138,9 @@ 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,7 +152,6 @@ 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 @@ -150,13 +161,15 @@ 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 @@ -166,13 +179,15 @@ Accept wildcard characters: False ``` ### -UsePrimaryWitnessServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UsePrimaryWitnessServer switch specifies that the DAG's currently configured witness server should be used if a witness is needed by the DAG members that are being activated. 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 @@ -182,13 +197,15 @@ 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/exchange/Restore-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md similarity index 91% rename from exchange/exchange-ps/exchange/Restore-DetailsTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md index c064436cf5..cab0ebafd3 100644 --- a/exchange/exchange-ps/exchange/Restore-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/restore-detailstemplate applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Restore-DetailsTemplate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/restore-detailstemplate +schema: 2.0.0 +title: Restore-DetailsTemplate --- # Restore-DetailsTemplate @@ -45,6 +46,9 @@ This example restores the default attributes to the User details template for th ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the GUID or specifies the details template type and language separated by a backslash, for example, en-us\\User. Details template types include: - User @@ -58,7 +62,6 @@ The Identity parameter specifies the GUID or specifies the details template type Type: DetailsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -68,6 +71,9 @@ 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,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/Restore-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md similarity index 94% rename from exchange/exchange-ps/exchange/Restore-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md index 8e775b1697..189ebe07d7 100644 --- a/exchange/exchange-ps/exchange/Restore-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/restore-mailbox applicable: Exchange Server 2010 -title: Restore-Mailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/restore-mailbox +schema: 2.0.0 +title: Restore-Mailbox --- # Restore-Mailbox @@ -83,6 +84,9 @@ This example bulk restores all the mailboxes in the MyDatabase mailbox database ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the mailbox that you want to restore. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -100,7 +104,6 @@ The Identity parameter specifies the mailbox that you want to restore. You can u Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -110,6 +113,9 @@ Accept wildcard characters: False ``` ### -RecoveryDatabase + +> Applicable: Exchange Server 2010 + The RecoveryDatabase parameter specifies the recovery database where you are restoring the mailbox from. You can use any value that uniquely identifies the database. For example: - Name @@ -120,7 +126,6 @@ The RecoveryDatabase parameter specifies the recovery database where you are res Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -130,6 +135,9 @@ Accept wildcard characters: False ``` ### -RecoveryMailbox + +> Applicable: Exchange Server 2010 + The RecoveryMailbox parameter specifies the mailbox to be used as the source mailbox. This parameter is required if the source mailbox is different from the target mailbox. You identify the mailbox by its GUID value. You can find the GUID value by using the Get-Mailbox or Get-MailboxStatistics cmdlets. @@ -138,7 +146,6 @@ You identify the mailbox by its GUID value. You can find the GUID value by using Type: StoreMailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -148,13 +155,15 @@ Accept wildcard characters: False ``` ### -TargetFolder + +> Applicable: Exchange Server 2010 + The TargetFolder parameter specifies the mailbox folder that's created on the mailbox specified. This parameter is required if the mailbox being restored is different from the target mailbox. (For example, the value specified with the Identity parameter isn't the same as the value specified with the RecoveryMailbox parameter.) In this case, the Restore-Mailbox command performs a merge. If the values are the same, the TargetFolder parameter isn't required. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -164,6 +173,9 @@ Accept wildcard characters: False ``` ### -AllowDuplicates + +> Applicable: Exchange Server 2010 + The AllowDuplicates switch copies mail items without checking if they're duplicates of existing items and without removing duplicate items. You don't need to specify a value with this switch. We recommend that you use this switch with the IncludeFolders parameter. @@ -172,7 +184,6 @@ We recommend that you use this switch with the IncludeFolders parameter. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -182,6 +193,9 @@ Accept wildcard characters: False ``` ### -AllContentKeywords + +> Applicable: Exchange Server 2010 + The AllContentKeywords parameter specifies the filters for all of the following: - Subject @@ -194,7 +208,6 @@ This allows an OR search of all these fields. If your search criteria are part o Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -204,13 +217,15 @@ Accept wildcard characters: False ``` ### -AttachmentFilenames + +> Applicable: Exchange Server 2010 + The AttachmentFilenames parameter specifies the filter for the attachment file name. You can use wildcard characters in the string. For example, you can use \*.txt to export items that have a .txt extension. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -220,13 +235,15 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010 + The BadItemLimit parameter specifies the number of corrupted items in a mailbox to skip before the export operation fails. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -236,6 +253,9 @@ 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`. @@ -245,7 +265,6 @@ 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 @@ -255,13 +274,15 @@ Accept wildcard characters: False ``` ### -ContentKeywords + +> Applicable: Exchange Server 2010 + The ContentKeywords parameter specifies the keyword filters for the message body and content of attachments in the source mailbox. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -271,13 +292,15 @@ Accept wildcard characters: False ``` ### -EndDate + +> Applicable: Exchange Server 2010 + The EndDate parameter specifies the end date for filtering content that will be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010. ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -287,13 +310,15 @@ Accept wildcard characters: False ``` ### -ExcludeFolders + +> Applicable: Exchange Server 2010 + The ExcludeFolders parameter specifies the list of folders to exclude during the export. Folders are excluded as they're entered. They aren't localized. For example, excluding calendar only excludes calendar in English because calendar in other languages is a different word. ```yaml Type: MapiFolderPath[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -303,13 +328,15 @@ Accept wildcard characters: False ``` ### -GlobalCatalog + +> Applicable: Exchange Server 2010 + The GlobalCatalog parameter specifies the global catalog to use to search for the target mailbox. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -319,13 +346,15 @@ Accept wildcard characters: False ``` ### -IncludeFolders + +> Applicable: Exchange Server 2010 + The IncludeFolders parameter specifies the list of folders to include during the export. Folders are included as they're entered. They aren't localized. For example, including calendar only includes calendar in English because calendar in other languages is a different word. ```yaml Type: MapiFolderPath[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -335,13 +364,15 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Server 2010 + The Locale parameter specifies the locale setting on a message to restore. With this filter set, only messages with the specified locale setting are extracted. ```yaml Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -351,13 +382,15 @@ Accept wildcard characters: False ``` ### -MaxThreads + +> Applicable: Exchange Server 2010 + The MaxThreads parameter specifies the maximum number of threads to use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -367,13 +400,15 @@ Accept wildcard characters: False ``` ### -RecipientKeywords + +> Applicable: Exchange Server 2010 + The RecipientKeywords parameter specifies the keyword filters for recipients of items in the source mailbox. This filter finds the search string even if it's part of a word. This isn't a whole word search. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -383,13 +418,15 @@ Accept wildcard characters: False ``` ### -SenderKeywords + +> Applicable: Exchange Server 2010 + The SenderKeywords parameter specifies the keyword filters for senders of items in the source mailbox. This filter finds the search string even if it's part of a word. This isn't a whole word search. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -399,13 +436,15 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Server 2010 + The StartDate parameter specifies the start date. The start date must be before the end date. ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -415,13 +454,15 @@ Accept wildcard characters: False ``` ### -SubjectKeywords + +> Applicable: Exchange Server 2010 + The SubjectKeywords parameter specifies the keyword filters for subjects of items in the source mailbox. This filter finds the search string even if it's part of a word. This isn't a whole word search. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -431,6 +472,9 @@ Accept wildcard characters: False ``` ### -ValidateOnly + +> Applicable: Exchange Server 2010 + The ValidateOnly switch tells the command to evaluate the conditions and requirements necessary to perform the operation, and then report 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. @@ -439,7 +483,6 @@ No changes are made when you use this switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -449,13 +492,15 @@ 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/exchange/Restore-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md similarity index 92% rename from exchange/exchange-ps/exchange/Restore-RecoverableItems.md rename to exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md index 5132660f97..0d5cf92b70 100644 --- a/exchange/exchange-ps/exchange/Restore-RecoverableItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/restore-recoverableitems applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Restore-RecoverableItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/restore-recoverableitems +schema: 2.0.0 +title: Restore-RecoverableItems --- # Restore-RecoverableItems @@ -119,6 +120,9 @@ This example bulk restores all the recoverable items for administrator. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox that contains the deleted items that you want to restore. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -136,9 +140,8 @@ In Exchange Online, you can specify multiple mailboxes separated by commas. If t ```yaml Type: GeneralMailboxOrMailUserIdParameter -Parameter Sets: OnPremises +Parameter Sets: OnPremises, Cloud Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -147,20 +150,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: GeneralMailboxOrMailUserIdParameter[] -Parameter Sets: Cloud -Aliases: -Applicable: Exchange Online +### -EntryID -Required: False -Position: 1 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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.). @@ -169,7 +162,6 @@ 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 @@ -179,6 +171,9 @@ 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". @@ -187,7 +182,6 @@ 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 @@ -197,6 +191,9 @@ 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) @@ -209,7 +206,6 @@ 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 @@ -219,6 +215,9 @@ 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". @@ -227,7 +226,6 @@ 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 @@ -237,13 +235,15 @@ 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 @@ -253,6 +253,9 @@ 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. @@ -263,7 +266,6 @@ 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 @@ -273,6 +275,9 @@ Accept wildcard characters: False ``` ### -NoOutput + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The NoOutput switch restores the deleted items directly without any command output in the console. You don't need to specify a value with this switch. @@ -281,7 +286,6 @@ The NoOutput switch restores the deleted items directly without any command outp Type: SwitchParameter Parameter Sets: Cloud Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -291,6 +295,9 @@ Accept wildcard characters: False ``` ### -PolicyTag + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill PolicyTag Description }} @@ -299,7 +306,6 @@ This parameter is available only in the cloud-based service. Type: String[] Parameter Sets: Default Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -309,6 +315,9 @@ Accept wildcard characters: False ``` ### -RestoreTargetFolder + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The RestoreTargetFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure. @@ -327,7 +336,6 @@ The preceding or trailing `/` will be ignored. Then, it will be treated as the r Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -337,13 +345,15 @@ 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 @@ -353,6 +363,9 @@ 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. @@ -367,7 +380,6 @@ If you don't use this parameter, the command searches those three folders. Type: RecoverableItemsFolderType Parameter Sets: OnPrem Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -377,13 +389,15 @@ Accept wildcard characters: False ``` ### -SubjectContains + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SubjectContains parameter filters the deleted 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/exchange/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md similarity index 90% rename from exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md index fd5c0c4ae9..edf11e3e81 100644 --- a/exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxdatabasecopy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-MailboxDatabaseCopy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxdatabasecopy +schema: 2.0.0 +title: Resume-MailboxDatabaseCopy --- # Resume-MailboxDatabaseCopy @@ -65,13 +66,15 @@ This example resumes replication and replay activity for the copy of the databas ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the database whose copying is being resumed. ```yaml Type: DatabaseCopyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,6 +84,9 @@ 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`. @@ -90,7 +96,6 @@ 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 @@ -100,13 +105,15 @@ Accept wildcard characters: False ``` ### -DisableReplayLag + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DisableReplayLag switch disables any configured replay lag time for the database copy when the passive copy is resumed. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: DisableReplayLag Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -116,13 +123,15 @@ Accept wildcard characters: False ``` ### -DisableReplayLagReason + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DisableReplayLagReason parameter is used with the DisableReplayLag parameter to specify an administrative reason for disabling replay lag time for a passive copy. ```yaml Type: String Parameter Sets: DisableReplayLag Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,13 +141,15 @@ 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,13 +159,15 @@ Accept wildcard characters: False ``` ### -ReplicationOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplicationOnly switch resumes replication without affecting the activation setting (for example, the ActivationSuspended property for the database copy remains set to True). 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 @@ -164,13 +177,15 @@ 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/exchange/Resume-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md index 48f67e84d6..ad87264ed4 100644 --- a/exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxexportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-MailboxExportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxexportrequest +schema: 2.0.0 +title: Resume-MailboxExportRequest --- # Resume-MailboxExportRequest @@ -54,13 +55,15 @@ This example resumes any failed export move requests. ## 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). Use the following syntax: `Alias\Name`. ```yaml Type: MailboxExportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -70,6 +73,9 @@ 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,7 +85,6 @@ 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,13 +94,15 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/Resume-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md index f1d190bae5..981901c97a 100644 --- a/exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboximportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Resume-MailboxImportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboximportrequest +schema: 2.0.0 +title: Resume-MailboxImportRequest --- # Resume-MailboxImportRequest @@ -56,13 +57,15 @@ This example resumes all failed import requests. ## 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 created the request using the Name parameter, use the following syntax: `Alias\Name`. ```yaml Type: MailboxImportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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,7 +107,6 @@ 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,13 +116,15 @@ 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/exchange/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md index b7faf00b00..9c987fd7f4 100644 --- a/exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxrestorerequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Resume-MailboxRestoreRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-mailboxrestorerequest +schema: 2.0.0 +title: Resume-MailboxRestoreRequest --- # Resume-MailboxRestoreRequest @@ -50,6 +51,9 @@ This example resumes any restore request with the status of Failed. ## 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). @@ -58,7 +62,6 @@ If you didn't specify a name for the restore request when it was created, Exchan Type: MailboxRestoreRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -68,6 +71,9 @@ 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`. @@ -77,7 +83,6 @@ 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,6 +92,9 @@ 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,7 +103,6 @@ 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,13 +112,15 @@ 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/exchange/Resume-Message.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md similarity index 92% rename from exchange/exchange-ps/exchange/Resume-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-Message.md index 3015c97f9a..5be233cfd3 100644 --- a/exchange/exchange-ps/exchange/Resume-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-message applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-Message -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-message +schema: 2.0.0 +title: Resume-Message --- # Resume-Message @@ -58,13 +59,15 @@ This example resumes delivery of all messages in a suspended state and for which ## 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: True Position: 1 @@ -74,6 +77,9 @@ 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 ("). @@ -82,7 +88,6 @@ 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: True Position: Named @@ -92,6 +97,9 @@ 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`. @@ -101,7 +109,6 @@ 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 @@ -111,6 +118,9 @@ 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 @@ -126,7 +136,6 @@ 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 @@ -136,13 +145,15 @@ 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/exchange/Resume-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Resume-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md index 81384c86be..44625d4a17 100644 --- a/exchange/exchange-ps/exchange/Resume-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-moverequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Resume-MoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-moverequest +schema: 2.0.0 +title: Resume-MoveRequest --- # Resume-MoveRequest @@ -59,6 +60,9 @@ This example resumes any move requests that have the suspend comment "Resume aft ## 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 the following values: - GUID @@ -73,7 +77,6 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c Type: MoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -83,6 +86,9 @@ 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`. @@ -92,7 +98,6 @@ 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 @@ -102,6 +107,9 @@ 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,7 +118,6 @@ 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 @@ -120,6 +127,9 @@ Accept wildcard characters: False ``` ### -ProxyToMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ProxyToMailbox parameter specifies the move destination by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example: @@ -139,7 +149,6 @@ The ProxyToMailbox parameter specifies the move destination by the location of t Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -149,6 +158,9 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendWhenReadyToComplete switch suspends the move request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch. Instead of this switch, we recommend using the Set-MoveRequest cmdlet with the CompleteAfter parameter. @@ -157,7 +169,6 @@ Instead of this switch, we recommend using the Set-MoveRequest cmdlet with the C Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -167,13 +178,15 @@ 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/exchange/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md similarity index 93% rename from exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md index 42768b7cfb..0674293078 100644 --- a/exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfoldermigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-PublicFolderMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfoldermigrationrequest +schema: 2.0.0 +title: Resume-PublicFolderMigrationRequest --- # Resume-PublicFolderMigrationRequest @@ -52,6 +53,9 @@ This example resumes any failed migration requests. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the migration request that you want to resume. You can use the following values: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the migration request that you want to resume. Type: PublicFolderMigrationRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,13 +95,15 @@ 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 @@ -106,13 +113,15 @@ 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/exchange/Resume-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md similarity index 93% rename from exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md index af943a8370..4b5d3dd858 100644 --- a/exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfoldermoverequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-PublicFolderMoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfoldermoverequest +schema: 2.0.0 +title: Resume-PublicFolderMoveRequest --- # Resume-PublicFolderMoveRequest @@ -57,13 +58,15 @@ This example resumes a move request that has the suspend comment "Resume after 1 ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the public folder move request. The default identity is \\PublicFolderMove. ```yaml Type: PublicFolderMoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,13 +115,15 @@ 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/exchange/Resume-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md similarity index 96% rename from exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md index a781b34c89..c2e5b71916 100644 --- a/exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfolderreplication applicable: Exchange Server 2010 -title: Resume-PublicFolderReplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-publicfolderreplication +schema: 2.0.0 +title: Resume-PublicFolderReplication --- # Resume-PublicFolderReplication @@ -42,6 +43,9 @@ This example resumes content replication for the entire organization. ## PARAMETERS ### -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`. @@ -51,7 +55,6 @@ 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 @@ -61,13 +64,15 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Resume-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md similarity index 91% rename from exchange/exchange-ps/exchange/Resume-Queue.md rename to exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md index 43bb312d87..64ef045058 100644 --- a/exchange/exchange-ps/exchange/Resume-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/resume-queue applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Resume-Queue -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/resume-queue +schema: 2.0.0 +title: Resume-Queue --- # Resume-Queue @@ -54,13 +55,15 @@ This example resumes processing of all queues where the NextHopDomain is Fourthc ## 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: True Position: 1 @@ -70,6 +73,9 @@ 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 ("). @@ -78,7 +84,6 @@ 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: True Position: Named @@ -88,6 +93,9 @@ 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,7 +105,6 @@ 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,6 +114,9 @@ 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,7 +132,6 @@ 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 @@ -132,13 +141,15 @@ 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/exchange/Retry-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md similarity index 91% rename from exchange/exchange-ps/exchange/Retry-Queue.md rename to exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md index c34b537241..c3d1a00058 100644 --- a/exchange/exchange-ps/exchange/Retry-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/retry-queue applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Retry-Queue -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/retry-queue +schema: 2.0.0 +title: Retry-Queue --- # Retry-Queue @@ -60,13 +61,15 @@ This example forces a connection attempt for all queues that meet the following ## 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: True Position: 1 @@ -76,6 +79,9 @@ 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 ("). @@ -84,7 +90,6 @@ 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: True Position: Named @@ -94,6 +99,9 @@ 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,7 +111,6 @@ 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,13 +120,15 @@ Accept wildcard characters: False ``` ### -Resubmit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Resubmit parameter specifies whether the queue contents should be resubmitted to the categorizer before a connection is established. Valid input for this parameter is $true or $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 @@ -129,6 +138,9 @@ 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 @@ -144,7 +156,6 @@ 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 @@ -154,13 +165,15 @@ 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/exchange/Rotate-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md index d424e6898b..deb6be57a5 100644 --- a/exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/rotate-dkimsigningconfig applicable: Exchange Online, Exchange Online Protection -title: Rotate-DkimSigningConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/rotate-dkimsigningconfig +schema: 2.0.0 +title: Rotate-DkimSigningConfig --- # Rotate-DkimSigningConfig @@ -43,6 +44,9 @@ This example rotates the DKIM signing policy for the contoso.com domain. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the DKIM signing policy that you want to rotate. You can use any value that uniquely identifies the policy. For example: - Name: The domain name (for example, contoso.com). @@ -53,7 +57,6 @@ The Identity parameter specifies the DKIM signing policy that you want to rotate Type: DkimSigningConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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 @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ 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/exchange/Search-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md similarity index 87% rename from exchange/exchange-ps/exchange/Search-AdminAuditLog.md rename to exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md index f42ad8e781..cdbe4c3e87 100644 --- a/exchange/exchange-ps/exchange/Search-AdminAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/search-adminauditlog applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: Search-AdminAuditLog -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/search-adminauditlog +schema: 2.0.0 +title: Search-AdminAuditLog --- # Search-AdminAuditLog @@ -94,6 +95,9 @@ This example returns entries in the administrator audit log of an Exchange Onlin ## PARAMETERS ### -Cmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Cmdlets parameter filters the results by the cmdlets that were used. You can specify multiple cmdlets separated by commas. In the results of this cmdlet, this property is named **CmdletName**. @@ -102,7 +106,6 @@ In the results of this cmdlet, this property is named **CmdletName**. 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 @@ -112,6 +115,9 @@ 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. @@ -120,7 +126,6 @@ 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,6 +135,9 @@ Accept wildcard characters: False ``` ### -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". @@ -145,7 +153,6 @@ In the results of this cmdlet, the date/time when the change was made (the cmdle 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: False Position: Named @@ -155,6 +162,9 @@ 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 filters the results by changes that were made (cmdlets that were run) by users outside of your organization. Valid values are: - $true: Only return audit log entries where the change was made by an external user. In Exchange Online, use value to return audit log entries for changes that were made by Microsoft datacenter administrators. @@ -164,7 +174,6 @@ The ExternalAccess parameter filters the results by changes that were made (cmdl 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 @@ -174,6 +183,9 @@ Accept wildcard characters: False ``` ### -IsSuccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The IsSuccess parameter filters the results by whether the changes were successful. Valid values are: - $true: Only return audit log entries where the change was successful (in other words, the cmdlet ran successfully). @@ -185,7 +197,6 @@ In the results of this cmdlet, this property is named **Succeeded**. Type: Boolean 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 @@ -195,6 +206,9 @@ 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 filters the results by the object that was modified (the mailbox, public folder, Send connector, transport rule, accepted domain, etc. that the cmdlet operated on). A valid value depends on how the object is represented in the audit log. For example: - Name @@ -209,7 +223,6 @@ 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, Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -219,6 +232,9 @@ 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 filters the results by the parameters that were used. You can only use this parameter with the Cmdlets parameter (you can't use it by itself). You can specify multiple parameters separated by commas. In the results of this cmdlet, this property is named **CmdletParameters** @@ -227,7 +243,6 @@ In the results of this cmdlet, this property is named **CmdletParameters** 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 @@ -237,6 +252,9 @@ 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. The default value is 1000. The maximum results to return is 250,000. @@ -245,7 +263,6 @@ The maximum results to return is 250,000. Type: Int32 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 @@ -255,6 +272,9 @@ 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". @@ -270,7 +290,6 @@ In the results of this cmdlet, the date/time when the change was made (the cmdle 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: False Position: Named @@ -280,13 +299,15 @@ Accept wildcard characters: False ``` ### -StartIndex + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The StartIndex parameter specifies the position in the result set where the displayed results start. ```yaml Type: Int32 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 @@ -296,6 +317,9 @@ 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 filters the results by the user who made the change (who ran the cmdlet). A typical value for this parameter is the user principal name (UPN; for example, helpdesk@contoso.com). But, updates that were made by system accounts without email addresses might use the Domain\\Username syntax (for example, NT AUTHORITY\SYSTEM (MSExchangeHMHost)). @@ -308,7 +332,6 @@ In the results of this cmdlet, this property is named **Caller** 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/exchange/Search-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/Search-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md index 942951ea8b..f6433b794c 100644 --- a/exchange/exchange-ps/exchange/Search-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/search-mailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Search-Mailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/search-mailbox +schema: 2.0.0 +title: Search-Mailbox --- # Search-Mailbox @@ -115,6 +116,9 @@ This example searches all mailboxes in your organization for messages that conta ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the mailbox to search. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -132,7 +136,6 @@ The Identity parameter specifies the identity of the mailbox to search. You can Type: MailboxOrMailUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -142,6 +145,9 @@ Accept wildcard characters: False ``` ### -EstimateResultOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EstimateResultOnly switch returns only an estimate of the total number and size of messages. Messages aren't copied to the target mailbox. You don't need to specify a value with this switch. You can't use this switch with the TargetMailbox parameter. @@ -150,7 +156,6 @@ You can't use this switch with the TargetMailbox parameter. Type: SwitchParameter Parameter Sets: EstimateResult Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -160,13 +165,15 @@ Accept wildcard characters: False ``` ### -TargetFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetFolder parameter specifies a folder name in which search results are saved in the target mailbox. The folder is created in the target mailbox upon execution. ```yaml Type: String Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -176,6 +183,9 @@ Accept wildcard characters: False ``` ### -TargetMailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetMailbox parameter specifies the destination mailbox where search results are copied. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -195,7 +205,6 @@ You must use this parameter with the TargetFolder parameter. You can't use this Type: MailboxIdParameter Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -205,6 +214,9 @@ 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`. @@ -214,7 +226,6 @@ 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 @@ -224,6 +235,9 @@ Accept wildcard characters: False ``` ### -DeleteContent + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **Note**: You need to be assigned the Mailbox Import Export management role to use this switch. By default, this role isn't assigned to any role group (including Organization Management). Typically, you assign a role to a built-in or custom role group. The DeleteContent switch specifies that the messages returned by the search be permanently deleted from the source mailbox. You don't need to specify a value with this switch. @@ -236,7 +250,6 @@ Before you use the DeleteContent switch to delete content, we recommend that you Type: SwitchParameter Parameter Sets: Mailbox, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -246,13 +259,15 @@ 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 @@ -262,6 +277,9 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DoNotIncludeArchive switch specifies that the user's archive mailbox shouldn't be included in the search. You don't need to specify a value for this switch. By default, the archive mailbox is always searched. @@ -272,7 +290,6 @@ If auto-expanding archiving is enabled for an Exchange Online mailbox, only the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -282,6 +299,9 @@ 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 hide the confirmation prompt when you use the DeleteContent switch to permanently delete messages. @@ -290,7 +310,6 @@ Use this switch to hide the confirmation prompt when you use the DeleteContent s Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -300,13 +319,15 @@ Accept wildcard characters: False ``` ### -IncludeUnsearchableItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IncludeUnsearchableItems switch includes items that couldn't be indexed by Exchange Search in the search 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 @@ -316,6 +337,9 @@ Accept wildcard characters: False ``` ### -LogLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogLevel parameter specifies the logging level for the search. It can have one of the following values: - Suppress: No logs are kept. @@ -330,7 +354,6 @@ When you included this parameter, an email message is created and sent to the ma Type: LoggingLevel Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -340,6 +363,9 @@ Accept wildcard characters: False ``` ### -LogOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogOnly switch performs a search, but only generates a log. Messages returned by the search aren't copied to the target mailbox. You don't need to specify a value with this switch. The logging level is specified by using the LogLevel parameter. @@ -348,7 +374,6 @@ The logging level is specified by using the LogLevel parameter. Type: SwitchParameter Parameter Sets: Mailbox Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -358,6 +383,9 @@ Accept wildcard characters: False ``` ### -SearchDumpster + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SearchDumpster switch specifies whether to include the Recoverable Items folder in the search. The Recoverable items folder stores items that were deleted from the Deleted Items folder or items that were hard-deleted until they're purged from the mailbox database. By default, the Recoverable Items folder is always included in the search. To exclude the Recoverable Items folder from the search, use this exact syntax: `-SearchDumpster:$false`. @@ -366,7 +394,6 @@ By default, the Recoverable Items folder is always included in the search. To ex Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -376,6 +403,9 @@ Accept wildcard characters: False ``` ### -SearchDumpsterOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SearchDumpsterOnly switch specifies that only the Recoverable Items folder of the specified mailbox is searched. You don't need to specify a value with this switch. The Recoverable items folder stores items that were deleted from the Deleted Items folder or items that were hard-deleted until they're purged from the mailbox database. @@ -386,7 +416,6 @@ You can also use this switch with the DeleteContent switch to delete messages fr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -396,6 +425,9 @@ Accept wildcard characters: False ``` ### -SearchQuery + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SearchQuery parameter specifies a search string or a query formatted using Keyword Query Language (KQL). For more information about KQL in Exchange, see [Message properties and search operators for In-Place eDiscovery](https://learn.microsoft.com/exchange/security-and-compliance/in-place-ediscovery/message-properties-and-search-operators). If this parameter is empty, all messages are returned. @@ -406,7 +438,6 @@ If this parameter is empty, all messages are returned. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -416,13 +447,15 @@ 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/exchange/Search-MailboxAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md similarity index 91% rename from exchange/exchange-ps/exchange/Search-MailboxAuditLog.md rename to exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md index f6ff4a429a..6a8dbffcc7 100644 --- a/exchange/exchange-ps/exchange/Search-MailboxAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/search-mailboxauditlog applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Search-MailboxAuditLog -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/search-mailboxauditlog +schema: 2.0.0 +title: Search-MailboxAuditLog --- # Search-MailboxAuditLog @@ -89,6 +90,9 @@ This example retrieves mailbox audit log entries for Ken Kwok's mailbox for acti ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies a single mailbox to retrieve mailbox audit log entries from. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -106,7 +110,6 @@ The Identity parameter specifies a single mailbox to retrieve mailbox audit log 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 @@ -116,6 +119,9 @@ 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,7 +130,6 @@ 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 @@ -134,6 +139,9 @@ Accept wildcard characters: False ``` ### -EndDate + +> Applicable: Exchange Server 2010, 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". @@ -142,7 +150,6 @@ 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 Required: False Position: Named @@ -152,6 +159,9 @@ Accept wildcard characters: False ``` ### -ExternalAccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalAccess parameter specifies whether to return only audit log entries for mailbox access by users that are outside of your organization. In Exchange Online, this parameter returns audit log entries for mailbox access by Microsoft datacenter administrators. Valid values are: $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned. @@ -162,7 +172,6 @@ $false: Audit log entries for mailbox access by external users or Microsoft data 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 @@ -172,6 +181,9 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The GroupMailbox switch is required to include Microsoft 365 Groups in the search. You don't need to specify a value with this switch. @@ -180,7 +192,6 @@ The GroupMailbox switch is required to include Microsoft 365 Groups in the searc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -190,6 +201,9 @@ Accept wildcard characters: False ``` ### -HasAttachments + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The HasAttachments parameter filters the search by messages that have attachments. Valid values are: - $true: Only messages with attachments are included in the search. @@ -199,7 +213,6 @@ The HasAttachments parameter filters the search by messages that have attachment Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -209,6 +222,9 @@ Accept wildcard characters: False ``` ### -IncludeInactiveMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IncludeInactiveMailbox Description }} @@ -217,7 +233,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -227,6 +242,9 @@ Accept wildcard characters: False ``` ### -LogonTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LogonTypes parameter specifies the type of logons. Valid values are: - Admin: Audit log entries for mailbox access by administrator logons are returned. @@ -237,7 +255,6 @@ The LogonTypes parameter specifies the type of logons. Valid values are: 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 @@ -247,6 +264,9 @@ Accept wildcard characters: False ``` ### -Mailboxes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailboxes parameter specifies the mailboxes to retrieve mailbox audit log entries from. You can use this parameter to search audit logs for multiple mailboxes. You enter multiple mailboxes separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -257,7 +277,6 @@ You can't use this parameter with the ShowDetails switch. Type: MultiValuedProperty Parameter Sets: MultipleMailboxesSearch Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -267,6 +286,9 @@ Accept wildcard characters: False ``` ### -Operations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Operations parameter filters the search results by the mailbox actions that are logged by mailbox audit logging. Valid values are: - AddFolderPermissions (Exchange 2019 and Exchange Online only. Although this value is accepted, it's already included in the UpdateFolderPermissions action and isn't audited separately.) @@ -299,7 +321,6 @@ 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 Required: False Position: Named @@ -309,13 +330,15 @@ 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 mailbox audit log entries to return. Valid values include an integer from 1 through 250000. By default, 1000 entries are returned. ```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 @@ -325,6 +348,9 @@ Accept wildcard characters: False ``` ### -ShowDetails + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowDetails switch retrieves the details of each log entry from the mailbox. You don't need to specify a value with this switch. By default, all fields for each returned log entry are displayed in a list view. @@ -335,7 +361,6 @@ You can't use this switch with the Mailboxes parameter. 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 @@ -345,6 +370,9 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Server 2010, 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". @@ -353,7 +381,6 @@ 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 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md similarity index 87% rename from exchange/exchange-ps/exchange/Search-MessageTrackingReport.md rename to exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md index b56afd8580..8cbea54ce7 100644 --- a/exchange/exchange-ps/exchange/Search-MessageTrackingReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/search-messagetrackingreport applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Search-MessageTrackingReport -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/search-messagetrackingreport +schema: 2.0.0 +title: Search-MessageTrackingReport --- # Search-MessageTrackingReport @@ -79,6 +80,9 @@ This example returns the message tracking reports that the Help desk can analyze ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter scopes the search to the specified mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -100,7 +104,6 @@ When you use this parameter with the Sender parameter, the specified mailbox is 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 @@ -110,6 +113,9 @@ Accept wildcard characters: False ``` ### -Sender + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Sender parameter specifies the email address of the message sender for messages that are sent to the mailbox that's specified by the Identity parameter. You need to use this parameter with the Identity parameter. @@ -118,7 +124,6 @@ You need to use this parameter with the Identity parameter. Type: SmtpAddress Parameter Sets: SearchAsSender Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -128,6 +133,9 @@ 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 track messages for any user. You don't need to specify a value with this switch. By default, users can only track messages that they send or receive from their own mailbox. @@ -136,7 +144,6 @@ By default, users can only track messages that they send or receive from their o 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 @@ -146,6 +153,9 @@ 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`. @@ -155,7 +165,6 @@ 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 @@ -165,6 +174,9 @@ 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. @@ -173,7 +185,6 @@ 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,6 +194,9 @@ 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. @@ -191,7 +205,6 @@ 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 @@ -201,13 +214,15 @@ Accept wildcard characters: False ``` ### -MessageEntryId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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, Exchange Online Required: False Position: Named @@ -217,13 +232,15 @@ Accept wildcard characters: False ``` ### -MessageId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -233,6 +250,9 @@ Accept wildcard characters: False ``` ### -Recipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recipients parameter filters the results by the email addresses of the specified recipients. You can specify multiple email addresses separated by commas. You can't use this parameter with the Sender parameter. @@ -241,7 +261,6 @@ You can't use this parameter with the Sender parameter. Type: SmtpAddress[] Parameter Sets: SearchAsRecipient Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -251,13 +270,15 @@ 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 @@ -267,13 +288,15 @@ Accept wildcard characters: False ``` ### -Subject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Subject parameter searches for messages with the specified Subject field value. If the value contains spaces, enclosed 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: False Position: Named @@ -283,6 +306,9 @@ 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. @@ -295,7 +321,6 @@ 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 @@ -305,13 +330,15 @@ 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/exchange/Search-UnifiedAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md similarity index 94% rename from exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md rename to exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md index 9043d4d2b9..1f04a228d5 100644 --- a/exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/search-unifiedauditlog applicable: Exchange Online, Exchange Online Protection -title: Search-UnifiedAuditLog -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/search-unifiedauditlog +schema: 2.0.0 +title: Search-UnifiedAuditLog --- # Search-UnifiedAuditLog @@ -101,6 +102,9 @@ This example searches the unified audit log from May 1, 2023 to May 8, 2023 for ## PARAMETERS ### -EndDate + +> Applicable: Exchange Online, Exchange Online Protection + The EndDate parameter specifies the end date of the date range. Entries are stored in the unified audit log in Coordinated Universal Time (UTC). If you specify a date/time value without a time zone, the value is in UTC. To specify a date/time value for this parameter, use either of the following options: @@ -114,7 +118,6 @@ If you don't include a timestamp in the value for this parameter, the default ti Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -124,6 +127,9 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Online, Exchange Online Protection + The StartDate parameter specifies the start date of the date range. Entries are stored in the unified audit log in Coordinated Universal Time (UTC). If you specify a date/time value without a time zone, the value is in UTC. To specify a date/time value for this parameter, use either of the following options: @@ -137,7 +143,6 @@ If you don't include a timestamp in the value for this parameter, the default ti Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -147,6 +152,9 @@ Accept wildcard characters: False ``` ### -Formatted + +> Applicable: Exchange Online, Exchange Online Protection + The Formatted switch causes attributes that are normally returned as integers (for example, RecordType and Operation) to be formatted as descriptive strings. You don't need to specify a value with this switch. In addition, this switch makes AuditData more readable. @@ -155,7 +163,6 @@ In addition, this switch makes AuditData more readable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -165,13 +172,15 @@ Accept wildcard characters: False ``` ### -FreeText + +> Applicable: Exchange Online, Exchange Online Protection + The FreeText parameter filters the log entries by the specified text string. 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 @@ -181,6 +190,9 @@ Accept wildcard characters: False ``` ### -HighCompleteness + +> Applicable: Exchange Online, Exchange Online Protection + **Note**: This parameter is currently in Preview, isn't available in all organizations, and is subject to change. The HighCompleteness switch specifies completeness instead performance in the results. You don't need to specify a value with this switch. @@ -191,7 +203,6 @@ When you use this switch, the query returns more complete search results but mig Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -201,13 +212,15 @@ Accept wildcard characters: False ``` ### -IPAddresses + +> Applicable: Exchange Online, Exchange Online Protection + The IPAddresses parameter filters the log entries by the specified IP addresses. You specify multiple IP addresses separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -217,13 +230,15 @@ Accept wildcard characters: False ``` ### -LongerRetentionEnabled + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill LongerRetentionEnabled Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -233,6 +248,9 @@ Accept wildcard characters: False ``` ### -ObjectIds + +> Applicable: Exchange Online, Exchange Online Protection + The ObjectIds parameter filters the log entries by object ID. The object ID is the target object that was acted upon, and depends on the RecordType and Operations values of the event. For example, for SharePoint operations, the object ID is the URL path to a file, folder, or site. To search logs in a site, add a wildcard (\*) in front of the site URL (for example, `"https://contoso.sharepoint.com/sites/test/*"`). @@ -247,7 +265,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -257,6 +274,9 @@ Accept wildcard characters: False ``` ### -Operations + +> Applicable: Exchange Online, Exchange Online Protection + The Operations parameter filters the log entries by operation. The available values for this parameter depend on the RecordType value. 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"`. @@ -265,7 +285,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -275,13 +294,15 @@ Accept wildcard characters: False ``` ### -RecordType + +> Applicable: Exchange Online, Exchange Online Protection + The RecordType parameter filters the log entries by record type. 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: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -291,13 +312,15 @@ Accept wildcard characters: False ``` ### -ResultSize + +> Applicable: Exchange Online, Exchange Online Protection + The ResultSize parameter specifies the maximum number of results to return. The default value is 100, maximum is 5,000. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -307,6 +330,9 @@ Accept wildcard characters: False ``` ### -SessionCommand + +> Applicable: Exchange Online, Exchange Online Protection + The SessionCommand parameter specifies how much information is returned and how it's organized. This parameter is required if you want to retrieve more than the default limit of 100 results. Valid values are: - ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and has been optimized for search latency. @@ -318,7 +344,6 @@ The SessionCommand parameter specifies how much information is returned and how Type: UnifiedAuditSessionCommand Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -328,6 +353,9 @@ Accept wildcard characters: False ``` ### -SessionId + +> Applicable: Exchange Online, Exchange Online Protection + The SessionId parameter specifies an ID you provide in the form of a string to identify a command (the cmdlet and its parameters) that will be run multiple times to return paged data. The SessionId can be any string value you choose. When the cmdlet is run sequentially with the same session ID, the cmdlet will return the data in sequential blocks of the size specified by ResultSize. @@ -338,7 +366,6 @@ For a given session ID, if you use the SessionCommand value ReturnLargeSet, and Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -348,6 +375,9 @@ Accept wildcard characters: False ``` ### -SiteIds + +> Applicable: Exchange Online, Exchange Online Protection + The SiteIds parameter filters the log entries by the SharePoint SiteId (GUID). You can enter multiple values separated by commas: `Value1, Value2,...ValueN`. To obtain the SiteId for a SharePoint site, append `/_api/site/id` to the URL of the site collection you want to specify. For example, change the URL `https://contoso.sharepoint.com/sites/hr-project` to `https://contoso.sharepoint.com/sites/hr-project/_api/site/id`. An XML payload is returned and the SiteId for the site collection is displayed in the Edm.Guid property; for example: `14ab81b6-f23d-476a-8cac-ad5dbd2910f7`. @@ -356,7 +386,6 @@ To obtain the SiteId for a SharePoint site, append `/_api/site/id` to the URL of Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -366,6 +395,9 @@ Accept wildcard characters: False ``` ### -UserIds + +> Applicable: Exchange Online, Exchange Online Protection + The UserIds parameter filters the log entries by the account (UserPrincipalName) of the user who performed the action. For example, laura@contoso.onmicrosoft.com. 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"`. @@ -374,7 +406,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md similarity index 91% rename from exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md rename to exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md index dd6524d3fd..bcc18e5b6f 100644 --- a/exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/send-textmessagingverificationcode applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Send-TextMessagingVerificationCode -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/send-textmessagingverificationcode +schema: 2.0.0 +title: Send-TextMessagingVerificationCode --- # Send-TextMessagingVerificationCode @@ -61,6 +62,9 @@ This example sends the text messaging verification code to Tony Smith's mobile p ## 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 @@ -78,7 +82,6 @@ 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 @@ -88,6 +91,9 @@ 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`. @@ -97,7 +103,6 @@ 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 @@ -107,6 +112,9 @@ 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. @@ -115,7 +123,6 @@ 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,13 +132,15 @@ 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/exchange/Set-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ADServerSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md index fbc8c31fba..f8ba09a3e3 100644 --- a/exchange/exchange-ps/exchange/Set-ADServerSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-adserversettings applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ADServerSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-adserversettings +schema: 2.0.0 +title: Set-ADServerSettings --- # Set-AdServerSettings @@ -72,13 +73,15 @@ This example sets the scope of the current session to the entire forest and desi ## PARAMETERS ### -PreferredServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PreferredServer parameter specifies the FQDN of the domain controller to be used for this session. ```yaml Type: Fqdn Parameter Sets: SingleDC Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -88,13 +91,15 @@ Accept wildcard characters: False ``` ### -RunspaceServerSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RunspaceServerSettings parameter specifies whether to pass an entire configuration object to the command to be processed. This parameter is useful in scripts where an entire object must be passed to the command. ```yaml Type: RunspaceServerSettingsPresentationObject Parameter Sets: Instance Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -104,13 +109,15 @@ Accept wildcard characters: False ``` ### -ConfigurationDomainController + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConfigurationDomainController parameter specifies the fully qualified domain name (FQDN) of the configuration domain controller to be used for reading Exchange configuration information in this session. ```yaml Type: Fqdn Parameter Sets: FullParams Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,6 +127,9 @@ 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,7 +139,6 @@ 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,13 +148,15 @@ Accept wildcard characters: False ``` ### -PreferredGlobalCatalog + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PreferredGlobalCatalog parameter specifies the FQDN of the global catalog server to be used for reading recipient information in this session. ```yaml Type: Fqdn Parameter Sets: FullParams Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -155,13 +166,15 @@ Accept wildcard characters: False ``` ### -RecipientViewRoot + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientViewRoot parameter specifies the organizational unit (OU) to include in the recipient scope for this session. When you specify a recipient scope with this parameter, only the recipients included in the scope are returned. To specify an OU, use the syntax `/`. ```yaml Type: String Parameter Sets: SingleDC, FullParams Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,13 +184,15 @@ Accept wildcard characters: False ``` ### -SetPreferredDomainControllers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SetPreferredDomainControllers parameter specifies the list of domain controllers used to read information from Active Directory in this session. You must specify the FQDN of the domain controllers. Separate multiple domain controllers using commas. ```yaml Type: MultiValuedProperty Parameter Sets: FullParams Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -187,6 +202,9 @@ Accept wildcard characters: False ``` ### -ViewEntireForest + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ViewEntireForest parameter specifies whether all the objects in the forest are viewed and managed in this session. Valid values are $true and $false. When you specify a value of $true, the value stored in the RecipientViewRoot parameter is removed and all of the recipients in the forest can be viewed and managed. @@ -195,7 +213,6 @@ When you specify a value of $true, the value stored in the RecipientViewRoot par Type: Boolean Parameter Sets: SingleDC, FullParams Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -205,13 +222,15 @@ 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/exchange/Set-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ADSite.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md index b2769997e3..eee5cdfdb0 100644 --- a/exchange/exchange-ps/exchange/Set-ADSite.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-adsite applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ADSite -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-adsite +schema: 2.0.0 +title: Set-ADSite --- # Set-AdSite @@ -46,13 +47,15 @@ This example configures the Active Directory site named Default-First-Site-Name ## 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 you want to modify. You can use any value that uniquely identifies the site. For example, you can use the name, GUID or distinguished name (DN) of the Active Directory site. ```yaml Type: AdSiteIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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 @@ -97,13 +104,15 @@ Accept wildcard characters: False ``` ### -HubSiteEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The HubSiteEnabled parameter specifies whether this site acts as a hub 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 @@ -113,6 +122,9 @@ Accept wildcard characters: False ``` ### -InboundMailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InboundMailEnabled parameter enables or disables receiving incoming messages for all the Exchange located in the Active Directory site. Typically, this parameter is used after Active Directory site failover or maintenance. Valid input for this parameter is $true or $false. The default value is $true. If you set the value to $false, none of the Exchange servers in the Active Directory site will be able to receive incoming messages. @@ -121,7 +133,6 @@ Valid input for this parameter is $true or $false. The default value is $true. I Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,13 +142,15 @@ Accept wildcard characters: False ``` ### -PartnerId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,13 +160,15 @@ 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/exchange/Set-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md index cb0c15498e..f2b0889e2e 100644 --- a/exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-atpbuiltinprotectionrule applicable: Exchange Online -title: Set-ATPBuiltInProtectionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-atpbuiltinprotectionrule +schema: 2.0.0 +title: Set-ATPBuiltInProtectionRule --- # Set-ATPBuiltInProtectionRule @@ -65,6 +66,9 @@ This example remove all exceptions from the Built-in protection preset security ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -77,7 +81,6 @@ The name of the only rule is ATP Built-In Protection Rule. Type: DehydrateableRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -87,13 +90,15 @@ 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 @@ -103,6 +108,9 @@ 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`. @@ -112,7 +120,6 @@ 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 @@ -122,13 +129,15 @@ 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 @@ -138,6 +147,9 @@ 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 @@ -153,7 +165,6 @@ 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 @@ -163,6 +174,9 @@ 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 @@ -182,7 +196,6 @@ 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 @@ -192,13 +205,15 @@ 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/exchange/Set-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md index a2820af421..3c1ecdf0e9 100644 --- a/exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-atpprotectionpolicyrule applicable: Exchange Online -title: Set-ATPProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-atpprotectionpolicyrule +schema: 2.0.0 +title: Set-ATPProtectionPolicyRule --- # Set-ATPProtectionPolicyRule @@ -63,6 +64,9 @@ This example removes all conditions and exceptions from the Standard preset secu ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -75,7 +79,6 @@ 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 @@ -85,13 +88,15 @@ 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 @@ -101,6 +106,9 @@ 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. @@ -110,7 +118,6 @@ 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 @@ -120,13 +127,15 @@ 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 @@ -136,6 +145,9 @@ 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 @@ -151,7 +163,6 @@ 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 @@ -161,6 +172,9 @@ 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 @@ -178,7 +192,6 @@ 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 @@ -188,6 +201,9 @@ Accept wildcard characters: False ``` ### -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. We highly recommend that you use the default rule names for clarity and consistency. @@ -196,7 +212,6 @@ By default, the rules are named Standard Preset Security Policy or Strict Preset Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -206,6 +221,9 @@ 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. @@ -216,7 +234,6 @@ You must use the default value for the rule. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -226,13 +243,15 @@ 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 @@ -242,6 +261,9 @@ 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 @@ -257,7 +279,6 @@ 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 @@ -267,6 +288,9 @@ 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 @@ -284,7 +308,6 @@ 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 @@ -294,13 +317,15 @@ 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/exchange/Set-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-AcceptedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md index cd7a31a975..20913063af 100644 --- a/exchange/exchange-ps/exchange/Set-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-accepteddomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-AcceptedDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-accepteddomain +schema: 2.0.0 +title: Set-AcceptedDomain --- # Set-AcceptedDomain @@ -55,13 +56,15 @@ This example makes the accepted domain Contoso the default accepted domain. ## 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 accepted domain you want to modify. You can use any value that uniquely identifies the accepted domain object. For example, you can use the name, GUID or distinguished name (DN) 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: True Position: 1 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -AddressBookEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AddressBookEnabled parameter specifies whether to enable recipient filtering for this accepted domain. The default values are: @@ -83,7 +89,6 @@ The AddressBookEnabled parameter specifies whether to enable recipient filtering Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -93,6 +98,9 @@ Accept wildcard characters: False ``` ### -CanHaveCloudCache + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill CanHaveCloudCache Description }} @@ -101,7 +109,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -111,6 +118,9 @@ 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`. @@ -120,7 +130,6 @@ 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 @@ -130,6 +139,9 @@ 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,7 +152,6 @@ 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 @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -DomainType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DomainType parameter specifies the accepted domain type. Valid values are: - Authoritative: This is the default value. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients. @@ -162,7 +176,6 @@ The DomainType parameter specifies the accepted domain type. Valid values are: Type: AcceptedDomainType 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 @@ -172,6 +185,9 @@ Accept wildcard characters: False ``` ### -EnableNego2Authentication + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -180,7 +196,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -190,6 +205,9 @@ Accept wildcard characters: False ``` ### -MakeDefault + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MakeDefault parameter specifies whether the accepted domain is the default domain. Valid values are: $true or $false. @@ -205,7 +223,6 @@ If you don't use non-SMTP email addresses in your organization, you don't need t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -215,13 +232,15 @@ Accept wildcard characters: False ``` ### -MatchSubDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MatchSubDomains parameter enables mail to be sent by and received from users on any subdomain of this accepted domain. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -231,6 +250,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Name parameter specifies a unique name for the accepted domain object. The default value is the DomainName property value. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). @@ -239,7 +261,6 @@ The Name parameter specifies a unique name for the accepted domain object. The d Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -249,6 +270,9 @@ Accept wildcard characters: False ``` ### -OutboundOnly + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The OutboundOnly parameter specifies whether this accepted domain is an internal relay domain for the on-premises deployment for organizations that have coexistence with a cloud-based organization. @@ -259,7 +283,6 @@ The authoritative accepted domain for the on-premises deployment is configured a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -269,6 +292,9 @@ Accept wildcard characters: False ``` ### -PendingCompletion + +> 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. @@ -277,7 +303,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -287,6 +312,9 @@ Accept wildcard characters: False ``` ### -PendingRemoval + +> 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. @@ -295,7 +323,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -305,6 +332,9 @@ Accept wildcard characters: False ``` ### -SendingFromDomainDisabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The SendingFromDomainDisabled parameter specifies whether to allow email to be sent from addresses in the domain. Valid values are: @@ -318,7 +348,6 @@ A common scenario is addresses in a legacy domain that still need to receive ema Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -328,6 +357,9 @@ Accept wildcard characters: False ``` ### -SendingToDomainDisabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The SendingToDomainDisabled specifies whether to prevent delivery of messages sent to recipients in the domain. Valid values are: @@ -341,7 +373,6 @@ A common scenario is to prevent email delivery to recipients in your unused Mico Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -351,13 +382,15 @@ 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/exchange/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-AccessToCustomerDataRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md index a8ff53f2c3..8ace1e620c 100644 --- a/exchange/exchange-ps/exchange/Set-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-accesstocustomerdatarequest applicable: Exchange Online, Exchange Online Protection -title: Set-AccessToCustomerDataRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-accesstocustomerdatarequest +schema: 2.0.0 +title: Set-AccessToCustomerDataRequest --- # Set-AccessToCustomerDataRequest @@ -44,6 +45,9 @@ This example approves the customer lockbox request EXSR123456 with a comment. ## PARAMETERS ### -ApprovalDecision + +> Applicable: Exchange Online, Exchange Online Protection + The ApprovalDecision parameter specifies the approval decision for the customer lockbox request. Valid values are: - Approve @@ -54,7 +58,6 @@ The ApprovalDecision parameter specifies the approval decision for the customer Type: AccessToCustomerDataApproverDecision Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -64,13 +67,15 @@ Accept wildcard characters: False ``` ### -RequestId + +> Applicable: Exchange Online, Exchange Online Protection + The RequestId parameter specifies the reference number of the customer lockbox request that you want to approve, deny, or cancel (for example, EXSR123456). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -80,13 +85,15 @@ 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 @@ -96,6 +103,9 @@ Accept wildcard characters: False ``` ### -ServiceName + +> Applicable: Exchange Online, Exchange Online Protection + The ServiceName parameter specifies the related service. Valid values are: - EOP @@ -107,7 +117,6 @@ The ServiceName parameter specifies the related service. Valid values are: Type: Microsoft.Exchange.Management.AccessToCustomerDataApproval.AccessToCustomerDataRequestServiceName Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md index 3649c7062d..401bc60ef8 100644 --- a/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncdeviceaccessrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-ActiveSyncDeviceAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncdeviceaccessrule +schema: 2.0.0 +title: Set-ActiveSyncDeviceAccessRule --- # Set-ActiveSyncDeviceAccessRule @@ -53,13 +54,15 @@ This example changes the organization's device access rule so that all devices e ## 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 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: True Position: 1 @@ -69,13 +72,15 @@ Accept wildcard characters: False ``` ### -AccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AccessLevel parameter specifies whether the devices are allowed, blocked or quarantined. ```yaml Type: DeviceAccessLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -85,6 +90,9 @@ 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`. @@ -94,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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,7 +122,6 @@ 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,13 +131,15 @@ 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/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md index ba3b345abe..c49f7f9016 100644 --- a/exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncdeviceautoblockthreshold applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ActiveSyncDeviceAutoblockThreshold -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncdeviceautoblockthreshold +schema: 2.0.0 +title: Set-ActiveSyncDeviceAutoblockThreshold --- # Set-ActiveSyncDeviceAutoblockThreshold @@ -56,13 +57,15 @@ This example sets the autoblock threshold rule RecentCommands with several setti ## 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: True Position: 1 @@ -72,13 +75,15 @@ Accept wildcard characters: False ``` ### -AdminEmailInsert + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdminEmailInsert parameter specifies the text to include in the email sent to the user when a mobile device triggers an autoblock threshold rule. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -88,13 +93,15 @@ Accept wildcard characters: False ``` ### -BehaviorTypeIncidenceDuration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BehaviorTypeIncidenceDuration parameter specifies the interval (in minutes) within which the BehaviorType must occur to trigger the autoblock rule. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -104,13 +111,15 @@ Accept wildcard characters: False ``` ### -BehaviorTypeIncidenceLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BehaviorTypeIncidenceLimit parameter specifies the number of occurrences of the behavior type needed to trigger blocking. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,6 +129,9 @@ 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`. @@ -129,7 +141,6 @@ 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 @@ -139,13 +150,15 @@ Accept wildcard characters: False ``` ### -DeviceBlockDuration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeviceBlockDuration parameter specifies the length of time (in minutes) that the mobile device is blocked. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -155,13 +168,15 @@ 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,13 +186,15 @@ 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/exchange/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md similarity index 81% rename from exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md index 1dae482742..4278f0d5d6 100644 --- a/exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncmailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-ActiveSyncMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncmailboxpolicy +schema: 2.0.0 +title: Set-ActiveSyncMailboxPolicy --- # Set-ActiveSyncMailboxPolicy @@ -117,13 +118,15 @@ This example sets several policy settings for the Mobile Device mailbox policy D ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the Mobile Device mailbox policy. ```yaml Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -133,6 +136,9 @@ 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 to Apple mobile devices. @@ -141,7 +147,6 @@ The AllowApplePushNotifications parameter specifies whether push notifications a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -151,13 +156,15 @@ 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 are allowed on the mobile phone. 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 @@ -167,13 +174,15 @@ Accept wildcard characters: False ``` ### -AllowBrowser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowBrowser parameter indicates 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 @@ -183,13 +192,15 @@ 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 @@ -199,13 +210,15 @@ 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 mobile phone. The default value is $true. This parameter doesn't control access to emails using non-Microsoft mobile phone email programs. ```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 @@ -215,13 +228,15 @@ 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 @@ -231,13 +246,15 @@ 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 mobile phone. ```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 @@ -247,13 +264,15 @@ 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 mobile phone. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs. ```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,13 +282,15 @@ 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 @@ -279,13 +300,15 @@ 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 @@ -295,13 +318,15 @@ 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 the Exchange ActiveSync mailbox policy can be sent to the mobile phone over a cellular data connection. ```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 @@ -311,13 +336,15 @@ Accept wildcard characters: False ``` ### -AllowNonProvisionableDevices + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowNonProvisionableDevices parameter specifies whether all mobile phones can synchronize with the server running Exchange. When set to $true, the AllowNonProvisionableDevices parameter enables all mobile phones to synchronize with the Exchange server, regardless of whether the phone can enforce all the specific settings established in the Mobile Device mailbox policy. This also includes mobile phones managed by a separate device management system. When set to $false, this parameter blocks mobile phones that aren't provisioned from synchronizing with the Exchange server. 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 @@ -327,13 +354,15 @@ 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 mobile phone. The default value is $true. This parameter doesn't control access by non-Microsoft email programs. ```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 @@ -343,13 +372,15 @@ 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 @@ -359,13 +390,15 @@ 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 @@ -375,13 +408,15 @@ 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 mobile phone can negotiate the encryption algorithm if 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 @@ -391,13 +426,15 @@ 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 @@ -407,13 +444,15 @@ 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 mobile phone 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 @@ -423,13 +462,15 @@ 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 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 @@ -439,13 +480,15 @@ 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 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 @@ -455,13 +498,15 @@ 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 executed on 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 @@ -471,13 +516,15 @@ 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 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 @@ -487,13 +534,15 @@ 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 password for the mobile phone 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 @@ -503,13 +552,15 @@ 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 mobile phone. ```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 @@ -519,13 +570,15 @@ 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 attachments can be downloaded. When set to $false, the AttachmentsEnabled parameter blocks the user 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 @@ -535,6 +588,9 @@ 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`. @@ -544,7 +600,6 @@ 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 @@ -554,13 +609,15 @@ Accept wildcard characters: False ``` ### -DeviceEncryptionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeviceEncryptionEnabled parameter specifies whether encryption is enabled. The DeviceEncryptionEnabled parameter, when set to $true, enables device encryption on the mobile phone. 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 @@ -570,13 +627,15 @@ Accept wildcard characters: False ``` ### -DevicePasswordEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DevicePasswordEnabled parameter specifies whether a password is required. When set to $true, the DevicePasswordEnabled parameter requires that the user set a password for the mobile phone. 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 @@ -586,13 +645,15 @@ 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 @@ -602,13 +663,15 @@ 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 @@ -618,13 +681,15 @@ 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 @@ -634,6 +699,9 @@ 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. @@ -642,7 +710,6 @@ 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 @@ -652,13 +719,15 @@ 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 @@ -668,13 +737,15 @@ 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 @@ -684,13 +755,15 @@ 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 @@ -700,13 +773,15 @@ 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 @@ -716,6 +791,9 @@ 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. The value is specified by entering one of the following values: - All @@ -729,7 +807,6 @@ 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 @@ -739,13 +816,15 @@ 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 mobile phone. 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 @@ -755,6 +834,9 @@ 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 mobile phone. The value is specified by entering one of the following values. - All @@ -768,7 +850,6 @@ The MaxEmailAgeFilter parameter specifies the maximum number of days of email it 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 @@ -778,13 +859,15 @@ 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 mobile phone. 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 @@ -794,13 +877,15 @@ 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 mobile phone. 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 @@ -810,13 +895,15 @@ 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 mobile phone can be inactive before the password is required to reactivate it. 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 @@ -826,13 +913,15 @@ 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 mobile phone 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 @@ -842,13 +931,15 @@ 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 @@ -858,13 +949,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the friendly name of the Mobile Device mailbox policy. ```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 @@ -874,13 +967,15 @@ 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 the recovery password for the mobile phone is stored on an Exchange server. When set to $true, the PasswordRecoveryEnabled parameter enables you to store the recovery password for the mobile phone 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 @@ -890,13 +985,15 @@ 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 @@ -906,13 +1003,15 @@ 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 @@ -922,13 +1021,15 @@ 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 @@ -938,13 +1039,15 @@ 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 mobile phone 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 @@ -954,13 +1057,15 @@ 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 @@ -970,13 +1075,15 @@ 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 mobile phone 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 @@ -986,13 +1093,15 @@ 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 storage card encryption is enabled for the mailbox policy. Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter to $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 @@ -1002,13 +1111,15 @@ Accept wildcard characters: False ``` ### -UnapprovedInROMApplicationList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UnapprovedInROMApplicationList parameter contains 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 @@ -1018,13 +1129,15 @@ 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 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 @@ -1034,13 +1147,15 @@ 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 @@ -1050,13 +1165,15 @@ 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/exchange/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md index 78b5bcd932..1e6711eb7b 100644 --- a/exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncorganizationsettings applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-ActiveSyncOrganizationSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncorganizationsettings +schema: 2.0.0 +title: Set-ActiveSyncOrganizationSettings --- # Set-ActiveSyncOrganizationSettings @@ -51,13 +52,15 @@ This example sets the default access level to quarantine and sets two administra ## 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 modify. 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 @@ -67,6 +70,9 @@ Accept wildcard characters: False ``` ### -AdminMailRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AdminMailRecipients parameter specifies the email addresses of the administrators for reporting purposes. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -77,7 +83,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -87,13 +92,15 @@ Accept wildcard characters: False ``` ### -AllowAccessForUnSupportedPlatform + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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, Exchange Online Required: False Position: Named @@ -103,6 +110,9 @@ Accept wildcard characters: False ``` ### -AllowRMSSupportForUnenlightenedApps + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The AllowRMSSupportForUnenlightenedApps parameter specifies whether to allow Rights Management Services (RMS) protected messages for ActiveSync clients that don't support RMS. Valid values are: @@ -114,7 +124,6 @@ The AllowRMSSupportForUnenlightenedApps parameter specifies whether to allow Rig Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -124,6 +133,9 @@ 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`. @@ -133,7 +145,6 @@ 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 @@ -143,6 +154,9 @@ Accept wildcard characters: False ``` ### -DefaultAccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultAccessLevel parameter specifies the access level for new and existing device partnerships. Valid values are: - Allow (This is the default value) @@ -155,7 +169,6 @@ If you change this value from Allow to Block or Quarantine, all existing connect Type: DeviceAccessLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -165,6 +178,9 @@ 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. @@ -173,7 +189,6 @@ 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,6 +198,9 @@ Accept wildcard characters: False ``` ### -EnableMobileMailboxPolicyWhenCAInplace + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill EnableMobileMailboxPolicyWhenCAInplace Description }} @@ -191,7 +209,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -201,6 +218,9 @@ Accept wildcard characters: False ``` ### -OtaNotificationMailInsert + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OtaNotificationMailInsert parameter specifies the text to include in an email message that's sent to users who need to update their older devices to use the new Exchange ActiveSync features in Microsoft Exchange. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks ("). @@ -209,7 +229,6 @@ The maximum length is 256 characters. If the value contains spaces, enclose 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 @@ -219,6 +238,9 @@ Accept wildcard characters: False ``` ### -TenantAdminPreference + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill TenantAdminPreference Description }} @@ -227,7 +249,6 @@ This parameter is available only in the cloud-based service. Type: TenantAdminPreference Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -237,6 +258,9 @@ Accept wildcard characters: False ``` ### -UserMailInsert + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserMailInsert parameter specifies an informational footer that's added to the email message sent to users when their mobile device isn't synchronized because the device is quarantined. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks ("). @@ -245,7 +269,6 @@ The maximum length is 256 characters. If the value contains spaces, enclose 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 @@ -255,13 +278,15 @@ 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/exchange/Set-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md index e46e295975..553a2e0e53 100644 --- a/exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ActiveSyncVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-activesyncvirtualdirectory +schema: 2.0.0 +title: Set-ActiveSyncVirtualDirectory --- # Set-ActiveSyncVirtualDirectory @@ -82,6 +83,9 @@ This example configures the external URL on the default Exchange ActiveSync virt ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -94,7 +98,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -104,13 +107,15 @@ Accept wildcard characters: False ``` ### -ActiveSyncServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveSyncServer parameter specifies the URL of the Mailbox server. This value is in the following format: https://servername/Microsoft-Server-ActiveSync. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,13 +125,15 @@ Accept wildcard characters: False ``` ### -BadItemReportingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemReportingEnabled parameter specifies whether items that can't be synchronized should be reported to the user. If set to $true, the user receives a notification when an item can't be synchronized to the mobile phone. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,6 +143,9 @@ Accept wildcard characters: False ``` ### -BasicAuthEnabled + +> 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. @@ -145,7 +155,6 @@ 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 @@ -155,13 +164,15 @@ Accept wildcard characters: False ``` ### -ClientCertAuth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientCertAuth parameter specifies the status of client certificate authentication. By default, client certificate authentication is disabled. The default setting is Ignore. ```yaml Type: ClientCertAuthTypes Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,13 +182,15 @@ Accept wildcard characters: False ``` ### -CompressionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompressionEnabled parameter is a Boolean value that identifies the compression applied to the specified Exchange ActiveSync virtual directory. The default setting 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 @@ -187,6 +200,9 @@ 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`. @@ -196,7 +212,6 @@ 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 @@ -206,13 +221,15 @@ 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 @@ -222,6 +239,9 @@ 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. @@ -234,7 +254,6 @@ 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 @@ -244,6 +263,9 @@ 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. @@ -253,7 +275,6 @@ 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 @@ -263,6 +284,9 @@ 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. @@ -275,7 +299,6 @@ 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 @@ -285,6 +308,9 @@ 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 @@ -314,7 +340,6 @@ Although you can specify any of these values, whether or not the authentication Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -324,13 +349,15 @@ 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 @@ -340,13 +367,15 @@ Accept wildcard characters: False ``` ### -InstallIsapiFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InstallIsapiFilter parameter specifies whether the Internet Server API (ISAPI) filter is installed. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,13 +385,15 @@ Accept wildcard characters: False ``` ### -InternalAuthenticationMethods + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalAuthenticationMethods parameter specifies the authentication methods supported by the server that contains the virtual directory when access is requested from inside the network firewall. If this parameter isn't set, all authentication methods can be used. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -372,13 +403,15 @@ 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 @@ -388,13 +421,15 @@ Accept wildcard characters: False ``` ### -MobileClientCertificateAuthorityURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MobileClientCertificateAuthorityURL parameter specifies the URL for the certification authority (CA) used by the mobile phone. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -404,13 +439,15 @@ Accept wildcard characters: False ``` ### -MobileClientCertificateProvisioningEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MobileClientCertificateProvisioningEnabled parameter specifies whether the Autodiscover service returns the Certificate Services server URL in the XML file. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -420,13 +457,15 @@ Accept wildcard characters: False ``` ### -MobileClientCertTemplateName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MobileClientCertTemplateName parameter specifies the template name for the client 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 @@ -436,13 +475,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the Exchange ActiveSync virtual directory. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -452,13 +493,15 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsActionForUnknownServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteDocumentsActionForUnknownServers parameter specifies the action that occurs when a Microsoft Windows SharePoint Services or Microsoft Windows file share request comes in via Exchange ActiveSync. When a request arrives, Exchange ActiveSync looks for the requested host name in the Allow and Block lists. If the host name isn't found in either list, the action specified in this parameter, either Block or Allow, is performed. ```yaml Type: RemoteDocumentsActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -468,13 +511,15 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsAllowedServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteDocumentsAllowedServers parameter is a multivalued property that lists all the allowed servers for remote document access. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -484,13 +529,15 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsBlockedServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteDocumentsBlockedServers parameter is a multivalued property that lists all the blocked servers for remote document access. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -500,13 +547,15 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsInternalDomainSuffixList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteDocumentsInternalDomainSuffixList parameter is used in organizations that don't run Windows Internet Name Service (WINS) in their network. In these environments, you can specify one or more FQDNs that Exchange ActiveSync treats as internal when a request for remote file access is received. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -516,13 +565,15 @@ Accept wildcard characters: False ``` ### -SendWatsonReport + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendWatsonReport parameter specifies whether a Watson report is sent for errors and events. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -532,13 +583,15 @@ 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 @@ -548,13 +601,15 @@ Accept wildcard characters: False ``` ### -WindowsAuthEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WindowsAuthEnabled parameter specifies whether Integrated Windows authentication is enabled. 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 diff --git a/exchange/exchange-ps/exchange/Set-AdSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdSiteLink.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AdSiteLink.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AdSiteLink.md index 0bdcffba25..ed6d2f74f1 100644 --- a/exchange/exchange-ps/exchange/Set-AdSiteLink.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdSiteLink.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-adsitelink applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AdSiteLink -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-adsitelink +schema: 2.0.0 +title: Set-AdSiteLink --- # Set-AdSiteLink @@ -48,13 +49,15 @@ This example assigns an Exchange-specific cost of 25 to the IP site link DEFAULT ## 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 you want to modify. ```yaml Type: AdSiteLinkIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -91,7 +99,6 @@ 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,13 +108,15 @@ Accept wildcard characters: False ``` ### -ExchangeCost + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExchangeCost parameter specifies an Exchange-specific cost for the IP site link. This cost is used instead of the Active Directory-assigned cost. To clear the value of the ExchangeCost parameter and revert to using the cost of the IP site link specified in Active Directory, set the value of the ExchangeCost parameter to $null. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -117,6 +126,9 @@ 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 can pass across the Active Directory IP site link. The default value is unlimited. When you enter a value, qualify the value with one of the following units: @@ -135,7 +147,6 @@ The valid input range for this parameter is from 64 KB through Int64. To remove Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -145,13 +156,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a unique name for the IP site link. The name that you assign overwrites the current identity of the IP site link. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -161,13 +174,15 @@ 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/exchange/Set-AdaptiveScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdaptiveScope.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-AdaptiveScope.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AdaptiveScope.md index 6560f5f4ab..7cceb9aafb 100644 --- a/exchange/exchange-ps/exchange/Set-AdaptiveScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdaptiveScope.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-adaptivescope applicable: Security & Compliance -title: Set-AdaptiveScope -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-adaptivescope +schema: 2.0.0 +title: Set-AdaptiveScope --- # Set-AdaptiveScope @@ -58,6 +59,9 @@ This example modifies the filter in exiting adaptive scope named Project X. The ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the adaptive scope that you want to modify. You can use any value that uniquely identifies the adaptive scope. For example: - Name @@ -68,7 +72,6 @@ The Identity parameter specifies the adaptive scope that you want to modify. You Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -78,13 +81,15 @@ Accept wildcard characters: False ``` ### -AdministrativeUnit + +> Applicable: Security & Compliance + {{ Fill AdministrativeUnit Description }} ```yaml Type: Guid -Parameter Sets: AdministrativeUnit +Parameter Sets: Default, AdaptiveScopeRawQuery, AdministrativeUnit Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -93,20 +98,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Guid -Parameter Sets: Default, AdaptiveScopeRawQuery -Aliases: -Applicable: Security & Compliance +### -FilterConditions -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Security & Compliance -### -FilterConditions 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"}` @@ -118,7 +113,6 @@ You can't use this parameter with the RawQuery parameter. Type: PswsHashtable Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -128,6 +122,9 @@ 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. @@ -136,7 +133,6 @@ You can't use this parameter with the FilterConditions parameter. Type: String Parameter Sets: AdaptiveScopeRawQuery Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -146,13 +142,15 @@ 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/exchange/Set-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-AddressBookPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md index 6438ed69a2..e828bb944b 100644 --- a/exchange/exchange-ps/exchange/Set-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-addressbookpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-AddressBookPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-addressbookpolicy +schema: 2.0.0 +title: Set-AddressBookPolicy --- # Set-AddressBookPolicy @@ -50,13 +51,15 @@ This example changes the OAB that the address book policy All Fabrikam ABP uses ## 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 that you want to modify. ```yaml Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -66,13 +69,15 @@ 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. ```yaml 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 @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ 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. @@ -109,7 +119,6 @@ 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 @@ -119,13 +128,15 @@ 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 global address list (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: False Position: Named @@ -135,13 +146,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name that you want this address book policy to be called. Use this parameter to change 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: False Position: Named @@ -151,13 +164,15 @@ 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 offline address book (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: False Position: Named @@ -167,6 +182,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/exchange/new-addresslist#-recipientfilter) results from the address list that's specified by this parameter. @@ -185,7 +203,6 @@ 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: False Position: Named @@ -195,13 +212,15 @@ 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/exchange/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md index 686f5b3185..730ae2ea90 100644 --- a/exchange/exchange-ps/exchange/Set-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-addresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-AddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-addresslist +schema: 2.0.0 +title: Set-AddressList --- # Set-AddressList @@ -88,6 +89,9 @@ This example modifies the type of recipients and the department of the recipient ## 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 modify. You can use any value that uniquely identifies the address list. For example: - Name @@ -99,7 +103,6 @@ The Identity parameter specifies the address list that you want to modify. You c Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -109,6 +112,9 @@ 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. 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. @@ -121,7 +127,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -131,6 +136,9 @@ 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. @@ -143,7 +151,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -153,6 +160,9 @@ 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. @@ -165,7 +175,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -175,6 +184,9 @@ 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. @@ -187,7 +199,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -197,6 +208,9 @@ 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. @@ -209,7 +223,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -219,6 +232,9 @@ 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. @@ -231,7 +247,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -241,6 +256,9 @@ 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. @@ -253,7 +271,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -263,6 +280,9 @@ 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. @@ -275,7 +295,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -285,6 +304,9 @@ 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. @@ -297,7 +319,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -307,6 +328,9 @@ 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. @@ -319,7 +343,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -329,6 +352,9 @@ 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. @@ -341,7 +367,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -351,6 +376,9 @@ 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. @@ -363,7 +391,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -373,6 +400,9 @@ 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. @@ -385,7 +415,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -395,6 +424,9 @@ 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. @@ -407,7 +439,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -417,6 +448,9 @@ 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. @@ -429,7 +463,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -439,6 +472,9 @@ 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. @@ -451,7 +487,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -461,6 +496,9 @@ 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. @@ -473,7 +511,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -483,6 +520,9 @@ 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. @@ -495,7 +535,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -505,6 +544,9 @@ 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`. @@ -514,7 +556,6 @@ 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 @@ -524,13 +565,15 @@ 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 group. The display name is visible in the Exchange admin center and in 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, Exchange Online Required: False Position: Named @@ -540,6 +583,9 @@ 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. @@ -548,7 +594,6 @@ 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 @@ -558,6 +603,9 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch. @@ -566,7 +614,6 @@ The ForceUpgrade switch suppresses the confirmation message that appears if the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -576,6 +623,9 @@ 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. @@ -591,7 +641,6 @@ You can specify multiple values separated by commas. When you use multiple value Type: WellKnownRecipientType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -601,13 +650,15 @@ Accept wildcard characters: False ``` ### -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 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: False Position: Named @@ -617,6 +668,9 @@ 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: @@ -632,7 +686,6 @@ 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 @@ -642,6 +695,9 @@ 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. @@ -657,7 +713,6 @@ 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 @@ -667,13 +722,15 @@ 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/exchange/Set-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md index 09836f6007..6257f3e46a 100644 --- a/exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-addressrewriteentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AddressRewriteEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-addressrewriteentry +schema: 2.0.0 +title: Set-AddressRewriteEntry --- # Set-AddressRewriteEntry @@ -59,13 +60,15 @@ This example changes the existing address rewrite entry named "Address entry for ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the address rewrite entry you want to modify. You can specify the name or GUID of the address rewrite entry. ```yaml Type: AddressRewriteEntryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -75,6 +78,9 @@ 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,7 +90,6 @@ 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,6 +99,9 @@ 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. @@ -102,7 +110,6 @@ 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 @@ -112,13 +119,15 @@ Accept wildcard characters: False ``` ### -ExceptionList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExceptionList parameter specifies the domain names that should be excluded from address rewriting when the InternalAddress parameter contains a value that specifies multiple domain names. You can separate multiple domain names included with the ExceptionList parameter with commas. For more information about how to add values to or remove values from multivalued properties, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -128,6 +137,9 @@ 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. @@ -136,7 +148,6 @@ 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: False Position: Named @@ -146,6 +157,9 @@ 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 @@ -156,7 +170,6 @@ 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: False Position: Named @@ -166,13 +179,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -182,6 +197,9 @@ 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,7 +210,6 @@ 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 @@ -202,13 +219,15 @@ 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/exchange/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md index 6812c3cc6d..16f2e9cb10 100644 --- a/exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-adminauditlogconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-AdminAuditLogConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-adminauditlogconfig +schema: 2.0.0 +title: Set-AdminAuditLogConfig --- # Set-AdminAuditLogConfig @@ -75,6 +76,9 @@ This example enables administrator audit logging only for specific parameters th ## PARAMETERS ### -Identity + +> 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. @@ -83,7 +87,6 @@ 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: 1 @@ -93,6 +96,9 @@ Accept wildcard characters: False ``` ### -AdminAuditLogAgeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdminAuditLogAgeLimit parameter specifies how long each log entry should be kept before it's deleted. The default age limit is 90 days. @@ -109,7 +115,6 @@ Setting the age limit to 0 purges the audit log of all entries. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -119,6 +124,9 @@ Accept wildcard characters: False ``` ### -AdminAuditLogCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdminAuditLogCmdlets parameter specifies which cmdlets should be audited. You can specify one or more cmdlets, separated by commas. You can also use the wildcard character (\*) to match multiple cmdlets in one or more of the entries in the cmdlet list. To audit all cmdlets, specify only the wildcard character (\*). @@ -127,7 +135,6 @@ The AdminAuditLogCmdlets parameter specifies which cmdlets should be audited. Yo Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -137,6 +144,9 @@ Accept wildcard characters: False ``` ### -AdminAuditLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. Valid values are: @@ -152,7 +162,6 @@ Changes to the administrator audit log configuration are always logged, regardle Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -162,6 +171,9 @@ Accept wildcard characters: False ``` ### -AdminAuditLogExcludedCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdminAuditLogExcludedCmdlets parameter specifies which cmdlets should be excluded from auditing. Use this parameter if you want to exclude specific cmdlets you don't want to audit even if they match a wildcard string specified in the AdminAuditLogCmdlets parameter. @@ -174,7 +186,6 @@ If you want to clear the list, specify a value of $null. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -184,6 +195,9 @@ Accept wildcard characters: False ``` ### -AdminAuditLogParameters + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdminAuditLogParameters parameter specifies which parameters should be audited on the cmdlets you specified using the AdminAuditLogCmdlets parameter. You can specify one or more parameters, separated by commas. You can also use the wildcard character (\*) to match multiple parameters in one or more of the entries in the parameters list. To audit all parameters, specify only the wildcard character (\*). @@ -192,7 +206,6 @@ The AdminAuditLogParameters parameter specifies which parameters should be audit Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -202,6 +215,9 @@ 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`. @@ -211,7 +227,6 @@ 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 Default value: None @@ -220,6 +235,9 @@ 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. @@ -228,7 +246,6 @@ 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 @@ -238,6 +255,9 @@ 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. @@ -246,7 +266,6 @@ 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 Default value: None @@ -255,6 +274,9 @@ Accept wildcard characters: False ``` ### -LogLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The LogLevel parameter specifies whether additional properties should be included in the log entries. Valid values are: @@ -266,7 +288,6 @@ The LogLevel parameter specifies whether additional properties should be include Type: AuditLogLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -276,6 +297,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Name parameter specifies the name of the AdminAuditLogConfig object. @@ -286,7 +310,6 @@ You don't need to specify this parameter when you configure administrator audit Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -296,6 +319,9 @@ Accept wildcard characters: False ``` ### -TestCmdletLoggingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TestCmdletLoggingEnabled parameter specifies whether test cmdlets (cmdlet names that begin with the verb Test) results are included in admin audit logging. Valid values are: @@ -309,7 +335,6 @@ Test cmdlets can produce a large amount of information. As such, you should only Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -319,6 +344,9 @@ Accept wildcard characters: False ``` ### -UnifiedAuditLogIngestionEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only in the cloud-based service. The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or disable the recording of user and admin activities in the Microsoft 365 audit log. Valid values are: @@ -330,7 +358,6 @@ The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or dis Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named Default value: None @@ -339,13 +366,15 @@ 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 Default value: None diff --git a/exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md index a552fa50b5..785a2d2c7c 100644 --- a/exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-antiphishpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-AntiPhishPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-antiphishpolicy +schema: 2.0.0 +title: Set-AntiPhishPolicy --- # Set-AntiPhishPolicy @@ -90,6 +91,9 @@ In Microsoft Defender for Office 365, this example modifies the default antiphis ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the antiphish policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -100,7 +104,6 @@ The Identity parameter specifies the antiphish policy that you want to modify. Y Type: AntiPhishPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -110,13 +113,15 @@ 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 @@ -126,6 +131,9 @@ 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: @@ -137,7 +145,6 @@ 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 @@ -147,6 +154,9 @@ 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`. @@ -156,7 +166,6 @@ 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,6 +175,9 @@ 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: @@ -177,7 +189,6 @@ The DmarcQuarantineAction parameter specifies the action to take when a message Type: SpoofDmarcQuarantineAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -187,6 +198,9 @@ 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: @@ -200,7 +214,6 @@ 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 @@ -210,6 +223,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. To enable or disable an existing anti-phishing policy (the combination of the antiphish rule and the associated antiphish policy), use the **Enable-AntiPhishRule** or **Disable-AntiPhishRule** cmdlets. @@ -222,7 +238,6 @@ 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 @@ -232,6 +247,9 @@ 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. @@ -241,7 +259,6 @@ 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 @@ -251,6 +268,9 @@ 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: @@ -262,7 +282,6 @@ The EnableMailboxIntelligence parameter specifies whether to enable or disable m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -272,6 +291,9 @@ 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: @@ -287,7 +309,6 @@ 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 @@ -297,6 +318,9 @@ 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: @@ -308,7 +332,6 @@ The EnableOrganizationDomainsProtection parameter specifies whether to enable do Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -318,6 +341,9 @@ 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: @@ -329,7 +355,6 @@ The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the saf Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -339,6 +364,9 @@ 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: @@ -350,7 +378,6 @@ The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -360,6 +387,9 @@ 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: @@ -371,7 +401,6 @@ 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 @@ -381,6 +410,9 @@ 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: @@ -392,7 +424,6 @@ The EnableTargetedDomainsProtection parameter specifies whether to enable domain Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -402,6 +433,9 @@ 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: @@ -413,7 +447,6 @@ The EnableTargetedUserProtection parameter specifies whether to enable user impe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -423,6 +456,9 @@ 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: @@ -439,7 +475,6 @@ 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 @@ -449,6 +484,9 @@ 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: @@ -460,7 +498,6 @@ The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -470,6 +507,9 @@ 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: @@ -486,7 +526,6 @@ 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 @@ -496,6 +535,9 @@ 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. @@ -508,7 +550,6 @@ The maximum number of entries is approximately 1000. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -518,6 +559,9 @@ 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. @@ -528,7 +572,6 @@ The maximum number of entries is approximately 1000. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -538,6 +581,9 @@ 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: @@ -549,7 +595,6 @@ 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 @@ -559,6 +604,9 @@ 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: @@ -571,7 +619,6 @@ The ImpersonationProtectionState parameter specifies the configuration of impers Type: ImpersonationProtectionState Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -581,6 +628,9 @@ 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: @@ -598,7 +648,6 @@ This parameter is meaningful only if the EnableMailboxIntelligence and EnableMai Type: ImpersonationAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -608,6 +657,9 @@ 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. @@ -618,7 +670,6 @@ 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 @@ -628,6 +679,9 @@ 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: @@ -646,7 +700,6 @@ 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 @@ -656,6 +709,9 @@ 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). @@ -664,7 +720,6 @@ 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 @@ -674,6 +729,9 @@ 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: @@ -687,7 +745,6 @@ 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 @@ -697,13 +754,15 @@ 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 @@ -713,6 +772,9 @@ 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 @@ -729,7 +791,6 @@ 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 @@ -739,6 +800,9 @@ 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. @@ -749,7 +813,6 @@ 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 @@ -759,6 +822,9 @@ 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: @@ -774,7 +840,6 @@ The TargetedDomainProtectionAction parameter specifies the action to take on det Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -784,6 +849,9 @@ 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: @@ -802,7 +870,6 @@ 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 @@ -812,6 +879,9 @@ 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. @@ -822,7 +892,6 @@ You can specify multiple domains separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -832,6 +901,9 @@ 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. @@ -842,7 +914,6 @@ 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 @@ -852,6 +923,9 @@ 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: @@ -867,7 +941,6 @@ The TargetedUserProtectionAction parameter specifies the action to take on detec Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -877,6 +950,9 @@ 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: @@ -895,7 +971,6 @@ 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 @@ -905,6 +980,9 @@ 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. @@ -920,7 +998,6 @@ This parameter uses the syntax: "DisplayName;EmailAddress". Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -930,13 +1007,15 @@ 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/exchange/Set-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-AntiPhishRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md index 9d41dff174..bd9e6273a9 100644 --- a/exchange/exchange-ps/exchange/Set-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-antiphishrule applicable: Exchange Online, Exchange Online Protection -title: Set-AntiPhishRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-antiphishrule +schema: 2.0.0 +title: Set-AntiPhishRule --- # Set-AntiPhishRule @@ -55,6 +56,9 @@ This example modifies the existing antiphish rule named Engineering Department P ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the antiphish rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the antiphish rule that you want to modify. You Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -75,6 +78,9 @@ 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: - Name @@ -85,7 +91,6 @@ The AntiPhishPolicy parameter specifies the antiphish policy that's associated w Type: AntiPhishPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -95,13 +100,15 @@ 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 @@ -111,6 +118,9 @@ 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`. @@ -120,7 +130,6 @@ 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 @@ -130,13 +139,15 @@ 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 @@ -146,6 +157,9 @@ 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 @@ -161,7 +175,6 @@ 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 @@ -171,6 +184,9 @@ 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 @@ -186,7 +202,6 @@ 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 @@ -196,13 +211,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -212,6 +229,9 @@ 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: @@ -226,7 +246,6 @@ 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 @@ -236,13 +255,15 @@ 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 @@ -252,6 +273,9 @@ 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 @@ -267,7 +291,6 @@ 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 @@ -277,6 +300,9 @@ 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 @@ -294,7 +320,6 @@ 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 @@ -304,13 +329,15 @@ 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/exchange/Set-App.md b/exchange/exchange-ps/ExchangePowerShell/Set-App.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-App.md rename to exchange/exchange-ps/ExchangePowerShell/Set-App.md index af5a021961..6bcf4a27c5 100644 --- a/exchange/exchange-ps/exchange/Set-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-App.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-app applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-App -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-app +schema: 2.0.0 +title: Set-App --- # Set-App @@ -64,13 +65,15 @@ This example disables the organization app named FinanceTestApp across the organ ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Identity parameter specifies the AppID (GUID value) of the app that you want to modify. 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, Exchange Online Protection Required: True Position: 1 @@ -80,6 +83,9 @@ 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`. @@ -89,7 +95,6 @@ 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,6 +104,9 @@ 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 the organization app for the specified users. Valid values are: - Enabled: The organization app is enabled. @@ -111,7 +119,6 @@ You use this parameter with the OrganizationApp switch. Type: DefaultStateForUser Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -121,6 +128,9 @@ 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. @@ -129,7 +139,6 @@ 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 @@ -139,6 +148,9 @@ 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 enabled for the specified users. This is the default value. @@ -150,7 +162,6 @@ This setting overrides the ProvidedTo, UserList, and DefaultStateForUser setting Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -160,13 +171,15 @@ 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 @@ -176,13 +189,15 @@ Accept wildcard characters: False ``` ### -PrivateCatalog + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrivateCatalog switch specifies that the app you want to modify 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 @@ -192,6 +207,9 @@ 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 value are: - Everyone: The app is provided to every user in the organization. This is the default value. 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. @@ -203,7 +221,6 @@ 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 @@ -213,6 +230,9 @@ 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: @@ -236,7 +256,6 @@ 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 @@ -246,13 +265,15 @@ 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/exchange/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md index d7b88cea53..b655ee04bb 100644 --- a/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-appretentioncompliancepolicy applicable: Security & Compliance -title: Set-AppRetentionCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-appretentioncompliancepolicy +schema: 2.0.0 +title: Set-AppRetentionCompliancePolicy --- # Set-AppRetentionCompliancePolicy @@ -158,6 +159,9 @@ This example is similar to Example 2, except multiple deleted resources are spec ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the app retention compliance policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -168,7 +172,6 @@ The Identity parameter specifies the app retention compliance policy that you wa Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -178,6 +181,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch specifies whether to redistribute the policy to all locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -188,7 +194,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistributionParameterSet Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -198,6 +203,9 @@ Accept wildcard characters: False ``` ### -AddAdaptiveScopeLocation + +> Applicable: Security & Compliance + The AddAdaptiveScopeLocation parameter specifies the adaptive scope location to add to 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 @@ -210,7 +218,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -220,6 +227,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -238,7 +248,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -248,6 +257,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocationException + +> Applicable: Security & Compliance + The AddExchangeLocationException parameter specifies the mailboxes to add to the list of excluded mailboxes when you're using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -266,7 +278,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -276,6 +287,9 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocation + +> Applicable: Security & Compliance + The AddModernGroupLocation parameter specifies the Microsoft 365 Groups to add to the list of included Microsoft 365 Groups when you aren't using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -291,7 +305,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -301,6 +314,9 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocationException + +> Applicable: Security & Compliance + The AddModernGroupLocationException parameter specifies the Microsoft 365 Groups to add to the list of excluded Microsoft 365 Groups when you're using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -316,7 +332,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -326,6 +341,9 @@ 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`: @@ -356,7 +374,6 @@ This parameter uses the following syntax: `"LocationType:App1,LocationType:App2, Type: String[] Parameter Sets: Identity, AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -366,13 +383,15 @@ 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: Identity, AdaptiveScopeLocation, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -382,6 +401,9 @@ 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`. @@ -391,7 +413,6 @@ 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 @@ -401,6 +422,9 @@ Accept wildcard characters: False ``` ### -DeletedResources + +> Applicable: Security & Compliance + The DeletedResources parameter specifies the deleted mailbox or mail user to add as an exclusion to the respective location list. Use this parameter with the AddTeamsChatLocationException parameter for deleted mailboxes or mail users that need to be excluded from a Teams only retention policy. A valid value is a JSON string. Refer to the Examples section for syntax and usage examples of this parameter. @@ -415,7 +439,6 @@ To prevent active mailboxes or mail users with the same SMTP address from being Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -425,6 +448,9 @@ 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. @@ -434,7 +460,6 @@ The Enabled parameter enables or disables the policy. Valid values are: Type: Boolean Parameter Sets: Identity, AdaptiveScopeLocation, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -444,6 +469,9 @@ 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. @@ -452,7 +480,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity, AdaptiveScopeLocation, TeamLocation, InformationBarrierDefault Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -462,6 +489,9 @@ 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. @@ -472,7 +502,6 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -482,6 +511,9 @@ Accept wildcard characters: False ``` ### -RemoveAdaptiveScopeLocation + +> Applicable: Security & Compliance + The RemoveAdaptiveScopeLocation parameter specifies the adaptive scope location to remove from 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 @@ -494,7 +526,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -504,6 +535,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter specifies the mailboxes to remove from the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -522,7 +556,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -532,6 +565,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocationException + +> Applicable: Security & Compliance + The RemoveExchangeLocationException parameter specifies the mailboxes to remove from the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -550,7 +586,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -560,6 +595,9 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocation + +> Applicable: Security & Compliance + The RemoveModernGroupLocation parameter specifies the Microsoft 365 Groups to remove from the list of included groups when you aren't using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -575,7 +613,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -585,6 +622,9 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocationException + +> Applicable: Security & Compliance + The RemoveModernGroupLocationException parameter specifies the Microsoft 365 Groups to remove from the list of excluded groups when you're using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -600,7 +640,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -610,6 +649,9 @@ 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. @@ -623,7 +665,6 @@ Therefore, before you lock a policy, it's critical that you understand your orga Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -633,13 +674,15 @@ 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/exchange/Set-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md index 5c9bb418a3..b60f53f011 100644 --- a/exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-appretentioncompliancerule applicable: Security & Compliance -title: Set-AppRetentionComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-appretentioncompliancerule +schema: 2.0.0 +title: Set-AppRetentionComplianceRule --- # Set-AppRetentionComplianceRule @@ -52,6 +53,9 @@ This example updates the length of the retention duration for a rule named 563 M ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the app retention compliance rule that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -62,7 +66,6 @@ The Identity parameter specifies the app retention compliance rule that you want Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -72,13 +75,15 @@ 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 @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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"})`. @@ -117,7 +127,6 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -127,13 +136,15 @@ Accept wildcard characters: False ``` ### -ContentDateFrom + +> Applicable: Security & Compliance + {{ Fill ContentDateFrom Description }} ```yaml Type: System.DateTime Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -143,13 +154,15 @@ Accept wildcard characters: False ``` ### -ContentDateTo + +> Applicable: Security & Compliance + {{ Fill ContentDateTo Description }} ```yaml Type: System.DateTime Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -159,6 +172,9 @@ 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). @@ -167,7 +183,6 @@ 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 @@ -177,6 +192,9 @@ 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 @@ -196,7 +214,6 @@ You can specify multiple item class values by using the following syntax: `"Valu Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -206,6 +223,9 @@ 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 @@ -215,7 +235,6 @@ The ExpirationDateOption parameter specifies whether the expiration date is calc Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -225,6 +244,9 @@ Accept wildcard characters: False ``` ### -RetentionComplianceAction + +> Applicable: Security & Compliance + The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - Delete @@ -235,7 +257,6 @@ The RetentionComplianceAction parameter specifies the retention action for the r Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -245,6 +266,9 @@ 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. @@ -254,7 +278,6 @@ The RetentionDuration parameter specifies the hold duration for the retention ru Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -264,6 +287,9 @@ 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 @@ -277,7 +303,6 @@ Type: HoldDurationHint Parameter Sets: (All) Aliases: Accepted values: Days, Months, Years -Applicable: Security & Compliance Required: False Position: Named @@ -287,13 +312,15 @@ 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/exchange/Set-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md index dd98f50127..da2b6febfa 100644 --- a/exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-applicationaccesspolicy applicable: Exchange Online, Exchange Online Protection -title: Set-ApplicationAccessPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-applicationaccesspolicy +schema: 2.0.0 +title: Set-ApplicationAccessPolicy --- # Set-ApplicationAccessPolicy @@ -45,13 +46,15 @@ This example modifies the description of the specified policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the application access policy that you want to modify. 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 @@ -61,13 +64,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online, Exchange Online Protection + The Description parameter modifies the description of 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: True Position: Named @@ -77,6 +82,9 @@ 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`. @@ -86,7 +94,6 @@ 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 @@ -96,13 +103,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Exchange Online Protection + The WhatIf switch doesn't work on this cmdlet. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ArcConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md index 5bf267a358..91ed162e13 100644 --- a/exchange/exchange-ps/exchange/Set-ArcConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-arcconfig applicable: Exchange Online, Exchange Online Protection -title: Set-ArcConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-arcconfig +schema: 2.0.0 +title: Set-ArcConfig --- # Set-ArcConfig @@ -97,6 +98,9 @@ If no other ARC sealers exist after removing this entry from the list, using the ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the trusted ARC sealers list that you want to modify. Use one of the following values: - Default for your own organization. @@ -106,7 +110,6 @@ The Identity parameter specifies the trusted ARC sealers list that you want to m Type: HostedConnectionFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -116,6 +119,9 @@ Accept wildcard characters: False ``` ### -ArcTrustedSealers + +> Applicable: Exchange Online, Exchange Online Protection + The ArcTrustedSealers parameter specifies the domain name of the ARC sealers that you want to add. The domain name must match the domain that's shown in the `d` tag in the **ARC-Seal** and **ARC-Message-Signature** headers in affected email messages (for example, fabrikam.com). You can use Outlook to see these headers. @@ -130,7 +136,6 @@ To empty the list, use the value `" "` (a space enclosed in double quotation mar Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -140,6 +145,9 @@ 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`. @@ -149,7 +157,6 @@ 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 @@ -159,13 +166,15 @@ 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/exchange/Set-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md index bcdc6c3dd1..e0edc65f0c 100644 --- a/exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-atppolicyforo365 applicable: Exchange Online -title: Set-AtpPolicyForO365 -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-atppolicyforo365 +schema: 2.0.0 +title: Set-AtpPolicyForO365 --- # Set-AtpPolicyForO365 @@ -55,13 +56,15 @@ This example enables Safe Documents and Safe Attachments for SharePoint, OneDriv ## 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 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -AllowSafeDocsOpen + +> Applicable: Exchange Online + The AllowSafeDocsOpen parameter specifies whether users can click through and bypass the Protected View container even when Safe Documents identifies a file as malicious. Valid values are: - $true: Users are allowed to exit the Protected View container even if the document has been identified as malicious. @@ -82,7 +88,6 @@ This parameter is meaningful only when the EnableSafeDocs parameter value is $tr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -92,6 +97,9 @@ 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`. @@ -101,7 +109,6 @@ 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 @@ -111,6 +118,9 @@ Accept wildcard characters: False ``` ### -EnableATPForSPOTeamsODB + +> Applicable: Exchange Online + The EnableATPForSPOTeamsODB parameter enables or disables Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. Valid values are: - $true: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is enabled. SharePoint admins can use the DisallowInfectedFileDownload parameter on the [Set-SPOTenant](https://learn.microsoft.com/powershell/module/sharepoint-online/Set-SPOTenant) cmdlet to control whether users are allowed to download files that are found to be malicious. @@ -120,7 +130,6 @@ The EnableATPForSPOTeamsODB parameter enables or disables Safe Attachments for S Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -130,6 +139,9 @@ Accept wildcard characters: False ``` ### -EnableSafeDocs + +> Applicable: Exchange Online + The EnableSafeDocs parameter enables or disables Safe Documents in organizations with Microsoft 365 A5 or Microsoft 365 E5 Security licenses. Valid values are: - $true: Safe Documents is enabled and will upload user files to Microsoft Defender for Endpoint for scanning and verification. @@ -141,7 +153,6 @@ For more information about Safe Documents, see [Safe Documents in Microsoft 365 Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -151,13 +162,15 @@ 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/exchange/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md index 0bc5e542b8..6da40bc514 100644 --- a/exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AttachmentFilterListConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig +schema: 2.0.0 +title: Set-AttachmentFilterListConfig --- # Set-AttachmentFilterListConfig @@ -49,6 +50,9 @@ This example modifies the action that the Attachment Filtering agent takes on an ## PARAMETERS ### -Action + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Action parameter specifies how the Attachment Filtering agent handles an attachment that matches an entry on the attachment filter list. Valid values are: - Reject: This value prevents both the email message and attachment from being delivered to the recipient and issues a non-delivery report (NDR) to the sender. This is the default value. @@ -59,7 +63,6 @@ The Action parameter specifies how the Attachment Filtering agent handles an att Type: FilterActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -69,13 +72,15 @@ Accept wildcard characters: False ``` ### -AdminMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdminMessage parameter specifies the content of a text file that replaces attachments removed by the Attachment Filtering agent. The AdminMessage parameter only appears when the Attachment Filtering agent is configured to remove an attachment that's been identified as bad. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -85,6 +90,9 @@ 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,7 +102,6 @@ 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,6 +111,9 @@ 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. @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ Accept wildcard characters: False ``` ### -ExceptionConnectors + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExceptionConnectors parameter specifies a list of connectors that should be excluded from attachment filtering. Attachment filters aren't applied to email messages received through these connectors. You must use the connector GUID to specify the ExceptionConnectors parameter value. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,13 +149,15 @@ Accept wildcard characters: False ``` ### -RejectResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RejectResponse parameter specifies the message body that you want delivered in the NDR to senders whose messages contain an attachment that's blocked. The RejectResponse parameter is required only if you set the Action parameter to Reject. Don't exceed 240 characters in the parameter argument. When you pass an argument, you must enclose the RejectResponse parameter value in quotation marks (") if the phrase contains spaces, for example: "Message rejected". The default setting is Message rejected due to unacceptable attachments. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -154,13 +167,15 @@ 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/exchange/Set-AuditConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuditConfig.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-AuditConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AuditConfig.md index e2c5d20cfd..b3d1e6a800 100644 --- a/exchange/exchange-ps/exchange/Set-AuditConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuditConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-auditconfig applicable: Security & Compliance -title: Set-AuditConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-auditconfig +schema: 2.0.0 +title: Set-AuditConfig --- # Set-AuditConfig @@ -42,13 +43,15 @@ This example sets the auditing configuration for Exchange and SharePoint. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 1 @@ -58,6 +61,9 @@ Accept wildcard characters: False ``` ### -Workload + +> Applicable: Security & Compliance + The Workload parameter specifies where auditing is allowed. Valid values are: - Exchange @@ -71,7 +77,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -81,13 +86,15 @@ 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 @@ -97,13 +104,15 @@ 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/exchange/Set-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AuthConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md index a6ffa805ac..5bf2d3445c 100644 --- a/exchange/exchange-ps/exchange/Set-AuthConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-authconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AuthConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-authconfig +schema: 2.0.0 +title: Set-AuthConfig --- # Set-AuthConfig @@ -90,13 +91,15 @@ This example immediately rolls over the certificate configured as the next certi ## PARAMETERS ### -CertificateThumbprint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CertificateThumbprint parameter specifies the thumbprint of the certificate to be used by Exchange for server-to-server authentication. ```yaml Type: String Parameter Sets: CurrentCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -106,13 +109,15 @@ Accept wildcard characters: False ``` ### -ClearPreviousCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClearPreviousCertificate switch clears the certificate that was saved as the previous certificate in the authorization configuration. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: PublishAuthCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -122,6 +127,9 @@ 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`. @@ -131,7 +139,6 @@ 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 @@ -141,13 +148,15 @@ 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 @@ -157,6 +166,9 @@ 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. @@ -165,7 +177,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: CurrentCertificateParameter, PublishAuthCertificateParameter, NewCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -175,13 +186,15 @@ Accept wildcard characters: False ``` ### -NewCertificateEffectiveDate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NewCertificateEffectiveDate parameter specifies a date when the certificate configured as the next certificate should be used. ```yaml Type: DateTime Parameter Sets: NewCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,13 +204,15 @@ Accept wildcard characters: False ``` ### -NewCertificateThumbprint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NewCertificateThumbprint parameter specifies the thumbprint of the new certificate to be used as the next certificate in the authorization configuration. ```yaml Type: String Parameter Sets: NewCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -207,6 +222,9 @@ Accept wildcard characters: False ``` ### -PublishCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PublishCertificate switch immediately rolls over the specified certificate as the current certificate. You don't need to specify a value with this switch. The certificate is immediately deployed to all Client Access servers. @@ -215,7 +233,6 @@ The certificate is immediately deployed to all Client Access servers. Type: SwitchParameter Parameter Sets: PublishAuthCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -225,13 +242,15 @@ Accept wildcard characters: False ``` ### -Realm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Realm parameter specifies a security realm for partner applications. If a service or user presents a token from a domain that's not an accepted domain in the Exchange organization, the token must contain the specified realm to gain access to resources. ```yaml Type: String Parameter Sets: AuthConfigSettings Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,13 +260,15 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter isn't available in this release. ```yaml Type: ServerIdParameter Parameter Sets: CurrentCertificateParameter, NewCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -257,6 +278,9 @@ Accept wildcard characters: False ``` ### -ServiceName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ServiceName parameter identifies Microsoft Exchange to other partner applications such as SharePoint 2013. Exchange Setup configures the ServiceName parameter with a specific constant value. You shouldn't change this parameter. Changing the ServiceName parameter can result in server-to-server authentication with partner applications not functioning. @@ -265,7 +289,6 @@ Exchange Setup configures the ServiceName parameter with a specific constant val Type: String Parameter Sets: AuthConfigSettings Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -275,6 +298,9 @@ Accept wildcard characters: False ``` ### -SkipImmediateCertificateDeployment + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SkipImmediateCertificateDeployment switch specifies that the certificate shouldn't be used immediately. You don't need to specify a value with this switch. We don't recommend using this switch in a production environment. @@ -283,7 +309,6 @@ We don't recommend using this switch in a production environment. Type: SwitchParameter Parameter Sets: CurrentCertificateParameter, NewCertificateParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,13 +318,15 @@ 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/exchange/Set-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AuthRedirect.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md index e39dde30f7..1b39931a82 100644 --- a/exchange/exchange-ps/exchange/Set-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-authredirect applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AuthRedirect -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-authredirect +schema: 2.0.0 +title: Set-AuthRedirect --- # Set-AuthRedirect @@ -51,13 +52,15 @@ This example sets the TargetURL value for all existing OAuth redirection objects ## 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 modify. The object name uses the syntax `AuthRedirect-Bearer-GUID`. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect. ```yaml Type: AuthRedirectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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: True Position: Named @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ 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 2013 Client Access server that will process the Oauth request. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,13 +127,15 @@ 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/exchange/Set-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-AuthServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md index 7caef4d3c2..ee283c600e 100644 --- a/exchange/exchange-ps/exchange/Set-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-authserver applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AuthServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-authserver +schema: 2.0.0 +title: Set-AuthServer --- # Set-AuthServer @@ -94,6 +95,9 @@ This command disables the authorization server ACS. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the authorization server object that you want to modify. You can use any value that uniquely identifies the authorization server. For example: - Name @@ -104,7 +108,6 @@ 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 Required: True Position: 1 @@ -114,6 +117,9 @@ 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 }} @@ -122,7 +128,6 @@ 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 @@ -132,13 +137,15 @@ Accept wildcard characters: False ``` ### -AuthMetadataUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthMetadataUrl parameter specifies the URL of the authorization server. This can be the AuthMetadataUrl of your Exchange Online organization. ```yaml Type: String Parameter Sets: AuthMetadataUrl, NativeClientAuthServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -148,6 +155,9 @@ 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`. @@ -157,7 +167,6 @@ 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 @@ -167,13 +176,15 @@ 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 @@ -183,6 +194,9 @@ Accept wildcard characters: False ``` ### -DomainName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher). The DomainName parameter specifies the tenant domain that's linked with the AuthServer object. This parameter uses the syntax: "tenantname.onmicrosoft.com". @@ -193,7 +207,6 @@ This parameter is used to link Tenant to the corresponding authserver object in Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -203,6 +216,9 @@ 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. Only enabled authorization servers can issue and accept tokens. Disabling the authorization server prevents any partner applications configured to use the authorization server from getting a token. The Enabled parameter specifies whether the authorization server is enabled. Valid values are: @@ -214,7 +230,6 @@ 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 @@ -224,6 +239,9 @@ Accept wildcard characters: False ``` ### -IsDefaultAuthorizationEndpoint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsDefaultAuthorizationEndpoint parameter specifies whether this server is the default authorization endpoint. Valid values are: $true: The authorization server's URL is advertised to calling partner applications and applications that need to get their OAuth access tokens from the authorization server. @@ -234,7 +252,6 @@ $false: The authorization server's URL is not advertised. The default value is $ Type: Boolean Parameter Sets: NativeClientAuthServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -244,13 +261,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -260,13 +279,15 @@ Accept wildcard characters: False ``` ### -RefreshAuthMetadata + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RefreshAuthMetadata switch specifies whether Exchange should refresh the auth metadata from the specified URL. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: RefreshAuthMetadata Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -276,6 +297,9 @@ 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. @@ -284,7 +308,6 @@ 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 @@ -294,13 +317,15 @@ 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/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 5f9a01b922..dfbc58bcc8 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-authenticationpolicy applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-AuthenticationPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-authenticationpolicy +schema: 2.0.0 +title: Set-AuthenticationPolicy --- # Set-AuthenticationPolicy @@ -87,6 +88,9 @@ In Exchange Online, this example blocks legacy Exchange tokens from being issued ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + The Identity parameter specifies the authentication policy you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -97,7 +101,6 @@ The Identity parameter specifies the authentication policy you want to modify. Y Type: AuthPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -107,6 +110,9 @@ 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 Active Sync. @@ -118,7 +124,6 @@ The AllowBasicAuthActiveSync switch specifies whether to allow Basic authenticat Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -128,6 +133,9 @@ 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. @@ -139,7 +147,6 @@ The AllowBasicAuthAutodiscover switch specifies whether to allow Basic authentic Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -149,6 +156,9 @@ 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. @@ -160,7 +170,6 @@ The AllowBasicAuthImap switch specifies whether to allow Basic authentication wi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -170,6 +179,9 @@ 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. @@ -181,7 +193,6 @@ The AllowBasicAuthMapi switch specifies whether to allow Basic authentication wi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -191,6 +202,9 @@ 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. @@ -202,7 +216,6 @@ The AllowBasicAuthOfflineAddressBook switch specifies whether to allow Basic aut Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -212,6 +225,9 @@ 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. @@ -223,7 +239,6 @@ The AllowBasicAuthOutlookService switch specifies whether to allow Basic authent Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -233,6 +248,9 @@ 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. @@ -244,7 +262,6 @@ The AllowBasicAuthPop switch specifies whether to allow Basic authentication wit Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -254,6 +271,9 @@ 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. @@ -265,7 +285,6 @@ The AllowBasicAuthPowerShell switch specifies whether to allow Basic authenticat Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -275,6 +294,9 @@ 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. @@ -286,7 +308,6 @@ The AllowBasicAuthReporting Web Services switch specifies whether to allow Basic Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -296,6 +317,9 @@ 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. @@ -307,7 +331,6 @@ The AllowBasicAuthRpc switch specifies whether to allow Basic authentication wit Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -317,6 +340,9 @@ 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. @@ -328,7 +354,6 @@ The AllowBasicAuthSmtp switch specifies whether to allow Basic authentication wi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -338,6 +363,9 @@ 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). @@ -349,7 +377,6 @@ The AllowBasicAuthWebServices switch specifies whether to allow Basic authentica Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -359,6 +386,9 @@ 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 to allow legacy Exchange tokens to be issued to Outlook add-ins. You don't need to specify a value with this switch. @@ -377,7 +407,6 @@ The switch applies to the entire organization. The Identity parameter is require Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -387,6 +416,9 @@ 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. @@ -398,7 +430,6 @@ The BlockLegacyAuthActiveSync switch specifies whether to allow only modern auth Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -408,6 +439,9 @@ 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. @@ -419,7 +453,6 @@ The BlockLegacyAuthAutodiscover switch specifies whether to allow only modern au Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -429,6 +462,9 @@ 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. @@ -440,7 +476,6 @@ The BlockLegacyAuthImap switch specifies whether to allow only modern authentica Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -450,6 +485,9 @@ 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. @@ -461,7 +499,6 @@ The BlockLegacyAuthMapi switch specifies whether to allow only modern authentica Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -471,6 +508,9 @@ 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. @@ -482,7 +522,6 @@ The BlockLegacyAuthOfflineAddressBook switch specifies whether to allow only mod Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -492,6 +531,9 @@ 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. @@ -503,7 +545,6 @@ The BlockLegacyAuthPop switch specifies whether to allow only modern authenticat Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -513,6 +554,9 @@ 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. @@ -524,7 +568,6 @@ The BlockLegacyAuthRpc switch specifies whether to allow only modern authenticat Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -534,6 +577,9 @@ 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. @@ -545,7 +591,6 @@ The BlockLegacyAuthWebServices switch specifies whether to allow only modern aut Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -555,6 +600,9 @@ Accept wildcard characters: False ``` ### -BlockLegacyExchangeTokens + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The BlockLegacyExchangeTokens switch specifies to block legacy Exchange tokens being issued to Outlook add-ins. You don't need to specify a value with this switch. @@ -575,7 +623,6 @@ The switch applies to the entire organization. The Identity parameter is require Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -585,6 +632,9 @@ 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. @@ -593,7 +643,6 @@ The BlockModernAuthActiveSync switch specifies whether to block modern authentic Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -603,6 +652,9 @@ 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. @@ -611,7 +663,6 @@ The BlockModernAuthAutodiscover switch specifies whether to block modern authent Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -621,6 +672,9 @@ 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. @@ -629,7 +683,6 @@ The BlockModernAuthImap switch specifies whether to block modern authentication Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -639,6 +692,9 @@ 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. @@ -647,7 +703,6 @@ The BlockModernAuthMapi switch specifies whether to block modern authentication Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -657,6 +712,9 @@ 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. @@ -665,7 +723,6 @@ The BlockModernAuthOfflineAddressBook switch specifies whether to block modern a Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -675,6 +732,9 @@ 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. @@ -683,7 +743,6 @@ The BlockModernAuthPop switch specifies whether to block modern authentication w Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -693,6 +752,9 @@ 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. @@ -701,7 +763,6 @@ The BlockModernAuthRpc switch specifies whether to block modern authentication w Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -711,6 +772,9 @@ 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. @@ -719,7 +783,6 @@ The BlockModernAuthWebServices switch specifies whether to block modern authenti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -729,6 +792,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> 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`. @@ -738,7 +804,6 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -748,6 +813,9 @@ Accept wildcard characters: False ``` ### -TenantId + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill TenantId Description }} @@ -756,7 +824,6 @@ 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 @@ -766,13 +833,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> 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: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md index 08f50e337c..bc67c44026 100644 --- a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-autosensitivitylabelpolicy applicable: Security & Compliance -title: Set-AutoSensitivityLabelPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-autosensitivitylabelpolicy +schema: 2.0.0 +title: Set-AutoSensitivityLabelPolicy --- # Set-AutoSensitivityLabelPolicy @@ -103,6 +104,9 @@ This example adds the specified URLs to the SharePoint and OneDrive locations fo ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the auto-labeling policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -113,7 +117,6 @@ The Identity parameter specifies the auto-labeling policy that you want to modif Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -123,6 +126,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter adds email messages to the policy if they're not already included. The valid value for this parameter is All. If the policy doesn't already include email messages (in the output of the Get-AutoSensitivityLabelPolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures: @@ -143,7 +149,6 @@ You can't specify inclusions and exclusions in the same policy. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -153,6 +158,9 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocation + +> Applicable: Security & Compliance + The AddOneDriveLocation parameter specifies the OneDrive sites to add to the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -161,7 +169,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddOneDriveLocationException parameter specifies the OneDrive sites to add to the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -179,7 +189,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites when you aren't using the value All for the SharePointLocation parameter. You identify the site by its URL value. SharePoint sites can't be added to the policy until they have been indexed. @@ -199,7 +211,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddSharePointLocationException parameter specifies the SharePoint sites to add to the list of excluded sites when you use the value All for the SharePointLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -217,7 +231,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The ApplySensitivityLabel parameter selects which label to be used for the policy. This will override the previous label on the policy. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -243,6 +258,9 @@ Accept wildcard characters: False ``` ### -AutoEnableAfter + +> Applicable: Security & Compliance + The AutoEnableAfter parameter allows you to automatically turn on the policy after a set time period in simulation with no modifications to the policy. You need to explicitly set this parameter after each policy edit to keep or reset the automatic turn on timeline. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -255,7 +273,6 @@ You must use this parameter with the -StartSimulation parameter. Type: System.TimeSpan Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -265,13 +282,15 @@ 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: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -281,6 +300,9 @@ 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`. @@ -290,7 +312,6 @@ 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 @@ -300,6 +321,9 @@ 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. @@ -309,7 +333,6 @@ The Enabled parameter enables or disables the policy. Valid values are: Type: Boolean Parameter Sets: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -319,6 +342,9 @@ 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, one of the following statements must be true: @@ -334,7 +360,6 @@ You can't use this parameter with the OneDriveSharedBy parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -344,13 +369,15 @@ Accept wildcard characters: False ``` ### -ExceptIfOneDriveSharedByMemberOf + +> Applicable: Security & Compliance + {{ Fill ExceptIfOneDriveSharedByMemberOf Description }} ```yaml Type: RecipientIdParameter[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -360,13 +387,15 @@ Accept wildcard characters: False ``` ### -ExchangeAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill ExchangeAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -376,13 +405,15 @@ Accept wildcard characters: False ``` ### -ExchangeAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill ExchangeAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -392,6 +423,9 @@ Accept wildcard characters: False ``` ### -ExchangeSender + +> Applicable: Security & Compliance + The ExchangeSender parameter specifies the users whose email is included in the policy. You specify 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: `"","",...""`. @@ -407,7 +441,6 @@ You can't use this parameter with the ExchangeSenderException or ExchangeSenderM Type: SmtpAddress[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -417,6 +450,9 @@ 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: `"","",...""`. @@ -432,7 +468,6 @@ You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf p Type: SmtpAddress[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -442,6 +477,9 @@ 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: `"","",...""`. @@ -459,7 +497,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: SmtpAddress[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -469,6 +506,9 @@ 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: `"","",...""`. @@ -486,7 +526,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: SmtpAddress[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -496,6 +535,9 @@ 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. @@ -506,7 +548,6 @@ To clear an existing email address, use the value $null. Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -516,6 +557,9 @@ 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. @@ -524,7 +568,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -534,13 +577,15 @@ Accept wildcard characters: False ``` ### -Locations + +> Applicable: Security & Compliance + {{ Fill Locations Description }} ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -550,6 +595,9 @@ 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. @@ -562,7 +610,6 @@ Type: PolicyMode Parameter Sets: (All) Aliases: Accepted values: Enable, TestWithNotifications, TestWithoutNotifications, Disable, PendingDeletion -Applicable: Security & Compliance Required: False Position: Named @@ -572,13 +619,15 @@ Accept wildcard characters: False ``` ### -OneDriveAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill OneDriveAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -588,13 +637,15 @@ Accept wildcard characters: False ``` ### -OneDriveAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill OneDriveAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -604,6 +655,9 @@ 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, one of the following statements must be true: @@ -619,7 +673,6 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -629,13 +682,15 @@ Accept wildcard characters: False ``` ### -OneDriveSharedByMemberOf + +> Applicable: Security & Compliance + {{ Fill OneDriveSharedByMemberOf Description }} ```yaml Type: RecipientIdParameter[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -645,6 +700,9 @@ 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. @@ -656,7 +714,6 @@ This parameter works only on Exchange locations. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -666,6 +723,9 @@ 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. @@ -674,7 +734,6 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -684,13 +743,15 @@ Accept wildcard characters: False ``` ### -PolicyTemplateInfo + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: PswsHashtable Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -700,6 +761,9 @@ Accept wildcard characters: False ``` ### -Priority + +> 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 for this parameter depend on the number of existing policies. For example, if there are 5 existing policies: @@ -714,7 +778,6 @@ If you modify the priority value of a policy, the position of the policy in the Type: System.Int32 Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -724,6 +787,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter removes email messages from the policy if they're already included. The valid value for this parameter is All. If the policy already includes email messages (in the output of the Get-AutoSensitivityLabelPolicy cmdlet, the ExchangeLocation property value is All), you can use `-RemoveExchangeLocation All` to prevent the policy from applying to email messages. @@ -734,7 +800,6 @@ You can't use this parameter if email (the value Exchange) is used by any of the Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -744,6 +809,9 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocation + +> Applicable: Security & Compliance + The RemoveOneDriveLocation parameter specifies the OneDrive sites to remove from the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -752,7 +820,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + This RemoveOneDriveLocationException parameter specifies the OneDrive sites to remove from the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -770,7 +840,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites when you aren't using the value All for the SharePointLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -788,7 +860,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveSharePointLocationException parameter specifies the SharePoint sites to remove from the list of excluded sites when you use the value All for the SharePointLocation parameter. You identify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -806,7 +880,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RetryDistribution switch redistributes the policy to all OneDrive and SharePoint locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -826,7 +902,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistributionParameterSet Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -836,13 +911,15 @@ Accept wildcard characters: False ``` ### -SharePointAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill SharePointAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -852,13 +929,15 @@ Accept wildcard characters: False ``` ### -SharePointAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill SharePointAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -868,6 +947,9 @@ Accept wildcard characters: False ``` ### -SpoAipIntegrationEnabled + +> Applicable: Security & Compliance + The SpoAipIntegrationEnabled parameter enables or disables built-in labeling for supported Office files in SharePoint and OneDrive. Valid values are: - $true: Users can apply your sensitivity labels in Office for the web. Users see the Sensitivity button on the ribbon so they can apply labels, and they see the name of any applied label on the status bar. @@ -877,7 +959,6 @@ The SpoAipIntegrationEnabled parameter enables or disables built-in labeling for Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -887,6 +968,9 @@ Accept wildcard characters: False ``` ### -StartSimulation + +> Applicable: Security & Compliance + Use the StartSimulation parameter to restart the simulation for updated results. Valid values are: - $true: Restart the simulation for updated results. **Any edits to an auto-labeling policy require restarting the simulation by using this value.** @@ -896,7 +980,6 @@ Use the StartSimulation parameter to restart the simulation for updated results. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -906,13 +989,15 @@ 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/exchange/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md index f477c1b30d..1b532e043a 100644 --- a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-autosensitivitylabelrule applicable: Security & Compliance -title: Set-AutoSensitivityLabelRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-autosensitivitylabelrule +schema: 2.0.0 +title: Set-AutoSensitivityLabelRule --- # Set-AutoSensitivityLabelRule @@ -98,6 +99,9 @@ This example changes the rule property "Comment" with the rule name "SocialSecur ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the auto-labeling policy rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -108,7 +112,6 @@ The Identity parameter specifies the auto-labeling policy rule that you want to Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -118,6 +121,9 @@ 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. @@ -129,7 +135,6 @@ Type: AccessScope Parameter Sets: (All) Aliases: Accepted values: InOrganization, NotInOrganization, None -Applicable: Security & Compliance Required: False Position: Named @@ -139,13 +144,15 @@ Accept wildcard characters: False ``` ### -ActivationDate + +> Applicable: Security & Compliance + {{ Fill ActivationDate Description }} ```yaml Type: System.DateTime Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -155,6 +162,9 @@ 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"` @@ -169,7 +179,6 @@ 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 @@ -179,6 +188,9 @@ 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. @@ -189,7 +201,6 @@ 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 @@ -199,13 +210,15 @@ 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 @@ -215,6 +228,9 @@ 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`. @@ -224,7 +240,6 @@ 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,6 +249,9 @@ 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"})`. @@ -246,7 +264,6 @@ To use groups: `@(@{operator="And"; groups=@(@{name="Default"; operator="Or"; se Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -256,13 +273,15 @@ 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 @@ -272,6 +291,9 @@ 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"`. @@ -280,7 +302,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -290,13 +311,15 @@ Accept wildcard characters: False ``` ### -DefaultSpoDocLibraryHasLabel + +> Applicable: Security & Compliance + {{ Fill DefaultSpoDocLibraryHasLabel Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -306,6 +329,9 @@ 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. @@ -315,7 +341,6 @@ 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 @@ -325,13 +350,15 @@ 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 @@ -341,6 +368,9 @@ 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. @@ -350,7 +380,6 @@ The DocumentIsPasswordProtected parameter specifies a condition for the auto-lab Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -360,6 +389,9 @@ 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. @@ -369,7 +401,6 @@ The DocumentIsUnsupported parameter specifies a condition for the auto-labeling Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -379,6 +410,9 @@ Accept wildcard characters: False ``` ### -DocumentNameMatchesWords + +> Applicable: Security & Compliance + The DocumentNameMatchesWords parameter specifies a condition for the auto-labeling policy rule that looks for whole word matches in the name of message attachments. You can specify multiple words separated by commas. - Single word: `"no_reply"` @@ -390,7 +424,6 @@ The maximum individual word length is 128 characters. The maximum number of word Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -400,6 +433,9 @@ 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: @@ -418,7 +454,6 @@ 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 @@ -428,6 +463,9 @@ 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. @@ -439,7 +477,6 @@ Type: AccessScope Parameter Sets: (All) Aliases: Accepted values: InOrganization, NotInOrganization, None -Applicable: Security & Compliance Required: False Position: Named @@ -449,6 +486,9 @@ 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"` @@ -463,7 +503,6 @@ 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 @@ -473,6 +512,9 @@ 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. @@ -483,7 +525,6 @@ 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 @@ -493,6 +534,9 @@ 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"})`. @@ -501,7 +545,6 @@ This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minC Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -511,13 +554,15 @@ 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 @@ -527,6 +572,9 @@ 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"`. @@ -535,7 +583,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -545,13 +592,15 @@ 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 @@ -561,6 +610,9 @@ 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. @@ -570,7 +622,6 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -580,6 +631,9 @@ 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. @@ -589,7 +643,6 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the auto- Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -599,6 +652,9 @@ 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"` @@ -611,7 +667,6 @@ 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 @@ -621,6 +676,9 @@ 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: @@ -639,7 +697,6 @@ 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 @@ -649,6 +706,9 @@ 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 @@ -662,7 +722,6 @@ 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 @@ -672,6 +731,9 @@ 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"` @@ -686,7 +748,6 @@ 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 @@ -696,6 +757,9 @@ 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. @@ -706,7 +770,6 @@ 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 @@ -716,6 +779,9 @@ 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"`. @@ -724,7 +790,6 @@ 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 @@ -734,6 +799,9 @@ 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. @@ -742,7 +810,6 @@ 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 @@ -752,6 +819,9 @@ 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. @@ -761,7 +831,6 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the aut Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -771,13 +840,15 @@ 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 @@ -787,6 +858,9 @@ 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. @@ -795,7 +869,6 @@ 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 @@ -805,6 +878,9 @@ 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. @@ -817,7 +893,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -827,6 +902,9 @@ 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 @@ -844,7 +922,6 @@ 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 @@ -854,6 +931,9 @@ 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. @@ -862,7 +942,6 @@ 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 @@ -872,6 +951,9 @@ 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. @@ -882,7 +964,6 @@ 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 @@ -892,13 +973,15 @@ 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 @@ -908,13 +991,15 @@ 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 @@ -924,6 +1009,9 @@ 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"` @@ -938,7 +1026,6 @@ 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 @@ -948,6 +1035,9 @@ 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. @@ -958,7 +1048,6 @@ 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 @@ -968,13 +1057,15 @@ 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 @@ -984,6 +1075,9 @@ 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. @@ -992,7 +1086,6 @@ 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 @@ -1002,13 +1095,15 @@ 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 @@ -1018,6 +1113,9 @@ 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. @@ -1027,7 +1125,6 @@ The ProcessingLimitExceeded parameter specifies a condition for the auto-labelin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1037,13 +1134,15 @@ 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 @@ -1053,6 +1152,9 @@ 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. @@ -1065,7 +1167,6 @@ Type: RuleSeverity Parameter Sets: (All) Aliases: Accepted values: Low, Medium, High, None, Informational, Information -Applicable: Security & Compliance Required: False Position: Named @@ -1075,6 +1176,9 @@ 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 @@ -1086,7 +1190,6 @@ Type: PolicyRuleErrorAction Parameter Sets: (All) Aliases: Accepted values: Ignore, RetryThenBlock -Applicable: Security & Compliance Required: False Position: Named @@ -1096,6 +1199,9 @@ 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. @@ -1104,7 +1210,6 @@ 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 @@ -1114,6 +1219,9 @@ 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. @@ -1126,7 +1234,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1136,6 +1243,9 @@ 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 @@ -1153,7 +1263,6 @@ 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 @@ -1163,6 +1272,9 @@ 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. @@ -1171,7 +1283,6 @@ 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 @@ -1181,13 +1292,15 @@ 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 @@ -1197,6 +1310,9 @@ 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. @@ -1207,7 +1323,6 @@ 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 @@ -1217,13 +1332,15 @@ 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 @@ -1233,6 +1350,9 @@ Accept wildcard characters: False ``` ### -Workload + +> Applicable: Security & Compliance + The Workload parameter specifies the workload. Valid values are: - Exchange @@ -1244,7 +1364,6 @@ Type: Workload Parameter Sets: (All) Aliases: Accepted values: Exchange, SharePoint, OneDriveForBusiness -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md index 21d6376337..bfe1b41ab2 100644 --- a/exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-autodiscovervirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-AutodiscoverVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-autodiscovervirtualdirectory +schema: 2.0.0 +title: Set-AutodiscoverVirtualDirectory --- # Set-AutodiscoverVirtualDirectory @@ -67,6 +68,9 @@ This example sets Integrated Windows authentication for the Autodiscover virtual ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -79,7 +83,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -89,6 +92,9 @@ 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. @@ -98,7 +104,6 @@ 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 @@ -108,6 +113,9 @@ 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`. @@ -117,7 +125,6 @@ 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 @@ -127,6 +134,9 @@ 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. @@ -136,7 +146,6 @@ 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 @@ -146,13 +155,15 @@ 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 @@ -162,6 +173,9 @@ 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. @@ -174,7 +188,6 @@ 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 @@ -184,6 +197,9 @@ 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. @@ -193,7 +209,6 @@ 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 @@ -203,6 +218,9 @@ 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. @@ -215,7 +233,6 @@ 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 @@ -225,6 +242,9 @@ 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. @@ -233,7 +253,6 @@ 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 @@ -243,6 +262,9 @@ 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. @@ -251,7 +273,6 @@ 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 @@ -261,6 +282,9 @@ 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. @@ -270,7 +294,6 @@ 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 @@ -280,13 +303,15 @@ 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 @@ -296,6 +321,9 @@ 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. @@ -305,7 +333,6 @@ 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 @@ -315,6 +342,9 @@ 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. @@ -324,7 +354,6 @@ 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/exchange/Set-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-AvailabilityConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md index 7fc266524e..c66f690223 100644 --- a/exchange/exchange-ps/exchange/Set-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-availabilityconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-AvailabilityConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-availabilityconfig +schema: 2.0.0 +title: Set-AvailabilityConfig --- # Set-AvailabilityConfig @@ -66,6 +67,9 @@ In Exchange Online, this example allows free/busy sharing only with the specifie ## PARAMETERS ### -AllowedTenantIds + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. 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. @@ -78,7 +82,6 @@ To add or remove tenant IDs without affecting other existing values, use the fol Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -88,6 +91,9 @@ 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`. @@ -97,7 +103,6 @@ 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 @@ -107,6 +112,9 @@ 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. @@ -115,7 +123,6 @@ 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,6 +132,9 @@ Accept wildcard characters: False ``` ### -OrgWideAccount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The OrgWideAccount parameter specifies who has permission to issue proxy Availability service requests on an organization-wide basis. You can specify the following types of users or groups (security principals) for this parameter: @@ -150,7 +160,6 @@ 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 Required: False Position: Named @@ -160,6 +169,9 @@ Accept wildcard characters: False ``` ### -PerUserAccount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PerUserAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on a per-user basis. @@ -181,7 +193,6 @@ 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 Required: False Position: Named @@ -191,13 +202,15 @@ 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/exchange/Set-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md rename to exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md index 051ad1654f..ca7105eb69 100644 --- a/exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-availabilityreportoutage applicable: Exchange Server 2010 -title: Set-AvailabilityReportOutage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-availabilityreportoutage +schema: 2.0.0 +title: Set-AvailabilityReportOutage --- # Set-AvailabilityReportOutage @@ -59,13 +60,15 @@ This example overrides the specified outage with a new downtime value of 40 minu ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the outage to add to the outage reporting. ```yaml Type: AvailabilityReportOutageIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -75,13 +78,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010 + The Comment parameter describes the outage that was inserted. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -91,13 +96,15 @@ 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 @@ -107,13 +114,15 @@ Accept wildcard characters: False ``` ### -ResetToOriginal + +> Applicable: Exchange Server 2010 + The ResetToOriginal switch resets the previously selected outage value to the default value. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ResetToOriginal Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -123,6 +132,9 @@ 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`. @@ -132,7 +144,6 @@ 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 @@ -142,13 +153,15 @@ 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: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -158,6 +171,9 @@ 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. @@ -166,7 +182,6 @@ 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 @@ -176,13 +191,15 @@ 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 @@ -192,13 +209,15 @@ 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 @@ -208,13 +227,15 @@ 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/exchange/Set-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-CASMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md index 6ff7e5c704..1273e6d10c 100644 --- a/exchange/exchange-ps/exchange/Set-CASMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-casmailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-CASMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-casmailbox +schema: 2.0.0 +title: Set-CASMailbox --- # Set-CASMailbox @@ -108,6 +109,9 @@ This example sets the display name and disables Outlook Anywhere access for the ## 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 configure. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -125,7 +129,6 @@ The Identity parameter specifies the mailbox that you want to configure. You can 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 @@ -135,6 +138,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncAllowedDeviceIDs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + TheActiveSyncAllowedDeviceIDs parameter specifies one or more Exchange ActiveSync device IDs that are allowed to synchronize with the mailbox. A device ID is a text string that uniquely identifies the device. Use the Get-MobileDevice cmdlet to see the devices that have Exchange ActiveSync partnerships with the mailbox. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -147,7 +153,6 @@ To clear the list of device IDs, use the value $null for this parameter. 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 @@ -157,6 +162,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncBlockedDeviceIDs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncBlockedDeviceIDs parameter specifies one or more Exchange ActiveSync device IDs that aren't allowed to synchronize with the mailbox. A device ID is a text string that uniquely identifies the device. Use the Get-MobileDevice cmdlet to see the devices that have Exchange ActiveSync partnerships with the mailbox. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -169,7 +177,6 @@ To clear the list of device IDs, use the value $null for this parameter. 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 @@ -179,6 +186,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncDebugLogging + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync debug logging for the mailbox. Valid values are: - $true: ActiveSync debug logging is enabled for 48 hours in Exchange Online, and 72 hours in Exchange Server. After the time period expires, the value reverts to $false. @@ -188,7 +198,6 @@ The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync deb 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 @@ -198,6 +207,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncEnabled parameter enables or disables access to the mailbox using Exchange ActiveSync. Valid values are: - $true: Access to the mailbox using ActiveSync is enabled. This is the default value. @@ -209,7 +221,6 @@ For more information, see [Enable or disable Exchange ActiveSync for a mailbox i 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 @@ -219,6 +230,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncMailboxPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncMailboxPolicy parameter specifies the Exchange ActiveSync mailbox policy for the mailbox. You can use any value that uniquely identifies the Exchange ActiveSync mailbox policy. For example: - Name @@ -231,7 +245,6 @@ The name of the default Exchange ActiveSync mailbox policy is Default. However, Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -241,6 +254,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncSuppressReadReceipt + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncSuppressReadReceipt parameter controls the behavior of read receipts for Exchange ActiveSync clients that access the mailbox. Valid values are: - $true: Read receipts are not automatically returned when the user opens a message sent with a read receipt request. @@ -250,7 +266,6 @@ The ActiveSyncSuppressReadReceipt parameter controls the behavior of read receip Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -260,6 +275,9 @@ 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`. @@ -269,7 +287,6 @@ 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 @@ -279,6 +296,9 @@ 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 ("). @@ -287,7 +307,6 @@ The DisplayName parameter specifies the display name of the mailbox. The display Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,6 +316,9 @@ 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. @@ -305,7 +327,6 @@ 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 @@ -315,6 +336,9 @@ Accept wildcard characters: False ``` ### -ECPEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ECPEnabled parameter enables or disables access the Exchange admin center (EAC) or the Exchange Control Panel (ECP) for the specified user. Valid values are: @@ -326,7 +350,6 @@ The ECPEnabled parameter enables or disables access the Exchange admin center (E Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -336,6 +359,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). @@ -363,7 +389,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -373,6 +398,9 @@ Accept wildcard characters: False ``` ### -EwsAllowEntourage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowEntourage parameter enables or disables access to the mailbox by Microsoft Entourage clients that use Exchange Web Services (for example, Entourage 2008 for Mac, Web Services Edition). - $true: Access to the mailbox using Microsoft Entourage is enabled. This is the default value. @@ -382,7 +410,6 @@ The EwsAllowEntourage parameter enables or disables access to the mailbox by Mic 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 @@ -392,6 +419,9 @@ Accept wildcard characters: False ``` ### -EwsAllowList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowList parameter specifies the Exchange Web Services applications (user agent strings) that are allowed to access the mailbox. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -404,7 +434,6 @@ This parameter is meaningful only when the EwsEnabled parameter is set to $true, 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 @@ -414,6 +443,9 @@ Accept wildcard characters: False ``` ### -EwsAllowMacOutlook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowMacOutlook parameter enables or disables access to the mailbox by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later). Valid values are: - $true: Outlook for Mac clients that use EWS are allowed to access the mailbox. This is the default value. @@ -425,7 +457,6 @@ In the cloud-based service, access for Outlook for Mac clients that use Microsof 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 @@ -435,6 +466,9 @@ Accept wildcard characters: False ``` ### -EwsAllowOutlook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowOutlook parameter enables or disables access to the mailbox by Outlook clients that use Exchange Web Services. Outlook uses Exchange Web Services for free/busy, out-of-office settings, and calendar sharing. Valid values are: - $true: Access to the mailbox using EWS in Outlook clients is enabled. @@ -444,7 +478,6 @@ The EwsAllowOutlook parameter enables or disables access to the mailbox by Outlo 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 @@ -454,6 +487,9 @@ Accept wildcard characters: False ``` ### -EwsApplicationAccessPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsApplicationAccessPolicy parameter controls access to the mailbox using Exchange Web Services applications. Valid values for this parameter are: @@ -467,7 +503,6 @@ This parameter doesn't affect access to the mailbox using Entourage, Outlook for Type: EwsApplicationAccessPolicy Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -477,6 +512,9 @@ Accept wildcard characters: False ``` ### -EwsBlockList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsBlockList parameter specifies the Exchange Web Services applications (user agent strings) that aren't allowed to access the mailbox using Exchange Web Services. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -489,7 +527,6 @@ This parameter is meaningful only when the EwsEnabled parameter is set to $true, 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 @@ -499,6 +536,9 @@ Accept wildcard characters: False ``` ### -EwsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsEnabled parameter enables or disables access to the mailbox using Exchange Web Services clients. Valid values are: - $true: Access to the mailbox using EWS is enabled. This is the default value. @@ -510,7 +550,6 @@ The value of this parameter is meaningful only if the EwsEnabled parameter on th 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 @@ -520,6 +559,9 @@ Accept wildcard characters: False ``` ### -HasActiveSyncDevicePartnership + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The HasActiveSyncDevicePartnership parameter specifies whether the mailbox has an Exchange ActiveSync device partnership established. Valid values are: @@ -531,7 +573,6 @@ The HasActiveSyncDevicePartnership parameter specifies whether the mailbox has a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -541,6 +582,9 @@ 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. @@ -554,7 +598,6 @@ 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 @@ -564,6 +607,9 @@ Accept wildcard characters: False ``` ### -ImapEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImapEnabled parameter enables or disables access to the mailbox using IMAP4 clients. Valid values are: - $true: Access to the mailbox using IMAP4 is enabled. This is the default value. @@ -575,7 +621,6 @@ For more information, see [Enable or Disable POP3 or IMAP4 access for a user in 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 @@ -585,6 +630,9 @@ Accept wildcard characters: False ``` ### -ImapEnableExactRFC822Size + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ImapEnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients that access the mailbox. Valid values are: @@ -598,7 +646,6 @@ We don't recommend changing this value unless you determine that the default set Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -608,6 +655,9 @@ Accept wildcard characters: False ``` ### -ImapForceICalForCalendarRetrievalOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImapForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to IMAP4 clients that access the mailbox. Valid values are: - $true: All meeting requests are in the iCal format. @@ -619,7 +669,6 @@ To change the value of this parameter, you also need to set the value of the Ima Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -629,6 +678,9 @@ Accept wildcard characters: False ``` ### -ImapMessagesRetrievalMimeFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImapMessagesRetrievalMimeFormat parameter specifies the message format for IMAP4 clients that access the mailbox. You can use an integer or a text value. Valid values are: - 0: TextOnly @@ -645,7 +697,6 @@ To change the value of this parameter, you also need to set the value of the Ima Type: MimeTextFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -655,6 +706,9 @@ Accept wildcard characters: False ``` ### -ImapSuppressReadReceipt + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImapSuppressReadReceipt parameter controls the behavior of read receipts for IMAP4 clients that access the mailbox. Valid values are: - $true: The user receives a read receipt when the recipient opens the message. @@ -666,7 +720,6 @@ To change the value of this parameter, you also need to set the value of the Ima 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 @@ -676,6 +729,9 @@ Accept wildcard characters: False ``` ### -ImapUseProtocolDefaults + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImapUseProtocolDefaults parameter specifies whether to use the IMAP4 protocol defaults for the mailbox. Valid values are: - $true: Use the protocol defaults for IMAP4 access to the mailbox. This is the default value. @@ -692,7 +748,6 @@ You need to set this parameter to $false when you use any of the following IMAP4 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 @@ -702,6 +757,9 @@ Accept wildcard characters: False ``` ### -IsOptimizedForAccessibility + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The IsOptimizedForAccessibility parameter specifies whether the mailbox is configured to use the light version of Outlook on the web. Valid values are: @@ -713,7 +771,6 @@ The IsOptimizedForAccessibility parameter specifies whether the mailbox is confi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -723,6 +780,9 @@ Accept wildcard characters: False ``` ### -MacOutlookEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MacOutlookEnabled parameter enables or disables access to the mailbox using Outlook for Mac clients that use Microsoft Sync technology. Valid values are: @@ -736,7 +796,6 @@ Access for older Outlook for Mac clients that use Exchange Web Services is contr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -746,6 +805,9 @@ Accept wildcard characters: False ``` ### -MAPIBlockOutlookNonCachedMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MAPIBlockOutlookNonCachedMode parameter controls access to the mailbox using Outlook in online or offline mode. Valid values are: @@ -757,7 +819,6 @@ The MAPIBlockOutlookNonCachedMode parameter controls access to the mailbox using Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -767,6 +828,9 @@ Accept wildcard characters: False ``` ### -MAPIBlockOutlookExternalConnectivity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MAPIBlockOutlookExternalConnectivity parameter enables or disables external access to the mailbox in Outlook by removing the external URLs from the Autodiscover response. This setting affects Outlook Anywhere, MAPI over HTTP, and Exchange Web Services (EWS). Valid values are: @@ -780,7 +844,6 @@ The MAPIBlockOutlookExternalConnectivity parameter enables or disables external Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -790,6 +853,9 @@ Accept wildcard characters: False ``` ### -MAPIBlockOutlookRpcHttp + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox in Outlook using Outlook Anywhere. Valid values are: @@ -801,7 +867,6 @@ The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -811,6 +876,9 @@ Accept wildcard characters: False ``` ### -MAPIBlockOutlookVersions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MAPIBlockOutlookVersions parameter blocks access to the mailbox for specific versions of Outlook. @@ -823,7 +891,6 @@ The default value is blank. To reset this parameter, use the value $null. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -833,6 +900,9 @@ Accept wildcard characters: False ``` ### -MAPIEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MAPIEnabled parameter enables or disables access to the mailbox using MAPI clients (for example, Outlook). Valid values are: - $true: Access to the mailbox using MAPI clients is enabled. This is the default value. @@ -844,7 +914,6 @@ For more information, see[Enable or disable MAPI for a mailbox in Exchange Onlin 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 @@ -854,6 +923,9 @@ Accept wildcard characters: False ``` ### -MapiHttpEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MapiHttpEnabled parameter enables or disables access to the mailbox in Outlook using MAPI over HTTP. Valid values are: @@ -866,7 +938,6 @@ The MapiHttpEnabled parameter enables or disables access to the mailbox in Outlo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -876,6 +947,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Name parameter specifies the unique name of the mailbox. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). @@ -884,7 +958,6 @@ The Name parameter specifies the unique name of the mailbox. The maximum length Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -894,6 +967,9 @@ Accept wildcard characters: False ``` ### -OneWinNativeOutlookEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OneWinNativeOutlookEnabled parameter enables or disables access to the mailbox using the new Outlook for Windows. @@ -906,7 +982,6 @@ Valid values are: Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -916,6 +991,9 @@ Accept wildcard characters: False ``` ### -OutlookMobileEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookMobileEnabled parameter enables or disables access to the mailbox using Outlook for iOS and Android. Valid values are: @@ -927,7 +1005,6 @@ The OutlookMobileEnabled parameter enables or disables access to the mailbox usi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -937,6 +1014,9 @@ Accept wildcard characters: False ``` ### -OWAEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAEnabled parameter enables or disables access to the mailbox using Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are: - $true: Access to the mailbox using Outlook on the web is enabled. This is the default value. @@ -948,7 +1028,6 @@ For more information, see [Enable or disable Outlook on the web for a mailbox in 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 @@ -958,6 +1037,9 @@ Accept wildcard characters: False ``` ### -OWAforDevicesEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAforDevicesEnabled parameter enables or disables access to the mailbox using the older Outlook Web App (OWA) app on iOS and Android devices. Valid values are: - $true: Access to the mailbox using OWA for Devices is enabled. This is the default value. @@ -967,7 +1049,6 @@ The OWAforDevicesEnabled parameter enables or disables access to the mailbox usi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -977,6 +1058,9 @@ Accept wildcard characters: False ``` ### -OwaMailboxPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OwaMailboxPolicy parameter specifies the Outlook on the web mailbox policy for the mailbox. You can use any value that uniquely identifies the Outlook on the web mailbox policy. For example: - Name @@ -989,7 +1073,6 @@ The name of the default Outlook on the web mailbox policy is Default. Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -999,6 +1082,9 @@ Accept wildcard characters: False ``` ### -PopEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PopEnabled parameter enables or disables access to the mailbox using POP3 clients. Valid values are: - $true: Access to the mailbox using POP3 clients is enabled. This is the default value. @@ -1010,7 +1096,6 @@ For more information, see [Enable or Disable POP3 or IMAP4 access for a user in 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 @@ -1020,6 +1105,9 @@ Accept wildcard characters: False ``` ### -PopEnableExactRFC822Size + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PopEnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients that access the mailbox. Valid values are: @@ -1033,7 +1121,6 @@ We don't recommend changing this value unless you determine that the default set Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1043,6 +1130,9 @@ Accept wildcard characters: False ``` ### -PopForceICalForCalendarRetrievalOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PopForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to POP3 clients that access the mailbox. Valid values are: - $true: All meeting requests are in the iCal format. @@ -1054,7 +1144,6 @@ To change the value of this parameter, you also need to set the value of the Pop Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1064,6 +1153,9 @@ Accept wildcard characters: False ``` ### -PopMessagesRetrievalMimeFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PopMessagesRetrievalMimeFormat parameter specifies the message format for POP3 clients that access the mailbox. You can use an integer or a text value. Valid values are: - 0: TextOnly @@ -1080,7 +1172,6 @@ To change the value of this parameter, you also need to set the value of the Pop Type: MimeTextFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1090,6 +1181,9 @@ Accept wildcard characters: False ``` ### -PopSuppressReadReceipt + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PopSuppressReadReceipt parameter controls the behavior of read receipts for POP3 clients that access the mailbox. Valid values are: - $true: The user receives a read receipt when the recipient opens the message. @@ -1101,7 +1195,6 @@ To change the value of this parameter, you also need to set the value of the Pop 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 @@ -1111,6 +1204,9 @@ Accept wildcard characters: False ``` ### -PopUseProtocolDefaults + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PopUseProtocolDefaults parameter specifies whether to use the POP3 protocol defaults for the mailbox. Valid values are: - $true: Use the protocol defaults for POP3 access to the mailbox. This is the default value. @@ -1127,7 +1223,6 @@ You need to set this parameter to $false when you use any of following parameter 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 @@ -1137,6 +1232,9 @@ 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. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. @@ -1145,7 +1243,6 @@ The PrimarySmtpAddress parameter specifies the primary return email address that Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1155,6 +1252,9 @@ Accept wildcard characters: False ``` ### -PublicFolderClientAccess + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolderClientAccess parameter enables or disables access to public folders in Microsoft Outlook. Valid values are: - $true: The user can access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true (the default value is $false). @@ -1164,7 +1264,6 @@ The PublicFolderClientAccess parameter enables or disables access to public fold Type: Boolean Parameter Sets: AdfsAuthenticationRawConfiguration, AdfsAuthenticationParameter Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1174,6 +1273,9 @@ Accept wildcard characters: False ``` ### -ResetAutoBlockedDevices + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ResetAutoBlockedDevices switch resets the status of blocked mobile devices that have exceeded the limits defined by the Set-ActiveSyncDeviceAutoblockThreshold cmdlet. You don't need to specify a value with this switch. @@ -1182,7 +1284,6 @@ The ResetAutoBlockedDevices switch resets the status of blocked mobile devices t Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1192,6 +1293,9 @@ 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). The maximum length is 20 characters. @@ -1200,7 +1304,6 @@ 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 @@ -1210,6 +1313,9 @@ Accept wildcard characters: False ``` ### -ShowGalAsDefaultView + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowGalAsDefaultView parameter specifies whether the global address list (GAL) is the default recipient picker for messages. Valid values are: - $true: Use the GAL as the primary address picker. This is the default value. @@ -1219,7 +1325,6 @@ The ShowGalAsDefaultView parameter specifies whether the global address list (GA 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 @@ -1229,6 +1334,9 @@ Accept wildcard characters: False ``` ### -SmtpClientAuthenticationDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SmtpClientAuthenticationDisabled parameter specifies whether to disable authenticated SMTP (SMTP AUTH) for the mailbox. Examples of clients and services that require authenticated SMTP to send email messages include: @@ -1250,7 +1358,6 @@ To selectively enable authenticated SMTP for specific mailboxes only: disable au Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1260,6 +1367,9 @@ Accept wildcard characters: False ``` ### -UniversalOutlookEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The UniversalOutlookEnabled parameter enables or disables access to the mailbox using Windows 10 Mail and Calendar. Valid values are: @@ -1271,7 +1381,6 @@ The UniversalOutlookEnabled parameter enables or disables access to the mailbox Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1281,13 +1390,15 @@ 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/exchange/Set-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-CASMailboxPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md index 5901e16225..f9fe838d34 100644 --- a/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-casmailboxplan applicable: Exchange Online, Exchange Online Protection -title: Set-CASMailboxPlan -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-casmailboxplan +schema: 2.0.0 +title: Set-CASMailboxPlan --- # Set-CASMailboxPlan @@ -52,6 +53,9 @@ This example disables Exchange ActiveSync and POP3 access to mailboxes in the CA ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the CAS mailbox plan that you want to modify. You can use any value that uniquely identifies the CAS mailbox plan. For example: - Name @@ -64,7 +68,6 @@ The display name and name of the CAS mailbox plan is the same as the correspondi Type: MailboxPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -74,6 +77,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The ActiveSyncEnabled parameter enables or disables access to the mailbox by using Exchange Active Sync (EAS). Valid values are: - $true: ActiveSync access to the mailbox is enabled. This is the default value. @@ -83,7 +89,6 @@ The ActiveSyncEnabled parameter enables or disables access to the mailbox by usi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -93,6 +98,9 @@ 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`. @@ -102,7 +110,6 @@ 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 @@ -112,13 +119,15 @@ Accept wildcard characters: False ``` ### -ECPEnabled + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill ECPEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -128,13 +137,15 @@ Accept wildcard characters: False ``` ### -EwsEnabled + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill EwsEnabled Description }} ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -144,6 +155,9 @@ Accept wildcard characters: False ``` ### -ImapEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The ImapEnabled parameter enables or disables access to the mailbox by using IMAP4 clients. Valid values are: - $true: IMAP4 access to the mailbox is enabled. This is default value for all CAS mailbox plans except ExchangeOnlineDeskless. @@ -153,7 +167,6 @@ The ImapEnabled parameter enables or disables access to the mailbox by using IMA Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -163,13 +176,15 @@ Accept wildcard characters: False ``` ### -MAPIEnabled + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill MAPIEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -179,13 +194,15 @@ Accept wildcard characters: False ``` ### -OWAEnabled + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill OWAEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -195,6 +212,9 @@ Accept wildcard characters: False ``` ### -OwaMailboxPolicy + +> Applicable: Exchange Online, Exchange Online Protection + The OwaMailboxPolicy parameter specifies the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailbox. You can use any value that uniquely identifies the policy. For example: - Name @@ -209,7 +229,6 @@ You can use the Get-OwaMailboxPolicy cmdlet to view the available Outlook on the Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -219,6 +238,9 @@ Accept wildcard characters: False ``` ### -PopEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The PopEnabled parameter enables or disables access to the mailbox by using POP3 clients. Valid values are: - $true: POP3 access to the mailbox is enabled. This is the default value. @@ -228,7 +250,6 @@ The PopEnabled parameter enables or disables access to the mailbox by using POP3 Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -238,13 +259,15 @@ 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/exchange/Set-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-CalendarNotification.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md index 29fe0d712f..9dad611f16 100644 --- a/exchange/exchange-ps/exchange/Set-CalendarNotification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-calendarnotification applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-CalendarNotification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-calendarnotification +schema: 2.0.0 +title: Set-CalendarNotification --- # Set-CalendarNotification @@ -59,6 +60,9 @@ This example configures the calendar in Tony's mailbox to send the following tex ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -76,7 +80,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -86,6 +89,9 @@ Accept wildcard characters: False ``` ### -CalendarUpdateNotification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarUpdateNotification parameter specifies whether calendar update text message notifications are sent to the user's mobile device. Valid values are: - $true: Calendar update text message notifications are enabled. @@ -95,7 +101,6 @@ The CalendarUpdateNotification parameter specifies whether calendar update text Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -105,6 +110,9 @@ Accept wildcard characters: False ``` ### -CalendarUpdateSendDuringWorkHour + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar update text notifications are sent to the user's mobile device during working hours only. Valid values are: - $true: Calendar update text message notifications are sent during working hours only. @@ -114,7 +122,6 @@ The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar update Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,6 +131,9 @@ 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`. @@ -133,7 +143,6 @@ 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,6 +152,9 @@ Accept wildcard characters: False ``` ### -DailyAgendaNotification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DailyAgendaNotification parameter specifies whether daily agenda text message notifications are sent to the user's mobile device. Valid values are: - $true: Daily agenda text message notifications are sent. @@ -152,7 +164,6 @@ The DailyAgendaNotification parameter specifies whether daily agenda text messag Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -162,6 +173,9 @@ Accept wildcard characters: False ``` ### -DailyAgendaNotificationSendTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DailyAgendaNotificationSendTime parameter specifies the time to send daily agenda text message notifications to the user's mobile device. To specify a value, enter it as a time span: hh:mm:ss where hh = hours, mm = minutes and ss = seconds. @@ -172,7 +186,6 @@ The default value is 08:00:00. Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -182,13 +195,15 @@ 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,13 +213,15 @@ Accept wildcard characters: False ``` ### -IgnoreDefaultScope + +> 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: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -214,6 +231,9 @@ Accept wildcard characters: False ``` ### -MeetingReminderNotification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MeetingReminderNotification parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device. Valid values are: - $true: Meeting reminder text message notifications are sent. @@ -223,7 +243,6 @@ The MeetingReminderNotification parameter specifies whether meeting reminder tex Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -233,6 +252,9 @@ Accept wildcard characters: False ``` ### -MeetingReminderSendDuringWorkHour + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MeetingReminderSendDuringWorkHour parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device during working hours only. Valid values are: - $true: Meeting update notifications are sent during working hours only. @@ -242,7 +264,6 @@ The MeetingReminderSendDuringWorkHour parameter specifies whether meeting remind Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -252,13 +273,15 @@ Accept wildcard characters: False ``` ### -NextDays + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NextDays parameter specifies how many days should be sent in the daily agenda text message notification to the user's mobile device. A valid value is an integer between 1 and 7. The default value is 1. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -268,13 +291,15 @@ 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/exchange/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-CalendarProcessing.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md index edc2b0bc9a..f0097ce955 100644 --- a/exchange/exchange-ps/exchange/Set-CalendarProcessing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-calendarprocessing applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-CalendarProcessing -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-calendarprocessing +schema: 2.0.0 +title: Set-CalendarProcessing --- # Set-CalendarProcessing @@ -156,6 +157,9 @@ This example rejects meeting requests from any user who isn't a member of the Ex ## 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 resource mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -173,7 +177,6 @@ The Identity parameter specifies the resource mailbox that you want to modify. 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 @@ -183,6 +186,9 @@ Accept wildcard characters: False ``` ### -AddAdditionalResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AddAdditionalResponse parameter specifies whether additional information (the value of the AdditionalResponse parameter) is added to meeting request responses. Valid values are: - $true: Text from the AdditionalResponse parameter is added to meeting request responses. @@ -194,7 +200,6 @@ This parameter is used only on resource mailboxes where the AutomateProcessing p 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 @@ -204,13 +209,15 @@ Accept wildcard characters: False ``` ### -AdditionalResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AdditionalResponse parameter specifies the additional information to be included in responses to meeting requests when the value of the AddAdditionalResponse parameter is $true. 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: False Position: Named @@ -220,6 +227,9 @@ Accept wildcard characters: False ``` ### -AddNewRequestsTentatively + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AddNewRequestsTentatively parameter specifies whether new meeting requests are added to the calendar as tentative. Valid values are: - $true: New calendar items are added to the calendar as tentative. This is the default value. @@ -229,7 +239,6 @@ The AddNewRequestsTentatively parameter specifies whether new meeting requests a 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 @@ -239,6 +248,9 @@ Accept wildcard characters: False ``` ### -AddOrganizerToSubject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request. Valid values are: - $true: The meeting organizer's name replaces any existing Subject value for the meeting request. This is the default value. @@ -252,7 +264,6 @@ This parameter is used only on resource mailboxes where the AutomateProcessing p 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 @@ -262,6 +273,9 @@ Accept wildcard characters: False ``` ### -AllBookInPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllBookInPolicy parameter specifies whether to automatically approve in-policy requests from all users to the resource mailbox. Valid values are: - $true: In-policy requests from all users are automatically approved. This is the default value. @@ -271,7 +285,6 @@ The AllBookInPolicy parameter specifies whether to automatically approve in-poli 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,6 +294,9 @@ Accept wildcard characters: False ``` ### -AllowConflicts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowConflicts parameter specifies whether to allow conflicting meeting requests. Valid values are: - $true: Conflicts are allowed. A recurring meeting series is accepted regardless of whether any occurrences conflict with existing bookings. The values of the ConflictPercentageAllowed or MaximumConflictInstances parameters are ignored. @@ -294,7 +310,6 @@ The AllowConflicts parameter specifies whether to allow conflicting meeting requ 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 @@ -304,6 +319,9 @@ Accept wildcard characters: False ``` ### -AllowRecurringMeetings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowRecurringMeetings parameter specifies whether to allow recurring meetings in meeting requests. Valid values are: - $true: Recurring meetings are allowed. This is the default value. @@ -313,7 +331,6 @@ The AllowRecurringMeetings parameter specifies whether to allow recurring meetin 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 @@ -323,6 +340,9 @@ Accept wildcard characters: False ``` ### -AllRequestInPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllRequestInPolicy parameter specifies whether to allow all users to submit in-policy requests to the resource mailbox. Valid values are: - $true: All users are allowed to submit in-policy requests to the resource mailbox. These requests require approval by a resource mailbox delegate if the AllBookInPolicy parameter is set to $false (the default value of AllBookInPolicy is $true). @@ -332,7 +352,6 @@ The AllRequestInPolicy parameter specifies whether to allow all users to submit 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 @@ -342,6 +361,9 @@ Accept wildcard characters: False ``` ### -AllRequestOutOfPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllRequestOutOfPolicy parameter specifies whether to allow all users to submit out-of-policy requests to the resource mailbox. Valid values are: - $true: All users are allowed to submit out-of-policy requests to the resource mailbox. Out-of-policy requests require approval by a resource mailbox delegate. @@ -351,7 +373,6 @@ The AllRequestOutOfPolicy parameter specifies whether to allow all users to subm 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 @@ -361,6 +382,9 @@ Accept wildcard characters: False ``` ### -AutomateProcessing + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutomateProcessing parameter enables or disables calendar processing on the mailbox. Valid values are: - None: Calendar processing is disabled on the mailbox. Both the resource booking attendant and the Calendar Attendant are disabled on the mailbox. @@ -377,7 +401,6 @@ The default value for user mailboxes is AutoUpdate, but you can't change the val Type: CalendarProcessingFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -387,6 +410,9 @@ Accept wildcard characters: False ``` ### -BookingType + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingType parameter specifies how reservations work on the resource mailbox. Valid values are: @@ -398,7 +424,6 @@ The BookingType parameter specifies how reservations work on the resource mailbo Type: Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -408,13 +433,15 @@ Accept wildcard characters: False ``` ### -BookingWindowInDays + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BookingWindowInDays parameter specifies the maximum number of days in advance that the resource can be reserved. A valid value is an integer from 0 through 1080. The default value is 180 days. The value 0 means today. ```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 @@ -424,6 +451,9 @@ Accept wildcard characters: False ``` ### -BookInPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BookInPolicy parameter specifies users or groups who are allowed to submit in-policy meeting requests to the resource mailbox that are automatically approved. You can use any value that uniquely identifies the user or group. For example: - Name @@ -445,7 +475,6 @@ To add users or groups without affecting the other entries, see Example 7. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -455,6 +484,9 @@ 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`. @@ -464,7 +496,6 @@ 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 @@ -474,6 +505,9 @@ Accept wildcard characters: False ``` ### -ConflictPercentageAllowed + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConflictPercentageAllowed parameter specifies the maximum percentage of meeting conflicts for new recurring meeting requests. A valid value is an integer from 0 through 100. The default value is 0. If a new recurring meeting request conflicts with existing reservations for the resource more than the percentage specified by this parameter, the recurring meeting request is automatically declined. When the value is 0, no conflicts are permitted for new recurring meeting requests. @@ -482,7 +516,6 @@ If a new recurring meeting request conflicts with existing reservations for the 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 @@ -492,6 +525,9 @@ Accept wildcard characters: False ``` ### -DeleteAttachments + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeleteAttachments parameter specifies whether to remove attachments from all incoming messages. Valid values are: - $true: Remove any attachments in incoming messages. This is the default value. @@ -503,7 +539,6 @@ This parameter is used only on resource mailboxes where the AutomateProcessing p 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 @@ -513,6 +548,9 @@ Accept wildcard characters: False ``` ### -DeleteComments + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests. Valid values are: - $true: Remove any text in the message body of incoming meeting requests. This is the default value. @@ -524,7 +562,6 @@ This parameter is used only on resource mailboxes where the AutomateProcessing p 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 @@ -534,6 +571,9 @@ Accept wildcard characters: False ``` ### -DeleteNonCalendarItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeleteNonCalendarItems parameter specifies whether to remove or keep all non-calendar-related messages that are received by the resource mailbox. Valid values are: - $true: Non-calendar messages are deleted. This is the default value. @@ -543,7 +583,6 @@ The DeleteNonCalendarItems parameter specifies whether to remove or keep all non 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 @@ -553,6 +592,9 @@ Accept wildcard characters: False ``` ### -DeleteSubject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests. Valid values are: - $true: Remove the Subject value of incoming meeting requests. This is the default value. @@ -564,7 +606,6 @@ This parameter is used only on resource mailboxes where the AutomateProcessing p 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 @@ -574,6 +615,9 @@ 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. @@ -582,7 +626,6 @@ 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 @@ -592,6 +635,9 @@ Accept wildcard characters: False ``` ### -EnableAutoRelease + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill EnableAutoRelease Description }} @@ -600,7 +646,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -610,6 +655,9 @@ Accept wildcard characters: False ``` ### -EnableResponseDetails + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EnableResponseDetails parameter specifies whether to include the reasons for accepting or declining a meeting in the response email message. Valid values are: - $true: The reasons for accepting or declining a meeting are included in the response message. This is the default value. @@ -619,7 +667,6 @@ The EnableResponseDetails parameter specifies whether to include the reasons for 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 @@ -629,6 +676,9 @@ Accept wildcard characters: False ``` ### -EnforceCapacity + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EnforceCapacity parameter specifies whether to restrict the number of attendees to the capacity of the workspace. For example, if capacity is set to 10, then only 10 people can book the workspace. Valid values are: @@ -640,7 +690,6 @@ The EnforceCapacity parameter specifies whether to restrict the number of attend Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -650,6 +699,9 @@ Accept wildcard characters: False ``` ### -EnforceSchedulingHorizon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EnforceSchedulingHorizon parameter controls the behavior of recurring meetings that extend beyond the date specified by the BookingWindowInDays parameter. Valid values are: - $true: A recurring meeting request is automatically declined if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. This is the default value. @@ -659,7 +711,6 @@ The EnforceSchedulingHorizon parameter controls the behavior of recurring meetin 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 @@ -669,6 +720,9 @@ Accept wildcard characters: False ``` ### -ForwardRequestsToDelegates + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForwardRequestsToDelegates parameter specifies whether to forward incoming meeting requests to the delegates that are configured for the resource mailbox. Valid values are: - $true: Forward incoming meeting requests to the delegates. This is the default value. @@ -678,7 +732,6 @@ The ForwardRequestsToDelegates parameter specifies whether to forward incoming m 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 @@ -688,6 +741,9 @@ 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: @@ -699,7 +755,6 @@ 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 @@ -709,6 +764,9 @@ Accept wildcard characters: False ``` ### -MaximumConflictInstances + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaximumConflictInstances parameter specifies the maximum number of conflicts for new recurring meeting requests when the AllowRecurringMeetings parameter is set to $true. A valid value is an integer from 0 through INT32 (2147483647). The default value is 0. If a new recurring meeting request conflicts with existing reservations for the resource more than the number of times specified by the MaximumConflictInstances parameter value, the recurring meeting request is automatically declined. When the value is 0, no conflicts are permitted for new recurring meeting requests. @@ -717,7 +775,6 @@ If a new recurring meeting request conflicts with existing reservations for the 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 @@ -727,6 +784,9 @@ Accept wildcard characters: False ``` ### -MaximumDurationInMinutes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaximumDurationInMinutes parameter specifies the maximum duration in minutes for meeting requests. A valid value is an integer from 0 through INT32 (2147483647). The default value is 1440 (24 hours). When the value is set to 0, the maximum duration of a meeting is unlimited. For recurring meetings, the value of this parameter applies to the length of an individual meeting instance. @@ -735,7 +795,6 @@ When the value is set to 0, the maximum duration of a meeting is unlimited. For 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 @@ -745,6 +804,9 @@ Accept wildcard characters: False ``` ### -MinimumDurationInMinutes + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MinimumDurationInMinutes parameter specifies the minimum duration in minutes for meeting requests in workspace mailboxes. A valid value is an integer from 0 through INT32 (2147483647). The default value is 0, which means there is no minimum duration. @@ -757,7 +819,6 @@ This parameter only works on workspace mailboxes. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -767,6 +828,9 @@ Accept wildcard characters: False ``` ### -OrganizerInfo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OrganizerInfo parameter specifies whether the resource mailbox sends organizer information when a meeting request is declined because of conflicts. Valid values are: - $true: Organizer information is sent when a meeting request is declined because of conflicts. This is the default value. @@ -776,7 +840,6 @@ The OrganizerInfo parameter specifies whether the resource mailbox sends organiz 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 @@ -786,6 +849,9 @@ Accept wildcard characters: False ``` ### -PostReservationMaxClaimTimeInMinutes + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill PostReservationMaxClaimTimeInMinutes Description }} @@ -794,7 +860,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -804,6 +869,9 @@ Accept wildcard characters: False ``` ### -ProcessExternalMeetingMessages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Exchange organization. Valid values are: - $true: Meeting requests from external senders are processed. @@ -813,7 +881,6 @@ The ProcessExternalMeetingMessages parameter specifies whether to process meetin 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 @@ -823,6 +890,9 @@ Accept wildcard characters: False ``` ### -RemoveCanceledMeetings + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The RemoveCanceledMeetings parameter specifies whether to automatically delete meetings that were cancelled by the organizer from the resource mailbox's calendar. Valid values are: @@ -834,7 +904,6 @@ The RemoveCanceledMeetings parameter specifies whether to automatically delete m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -844,6 +913,9 @@ Accept wildcard characters: False ``` ### -RemoveForwardedMeetingNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoveForwardedMeetingNotifications parameter specifies whether forwarded meeting notifications are moved to the Deleted Items folder after they're processed by the Calendar Attendant. Valid values are: - $true: Processed forwarded meeting notifications are deleted (moved to the Deleted Items folder). @@ -853,7 +925,6 @@ The RemoveForwardedMeetingNotifications parameter specifies whether forwarded me 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 @@ -863,6 +934,9 @@ Accept wildcard characters: False ``` ### -RemoveOldMeetingMessages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoveOldMeetingMessages parameter specifies whether the Calendar Attendant removes old and redundant updates and responses. Valid values are: - $true: Outdated and redundant meeting messages are deleted. This is the default value. @@ -872,7 +946,6 @@ The RemoveOldMeetingMessages parameter specifies whether the Calendar Attendant 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 @@ -882,6 +955,9 @@ Accept wildcard characters: False ``` ### -RemovePrivateProperty + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meetings that were sent by the organizer in the original requests. Valid values are: - $true: The private flag for incoming meeting requests is cleared (the meeting is no longer private). This is the default value. @@ -891,7 +967,6 @@ The RemovePrivateProperty parameter specifies whether to clear the private flag 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 @@ -901,6 +976,9 @@ Accept wildcard characters: False ``` ### -RequestInPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestInPolicy parameter specifies users who are allowed to submit in-policy meeting requests to the resource mailbox that require approval by a resource mailbox delegate. You can use any value that uniquely identifies the user. For example: - Name @@ -916,7 +994,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -926,6 +1003,9 @@ Accept wildcard characters: False ``` ### -RequestOutOfPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestOutOfPolicy parameter specifies users who are allowed to submit out-of-policy requests that require approval by a resource mailbox delegate. You can use any value that uniquely identifies the user. For example: - Name @@ -941,7 +1021,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -951,6 +1030,9 @@ Accept wildcard characters: False ``` ### -ResourceDelegates + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResourceDelegates parameter specifies users can approve or reject requests that are sent to the resource mailbox. You can use any value that uniquely identifies the user. For example: - Name @@ -966,7 +1048,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -976,6 +1057,9 @@ Accept wildcard characters: False ``` ### -ScheduleOnlyDuringWorkHours + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ScheduleOnlyDuringWorkHours parameter specifies whether to allow meetings to be scheduled outside of the working hours that are defined for the resource mailbox. Valid values are: - $true: Meeting requests that are outside of working hours are automatically rejected. @@ -987,7 +1071,6 @@ You configure the working hours of the resource mailbox by using the WorkDays, W 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 @@ -997,6 +1080,9 @@ Accept wildcard characters: False ``` ### -TentativePendingApproval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TentativePendingApproval parameter specifies whether to mark pending requests as tentative on the calendar. Valid values are: - $true: Meeting requests that are awaiting approval from a delegate appear in the calendar as tentative. This is the default value. @@ -1006,7 +1092,6 @@ The TentativePendingApproval parameter specifies whether to mark pending request 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 @@ -1016,13 +1101,15 @@ 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/exchange/Set-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md index db1f2c2ede..2e8136987e 100644 --- a/exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-caseholdpolicy applicable: Security & Compliance -title: Set-CaseHoldPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-caseholdpolicy +schema: 2.0.0 +title: Set-CaseHoldPolicy --- # Set-CaseHoldPolicy @@ -70,6 +71,9 @@ This example makes the following changes to the existing case hold policy named ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the case hold policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -80,7 +84,6 @@ The Identity parameter specifies the case hold policy that you want to modify. Y Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -90,6 +93,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -100,7 +106,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -110,6 +115,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: - A mailbox @@ -127,7 +135,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -137,13 +144,15 @@ Accept wildcard characters: False ``` ### -AddPublicFolderLocation + +> Applicable: Security & Compliance + The AddPublicFolderLocation parameter specifies that you want to add all public folders to the case hold policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -153,6 +162,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocation + +> Applicable: Security & Compliance + The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites when you aren't using 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"`. @@ -163,7 +175,6 @@ SharePoint sites can't be added to the policy until they have been indexed. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -173,13 +184,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -189,6 +202,9 @@ 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`. @@ -198,7 +214,6 @@ 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 @@ -208,6 +223,9 @@ 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. @@ -217,7 +235,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -227,6 +244,9 @@ 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. @@ -235,7 +255,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -245,6 +264,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: - A mailbox @@ -262,7 +284,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -272,13 +293,15 @@ Accept wildcard characters: False ``` ### -RemovePublicFolderLocation + +> Applicable: Security & Compliance + The RemovePublicFolderLocation parameter specifies that you want to remove all public folders from the case hold policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -288,6 +311,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocation + +> Applicable: Security & Compliance + The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites when you aren't using 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"`. @@ -296,7 +322,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -306,13 +331,15 @@ 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/exchange/Set-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-CaseHoldRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md index 3935336a80..dbff9b7266 100644 --- a/exchange/exchange-ps/exchange/Set-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-caseholdrule applicable: Security & Compliance -title: Set-CaseHoldRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-caseholdrule +schema: 2.0.0 +title: Set-CaseHoldRule --- # Set-CaseHoldRule @@ -45,6 +46,9 @@ This example disables the enabled case hold rule named "Internal Company Rule". ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the case hold rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the case hold rule that you want to modify. You Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -65,13 +68,15 @@ 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 @@ -81,6 +86,9 @@ 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`. @@ -90,7 +98,6 @@ 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 @@ -100,6 +107,9 @@ 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). @@ -108,7 +118,6 @@ 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 @@ -118,6 +127,9 @@ 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. @@ -127,7 +139,6 @@ 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 @@ -137,13 +148,15 @@ 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/exchange/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md index 1848e06aee..2c1ccddd22 100644 --- a/exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-classificationrulecollection applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-ClassificationRuleCollection -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-classificationrulecollection +schema: 2.0.0 +title: Set-ClassificationRuleCollection --- # Set-ClassificationRuleCollection @@ -45,6 +46,9 @@ 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`). @@ -53,7 +57,6 @@ 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 @@ -63,6 +66,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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. @@ -92,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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/exchange/Set-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-ClientAccessArray.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md index caa657f795..b024fee876 100644 --- a/exchange/exchange-ps/exchange/Set-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessarray applicable: Exchange Server 2010 -title: Set-ClientAccessArray -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessarray +schema: 2.0.0 +title: Set-ClientAccessArray --- # Set-ClientAccessArray @@ -60,6 +61,9 @@ This example associates the existing Client Access array named ContosoArray with ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the Client Access array that you want to modify. You can use these values: - Name (if the value doesn't contain spaces) @@ -72,7 +76,6 @@ The Identity parameter specifies the Client Access array that you want to modify Type: ClientAccessArrayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -82,6 +85,9 @@ 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,7 +97,6 @@ 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 @@ -101,13 +106,15 @@ 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 @@ -117,13 +124,15 @@ 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: False Position: Named @@ -133,13 +142,15 @@ Accept wildcard characters: False ``` ### -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. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -149,6 +160,9 @@ 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 @@ -161,7 +175,6 @@ To see a list of available sites, use the Get-ADSite cmdlet. Type: AdSiteIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -171,13 +184,15 @@ 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/exchange/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ClientAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md index 9a82144d26..8a6dcb0847 100644 --- a/exchange/exchange-ps/exchange/Set-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-ClientAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessrule +schema: 2.0.0 +title: Set-ClientAccessRule --- # Set-ClientAccessRule @@ -86,6 +87,9 @@ This example adds the IP address range 172.17.17.27/16 to the existing client ac ## 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 modify. You can use any value that uniquely identifies the client access rule. For example: - Name @@ -96,7 +100,6 @@ The Identity parameter specifies the client access rule that you want to modify. Type: ClientAccessRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -106,13 +109,15 @@ 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: False Position: Named @@ -122,6 +127,9 @@ 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. @@ -144,7 +152,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -154,6 +161,9 @@ 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. @@ -170,7 +180,6 @@ 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 @@ -180,6 +189,9 @@ 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: @@ -207,7 +219,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -217,13 +228,15 @@ 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 @@ -233,6 +246,9 @@ 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`. @@ -242,7 +258,6 @@ 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 @@ -252,6 +267,9 @@ 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. @@ -260,7 +278,6 @@ 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 @@ -270,13 +287,15 @@ 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. ```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 @@ -286,6 +305,9 @@ 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. @@ -308,7 +330,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -318,6 +339,9 @@ 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. @@ -334,7 +358,6 @@ 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 @@ -344,6 +367,9 @@ 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. @@ -371,7 +397,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -381,13 +406,15 @@ 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 @@ -397,13 +424,15 @@ 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 @@ -413,6 +442,9 @@ 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. @@ -425,7 +457,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -435,13 +466,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -451,13 +484,15 @@ 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 client access rule. A lower integer value indicates a higher priority, and a higher priority rule is evaluated before a lower priority rule. The default value is 1. ```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 @@ -467,6 +502,9 @@ 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. @@ -476,7 +514,6 @@ 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 @@ -486,13 +523,15 @@ 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 @@ -502,6 +541,9 @@ 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. @@ -514,7 +556,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -524,6 +565,9 @@ Accept wildcard characters: False ``` ### -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. @@ -563,7 +607,6 @@ 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 @@ -573,13 +616,15 @@ 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/exchange/Set-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ClientAccessServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md index 343bf8d337..03126a0603 100644 --- a/exchange/exchange-ps/exchange/Set-ClientAccessServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessserver applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ClientAccessServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessserver +schema: 2.0.0 +title: Set-ClientAccessServer --- # Set-ClientAccessServer @@ -73,6 +74,9 @@ This example configures the internal Autodiscover URL for the Active Directory s ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example: - Name @@ -84,7 +88,6 @@ The Identity parameter specifies the server that you want to modify. You can use Type: ClientAccessServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -AlternateServiceAccountCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AlternateServiceAccountCredential parameter specifies an alternative service account username and password that's typically used for Kerberos authentication in Exchange Server 2010 coexistence environments. You can specify multiple values separated by commas. 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). @@ -102,7 +108,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential[] Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -112,13 +117,15 @@ Accept wildcard characters: False ``` ### -Array + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ClientAccessArrayIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -128,13 +135,15 @@ Accept wildcard characters: False ``` ### -AutoDiscoverServiceInternalUri + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service. ```yaml Type: Uri Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -144,6 +153,9 @@ Accept wildcard characters: False ``` ### -AutoDiscoverSiteScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverSiteScope parameter specifies the Active Directory site that the Autodiscover service is authoritative for. Clients that connect to the Autodiscover service by using the internal URL need to exist in the specified site. To see the available Active Directory sites, use the Get-ADSite cmdlet. @@ -154,7 +166,6 @@ To specify multiple values, use the following syntax: `Value1,Value2,...ValueN`. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -164,13 +175,15 @@ Accept wildcard characters: False ``` ### -CleanUpInvalidAlternateServiceAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CleanUpInvalidAlternateServiceAccountCredentials switch specifies whether to remove a previously configured alternate service account that's no longer valid. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -180,6 +193,9 @@ 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`. @@ -189,7 +205,6 @@ 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 @@ -199,13 +214,15 @@ 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 @@ -215,6 +232,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogEnabled parameter specifies whether logging is enabled for Information Rights Management (IRM). Valid values are $true or $false. The default value is $true. @@ -223,7 +243,6 @@ The IrmLogEnabled parameter specifies whether logging is enabled for Information Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -233,6 +252,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxAge parameter specifies the max age for IRM logs. Logs older than the specified value are deleted. @@ -245,7 +267,6 @@ For example, to specify a 15-hour interval, enter 15:00:00. The default value is Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -255,6 +276,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxDirectorySize parameter specifies the maximum directory size for IRM logs. When the maximum directory size is reached, the server deletes the old log files first. @@ -275,7 +299,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -285,6 +308,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxFileSize parameter specifies the maximum size of the IRM log. This value can't be larger than the IrmLogMaxDirectorySize parameter value. @@ -306,7 +332,6 @@ The value of this parameter must be less than or equal to the value of the Recei Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -316,6 +341,9 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogPath parameter specifies the location of the IRM log files. The default location is %ExchangeInstallPath%Logging\\IRMLogs. @@ -324,7 +352,6 @@ The IrmLogPath parameter specifies the location of the IRM log files. The defaul Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -334,6 +361,9 @@ Accept wildcard characters: False ``` ### -IsOutOfService + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -342,7 +372,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -352,13 +381,15 @@ Accept wildcard characters: False ``` ### -RemoveAlternateServiceAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoveAlternateServiceAccountCredentials switch specifies whether to remove a previously distributed alternate service account. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -368,13 +399,15 @@ 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/exchange/Set-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ClientAccessService.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md index bff2cc0183..7595c91d57 100644 --- a/exchange/exchange-ps/exchange/Set-ClientAccessService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessservice applicable: Exchange Server 2016, Exchange Server 2019 -title: Set-ClientAccessService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-clientaccessservice +schema: 2.0.0 +title: Set-ClientAccessService --- # Set-ClientAccessService @@ -59,6 +60,9 @@ This example configures the internal Autodiscover URL for the Active Directory s ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example: - Name @@ -70,7 +74,6 @@ The Identity parameter specifies the server that you want to modify. You can use Type: ClientAccessServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -80,6 +83,9 @@ Accept wildcard characters: False ``` ### -AlternateServiceAccountCredential + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AlternateServiceAccountCredential parameter specifies an alternative service account that's typically used for Kerberos authentication in Exchange Server 2010 coexistence environments. 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). @@ -88,7 +94,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential[] Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -98,13 +103,15 @@ Accept wildcard characters: False ``` ### -Array + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ClientAccessArrayIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -114,13 +121,15 @@ Accept wildcard characters: False ``` ### -AutoDiscoverServiceInternalUri + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service. ```yaml Type: Uri Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,6 +139,9 @@ Accept wildcard characters: False ``` ### -AutoDiscoverSiteScope + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverSiteScope parameter specifies the Active Directory site that the Autodiscover service is authoritative for. Clients that connect to the Autodiscover service by using the internal URL need to exist in the specified site. To see the available Active Directory sites, use the Get-ADSite cmdlet. @@ -140,7 +152,6 @@ To specify multiple values, use the following syntax: `Value1,Value2,...ValueN`. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,13 +161,15 @@ Accept wildcard characters: False ``` ### -CleanUpInvalidAlternateServiceAccountCredentials + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The CleanUpInvalidAlternateServiceAccountCredentials switch specifies whether to remove a previously configured alternate service account that's no longer valid. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -166,6 +179,9 @@ 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`. @@ -175,7 +191,6 @@ 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 @@ -185,13 +200,15 @@ 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 @@ -201,13 +218,15 @@ Accept wildcard characters: False ``` ### -RemoveAlternateServiceAccountCredentials + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RemoveAlternateServiceAccountCredentials switch specifies whether to remove a previously distributed alternate service account. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: AlternateServiceAccount Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -217,13 +236,15 @@ 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/exchange/Set-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-Clutter.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md index 980d6d409c..6295ea4296 100644 --- a/exchange/exchange-ps/exchange/Set-Clutter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-clutter applicable: Exchange Online, Exchange Online Protection -title: Set-Clutter -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.Management-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-clutter +schema: 2.0.0 +title: Set-Clutter --- # Set-Clutter @@ -42,6 +43,9 @@ This example disables Clutter for the user Alexander Martinez. ## 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 @@ -59,7 +63,6 @@ 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 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -Enable + +> Applicable: Exchange Online, Exchange Online Protection + The Enable parameter specifies whether to enable or disable Clutter for the mailbox. Valid values are: - $true: Clutter is enabled for the mailbox. This is the default value. @@ -78,7 +84,6 @@ The Enable parameter specifies whether to enable or disable Clutter for the mail Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -88,13 +93,15 @@ 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/exchange/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md index 1f29b9f3c9..946e7c00bf 100644 --- a/exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-cmdletextensionagent applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-CmdletExtensionAgent -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-cmdletextensionagent +schema: 2.0.0 +title: Set-CmdletExtensionAgent --- # Set-CmdletExtensionAgent @@ -49,6 +50,9 @@ This example changes the priority of the fictitious "Validation Agent" cmdlet ex ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the cmdlet extension agent that you want to modify. You can use any value that uniquely identifies the agent. For example: - Name @@ -59,7 +63,6 @@ The Identity parameter specifies the cmdlet extension agent that you want to mod Type: CmdletExtensionAgentIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the cmdlet extension agent. The maximum length of the agent name is 64 characters. If the name contains spaces, enclose the name 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 @@ -120,13 +129,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the priority of the cmdlet extension agent. Higher priority agents are applied before lower priority agents. A valid value is an integer from 0 to 255. Lower integer values indicate higher priority. ```yaml Type: Byte Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,13 +147,15 @@ 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/exchange/Set-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-ComplianceCase.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md index 2975872e51..770e9bcbef 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancecase applicable: Security & Compliance -title: Set-ComplianceCase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancecase +schema: 2.0.0 +title: Set-ComplianceCase --- # Set-ComplianceCase @@ -49,6 +50,9 @@ This example adds a description and case Id to the existing eDiscovery case name ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the compliance case that you want to modify. You can use any value that uniquely identifies the case. For example: - Name @@ -58,7 +62,6 @@ The Identity parameter specifies the compliance case that you want to modify. Yo Type: ComplianceCaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -68,13 +71,15 @@ Accept wildcard characters: False ``` ### -CaseType + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: ComplianceCaseType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -Close + +> Applicable: Security & Compliance + The Close switch specifies that you want to close the compliance case. 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 @@ -100,6 +107,9 @@ 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`. @@ -109,7 +119,6 @@ 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 @@ -119,13 +128,15 @@ 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 @@ -135,13 +146,15 @@ 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 @@ -151,13 +164,15 @@ 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 compliance case. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -167,13 +182,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -183,13 +200,15 @@ Accept wildcard characters: False ``` ### -Reopen + +> Applicable: Security & Compliance + The Reopen switch specifies that you want to re-open a closed compliance case. 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 @@ -199,13 +218,15 @@ 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/exchange/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md index 095fd20c7a..ff864c2b6d 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-complianceretentioneventtype applicable: Security & Compliance -title: Set-ComplianceRetentionEventType -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-complianceretentioneventtype +schema: 2.0.0 +title: Set-ComplianceRetentionEventType --- # Set-ComplianceRetentionEventType @@ -43,6 +44,9 @@ This example add a comment to the retention event type named Fabrikam Project ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention event type that you want to modify. You can use any value that uniquely identifies the retention event type. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the retention event type that you want to modif Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -63,13 +66,15 @@ 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 @@ -79,6 +84,9 @@ 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`. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Set-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md index 2f6e6859f5..5deac2a4d9 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesearch applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Set-ComplianceSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesearch +schema: 2.0.0 +title: Set-ComplianceSearch --- # Set-ComplianceSearch @@ -86,6 +87,9 @@ You might have to change the language setting if you're using non-English keywor ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The Identity parameter specifies the compliance search that you want to modify. You can use any value that uniquely identifies the compliance search. For example: @@ -99,7 +103,6 @@ You can find these values by running the command Get-ComplianceSearch | Format-T Type: ComplianceSearchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: True Position: 1 @@ -109,6 +112,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. 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. @@ -120,7 +126,6 @@ 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 @@ -130,6 +135,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocationExclusion + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + This parameter is functional only in on-premises Exchange. This parameter specifies the mailboxes to add to the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. Valid values are: @@ -143,7 +151,6 @@ 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 @@ -153,6 +160,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocation + +> Applicable: Security & Compliance + This parameter is available only in the cloud-based service. The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites when you aren't using the value All for the SharePointLocation parameter. You identify the site by its URL value. @@ -163,7 +173,6 @@ 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 @@ -173,6 +182,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocationExclusion + +> Applicable: Security & Compliance + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -181,7 +193,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -191,6 +202,9 @@ 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. @@ -207,7 +221,6 @@ 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 @@ -217,6 +230,9 @@ 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`. @@ -226,7 +242,6 @@ 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 @@ -236,6 +251,9 @@ 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). @@ -244,7 +262,6 @@ 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 @@ -254,13 +271,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The Description parameter specifies a 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 @@ -270,6 +289,9 @@ 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. @@ -284,7 +306,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: False Position: Named @@ -294,6 +315,9 @@ 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: @@ -307,7 +331,6 @@ 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 @@ -317,6 +340,9 @@ 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. @@ -325,7 +351,6 @@ 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 @@ -335,6 +360,9 @@ 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 eDiscovery case will be searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case. @@ -347,7 +375,6 @@ 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 @@ -357,13 +384,15 @@ 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 @@ -373,6 +402,9 @@ 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: @@ -384,7 +416,6 @@ The IncludeUserAppContent parameter specifies that you want to search the cloud- Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -394,6 +425,9 @@ 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). @@ -402,7 +436,6 @@ 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 @@ -412,13 +445,15 @@ Accept wildcard characters: False ``` ### -Name + +> 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 @@ -428,6 +463,9 @@ 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. @@ -436,7 +474,6 @@ The PublicFolderLocation parameter specifies that you want to include all public Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -446,6 +483,9 @@ 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. @@ -454,7 +494,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -464,6 +503,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The RemoveExchangeLocation parameter specifies the mailboxes to remove from the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -475,7 +517,6 @@ 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 @@ -485,6 +526,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocationExclusion + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + This parameter is functional only in on-premises Exchange. This parameter specifies the mailboxes to remove from the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. Valid values are: @@ -498,7 +542,6 @@ 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 @@ -508,6 +551,9 @@ Accept wildcard characters: False ``` ### -RemovePublicFolderLocation + +> Applicable: Security & Compliance + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -516,7 +562,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -526,6 +571,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocation + +> Applicable: Security & Compliance + This parameter is available only in the cloud-based service. The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites when you aren't using the value All for the SharePointLocation parameter. You identify the site by its URL value. @@ -536,7 +584,6 @@ 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 @@ -546,6 +593,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocationExclusion + +> Applicable: Security & Compliance + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -554,7 +604,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -564,6 +613,9 @@ 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. @@ -574,7 +626,6 @@ 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 @@ -584,6 +635,9 @@ 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. @@ -592,7 +646,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -602,6 +655,9 @@ 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. @@ -610,7 +666,6 @@ 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/exchange/Set-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md index a490fa06ca..c08903b34e 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesearchaction applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Set-ComplianceSearchAction -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesearchaction +schema: 2.0.0 +title: Set-ComplianceSearchAction --- # Set-ComplianceSearchAction @@ -49,6 +50,9 @@ This example changes the export key on the export compliance search action named ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The Identity parameter specifies the compliance search action that you want to modify. 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`). @@ -58,7 +62,6 @@ The Identity parameter specifies the compliance search action that you want to m Type: ComplianceSearchActionIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: True Position: 1 @@ -68,6 +71,9 @@ Accept wildcard characters: False ``` ### -ChangeExportKey + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The ChangeExportKey switch creates a new export key for the compliance search action. You don't need to specify a value with this switch. This switch is meaningful only on export compliance search actions. @@ -76,7 +82,6 @@ This switch is meaningful only on export compliance search actions. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: False Position: Named @@ -86,6 +91,9 @@ 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`. @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ 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 @@ -121,13 +130,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Server 2016, Exchange Server 2019, 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: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md index 5301f61588..a526e2e24f 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesecurityfilter applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Set-ComplianceSecurityFilter -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancesecurityfilter +schema: 2.0.0 +title: Set-ComplianceSecurityFilter --- # Set-ComplianceSecurityFilter @@ -62,13 +63,15 @@ This example removes user annb@contoso.com to the compliance security filter nam ## PARAMETERS ### -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 modify. 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 @@ -78,6 +81,9 @@ Accept wildcard characters: False ``` ### -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. A valid value for this parameter is All, which means the filter is applied to all search actions. - Export: The filter is applied when exporting search results, or preparing them for analysis in eDiscovery Premium. @@ -90,7 +96,6 @@ 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: False Position: Named @@ -100,6 +105,9 @@ 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`. @@ -109,7 +117,6 @@ 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 @@ -119,13 +126,15 @@ 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 @@ -135,6 +144,9 @@ 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. 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). @@ -147,7 +159,6 @@ You can specify multiple filters of the same type. For example, `"Mailbox_Custom Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: False Position: Named @@ -157,6 +168,9 @@ 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 @@ -176,7 +190,6 @@ 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 @@ -186,6 +199,9 @@ 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. @@ -200,7 +216,6 @@ The values you specify will overwrite any existing entries. See the Examples sec Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: False Position: Named @@ -210,13 +225,15 @@ 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/exchange/Set-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-ComplianceTag.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md index ef1e0e1fd7..e66bf89b13 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancetag applicable: Security & Compliance -title: Set-ComplianceTag -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-compliancetag +schema: 2.0.0 +title: Set-ComplianceTag --- # Set-ComplianceTag @@ -67,6 +68,9 @@ This example modifies the existing label named HR Content by modifying the reten ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the label that you want to modify. You can use any value that uniquely identifies the tag. For example: - Name @@ -77,7 +81,6 @@ The Identity parameter specifies the label that you want to modify. You can use Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -87,13 +90,15 @@ Accept wildcard characters: False ``` ### -AutoApprovalPeriod + +> Applicable: Security & Compliance + {{ Fill AutoApprovalPeriod Description }} ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -103,13 +108,15 @@ 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 @@ -119,13 +126,15 @@ 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 @@ -135,6 +144,9 @@ 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`. @@ -144,7 +156,6 @@ 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,6 +165,9 @@ 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 @@ -166,7 +180,6 @@ 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 @@ -176,6 +189,9 @@ 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` @@ -209,7 +225,6 @@ You use the second variable as the value for this parameter. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -219,6 +234,9 @@ 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. @@ -232,7 +250,6 @@ 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 @@ -242,6 +259,9 @@ 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. @@ -250,7 +270,6 @@ 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 @@ -260,6 +279,9 @@ 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]},]}'` @@ -274,7 +296,6 @@ 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 @@ -284,13 +305,15 @@ Accept wildcard characters: False ``` ### -Notes + +> Applicable: Security & Compliance + The Notes parameter specifies an optional note. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is a user note". ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -300,13 +323,15 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + {{ Fill PriorityCleanup Description }} ```yaml Type: SwitchParameter Parameter Sets: PriorityCleanup Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -316,6 +341,9 @@ Accept wildcard characters: False ``` ### -RetentionDuration + +> Applicable: Security & Compliance + The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: - A positive integer. @@ -325,7 +353,6 @@ The RetentionDuration parameter specifies the number of days to retain the conte Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -335,13 +362,15 @@ 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 @@ -351,13 +380,15 @@ 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/exchange/Set-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md similarity index 78% rename from exchange/exchange-ps/exchange/Set-Contact.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Contact.md index a173246fe3..42a64c2585 100644 --- a/exchange/exchange-ps/exchange/Set-Contact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-contact applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-Contact -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-contact +schema: 2.0.0 +title: Set-Contact --- # Set-Contact @@ -85,6 +86,9 @@ Change the Company parameter value to Contoso. ## 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 modify. You can use any value that uniquely identifies the contact. For example: - Name @@ -96,7 +100,6 @@ The Identity parameter specifies the contact that you want to modify. You can us Type: ContactIdParameter 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 @@ -106,6 +109,9 @@ Accept wildcard characters: False ``` ### -AllowUMCallsFromNonUsers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllowUMCallsFromNonUsers parameter specifies whether to exclude the contact from Unified Messaging directory searches. @@ -114,7 +120,6 @@ The AllowUMCallsFromNonUsers parameter specifies whether to exclude the contact Type: AllowUMCallsFromNonUsersFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,13 +129,15 @@ Accept wildcard characters: False ``` ### -AssistantName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AssistantName parameter specifies the name of the contact's assistant. ```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 @@ -140,13 +147,15 @@ Accept wildcard characters: False ``` ### -City + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The City parameter specifies the contact's city. ```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 @@ -156,13 +165,15 @@ Accept wildcard characters: False ``` ### -Company + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Company parameter specifies the contact's company. ```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 @@ -172,6 +183,9 @@ 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`. @@ -181,7 +195,6 @@ 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 @@ -191,6 +204,9 @@ Accept wildcard characters: False ``` ### -CountryOrRegion + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CountryOrRegion parameter specifies the contact's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name). A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). @@ -201,7 +217,6 @@ The friendly name is returned in the CountryOrRegion property value by the Get-C Type: CountryInfo 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 @@ -211,6 +226,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -222,7 +240,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -232,13 +249,15 @@ Accept wildcard characters: False ``` ### -Department + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Department parameter specifies the contact's department. ```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 @@ -248,6 +267,9 @@ 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 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 ("). This parameter is meaningful only if the contact is mail-enabled. @@ -256,7 +278,6 @@ This parameter is meaningful only if the contact is mail-enabled. 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 @@ -266,6 +287,9 @@ 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. @@ -274,7 +298,6 @@ 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 @@ -284,13 +307,15 @@ Accept wildcard characters: False ``` ### -Fax + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Fax parameter specifies the contact's fax number. ```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 @@ -300,13 +325,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FirstName parameter specifies the user's first name. ```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 @@ -316,6 +343,9 @@ Accept wildcard characters: False ``` ### -GeoCoordinates + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GeoCoordinates parameter specifies the contact's location in latitude, longitude and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats: - Latitude and longitude: For example, "47.644125;-122.122411" @@ -327,7 +357,6 @@ The GeoCoordinates parameter specifies the contact's location in latitude, longi Type: GeoCoordinates Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -337,13 +366,15 @@ Accept wildcard characters: False ``` ### -HomePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HomePhone parameter specifies the contact's home telephone number. ```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 @@ -353,6 +384,9 @@ 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. @@ -366,7 +400,6 @@ 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 @@ -376,13 +409,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Initials parameter specifies the user's middle initials. ```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 @@ -392,13 +427,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LastName parameter specifies the user's last name. ```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 @@ -408,13 +445,15 @@ Accept wildcard characters: False ``` ### -Manager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Manager parameter specifies the contact's manager. ```yaml Type: UserContactIdParameter 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 @@ -424,13 +463,15 @@ Accept wildcard characters: False ``` ### -MobilePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MobilePhone parameter specifies the contact's primary mobile phone number. ```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 @@ -440,13 +481,15 @@ Accept wildcard characters: False ``` ### -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 contact. 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, Exchange Online Protection Required: False Position: Named @@ -456,13 +499,15 @@ 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 @@ -472,13 +517,15 @@ Accept wildcard characters: False ``` ### -Office + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Office parameter specifies the user's physical office name or number. ```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 @@ -488,13 +535,15 @@ Accept wildcard characters: False ``` ### -OtherFax + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherFax parameter specifies the contact's alternative fax number. ```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 @@ -504,13 +553,15 @@ Accept wildcard characters: False ``` ### -OtherHomePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherHomePhone parameter specifies the contact's alternative home telephone number. ```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 @@ -520,13 +571,15 @@ Accept wildcard characters: False ``` ### -OtherTelephone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherTelephone parameter specifies the contact's alternative office telephone number. ```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 @@ -536,13 +589,15 @@ Accept wildcard characters: False ``` ### -Pager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Pager parameter specifies the contact's pager number. ```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 @@ -552,13 +607,15 @@ Accept wildcard characters: False ``` ### -Phone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Phone parameter specifies the contact's office telephone number. ```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 @@ -568,13 +625,15 @@ Accept wildcard characters: False ``` ### -PhoneticDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -584,13 +643,15 @@ Accept wildcard characters: False ``` ### -PostalCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PostalCode parameter specifies the contact's postal code. ```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 @@ -600,13 +661,15 @@ Accept wildcard characters: False ``` ### -PostOfficeBox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PostOfficeBox parameter specifies the contact's post office box number. ```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 @@ -616,13 +679,15 @@ Accept wildcard characters: False ``` ### -SeniorityIndex + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SeniorityIndex parameter specifies the order in which this contact will display in a hierarchical address book. A contact with a value of 2 will display higher in an address book than a contact with a value of 1. ```yaml Type: Int32 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 @@ -632,6 +697,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -646,7 +714,6 @@ This parameter is meaningful only if the contact is mail-enabled. 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 @@ -656,13 +723,15 @@ Accept wildcard characters: False ``` ### -StateOrProvince + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The StateOrProvince parameter specifies the contact's state or province. ```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 @@ -672,13 +741,15 @@ Accept wildcard characters: False ``` ### -StreetAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The StreetAddress parameter specifies the contact's physical address. ```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 @@ -688,13 +759,15 @@ Accept wildcard characters: False ``` ### -TelephoneAssistant + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TelephoneAssistant parameter specifies the telephone number of the contact's assistant. ```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 @@ -704,13 +777,15 @@ Accept wildcard characters: False ``` ### -Title + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Title parameter specifies the contact's title. ```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 @@ -720,6 +795,9 @@ Accept wildcard characters: False ``` ### -UMCallingLineIds + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. Values for this parameter must be less than 128 characters in length and may include an optional plus sign (+) that precedes the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value. @@ -728,7 +806,6 @@ The UMCallingLineIds parameter specifies telephone numbers or extensions that ca Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -738,6 +815,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -758,7 +838,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -768,13 +847,15 @@ Accept wildcard characters: False ``` ### -WebPage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WebPage parameter specifies the contact's web page. ```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 @@ -784,13 +865,15 @@ 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 @@ -800,6 +883,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -811,7 +897,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ContentFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md index 80deb1646f..94fa3a8733 100644 --- a/exchange/exchange-ps/exchange/Set-ContentFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-contentfilterconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ContentFilterConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-contentfilterconfig +schema: 2.0.0 +title: Set-ContentFilterConfig --- # Set-ContentFilterConfig @@ -70,6 +71,9 @@ It defines two users for whom the Content Filter won't process messages. ## PARAMETERS ### -BypassedRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedRecipients parameter specifies the SMTP addresses of recipients who skip processing by the Content Filter agent. You can specify multiple recipients separated by commas (for example, `"recipient1@contoso.com","recipient2@contoso.com"`). The maximum number of recipient entries is 100. @@ -78,7 +82,6 @@ You can specify multiple recipients separated by commas (for example, `"recipien Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -88,6 +91,9 @@ Accept wildcard characters: False ``` ### -BypassedSenderDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedSenderDomains parameter specifies the sender email address domains of senders who skip processing by the Content Filter agent. You can specify multiple sender domains separated by commas (`"contoso.com","fabrikam.com"`). Use a wildcard character (\*) to specify a domain and all subdomains (for example: `*.contoso.com`). The maximum number of domain entries is 100. @@ -96,7 +102,6 @@ You can specify multiple sender domains separated by commas (`"contoso.com","fab Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -106,6 +111,9 @@ Accept wildcard characters: False ``` ### -BypassedSenders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedSenders parameter specifies the SMTP addresses of senders who skip processing by the Content Filter agent. You can specify multiple senders separated by commas (for example, `"sender1@contoso.com","sender2@contoso.com"`). The maximum number of recipient entries is 100. @@ -114,7 +122,6 @@ You can specify multiple senders separated by commas (for example, `"sender1@con Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,6 +131,9 @@ 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`. @@ -133,7 +143,6 @@ 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,6 +152,9 @@ 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. @@ -151,7 +163,6 @@ 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,6 +172,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter enables or disables the Content Filter agent on the computer on which you're running the command. Valid values are: - $true: The Content Filter agent is enabled. This is the default value. @@ -170,7 +184,6 @@ The Enabled parameter enables or disables the Content Filter agent on the comput Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -180,6 +193,9 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections from sources external to your Exchange organization are processed by the Content Filter agent. Valid values are: - $true: Messages from unauthenticated connections are processed by the Content Filter agent. This is the default value. @@ -189,7 +205,6 @@ The ExternalMailEnabled parameter specifies whether all messages from unauthenti Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -199,6 +214,9 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether all messages from authenticated connections and from authoritative domains in your enterprise are processed by the Content Filter agent. Valid values are: - $true: Messages from authenticated connections are processed by the Content Filter agent. @@ -208,7 +226,6 @@ The InternalMailEnabled parameter specifies whether all messages from authentica Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -218,6 +235,9 @@ Accept wildcard characters: False ``` ### -OutlookEmailPostmarkValidationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutlookEmailPostmarkValidationEnabled parameter specifies whether Outlook Email Postmark validation is enabled. - For outbound messages, the Content Filter agent applies a computational postmark header to help destination email systems distinguish legitimate email from spam. @@ -232,7 +252,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -242,13 +261,15 @@ Accept wildcard characters: False ``` ### -QuarantineMailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QuarantineMailbox parameter specifies an SMTP address to be used as a spam quarantine mailbox. A spam quarantine mailbox is required when you set the SCLQuarantineEnabled parameter to $true. All messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the SMTP address that you set in this parameter. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -258,13 +279,15 @@ Accept wildcard characters: False ``` ### -RejectionResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RejectionResponse parameter specifies the message body that you want delivered in the non-delivery report (NDR) to senders whose messages meet or exceed the SCLRejectThreshold value. The RejectionResponse parameter is required if you set the SCLRejectEnabled parameter to $true. The RejectionResponse parameter takes a string. Don't exceed 240 characters in the argument. When you pass an argument, you must enclose the RejectionResponse parameter in quotation marks (") if the phrase contains spaces, for example: "Message rejected". The default setting is Message rejected due to content restrictions. ```yaml Type: AsciiString Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -274,6 +297,9 @@ Accept wildcard characters: False ``` ### -SCLDeleteEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLDeleteEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. Valid values are: - $true: Messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. @@ -283,7 +309,6 @@ The SCLDeleteEnabled parameter specifies whether all messages that meet or excee Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,13 +318,15 @@ Accept wildcard characters: False ``` ### -SCLDeleteThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLDeleteThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to delete the message and not send an NDR. To enable this functionality, you must set the SCLDeleteEnabled parameter to $true. The default setting is 9. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -309,6 +336,9 @@ Accept wildcard characters: False ``` ### -SCLQuarantineEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLQuarantineEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. Valid values are: - $true: Messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. @@ -318,7 +348,6 @@ The SCLQuarantineEnabled parameter specifies whether all messages that meet or e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -328,13 +357,15 @@ Accept wildcard characters: False ``` ### -SCLQuarantineThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLQuarantineThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to quarantine the message. To enable quarantine functionality, you must set the SCLQuarantineEnabled parameter to $true, and provide a valid SMTP address in the QuarantineMailbox parameter. The default setting is 9. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -344,6 +375,9 @@ Accept wildcard characters: False ``` ### -SCLRejectEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLRejectEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR to the sender. Valid values are: - $true: Messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR is to the sender. @@ -353,7 +387,6 @@ The SCLRejectEnabled parameter specifies whether all messages that meet or excee Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -363,13 +396,15 @@ Accept wildcard characters: False ``` ### -SCLRejectThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SCLRejectThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to reject the message and send an NDR to the sender. To enable the delete functionality, you must set the SCLDeleteEnabled parameter to $true. Also, you can revise the default NDR message by editing the RejectionResponse parameter. The default setting is 7. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -379,13 +414,15 @@ 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/exchange/Set-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-DataClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md index a31254e845..1bcda49062 100644 --- a/exchange/exchange-ps/exchange/Set-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dataclassification applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-DataClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dataclassification +schema: 2.0.0 +title: Set-DataClassification --- # Set-DataClassification @@ -93,6 +94,9 @@ The first three commands return the list of document fingerprints in the data cl ## PARAMETERS ### -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 modify. You can use any value that uniquely identifies the data classification rule. For example: - Name @@ -103,7 +107,6 @@ The Identity parameter specifies the data classification rule that you want to m Type: DataClassificationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -113,6 +116,9 @@ 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`. @@ -122,7 +128,6 @@ 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 @@ -132,13 +137,15 @@ 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 data classification rule. You use the Description parameter with the Locale and Name parameters to specify descriptions for the data classification rule in different languages. The localized values of Description appear in the AllLocalizedDescriptions property of the data classification rule. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -148,13 +155,15 @@ 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 @@ -164,13 +173,15 @@ Accept wildcard characters: False ``` ### -Fingerprints + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Fingerprints parameter specifies the byte-encoded document files that are used as fingerprints by the data classification rule. 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. For instructions on how to add and remove document fingerprints from an existing data classification rule, see the Examples section. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -180,6 +191,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsDefault switch is used with the Locale parameter to specify the default language for the data classification rule. You don't need to specify a value with this switch. The default Locale value is stored in the DefaultCulture property. @@ -190,7 +204,6 @@ When you change the default Locale value, the Name value of the data classificat Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -200,6 +213,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Locale parameter adds or removes languages that are 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). @@ -210,7 +226,6 @@ Typically, you use the Locale parameter with the Name and Description parameters Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -220,6 +235,9 @@ 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. You use the Name parameter with the Locale and Description parameters to specify names for the data classification rule in different languages. The localized values of Name appear in the AllLocalizedNames property of the data classification rule. @@ -230,7 +248,6 @@ The value of the Name parameter is used in the Policy Tip that's presented to us Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -240,13 +257,15 @@ 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/exchange/Set-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md index 729b74f9f7..7525e8d697 100644 --- a/exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dataencryptionpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-DataEncryptionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dataencryptionpolicy +schema: 2.0.0 +title: Set-DataEncryptionPolicy --- # Set-DataEncryptionPolicy @@ -82,6 +83,9 @@ This example updates the data encryption policy named Europe Mailboxes after one ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the data encryption policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -92,7 +96,6 @@ The Identity parameter specifies the data encryption policy that you want to mod Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -102,15 +105,17 @@ Accept wildcard characters: False ``` ### -PermanentDataPurgeContact + +> Applicable: Exchange Online, Exchange Online Protection + The PermanentDataPurgeContact parameter specifies a contact for the purge of all data that's encrypted by the data encryption policy. If the value contains spaces, enclose the value in quotation marks. You need to use this parameter with the PermanentDataPurgeRequested and PermanentDataPurgeReason parameters. ```yaml Type: String -Parameter Sets: TenantAdminPurgeKeyRequest +Parameter Sets: TenantAdminPurgeKeyRequest, DCAdminPurgeKeyRequest Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -119,20 +124,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: DCAdminPurgeKeyRequest -Aliases: -Applicable: Exchange Online, Exchange Online Protection +### -PermanentDataPurgeReason -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online, Exchange Online Protection -### -PermanentDataPurgeReason The PermanentDataPurgeReason parameter specifies a descriptive reason for the purge of all data that's encrypted by the data encryption policy. If the value contains spaces, enclose the value in quotation marks. You need to use this parameter with the PermanentDataPurgeRequested and PermanentDataPurgeContact parameters. @@ -141,7 +136,6 @@ You need to use this parameter with the PermanentDataPurgeRequested and Permanen Type: String Parameter Sets: TenantAdminPurgeKeyRequest, DCAdminPurgeKeyRequest Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -151,6 +145,9 @@ Accept wildcard characters: False ``` ### -PermanentDataPurgeRequested + +> Applicable: Exchange Online, Exchange Online Protection + The PermanentDataPurgeRequested switch specifies whether to initiate the deletion of all data that's encrypted by the data encryption policy. You don't need to specify a value with this switch. You need to use this switch with the PermanentDataPurgeReason and PermanentDataPurgeContact parameters. @@ -161,7 +158,6 @@ After you use this switch, you can't assign the data encryption policy to other Type: SwitchParameter Parameter Sets: TenantAdminPurgeKeyRequest Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -171,13 +167,15 @@ Accept wildcard characters: False ``` ### -Refresh + +> Applicable: Exchange Online + Use the Refresh switch to update the data encryption policy in Exchange Online after you rotate any of the associated keys in the Azure Key Vault. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: RefreshKey Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -187,6 +185,9 @@ 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`. @@ -198,7 +199,6 @@ 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 @@ -208,13 +208,15 @@ 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 @@ -224,13 +226,15 @@ 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 @@ -240,6 +244,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online, Exchange Online Protection + The Enabled parameter enables or disable the data encryption policy. Valid values are: - $true: The policy is enabled. @@ -249,7 +256,6 @@ The Enabled parameter enables or disable the data encryption policy. Valid value Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -259,6 +265,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Exchange Online Protection + The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. Use this switch to delete all data that's encrypted by the data encryption policy (the PermanentDataPurgeRequested switch), but the associated Azure Key Vault has also been deleted. @@ -267,7 +276,6 @@ Use this switch to delete all data that's encrypted by the data encryption polic Type: SwitchParameter Parameter Sets: TenantAdminPurgeKeyRequest, DCAdminPurgeKeyRequest Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -277,13 +285,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -293,13 +303,15 @@ 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/exchange/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md index d5e6a1b952..f5681a4ca4 100644 --- a/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-databaseavailabilitygroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-DatabaseAvailabilityGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-databaseavailabilitygroup +schema: 2.0.0 +title: Set-DatabaseAvailabilityGroup --- # Set-DatabaseAvailabilityGroup @@ -133,13 +134,15 @@ This example configures the DAG DAG1 for AutoReseed using custom mount point pat ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the DAG that you want to modify. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -149,13 +152,15 @@ 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 @@ -165,13 +170,15 @@ Accept wildcard characters: False ``` ### -AllowCrossSiteRpcClientAccess + +> 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: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,13 +188,15 @@ Accept wildcard characters: False ``` ### -AlternateWitnessDirectory + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AlternateWitnessDirectory parameter specifies the name of an alternate directory that's used to store file share witness data. The specified directory must not be in use by any other DAGs or used for any other purpose. This parameter is used only as part of a datacenter switchover process. If the DAG is extended across multiple datacenters in a site resilience configuration, we recommend preconfiguring the alternate witness server and directory. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -197,13 +206,15 @@ Accept wildcard characters: False ``` ### -AlternateWitnessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AlternateWitnessServer parameter specifies the name of an alternate server that's used to store file share witness data. The specified server must not be a member of the DAG that's configured to use it. This parameter is used only as part of a datacenter switchover process. If the DAG is extended across multiple datacenters in a site resilience configuration, we recommend preconfiguring the alternate witness server and directory. ```yaml Type: FileShareWitnessServerName Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -213,13 +224,15 @@ Accept wildcard characters: False ``` ### -AutoDagAllServersInstalled + +> 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 @@ -229,13 +242,15 @@ Accept wildcard characters: False ``` ### -AutoDagAutoRedistributeEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AutoDagAutoRedistributeEnabled parameter specifies whether automatic DAG redistribution is enabled or disabled during AutoReseed. The default value is $true (enabled). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -245,13 +260,15 @@ Accept wildcard characters: False ``` ### -AutoDagAutoReseedEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagAutoReseedEnabled is used to enable or disable Autoreseed. The default value is $true (enabled). ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -261,13 +278,15 @@ Accept wildcard characters: False ``` ### -AutoDagBitlockerEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagBitlockerEnabled parameter ensures that Disk Reclaimer handles spare disks correctly and encrypts them with BitLocker. If Bitlocker is used to encrypt database disks, set the value of this parameter to $true on all Mailbox servers in the DAG after they are all running Exchange 2013 CU13 or later, or Exchange 2016 CU2 or later. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,13 +296,15 @@ Accept wildcard characters: False ``` ### -AutoDagDatabaseCopiesPerDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,13 +314,15 @@ Accept wildcard characters: False ``` ### -AutoDagDatabaseCopiesPerVolume + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagDatabaseCopiesPerVolume parameter is used to specify the configured number of database copies per volume. This parameter is used only with AutoReseed. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -309,13 +332,15 @@ Accept wildcard characters: False ``` ### -AutoDagDatabasesRootFolderPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagDatabasesRootFolderPath parameter specifies the directory containing the database mount points when using AutoReseed. This parameter is required when using AutoReseed. AutoReseed uses a default path of C:\\ExchangeDatabases. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -325,13 +350,15 @@ Accept wildcard characters: False ``` ### -AutoDagDiskReclaimerEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you will need to manually format the volume before the database(s) can be reseeded. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -341,13 +368,15 @@ Accept wildcard characters: False ``` ### -AutoDagTotalNumberOfDatabases + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,13 +386,15 @@ Accept wildcard characters: False ``` ### -AutoDagTotalNumberOfServers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -373,13 +404,15 @@ Accept wildcard characters: False ``` ### -AutoDagVolumesRootFolderPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagVolumesRootFolderPath parameter specifies the volume containing the mount points for all disks, including spare disks, when using the AutoReseed feature of the DAG. This parameter is required when using AutoReseed. AutoReseed uses a default path of C:\\ExchangeVolumes. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -389,6 +422,9 @@ 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`. @@ -398,7 +434,6 @@ 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 @@ -408,13 +443,15 @@ 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 @@ -424,13 +461,15 @@ 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 IP addresses to the DAG when a Mailbox server is added to a DAG. If you omit the DatabaseAvailabilityGroupIpAddresses parameter when creating a DAG, the system attempts to lease one or more IP addresses from a Dynamic Host Configuration Protocol (DHCP) server in your organization to assign to the DAG. You must specify this parameter each time an additional IP address is added to the DAG, such as in the case of multi-subnet DAGs. You must also specify all IP addresses previously assigned to the DAG each time the DatabaseAvailabilityGroupIpAddresses parameter is used. Setting the DatabaseAvailabilityGroupIpAddresses parameter to a value of 0.0.0.0 automatically configures the DAG to use DHCP. ```yaml Type: IPAddress[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -440,6 +479,9 @@ Accept wildcard characters: False ``` ### -DatacenterActivationMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DatacenterActivationMode parameter specifies the datacenter activation mode for the DAG. Valid values are: - Off: Datacenter activation mode is disabled. @@ -449,7 +491,6 @@ The DatacenterActivationMode parameter specifies the datacenter activation mode Type: DatacenterActivationModeOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -459,6 +500,9 @@ Accept wildcard characters: False ``` ### -DiscoverNetworks + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoverNetworks switch specifies whether to force a rediscovery of the network and network interfaces. You don't need to specify a value with this switch. By default, internal network heartbeats are sent between DAG members on the same subnet. If there's no response to the heartbeats, network discovery is performed automatically by the system. If you add or remove networks or change DAG network subnets, you can force rediscovery of all DAG networks by using the DiscoverNetworks switch. @@ -467,7 +511,6 @@ By default, internal network heartbeats are sent between DAG members on the same Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -477,13 +520,15 @@ 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 @@ -493,6 +538,9 @@ 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 @@ -502,7 +550,6 @@ 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 @@ -512,13 +559,15 @@ Accept wildcard characters: False ``` ### -ManualDagNetworkConfiguration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ManualDagNetworkConfiguration parameter specifies whether DAG networks should be automatically configured. If this parameter is set to $false, DAG networks are automatically configured. If this parameter is set to $true, you must manually configure DAG networks. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -528,13 +577,15 @@ Accept wildcard characters: False ``` ### -MetaCacheDatabaseVolumesPerServer + +> Applicable: Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -544,6 +595,9 @@ Accept wildcard characters: False ``` ### -NetworkCompression + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NetworkCompression parameter specifies the network compression option for the DAG. Valid values are: - Disabled: Network compression is disabled on all networks. @@ -555,7 +609,6 @@ The NetworkCompression parameter specifies the network compression option for th Type: NetworkOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -565,6 +618,9 @@ Accept wildcard characters: False ``` ### -NetworkEncryption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NetworkEncryption parameter specifies the network encryption option for the DAG. Valid values are: - Disabled: Network encryption is disabled on all networks. @@ -576,7 +632,6 @@ The NetworkEncryption parameter specifies the network encryption option for the Type: NetworkOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -586,6 +641,9 @@ Accept wildcard characters: False ``` ### -PreferenceMoveFrequency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The PreferenceMoveFrequency parameter specifies how frequently the Microsoft Exchange Replication service inspects and automatically rebalances the database copies. If the most preferred database copy (ActivationPreference value of 1) isn't the active copy, the most preferred database copy is activated by performing a lossless switchover. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -598,7 +656,6 @@ The default value is 01:00:00 (1 hour). To disable this feature, specify the val Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -608,13 +665,15 @@ Accept wildcard characters: False ``` ### -ReplayLagManagerEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplayLagManagerEnabled parameter specifies whether to disable the automatic playdown of log files for a lagged database copy. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -624,13 +683,15 @@ Accept wildcard characters: False ``` ### -ReplicationPort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplicationPort parameter specifies a Transmission Control Protocol (TCP) port for replication (log shipping and seeding) activity. If this parameter isn't specified, the default port for replication is TCP 64327. ```yaml Type: UInt16 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -640,13 +701,15 @@ 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 configuring 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 @@ -656,13 +719,15 @@ 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 @@ -672,13 +737,15 @@ 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 server that's used to store file share witness data. The specified directory must not be in use by any other DAGs. ```yaml Type: NonRootLocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -688,13 +755,15 @@ 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 that will act as a witness for the DAG. The server specified can't be a member of the DAG. ```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/exchange/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md index 1cf2e33f62..fef4f5bfc4 100644 --- a/exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-databaseavailabilitygroupnetwork applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-DatabaseAvailabilityGroupNetwork -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-databaseavailabilitygroupnetwork +schema: 2.0.0 +title: Set-DatabaseAvailabilityGroupNetwork --- # Set-DatabaseAvailabilityGroupNetwork @@ -57,13 +58,15 @@ This example disables the DAG network DAGNetwork02 in the DAG DAG2 for replicati ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the DAG network being configured. ```yaml Type: DatabaseAvailabilityGroupNetworkIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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 for the DAG network. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -108,13 +115,15 @@ 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,13 +133,15 @@ Accept wildcard characters: False ``` ### -IgnoreNetwork + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IgnoreNetwork parameter indicates that the specified network should be ignored and not used 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 @@ -140,13 +151,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter provides a name for the DAG network. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -156,13 +169,15 @@ Accept wildcard characters: False ``` ### -ReplicationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplicationEnabled parameter specifies whether the network can be used for replication activity. If this parameter isn't specified, the default behavior is to enable the network for 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 @@ -172,13 +187,15 @@ Accept wildcard characters: False ``` ### -Subnets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Subnets parameter specifies one or more subnets that are associated with the DAG network. ```yaml Type: DatabaseAvailabilityGroupSubnetId[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,13 +205,15 @@ 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/exchange/Set-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md similarity index 97% rename from exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md index 82ecf059aa..92c9983986 100644 --- a/exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-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/set-defaulttenantbriefingconfig applicable: Exchange Online -title: Set-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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-defaulttenantbriefingconfig +schema: 2.0.0 +title: Set-DefaultTenantBriefingConfig --- # Set-DefaultTenantBriefingConfig @@ -53,6 +53,9 @@ This example sets the default Briefing email configuration for the organization ## PARAMETERS ### -IsEnabledByDefault + +> Applicable: Exchange Online + The IsEnabledByDefault parameter specifies the default Briefing email configuration for the organization. Valid values are: - Opt-in: By default, all users in the organization are subscribed to receive the Briefing email. @@ -69,7 +72,6 @@ This setting does not affect users who've already updated their user settings to Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -79,13 +81,15 @@ 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/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantMyAnalyticsFeatureConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantMyAnalyticsFeatureConfig.md index 9c1ba06bb4..fff3da74c7 100644 --- a/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-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/set-defaulttenantmyanalyticsfeatureconfig applicable: Exchange Online -title: Set-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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-defaulttenantmyanalyticsfeatureconfig +schema: 2.0.0 +title: Set-DefaultTenantMyAnalyticsFeatureConfig --- # Set-DefaultTenantMyAnalyticsFeatureConfig @@ -70,6 +70,9 @@ This example sets the meeting effectiveness survey sampling rate to 20%. ## PARAMETERS ### -Feature + +> Applicable: Exchange Online + The Feature parameter specifies the Viva Insights feature to enable or disable. Valid values are: - Add-in @@ -85,7 +88,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: Dashboard, Add-in, Digest-email, Meeting-effectiveness-survey, Scheduled-send, All -Applicable: Exchange Online Required: False Position: Named @@ -95,6 +97,9 @@ Accept wildcard characters: False ``` ### -IsEnabled + +> Applicable: Exchange Online + The IsEnabled parameter enables or disables the Viva Insights feature specified by the Feature parameter. Valid values are: - $true: The feature is enabled. @@ -104,7 +109,6 @@ The IsEnabled parameter enables or disables the Viva Insights feature specified Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -114,13 +118,15 @@ 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 @@ -130,6 +136,9 @@ Accept wildcard characters: False ``` ### -SamplingRate + +> Applicable: Exchange Online + This parameter is available only in version 3.2.0 or later. The SamplingRate parameter specifies the meeting effectiveness survey sampling rate. The percentage value is expressed a a decimal (for example, 0.1 indicates 10%). A valid value is from 0.1 to 0.7. @@ -138,7 +147,6 @@ The SamplingRate parameter specifies the meeting effectiveness survey sampling r Type: Double Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md index e1280caf99..29f3444284 100644 --- a/exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-deliveryagentconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-DeliveryAgentConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-deliveryagentconnector +schema: 2.0.0 +title: Set-DeliveryAgentConnector --- # Set-DeliveryAgentConnector @@ -73,13 +74,15 @@ This example uses the temporary variable $ConnectorConfig to add the address spa ## 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: True Position: 1 @@ -89,13 +92,15 @@ 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: False Position: Named @@ -105,13 +110,15 @@ 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 @@ -121,6 +128,9 @@ 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,7 +140,6 @@ 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 @@ -140,13 +149,15 @@ 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: False Position: Named @@ -156,6 +167,9 @@ 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. @@ -164,7 +178,6 @@ 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 @@ -174,6 +187,9 @@ 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. @@ -182,7 +198,6 @@ 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 @@ -192,6 +207,9 @@ 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. @@ -200,7 +218,6 @@ 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 @@ -210,6 +227,9 @@ 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. @@ -218,7 +238,6 @@ The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -228,6 +247,9 @@ 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. @@ -236,7 +258,6 @@ The default value is 5. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -246,6 +267,9 @@ 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) @@ -261,7 +285,6 @@ The default value is unlimited. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -271,6 +294,9 @@ 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. @@ -279,7 +305,6 @@ The default value is 20. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -289,13 +314,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -305,6 +332,9 @@ 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. @@ -313,7 +343,6 @@ 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 @@ -323,13 +352,15 @@ 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/exchange/Set-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-DetailsTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md index dfeb2f1c61..bc06ecc309 100644 --- a/exchange/exchange-ps/exchange/Set-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-detailstemplate applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-DetailsTemplate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-detailstemplate +schema: 2.0.0 +title: Set-DetailsTemplate --- # Set-DetailsTemplate @@ -44,6 +45,9 @@ This example sets attributes for the User details template for the U.S. English ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the details template using a GUID or specifies a template type and language separated by a slash. The following is an example of the user template type and U.S. English language: en-us\\User. Details template types include: - User @@ -57,7 +61,6 @@ The Identity parameter specifies the details template using a GUID or specifies Type: DetailsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ 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 @@ -102,13 +109,15 @@ Accept wildcard characters: False ``` ### -Pages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,13 +127,15 @@ 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/exchange/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md index 0bbba58e9e..67733135b5 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconditionalaccesspolicy applicable: Security & Compliance -title: Set-DeviceConditionalAccessPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconditionalaccesspolicy +schema: 2.0.0 +title: Set-DeviceConditionalAccessPolicy --- # Set-DeviceConditionalAccessPolicy @@ -64,6 +65,9 @@ This example disables the existing mobile device conditional access policy named ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device conditional access policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -74,7 +78,6 @@ The Identity parameter specifies the mobile device conditional access policy tha Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -84,13 +87,15 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -100,13 +105,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -116,6 +123,9 @@ 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,7 +135,6 @@ 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,6 +144,9 @@ 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. @@ -144,7 +156,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -154,6 +165,9 @@ 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. @@ -162,7 +176,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -172,13 +185,15 @@ 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/exchange/Set-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md index f9e793ed4e..bbb4746bb1 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconditionalaccessrule applicable: Security & Compliance -title: Set-DeviceConditionalAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconditionalaccessrule +schema: 2.0.0 +title: Set-DeviceConditionalAccessRule --- # Set-DeviceConditionalAccessRule @@ -100,13 +101,15 @@ This example modifies the specified mobile device conditional access rule to blo ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device conditional access rule that you want to modify. The name of the rule uses the syntax `{}`. For example, `Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}`. You can find the name value by running the command: Get-DeviceConfigurationRule | Format-List Name. ```yaml Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -116,6 +119,9 @@ 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. @@ -124,7 +130,6 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -134,6 +139,9 @@ Accept wildcard characters: False ``` ### -AccountName + +> Applicable: Security & Compliance + The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. @@ -143,7 +151,6 @@ 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 @@ -153,6 +160,9 @@ 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. @@ -162,7 +172,6 @@ The AccountUserName parameter specifies the account user name. Valid values for Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -172,6 +181,9 @@ 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. @@ -187,7 +199,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -197,6 +208,9 @@ 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. @@ -209,7 +223,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -219,6 +232,9 @@ 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. @@ -231,7 +247,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -241,6 +256,9 @@ 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. @@ -257,7 +275,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -267,6 +284,9 @@ 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. @@ -282,7 +302,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -292,6 +311,9 @@ 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. @@ -307,7 +329,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -317,6 +338,9 @@ 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. @@ -332,7 +356,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -342,6 +365,9 @@ 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. @@ -357,7 +383,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -367,6 +392,9 @@ 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. @@ -379,7 +407,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -389,6 +416,9 @@ 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. @@ -404,7 +434,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -414,6 +443,9 @@ 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. @@ -430,7 +462,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -440,6 +471,9 @@ 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. @@ -452,7 +486,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -462,6 +495,9 @@ 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. @@ -474,7 +510,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -484,6 +519,9 @@ 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. @@ -496,7 +534,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -506,6 +543,9 @@ Accept wildcard characters: False ``` ### -AntiVirusSignatureStatus + +> Applicable: Security & Compliance + The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. @@ -517,7 +557,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -527,6 +566,9 @@ Accept wildcard characters: False ``` ### -AntiVirusStatus + +> Applicable: Security & Compliance + The AntiVirusStatus parameter specifies antivirus status. Valid values for this parameter are: - An integer. @@ -538,7 +580,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -548,6 +589,9 @@ 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 @@ -563,7 +607,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -573,6 +616,9 @@ Accept wildcard characters: False ``` ### -AutoUpdateStatus + +> Applicable: Security & Compliance + The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates @@ -588,7 +634,6 @@ This setting is available only on Windows 8.1 RT devices. Type: CAAutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -598,6 +643,9 @@ 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. @@ -610,7 +658,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -620,6 +667,9 @@ 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. @@ -636,7 +686,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -646,6 +695,9 @@ 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`. @@ -655,7 +707,6 @@ 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 @@ -665,13 +716,15 @@ 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 @@ -681,6 +734,9 @@ 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. @@ -690,7 +746,6 @@ The EmailAddress parameter specifies the email address. Valid values are: Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -700,6 +755,9 @@ 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. @@ -712,7 +770,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -722,6 +779,9 @@ 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. @@ -731,7 +791,6 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -741,6 +800,9 @@ 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 @@ -752,7 +814,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -762,6 +823,9 @@ 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. @@ -774,7 +838,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -784,6 +847,9 @@ 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. @@ -799,7 +865,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -809,6 +874,9 @@ 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. @@ -825,7 +893,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -835,6 +902,9 @@ 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. @@ -845,7 +915,6 @@ 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 @@ -855,6 +924,9 @@ 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: @@ -945,7 +1017,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -955,6 +1026,9 @@ Accept wildcard characters: False ``` ### -PasswordComplexity + +> Applicable: Security & Compliance + The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. @@ -964,7 +1038,6 @@ The PasswordComplexity parameter specifies the password complexity. Valid values Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -974,6 +1047,9 @@ 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. @@ -990,7 +1066,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1000,6 +1075,9 @@ 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. @@ -1016,7 +1094,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1026,6 +1103,9 @@ 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. @@ -1035,7 +1115,6 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1045,6 +1124,9 @@ 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. @@ -1061,7 +1143,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1071,6 +1152,9 @@ 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: @@ -1084,7 +1168,6 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1094,6 +1177,9 @@ 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. @@ -1110,7 +1196,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1120,6 +1205,9 @@ 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: @@ -1135,7 +1223,6 @@ 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 @@ -1145,6 +1232,9 @@ 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. @@ -1160,7 +1250,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1170,6 +1259,9 @@ 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: @@ -1191,7 +1283,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1201,6 +1292,9 @@ 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. @@ -1211,7 +1305,6 @@ The RequireEmailProfile parameter specifies whether an email profile is required Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1221,6 +1314,9 @@ 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. @@ -1233,7 +1329,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1243,6 +1338,9 @@ 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. @@ -1255,7 +1353,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1265,6 +1362,9 @@ 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: @@ -1344,7 +1444,6 @@ This setting is available only on Apple iOS 6+ devices. Type: CARatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1354,6 +1453,9 @@ 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. @@ -1368,7 +1470,6 @@ This setting is available only on Windows 8.1 RT devices. Type: CAUserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1378,13 +1479,15 @@ 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 @@ -1394,6 +1497,9 @@ 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. @@ -1406,7 +1512,6 @@ 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 @@ -1416,6 +1521,9 @@ 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`. @@ -1426,7 +1534,6 @@ 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/exchange/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md index ed19ba795f..77d264313a 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconfigurationpolicy applicable: Security & Compliance -title: Set-DeviceConfigurationPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconfigurationpolicy +schema: 2.0.0 +title: Set-DeviceConfigurationPolicy --- # Set-DeviceConfigurationPolicy @@ -64,6 +65,9 @@ This example disables the mobile device configuration policy named Engineering G ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device configuration policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -74,7 +78,6 @@ The Identity parameter specifies the mobile device configuration policy that you Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -84,13 +87,15 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -100,13 +105,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -116,6 +123,9 @@ 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,7 +135,6 @@ 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,6 +144,9 @@ 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. @@ -144,7 +156,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -154,6 +165,9 @@ 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. @@ -162,7 +176,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -172,13 +185,15 @@ 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/exchange/Set-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md index 3ea511f71e..222ac9e0f0 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconfigurationrule applicable: Security & Compliance -title: Set-DeviceConfigurationRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-deviceconfigurationrule +schema: 2.0.0 +title: Set-DeviceConfigurationRule --- # Set-DeviceConfigurationRule @@ -99,13 +100,15 @@ This example modifies the specified mobile device configuration rule to block sc ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the mobile device configuration rule that you want to modify. The name of the rule uses the syntax ` 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. @@ -123,7 +129,6 @@ You can specify multiple groups separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -133,6 +138,9 @@ Accept wildcard characters: False ``` ### -AccountName + +> Applicable: Security & Compliance + The AccountName parameter specifies the account name. Valid values for this parameter are: - A text value. @@ -142,7 +150,6 @@ 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 @@ -152,6 +159,9 @@ 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. @@ -161,7 +171,6 @@ The AccountUserName parameter specifies the account user name. Valid values for Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -171,6 +180,9 @@ 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. @@ -186,7 +198,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -196,6 +207,9 @@ 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. @@ -208,7 +222,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -218,6 +231,9 @@ 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. @@ -230,7 +246,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -240,6 +255,9 @@ 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. @@ -256,7 +274,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -266,6 +283,9 @@ 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. @@ -281,7 +301,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -291,6 +310,9 @@ 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. @@ -306,7 +328,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -316,6 +337,9 @@ 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. @@ -331,7 +355,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -341,6 +364,9 @@ 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. @@ -353,7 +379,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -363,6 +388,9 @@ 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. @@ -378,7 +406,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -388,6 +415,9 @@ 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. @@ -404,7 +434,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -414,6 +443,9 @@ 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. @@ -426,7 +458,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -436,6 +467,9 @@ 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. @@ -448,7 +482,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -458,6 +491,9 @@ 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. @@ -470,7 +506,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -480,6 +515,9 @@ Accept wildcard characters: False ``` ### -AntiVirusSignatureStatus + +> Applicable: Security & Compliance + The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are: - An integer. @@ -491,7 +529,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -501,6 +538,9 @@ Accept wildcard characters: False ``` ### -AntiVirusStatus + +> Applicable: Security & Compliance + The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are: - An integer. @@ -512,7 +552,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -522,6 +561,9 @@ 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 @@ -537,7 +579,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingAppsEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -547,6 +588,9 @@ Accept wildcard characters: False ``` ### -AutoUpdateStatus + +> Applicable: Security & Compliance + The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are: - AutomaticCheckForUpdates @@ -562,7 +606,6 @@ This setting is available only on Windows 8.1 RT devices. Type: AutoUpdateStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -572,6 +615,9 @@ 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. @@ -584,7 +630,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -594,6 +639,9 @@ 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. @@ -610,7 +658,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -620,6 +667,9 @@ 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`. @@ -629,7 +679,6 @@ 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 @@ -639,13 +688,15 @@ 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 @@ -655,6 +706,9 @@ 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. @@ -664,7 +718,6 @@ The EmailAddress parameter specifies the email address. Valid values are: Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -674,6 +727,9 @@ 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. @@ -686,7 +742,6 @@ This setting is available only on Windows Phone 8.1 devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -696,6 +751,9 @@ 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. @@ -705,7 +763,6 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -715,6 +772,9 @@ 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 @@ -726,7 +786,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Required Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -736,6 +795,9 @@ 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. @@ -748,7 +810,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -758,6 +819,9 @@ 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. @@ -773,7 +837,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -783,6 +846,9 @@ 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. @@ -799,7 +865,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -809,6 +874,9 @@ 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. @@ -819,7 +887,6 @@ 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 @@ -829,6 +896,9 @@ 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: @@ -919,7 +989,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingMovieEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -929,6 +998,9 @@ Accept wildcard characters: False ``` ### -PasswordComplexity + +> Applicable: Security & Compliance + The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are: - An integer. @@ -938,7 +1010,6 @@ The PasswordComplexity parameter specifies the password complexity. Valid values Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -948,6 +1019,9 @@ 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. @@ -964,7 +1038,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -974,6 +1047,9 @@ 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. @@ -990,7 +1066,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1000,6 +1075,9 @@ 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. @@ -1009,7 +1087,6 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1019,6 +1096,9 @@ 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. @@ -1035,7 +1115,6 @@ This setting is available on the following types of devices: Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1045,6 +1124,9 @@ 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: @@ -1058,7 +1140,6 @@ This setting is available only on Android 4+ devices. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1068,6 +1149,9 @@ 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. @@ -1084,7 +1168,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1094,6 +1177,9 @@ 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: @@ -1109,7 +1195,6 @@ 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 @@ -1119,6 +1204,9 @@ 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. @@ -1134,7 +1222,6 @@ This setting is available on the following types of devices: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1144,6 +1231,9 @@ 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: @@ -1165,7 +1255,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingRegionEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1175,6 +1264,9 @@ 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. @@ -1185,7 +1277,6 @@ The RequireEmailProfile parameter specifies whether an email profile is required Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1195,6 +1286,9 @@ 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. @@ -1207,7 +1301,6 @@ This setting is available only on Windows 8.1 RT devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1217,6 +1310,9 @@ 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. @@ -1229,7 +1325,6 @@ This setting is available only on Apple iOS 6+ devices. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1239,6 +1334,9 @@ 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: @@ -1318,7 +1416,6 @@ This setting is available only on Apple iOS 6+ devices. Type: RatingTvShowEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1328,6 +1425,9 @@ 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. @@ -1342,7 +1442,6 @@ This setting is available only on Windows 8.1 RT devices. Type: UserAccountControlStatusEntry Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1352,13 +1451,15 @@ 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 @@ -1368,6 +1469,9 @@ 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. @@ -1380,7 +1484,6 @@ 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 @@ -1390,6 +1493,9 @@ 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`. @@ -1400,7 +1506,6 @@ 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/exchange/Set-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DeviceTenantPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md index 4642570323..23f247c23a 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-devicetenantpolicy applicable: Security & Compliance -title: Set-DeviceTenantPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-devicetenantpolicy +schema: 2.0.0 +title: Set-DeviceTenantPolicy --- # Set-DeviceTenantPolicy @@ -64,13 +65,15 @@ This example disables your organization's mobile device tenant policy. ## PARAMETERS ### -RetryDistribution + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -80,13 +83,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -96,6 +101,9 @@ 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`. @@ -105,7 +113,6 @@ 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,6 +122,9 @@ 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,7 +134,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -134,6 +143,9 @@ 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. @@ -142,7 +154,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -152,13 +163,15 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the mobile device tenant policy that you want to modify, but there's only one in your organization. The name of the policy is a GUID value. For example, a6958701-c82c-4064-ac11-64e40e7f4032. You can find this value by running the command: Get-DeviceTenantPolicy | Format-List Name. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -168,13 +181,15 @@ 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/exchange/Set-DeviceTenantRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DeviceTenantRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md index e931196275..438c021a90 100644 --- a/exchange/exchange-ps/exchange/Set-DeviceTenantRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-devicetenantrule applicable: Security & Compliance -title: Set-DeviceTenantRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-devicetenantrule +schema: 2.0.0 +title: Set-DeviceTenantRule --- # Set-DeviceTenantRule @@ -55,13 +56,15 @@ This example modifies your organization's mobile device tenant rule by replacing ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the mobile device tenant rule that you want to modify, but there's only one in your organization. The name of the rule is a GUID. For example, 7577c5f3-05a4-4f55-a0a3-82aab5e98c84. You can find the name value by running the command Get-DeviceTenantRule | Format-List Name. ```yaml Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -ApplyPolicyTo + +> Applicable: Security & Compliance + The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are: - ExchangeOnline @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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. @@ -100,7 +108,6 @@ The BlockUnsupportedDevices parameter specifies whether to block access to your Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -110,6 +117,9 @@ 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`. @@ -119,7 +129,6 @@ 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,13 +138,15 @@ 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 @@ -145,6 +156,9 @@ 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. @@ -155,7 +169,6 @@ To enter multiple values and overwrite any existing entries, use the following s Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -165,13 +178,15 @@ 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/exchange/Set-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md index 918556255a..9bbd184a36 100644 --- a/exchange/exchange-ps/exchange/Set-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-distributiongroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-DistributionGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-distributiongroup +schema: 2.0.0 +title: Set-DistributionGroup --- # Set-DistributionGroup @@ -126,6 +127,9 @@ This example changes the name of an existing distribution group from Ed\_DirectR ## 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 modify. You can use any value that uniquely identifies the group. For example: - Name @@ -139,7 +143,6 @@ 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, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -149,6 +152,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -172,7 +178,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -182,6 +187,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -205,7 +213,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -215,6 +222,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -240,7 +250,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -250,6 +259,9 @@ 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: @@ -274,7 +286,6 @@ 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 @@ -284,6 +295,9 @@ 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: @@ -303,7 +317,6 @@ 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 @@ -313,6 +326,9 @@ 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: @@ -324,7 +340,6 @@ 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 @@ -334,6 +349,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -355,7 +373,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -365,6 +382,9 @@ 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. @@ -374,7 +394,6 @@ The ByPassNestedModerationEnabled parameter specifies how to handle message appr 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 @@ -384,6 +403,9 @@ 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: @@ -395,7 +417,6 @@ 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 @@ -405,6 +426,9 @@ 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`. @@ -414,7 +438,6 @@ 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 @@ -424,6 +447,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -435,7 +461,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -445,13 +470,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -461,13 +488,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -477,13 +506,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -493,13 +524,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -509,13 +542,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -525,13 +560,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -541,13 +578,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -557,13 +596,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -573,13 +614,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -589,13 +632,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -605,13 +650,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -621,13 +668,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -637,13 +686,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -653,13 +704,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -669,13 +722,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -685,6 +740,9 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The Description parameter specifies an optional description for the distribution group. If the value contains spaces, enclose the value in quotation marks. @@ -693,7 +751,6 @@ The Description parameter specifies an optional description for the distribution Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -703,6 +760,9 @@ 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 a group naming policy is enforced in your organization, users need to follow the naming constraints as specified by the DistributionGroupNameBlockedWordList parameter on the Set-OrganizationConfig cmdlet. To bypass this requirement, use the IgnoreNamingPolicy switch. @@ -711,7 +771,6 @@ 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 @@ -721,6 +780,9 @@ 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. @@ -729,7 +791,6 @@ 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 @@ -739,6 +800,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -766,7 +830,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection 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 @@ -776,6 +839,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: @@ -787,7 +853,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -797,6 +862,9 @@ Accept wildcard characters: False ``` ### -ExpansionServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExpansionServer parameter specifies the Exchange server that's used to expand the distribution group. The default value is blank ($null), which means expansion happens on the closest available Exchange server. If you specify an expansion server, and that server is unavailable, any messages that are sent to the distribution group can't be delivered. @@ -812,7 +880,6 @@ When you specify an expansion server, use the ExchangeLegacyDN. You can find thi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -822,6 +889,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -834,7 +904,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -844,6 +913,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -856,7 +928,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -866,6 +937,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -878,7 +952,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -888,6 +961,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -900,7 +976,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -910,6 +985,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -922,7 +1000,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -932,13 +1009,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 @@ -948,6 +1027,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this group. Although messages send on behalf of the group clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the group, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -973,7 +1055,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -983,6 +1064,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -992,7 +1076,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -1002,6 +1085,9 @@ 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. @@ -1014,7 +1100,6 @@ 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 @@ -1024,6 +1109,9 @@ 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. @@ -1037,7 +1125,6 @@ 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 @@ -1047,6 +1134,9 @@ 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. @@ -1055,7 +1145,6 @@ 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 @@ -1065,6 +1154,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -1076,7 +1168,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -1086,6 +1177,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -1100,7 +1194,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -1110,6 +1203,9 @@ 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 @@ -1148,7 +1244,6 @@ Owners that you specify with this parameter are not added as group members. You 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 @@ -1158,6 +1253,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxReceiveSize parameter specifies the maximum size of an email message that can be sent to this group. Messages that exceed the maximum size are rejected by the group. @@ -1179,7 +1277,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1189,6 +1286,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxSendSize parameter specifies the maximum size of an email message that can be sent by this group. @@ -1210,7 +1310,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1220,6 +1319,9 @@ 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. @@ -1229,7 +1331,6 @@ 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 @@ -1239,6 +1340,9 @@ 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. @@ -1249,7 +1353,6 @@ 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 @@ -1259,6 +1362,9 @@ 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 @@ -1280,7 +1386,6 @@ 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 @@ -1290,6 +1395,9 @@ 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. @@ -1301,7 +1409,6 @@ 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 @@ -1311,13 +1418,15 @@ Accept wildcard characters: False ``` ### -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 ("). ```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 @@ -1327,6 +1436,9 @@ 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. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but the email addresses of the group are no longer automatically updated by email address policies. @@ -1337,7 +1449,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm 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 @@ -1347,6 +1458,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1370,7 +1484,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1380,6 +1493,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1403,7 +1519,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1413,6 +1528,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1438,7 +1556,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1448,6 +1565,9 @@ Accept wildcard characters: False ``` ### -ReportToManagerEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owner (first one listed if more than one) of the group (defined by the ManagedBy property). Valid values are: - $true: Delivery status notifications are sent to the owner (first one listed if more than one) of the group. @@ -1459,7 +1579,6 @@ The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the r 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 @@ -1469,6 +1588,9 @@ Accept wildcard characters: False ``` ### -ReportToOriginatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are: - $true: Delivery status notifications are sent to the message senders. This is the default value. @@ -1480,7 +1602,6 @@ The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the r 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 @@ -1490,6 +1611,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, 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. @@ -1499,7 +1623,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -1509,6 +1632,9 @@ Accept wildcard characters: False ``` ### -ResetMigrationToUnifiedGroup + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The ResetMigrationToUnifiedGroup switch specifies whether you want to reset the flag that indicates the migration of the distribution group to a Microsoft 365 Group is in progress. You don't need to specify a value with this switch. @@ -1517,7 +1643,6 @@ The ResetMigrationToUnifiedGroup switch specifies whether you want to reset the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1527,6 +1652,9 @@ 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. @@ -1535,7 +1663,6 @@ 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 @@ -1545,6 +1672,9 @@ 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). @@ -1553,7 +1683,6 @@ 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 @@ -1563,6 +1692,9 @@ 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. @@ -1575,7 +1707,6 @@ 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 @@ -1585,6 +1716,9 @@ Accept wildcard characters: False ``` ### -SendOofMessageToOriginatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are: - $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender. @@ -1594,7 +1728,6 @@ The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of o 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 @@ -1604,6 +1737,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -1616,7 +1752,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -1626,6 +1761,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -1646,7 +1784,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1656,6 +1793,9 @@ Accept wildcard characters: False ``` ### -UpdateMemberCount + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill UpdateMemberCount Description }} @@ -1664,7 +1804,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1674,13 +1813,15 @@ 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 @@ -1690,6 +1831,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -1701,7 +1845,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-DkimSigningConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md index f2b0ed064b..e19324bbbd 100644 --- a/exchange/exchange-ps/exchange/Set-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dkimsigningconfig applicable: Exchange Online, Exchange Online Protection -title: Set-DkimSigningConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dkimsigningconfig +schema: 2.0.0 +title: Set-DkimSigningConfig --- # Set-DkimSigningConfig @@ -47,6 +48,9 @@ This example disables the DKIM signing policy for the contoso.com domain. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the DKIM signing policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name: The domain name (for example, contoso.com). @@ -57,7 +61,6 @@ The Identity parameter specifies the DKIM signing policy that you want to modify Type: DkimSigningConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -67,13 +70,15 @@ 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 @@ -83,6 +88,9 @@ 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. @@ -92,7 +100,6 @@ The BodyCanonicalization parameter specifies the canonicalization algorithm that Type: CanonicalizationType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -102,6 +109,9 @@ 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`. @@ -111,7 +121,6 @@ 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 @@ -121,6 +130,9 @@ 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. This is the default value. @@ -130,7 +142,6 @@ 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: False Position: Named @@ -140,6 +151,9 @@ 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. @@ -149,7 +163,6 @@ The HeaderCanonicalization parameter specifies the canonicalization algorithm th Type: CanonicalizationType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -159,6 +172,9 @@ Accept wildcard characters: False ``` ### -PublishTxtRecords + +> Applicable: Exchange Online, Exchange Online Protection + The PublishTxtRecords switch publishes the required data for the selected domain so the correct DKIM records can be created in DNS. You don't need to specify a value with this switch. If you're using a third party DNS service, you still need to create the CNAME records that point to the DKIM records that have been created for you. @@ -167,7 +183,6 @@ If you're using a third party DNS service, you still need to create the CNAME re Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -177,13 +192,15 @@ 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/exchange/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md index af75bf6d9d..9a42cbd854 100644 --- a/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpcompliancepolicy applicable: Security & Compliance -title: Set-DlpCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpcompliancepolicy +schema: 2.0.0 +title: Set-DlpCompliancePolicy --- # Set-DlpCompliancePolicy @@ -124,6 +125,9 @@ This example adds the specified workspace IDs to the Power BI location for the D ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the DLP policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -135,7 +139,6 @@ The Identity parameter specifies the DLP policy that you want to modify. You can Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -145,6 +148,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch redistributes the policy to all Exchange, OneDrive, and SharePoint locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported if you used this switch. @@ -155,7 +161,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -165,6 +170,9 @@ Accept wildcard characters: False ``` ### -AddEndpointDlpLocation + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. @@ -177,7 +185,6 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -187,6 +194,9 @@ Accept wildcard characters: False ``` ### -AddEndpointDlpLocationException + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. @@ -199,7 +209,6 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -209,6 +218,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter adds email messages to the DLP policy if they're not already included. The valid value for this parameter is All. If the policy doesn't already include email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures: @@ -223,7 +235,6 @@ If the policy doesn't already include email messages (in the output of the Get-D Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -233,6 +244,9 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocation + +> Applicable: Security & Compliance + The AddOneDriveLocation parameter adds OneDrive sites to the DLP policy if they're not already included. The valid value for this parameter is All. If the policy doesn't already include OneDrive sites (in the output of the Get-DlpCompliancePolicy cmdlet, the OneDriveLocation property value is blank), you can use this parameter in the following procedures: @@ -255,7 +269,6 @@ You can't specify inclusions and exclusions in the same policy. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -265,13 +278,15 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocationException + +> Applicable: Security & Compliance + Don't use this parameter. See the AddOneDriveLocation parameter for an explanation. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -281,6 +296,9 @@ Accept wildcard characters: False ``` ### -AddOnPremisesScannerDlpLocation + +> Applicable: Security & Compliance + The AddOnPremisesScannerDlpLocation parameter specifies the on-premises file shares and SharePoint document libraries and folders to add to the list of included repositories if you used 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: `"","",...""`. @@ -291,7 +309,6 @@ For more information about the DLP on-premises scanner, see [Learn about the dat Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -301,6 +318,9 @@ Accept wildcard characters: False ``` ### -AddOnPremisesScannerDlpLocationException + +> Applicable: Security & Compliance + The AddOnPremisesScannerDlpLocationExclusion parameter specifies the on-premises file shares and SharePoint document libraries and folders to add to the list of excluded repositories if you used 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: `"","",...""`. @@ -311,7 +331,6 @@ For more information about the DLP on-premises scanner, see [Learn about the dat Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -321,6 +340,9 @@ Accept wildcard characters: False ``` ### -AddPowerBIDlpLocation + +> Applicable: Security & Compliance + The AddPowerBIDlpLocation parameter specifies the Power BI workspace IDs to add to the list of included workspaces if you used the value All for the PowerBIDlpLocation parameter. Only workspaces hosted in Premium Gen2 capacities are permitted. You can find the workspace ID using one of the following procedures: @@ -335,7 +357,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddPowerBIDlpLocationException parameter specifies the Power BI workspace IDs to add to the list of excluded workspaces if you used the value All for the PowerBIDlpLocation parameter. Only workspaces hosted in Premium Gen2 capacities are permitted. You can find the workspace ID using one of the following procedures: @@ -359,7 +383,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites if you used 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. @@ -379,7 +405,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddSharePointLocationException parameter specifies the SharePoint sites to add to the list of excluded sites if you used 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. @@ -399,7 +427,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of included Teams chat and channel messages if you used 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: `"","",...""`. @@ -417,7 +447,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The AddTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of excluded Teams chat and channel messages if you used 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: `"","",...""`. @@ -435,7 +467,6 @@ 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 AddThirdPartyAppDlpLocation parameter specifies the non-Microsoft cloud apps to add to the list of included apps if you used the value All for the ThirdPartyAppDlpLocation parameter. @@ -457,7 +491,6 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -467,6 +500,9 @@ Accept wildcard characters: False ``` ### -AddThirdPartyAppDlpLocationException + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The AddThirdPartyAppDlpLocationException parameter specifies the non-Microsoft cloud apps to add to the list of excluded apps if you used the value All for the ThirdPartyAppDlpLocation parameter. @@ -479,7 +515,6 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -489,13 +524,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -505,6 +542,9 @@ 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`. @@ -514,7 +554,6 @@ 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 @@ -524,13 +563,15 @@ Accept wildcard characters: False ``` ### -EndpointDlpAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill EndpointDlpAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -540,13 +581,15 @@ Accept wildcard characters: False ``` ### -EndpointDlpAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill EndpointDlpAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -556,13 +599,15 @@ 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 @@ -572,6 +617,9 @@ 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 @("")`. @@ -585,7 +633,6 @@ Currently, supported values are: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -595,6 +642,9 @@ 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, one of the following statements must be true: @@ -610,7 +660,6 @@ You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMember Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -620,6 +669,9 @@ 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, one of the following statements must be true: @@ -637,7 +689,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -647,13 +698,15 @@ Accept wildcard characters: False ``` ### -ExchangeAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill ExchangeAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -663,13 +716,15 @@ Accept wildcard characters: False ``` ### -ExchangeAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill ExchangeAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -679,6 +734,9 @@ 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: `"","",...""`. @@ -696,7 +754,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -706,6 +763,9 @@ 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: `"","",...""`. @@ -723,7 +783,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -733,6 +792,9 @@ 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. @@ -741,7 +803,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -751,13 +812,15 @@ 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 @@ -767,6 +830,9 @@ 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`. @@ -794,7 +860,6 @@ After you create the `$loc` variable as shown in the previous examples, use the Type: String Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -804,6 +869,9 @@ 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. @@ -815,7 +883,6 @@ The Mode parameter specifies the action and notification level of the DLP policy Type: PolicyMode Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -825,13 +892,15 @@ Accept wildcard characters: False ``` ### -OneDriveAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill OneDriveAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -841,13 +910,15 @@ Accept wildcard characters: False ``` ### -OneDriveAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill OneDriveAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -857,6 +928,9 @@ 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, one of the following statements must be true: @@ -872,7 +946,6 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDri Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -882,6 +955,9 @@ 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, one of the following statements must be true: @@ -899,7 +975,6 @@ You can't use this parameter to specify Microsoft 365 Groups. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -909,6 +984,9 @@ 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. @@ -917,7 +995,6 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -927,6 +1004,9 @@ 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). @@ -935,7 +1015,6 @@ For more information about DLP policy templates, see [What the DLP policy templa Type: PswsHashtable Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -945,6 +1024,9 @@ Accept wildcard characters: False ``` ### -Priority + +> 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 for this parameter depend on the number of existing policies. For example, if there are 5 existing policies: @@ -959,7 +1041,6 @@ If you modify the priority value of a policy, the position of the policy in the Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -969,6 +1050,9 @@ Accept wildcard characters: False ``` ### -RemoveEndpointDlpLocation + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The RemoveEndpointDlpLocation parameter specifies the user accounts to remove from the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You specify the account by name or email address. @@ -981,7 +1065,6 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -991,6 +1074,9 @@ Accept wildcard characters: False ``` ### -RemoveEndpointDlpLocationException + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The RemoveEndpointDlpLocation parameter specifies the user accounts to remove from the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You specify the account by name or email address. @@ -1003,7 +1089,6 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1013,6 +1098,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter removes email messages from the DLP policy if they're already included. The valid value for this parameter is All. If the policy already includes email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is All), you can use `-RemoveExchangeLocation All` to prevent the policy from applying to email messages. @@ -1021,7 +1109,6 @@ If the policy already includes email messages (in the output of the Get-DlpCompl Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1031,6 +1118,9 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocation + +> Applicable: Security & Compliance + The RemoveOneDriveLocation parameter removes OneDrive sites from the DLP policy if they're already included. The valid value for this parameter is All. If the policy already includes OneDrive sites (in the output of the Get-DlpCompliancePolicy cmdlet, the OneDriveLocation property value is All), you can use `-RemoveOneDriveLocation All` to prevent the policy from applying to OneDrive sites. @@ -1041,7 +1131,6 @@ If the policy already includes OneDrive sites (in the output of the Get-DlpCompl Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1051,13 +1140,15 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocationException + +> Applicable: Security & Compliance + Don't use this parameter. See the RemoveOneDriveLocation parameter for an explanation. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1067,6 +1158,9 @@ Accept wildcard characters: False ``` ### -RemoveOnPremisesScannerDlpLocation + +> Applicable: Security & Compliance + The RemoveOnPremisesScannerDlpLocation parameter specifies the on-premises file shares and SharePoint document libraries and folders to remove from the list of included repositories if you used 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: `"","",...""`. @@ -1077,7 +1171,6 @@ For more information about the DLP on-premises scanner, see [Learn about the dat Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1087,6 +1180,9 @@ Accept wildcard characters: False ``` ### -RemoveOnPremisesScannerDlpLocationException + +> Applicable: Security & Compliance + The RemoveOnPremisesScannerDlpLocationException parameter specifies the on-premises file shares and SharePoint document libraries and folders to remove from the list of excluded repositories if you used 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: `"","",...""`. @@ -1097,7 +1193,6 @@ For more information about the DLP on-premises scanner, see [Learn about the dat Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1107,6 +1202,9 @@ Accept wildcard characters: False ``` ### -RemovePowerBIDlpLocation + +> Applicable: Security & Compliance + The RemovePowerBIDlpLocation parameter specifies the Power BI workspace IDs to remove from the list of included workspaces if you used the value All for the PowerBIDlpLocation parameter. Only workspaces hosted in Premium Gen2 capacities are permitted. You can find the workspace ID using one of the following procedures: @@ -1121,7 +1219,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemovePowerBIDlpLocationException parameter specifies the Power BI workspace IDs to remove the list of excluded workspaces if you used the value All for the PowerBIDlpLocation parameter. Only workspaces hosted in Premium Gen2 capacities are permitted. You can find the workspace ID using one of the following procedures: @@ -1145,7 +1245,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites if you used the value All for the SharePointLocation parameter. You specify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -1163,7 +1265,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveSharePointLocationException parameter specifies the SharePoint sites to remove from the list of excluded sites if you used the value All for the SharePointLocation parameter. You specify the site by its URL value. To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`. @@ -1181,7 +1285,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of included Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You specify 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: `"","",...""`. @@ -1199,7 +1305,6 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance + The RemoveTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of excluded Teams chat and channel messages if you used 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: `"","",...""`. @@ -1217,7 +1325,6 @@ 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 RemoveThirdPartyAppDlpLocation parameter specifies the non-Microsoft cloud apps to remove from the list of included apps if you used the value All for the ThirdPartyAppDlpLocation parameter. @@ -1239,7 +1349,6 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1249,6 +1358,9 @@ Accept wildcard characters: False ``` ### -RemoveThirdPartyAppDlpLocationException + +> Applicable: Security & Compliance + **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID. The RemoveThirdPartyAppDlpLocationException parameter specifies the non-Microsoft cloud apps tp remove from the list of excluded apps if you used the value All for the ThirdPartyAppDlpLocation parameter. @@ -1261,7 +1373,6 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1271,13 +1382,15 @@ Accept wildcard characters: False ``` ### -SharePointAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill SharePointAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1287,13 +1400,15 @@ Accept wildcard characters: False ``` ### -SharePointAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill SharePointAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1303,13 +1418,15 @@ Accept wildcard characters: False ``` ### -StartSimulation + +> Applicable: Security & Compliance + {{ Fill StartSimulation Description }} ```yaml Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1319,13 +1436,15 @@ Accept wildcard characters: False ``` ### -TeamsAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill TeamsAdaptiveScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1335,13 +1454,15 @@ Accept wildcard characters: False ``` ### -TeamsAdaptiveScopesException + +> Applicable: Security & Compliance + {{ Fill TeamsAdaptiveScopesException Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1351,13 +1472,15 @@ 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/exchange/Set-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-DlpComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md index 4a833c4d4b..b073615ba1 100644 --- a/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpcompliancerule applicable: Security & Compliance -title: Set-DlpComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpcompliancerule +schema: 2.0.0 +title: Set-DlpComplianceRule --- # Set-DlpComplianceRule @@ -259,6 +260,9 @@ This example uses the AdvancedRule parameter to read the following complex condi ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the DLP rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -270,7 +274,6 @@ The Identity parameter specifies the DLP rule that you want to modify. You can u Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -280,6 +283,9 @@ 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. @@ -290,7 +296,6 @@ 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 @@ -300,13 +305,15 @@ 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 @@ -316,6 +323,9 @@ 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"}`. @@ -327,7 +337,6 @@ 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 @@ -337,6 +346,9 @@ 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, but is read from a file that contains additional operators and combinations that aren't traditionally supported. @@ -347,7 +359,6 @@ For syntax details, see Example 2. Type: String Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -357,13 +368,15 @@ 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 @@ -373,6 +386,9 @@ 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"` @@ -387,7 +403,6 @@ 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 @@ -397,6 +412,9 @@ 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. @@ -407,7 +425,6 @@ 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 @@ -417,6 +434,9 @@ 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. @@ -425,7 +445,6 @@ Use the EnforcePortalAccess parameter to control whether external users are requ Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -435,6 +454,9 @@ 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. @@ -447,7 +469,6 @@ 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 @@ -457,13 +478,15 @@ 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 @@ -473,6 +496,9 @@ 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. @@ -482,7 +508,6 @@ 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 @@ -492,6 +517,9 @@ 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. @@ -502,7 +530,6 @@ 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 @@ -512,13 +539,15 @@ 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 @@ -528,6 +557,9 @@ 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`. @@ -539,7 +571,6 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Security & Compliance Required: False Position: Named @@ -549,6 +580,9 @@ 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`. @@ -557,7 +591,6 @@ 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 @@ -567,6 +600,9 @@ 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 types, 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 a sensitivity label: `@(@{operator = "And"; groups = @(@{operator="Or";name="Default";labels=@(@{name="Confidential";type="Sensitivity"})})})`. @@ -577,7 +613,6 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -587,13 +622,15 @@ 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 @@ -603,13 +640,15 @@ 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 @@ -619,13 +658,15 @@ Accept wildcard characters: False ``` ### -ContentIsNotLabeled + +> Applicable: Security & Compliance + {{ Fill ContentIsNotLabeled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -635,13 +676,15 @@ Accept wildcard characters: False ``` ### -ContentIsShared + +> Applicable: Security & Compliance + {{ Fill ContentIsShared Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -651,6 +694,9 @@ 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"`. @@ -659,7 +705,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -669,6 +714,9 @@ 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. @@ -678,7 +726,6 @@ 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 @@ -688,6 +735,9 @@ 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. @@ -698,7 +748,6 @@ 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 @@ -708,13 +757,15 @@ 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 @@ -724,13 +775,15 @@ Accept wildcard characters: False ``` ### -DocumentCreatedByMemberOf + +> Applicable: Security & Compliance + {{ Fill DocumentCreatedByMemberOf Description }} ```yaml Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -740,6 +793,9 @@ 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. @@ -749,7 +805,6 @@ The DocumentIsPasswordProtected parameter specifies a condition for the DLP rule Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -759,6 +814,9 @@ 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. @@ -768,7 +826,6 @@ The DocumentIsUnsupported parameter specifies a condition for the DLP rule that Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -778,6 +835,9 @@ 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"`. @@ -788,7 +848,6 @@ 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 @@ -798,6 +857,9 @@ 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. @@ -806,7 +868,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -816,6 +877,9 @@ 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"` @@ -828,7 +892,6 @@ 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 @@ -838,6 +901,9 @@ 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: @@ -856,7 +922,6 @@ 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 @@ -866,6 +931,9 @@ 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. @@ -874,7 +942,6 @@ 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 Default value: None @@ -883,6 +950,9 @@ 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. @@ -891,7 +961,6 @@ 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 @@ -901,13 +970,15 @@ 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 @@ -917,6 +988,9 @@ 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"=""},...)`. @@ -945,7 +1019,6 @@ 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 @@ -955,6 +1028,9 @@ 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. @@ -964,7 +1040,6 @@ The EnforcePortalAccess parameter specifies whether external recipients are requ Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -974,6 +1049,9 @@ 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). @@ -992,7 +1070,6 @@ This parameter works with the following conditions or exceptions only: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1002,6 +1079,9 @@ 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. @@ -1012,7 +1092,6 @@ 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 @@ -1022,6 +1101,9 @@ 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"` @@ -1036,7 +1118,6 @@ 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 @@ -1046,6 +1127,9 @@ 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. @@ -1056,7 +1140,6 @@ 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 @@ -1066,6 +1149,9 @@ 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. @@ -1076,7 +1162,6 @@ 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 @@ -1086,6 +1171,9 @@ 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 types, 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 a sensitivity label: `@(@{operator = "And"; groups = @(@{operator="Or";name="Default";labels=@(@{name="Confidential";type="Sensitivity"})})})`. @@ -1096,7 +1184,6 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1106,13 +1193,15 @@ 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 @@ -1122,13 +1211,15 @@ 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 @@ -1138,13 +1229,15 @@ Accept wildcard characters: False ``` ### -ExceptIfContentIsShared + +> Applicable: Security & Compliance + {{ Fill ExceptIfContentIsShared Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1154,6 +1247,9 @@ 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"`. @@ -1162,7 +1258,6 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1172,6 +1267,9 @@ 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. @@ -1182,7 +1280,6 @@ 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 @@ -1192,13 +1289,15 @@ 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 @@ -1208,13 +1307,15 @@ Accept wildcard characters: False ``` ### -ExceptIfDocumentCreatedByMemberOf + +> Applicable: Security & Compliance + {{ Fill ExceptIfDocumentCreatedByMemberOf Description }} ```yaml Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1224,6 +1325,9 @@ 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. @@ -1233,7 +1337,6 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1243,6 +1346,9 @@ 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. @@ -1252,7 +1358,6 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the DLP r Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1262,6 +1367,9 @@ 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"`. @@ -1272,7 +1380,6 @@ 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 @@ -1282,6 +1389,9 @@ 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. @@ -1290,7 +1400,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1300,6 +1409,9 @@ 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"` @@ -1312,7 +1424,6 @@ 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 @@ -1322,6 +1433,9 @@ 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: @@ -1340,7 +1454,6 @@ 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 @@ -1350,6 +1463,9 @@ 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. @@ -1358,7 +1474,6 @@ 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 @@ -1368,6 +1483,9 @@ 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"` @@ -1382,7 +1500,6 @@ 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,6 +1509,9 @@ 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. @@ -1402,7 +1522,6 @@ 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 @@ -1412,6 +1531,9 @@ 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"`. @@ -1420,7 +1542,6 @@ 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 @@ -1430,6 +1551,9 @@ 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, and the message was sent or received over an authenticated connection. @@ -1441,7 +1565,6 @@ 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 @@ -1451,6 +1574,9 @@ 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. @@ -1462,7 +1588,6 @@ 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 @@ -1472,6 +1597,9 @@ 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. @@ -1482,7 +1610,6 @@ 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 @@ -1492,6 +1619,9 @@ 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. @@ -1500,7 +1630,6 @@ 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 @@ -1510,6 +1639,9 @@ 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: @@ -1528,7 +1660,6 @@ 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 @@ -1538,6 +1669,9 @@ 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. @@ -1555,7 +1689,6 @@ 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 @@ -1565,6 +1698,9 @@ 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. @@ -1574,7 +1710,6 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the DLP Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1584,6 +1719,9 @@ 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 @@ -1624,7 +1762,6 @@ 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 @@ -1634,6 +1771,9 @@ 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 @@ -1674,7 +1814,6 @@ 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 @@ -1684,13 +1823,15 @@ 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 @@ -1700,6 +1841,9 @@ 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 @@ -1740,7 +1884,6 @@ 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 @@ -1750,6 +1893,9 @@ 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 @@ -1790,7 +1936,6 @@ 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 @@ -1800,6 +1945,9 @@ 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. @@ -1808,7 +1956,6 @@ 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 @@ -1818,6 +1965,9 @@ 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. @@ -1830,7 +1980,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1840,6 +1989,9 @@ 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. @@ -1848,7 +2000,6 @@ 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 @@ -1858,6 +2009,9 @@ 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. @@ -1866,7 +2020,6 @@ 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 @@ -1876,6 +2029,9 @@ 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"` @@ -1890,7 +2046,6 @@ 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 @@ -1900,6 +2055,9 @@ 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. @@ -1910,7 +2068,6 @@ 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 @@ -1920,6 +2077,9 @@ 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. @@ -1930,7 +2090,6 @@ 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 @@ -1940,6 +2099,9 @@ 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. @@ -1948,7 +2110,6 @@ 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 @@ -1958,6 +2119,9 @@ 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 are unscannable. 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. @@ -1966,7 +2130,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1976,6 +2139,9 @@ 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 @@ -1988,7 +2154,6 @@ 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 @@ -1998,13 +2163,15 @@ 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 @@ -2014,6 +2181,9 @@ 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. @@ -2022,7 +2192,6 @@ 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 @@ -2032,6 +2201,9 @@ 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"` @@ -2046,7 +2218,6 @@ 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 @@ -2056,6 +2227,9 @@ 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. @@ -2066,7 +2240,6 @@ 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 @@ -2076,6 +2249,9 @@ 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"`. @@ -2084,7 +2260,6 @@ 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 @@ -2094,6 +2269,9 @@ 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. @@ -2105,7 +2283,6 @@ 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 @@ -2115,6 +2292,9 @@ 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. @@ -2128,7 +2308,6 @@ 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 @@ -2138,6 +2317,9 @@ 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. @@ -2149,7 +2331,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2159,6 +2340,9 @@ 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. @@ -2170,7 +2354,6 @@ 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 @@ -2180,6 +2363,9 @@ 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. @@ -2190,7 +2376,6 @@ 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 @@ -2200,6 +2385,9 @@ 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. @@ -2208,7 +2396,6 @@ 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 @@ -2218,6 +2405,9 @@ 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 @@ -2246,7 +2436,6 @@ 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 @@ -2256,13 +2445,15 @@ 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 @@ -2272,6 +2463,9 @@ 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: @@ -2290,7 +2484,6 @@ 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 @@ -2300,6 +2493,9 @@ 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. @@ -2317,7 +2513,6 @@ You can use this condition 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 @@ -2327,13 +2522,15 @@ 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 @@ -2343,6 +2540,9 @@ 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. @@ -2351,7 +2551,6 @@ 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 @@ -2361,6 +2560,9 @@ 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: @@ -2375,7 +2577,6 @@ The maximum individual regular expression length is 128 characters. The maximum Type: PswsHashtable Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2385,6 +2586,9 @@ 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. @@ -2397,7 +2601,6 @@ 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 @@ -2407,6 +2610,9 @@ 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. @@ -2420,7 +2626,6 @@ You can specify multiple values separated by commas. The values WithoutJustifica Type: OverrideOption[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2430,13 +2635,15 @@ 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 @@ -2446,13 +2653,15 @@ 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 @@ -2462,6 +2671,9 @@ 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): @@ -2475,7 +2687,6 @@ This parameter has a 5000 character limit, and supports plain text, HTML tags an Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2485,13 +2696,15 @@ 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 @@ -2501,13 +2714,15 @@ 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 @@ -2517,6 +2732,9 @@ 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 }} @@ -2527,7 +2745,6 @@ 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 @@ -2537,13 +2754,15 @@ 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 @@ -2553,13 +2772,15 @@ 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 @@ -2569,13 +2790,15 @@ 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 @@ -2585,6 +2808,9 @@ 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). @@ -2595,7 +2821,6 @@ To enter multiple values and overwrite any existing entries, use the following s Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2605,6 +2830,9 @@ 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. @@ -2614,7 +2842,6 @@ 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 @@ -2624,13 +2851,15 @@ 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 @@ -2640,6 +2869,9 @@ 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. @@ -2653,7 +2885,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2663,6 +2894,9 @@ 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 @@ -2674,7 +2908,6 @@ 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 @@ -2684,13 +2917,15 @@ 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 @@ -2700,6 +2935,9 @@ 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 the 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. @@ -2710,7 +2948,6 @@ 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 @@ -2720,6 +2957,9 @@ 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: @@ -2734,7 +2974,6 @@ 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 @@ -2744,6 +2983,9 @@ 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. @@ -2753,7 +2995,6 @@ The ProcessingLimitExceeded parameter specifies a condition for the DLP rule tha Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2763,6 +3004,9 @@ 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: @@ -2774,7 +3018,6 @@ The Quarantine parameter specifies an action that quarantines messages. Valid va Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2784,6 +3027,9 @@ 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 @@ -2824,7 +3070,6 @@ 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 @@ -2834,6 +3079,9 @@ 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 @@ -2874,7 +3122,6 @@ 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 @@ -2884,6 +3131,9 @@ 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. @@ -2892,7 +3142,6 @@ 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 Default value: None @@ -2901,13 +3150,15 @@ 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 @@ -2917,6 +3168,9 @@ 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. @@ -2925,7 +3179,6 @@ 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 @@ -2935,6 +3188,9 @@ 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 contain spaces or colons ( : ). The maximum header value length is 128 characters. @@ -2945,7 +3201,6 @@ 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 @@ -2955,6 +3210,9 @@ 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. @@ -2966,7 +3224,6 @@ 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 @@ -2976,6 +3233,9 @@ 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. @@ -2987,7 +3247,6 @@ The ReportSeverityLevel parameter specifies the severity level of the incident r Type: RuleSeverity Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -2997,13 +3256,15 @@ 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 @@ -3013,13 +3274,15 @@ 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 @@ -3029,6 +3292,9 @@ 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: Ignore the failure of the rule and thereby any actions in that rule and move to the next rule. @@ -3039,7 +3305,6 @@ 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 @@ -3049,6 +3314,9 @@ 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 @@ -3089,7 +3357,6 @@ 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 @@ -3099,6 +3366,9 @@ 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 @@ -3139,7 +3409,6 @@ 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 @@ -3149,6 +3418,9 @@ 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. @@ -3167,7 +3439,6 @@ 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 @@ -3177,6 +3448,9 @@ 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. @@ -3185,7 +3459,6 @@ 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 @@ -3195,6 +3468,9 @@ 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. @@ -3207,7 +3483,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3217,6 +3492,9 @@ 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. @@ -3225,7 +3503,6 @@ 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 @@ -3235,6 +3512,9 @@ 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. @@ -3243,7 +3523,6 @@ 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 @@ -3253,6 +3532,9 @@ 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. @@ -3263,7 +3545,6 @@ 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 @@ -3273,6 +3554,9 @@ 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) @@ -3285,7 +3569,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: All Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3295,6 +3578,9 @@ 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. @@ -3304,7 +3590,6 @@ The StopPolicyProcessing parameter specifies an action that stops processing mor Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3314,6 +3599,9 @@ 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"` @@ -3328,7 +3616,6 @@ 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 @@ -3338,6 +3625,9 @@ 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. @@ -3348,7 +3638,6 @@ 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 @@ -3358,6 +3647,9 @@ 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. @@ -3368,7 +3660,6 @@ 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 @@ -3378,6 +3669,9 @@ 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. @@ -3386,7 +3680,6 @@ 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 @@ -3396,13 +3689,15 @@ 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 @@ -3412,13 +3707,15 @@ 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 @@ -3428,6 +3725,9 @@ 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 are unscannable. 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. @@ -3436,7 +3736,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -3446,13 +3745,15 @@ 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 @@ -3462,6 +3763,9 @@ 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 @@ -3474,7 +3778,6 @@ 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/exchange/Set-DlpEdmSchema.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DlpEdmSchema.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md index be8d02a43c..ff08d1f09f 100644 --- a/exchange/exchange-ps/exchange/Set-DlpEdmSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpedmschema applicable: Security & Compliance -title: Set-DlpEdmSchema -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpedmschema +schema: 2.0.0 +title: Set-DlpEdmSchema --- # Set-DlpEdmSchema @@ -44,6 +45,9 @@ This example modifies a DLP EDM schema using the edm.xml file in the C:\\My Docu ## 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`). @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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/exchange/Set-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md index aa9f4a5616..f6c00c3061 100644 --- a/exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpkeyworddictionary applicable: Security & Compliance -title: Set-DlpKeywordDictionary -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpkeyworddictionary +schema: 2.0.0 +title: Set-DlpKeywordDictionary --- # Set-DlpKeywordDictionary @@ -107,13 +108,15 @@ After you use Notepad to modify the terms and save the file, the last four comma ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the name of the DLP keyword dictionary that you want to modify. If the value contains spaces, enclose the value in quotation marks. ```yaml Type: SensitiveInformationTypeIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -123,6 +126,9 @@ 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`. @@ -132,7 +138,6 @@ 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 @@ -142,13 +147,15 @@ 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 @@ -158,13 +165,15 @@ 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 @@ -174,6 +183,9 @@ 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. The maximum file size is up to 1 MB of terms after compression. The organization limit for all dictionaries is also 1 MB after compression. @@ -182,7 +194,6 @@ The maximum file size is up to 1 MB of terms after compression. The organization Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -192,13 +203,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -208,13 +221,15 @@ 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/exchange/Set-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-DlpPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md index 74002da4a2..2c22ce748c 100644 --- a/exchange/exchange-ps/exchange/Set-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlppolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-DlpPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlppolicy +schema: 2.0.0 +title: Set-DlpPolicy --- # Set-DlpPolicy @@ -49,6 +50,9 @@ This example disables the DLP policy named Employee Numbers. ## 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 modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -59,7 +63,6 @@ The Identity parameter specifies the DLP policy that you want to modify. You can Type: DlpPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ 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 @@ -120,6 +129,9 @@ 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: When a message matches the conditions specified by the DLP policy, the actions specified by the policy aren't enforced and no notification emails are sent. @@ -132,7 +144,6 @@ If the State parameter is set to Disabled, the value of the Mode parameter is ir Type: RuleMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -142,13 +153,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a unique 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: Named @@ -158,13 +171,15 @@ 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. ```yaml Type: RuleState Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -174,13 +189,15 @@ 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/exchange/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md index e6a09ab1b6..caed393985 100644 --- a/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpsensitiveinformationtype applicable: Security & Compliance -title: Set-DlpSensitiveInformationType -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpsensitiveinformationtype +schema: 2.0.0 +title: Set-DlpSensitiveInformationType --- # Set-DlpSensitiveInformationType @@ -93,6 +94,9 @@ The first three commands return the list of document fingerprints in the sensiti ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the sensitive information type rule that you want to modify. You can use any value that uniquely identifies the sensitive information type rule. For example: - Name @@ -103,7 +107,6 @@ The Identity parameter specifies the sensitive information type rule that you wa Type: SensitiveInformationTypeIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -113,6 +116,9 @@ 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`. @@ -124,7 +130,6 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Security & Compliance Required: False Position: Named @@ -134,13 +139,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Security & Compliance + The Description parameter specifies a description for the sensitive information type rule. You use the Description parameter with the Locale and Name parameters to specify descriptions for the sensitive information type rule in different languages. The localized values of Description appear in the AllLocalizedDescriptions property of the sensitive information type rule. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -150,13 +157,15 @@ 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 @@ -166,13 +175,15 @@ Accept wildcard characters: False ``` ### -Fingerprints + +> Applicable: Security & Compliance + The Fingerprints parameter specifies the byte-encoded document files that are used as fingerprints by the sensitive information type rule. For instructions on how to import documents to use as templates for fingerprints, see [New-DlpFingerprint](https://learn.microsoft.com/powershell/module/exchange/new-dlpfingerprint) or the Examples section. For instructions on how to add and remove document fingerprints from an existing sensitive information type rule, see the Examples section. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -182,13 +193,15 @@ 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 @@ -198,6 +211,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Security & Compliance + The Locale parameter adds or removes languages that are 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). @@ -208,7 +224,6 @@ Typically, you use the Locale parameter with the Name and Description parameters Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -218,6 +233,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Security & Compliance + The Name parameter specifies a name for the sensitive information type rule. The value must be less than 256 characters. You use the Name parameter with the Locale and Description parameters to specify names for the sensitive information type rule in different languages. The localized values of Name appear in the AllLocalizedNames property of the sensitive information type rule. @@ -228,7 +246,6 @@ The value of the Name parameter is used in the Policy Tip that's presented to us Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -238,13 +255,15 @@ Accept wildcard characters: False ``` ### -Threshold + +> Applicable: Security & Compliance + {{ Fill Threshold Description }} ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -254,13 +273,15 @@ 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 @@ -270,13 +291,15 @@ 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/exchange/Set-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md index 944203816e..f48463d803 100644 --- a/exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpsensitiveinformationtyperulepackage applicable: Security & Compliance -title: Set-DlpSensitiveInformationTypeRulePackage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dlpsensitiveinformationtyperulepackage +schema: 2.0.0 +title: Set-DlpSensitiveInformationTypeRulePackage --- # Set-DlpSensitiveInformationTypeRulePackage @@ -44,6 +45,9 @@ 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`). @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ 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`. @@ -73,7 +79,6 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Security & Compliance Required: False Position: Named @@ -83,13 +88,15 @@ 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/exchange/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md index 4b26f36939..dbd51f1ea0 100644 --- a/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-dynamicdistributiongroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-DynamicDistributionGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-dynamicdistributiongroup +schema: 2.0.0 +title: Set-DynamicDistributionGroup --- # Set-DynamicDistributionGroup @@ -151,6 +152,9 @@ This example applies the following changes to the existing dynamic distribution ## 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 modify. You can use any value that uniquely identifies the dynamic distribution group. For example: - Name @@ -164,7 +168,6 @@ The Identity parameter specifies the dynamic distribution group that you want to Type: DynamicGroupIdParameter 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 @@ -174,6 +177,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -197,7 +203,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -207,6 +212,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -230,7 +238,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -240,6 +247,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -265,7 +275,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -275,6 +284,9 @@ 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: @@ -299,7 +311,6 @@ 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 @@ -309,6 +320,9 @@ 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: @@ -328,7 +342,6 @@ 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 @@ -338,6 +351,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -359,7 +375,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -369,6 +384,9 @@ 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. 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. @@ -381,7 +399,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -391,6 +408,9 @@ 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. @@ -403,7 +423,6 @@ To add or remove one or more values without affecting any existing entries, use 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,6 +432,9 @@ 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. @@ -425,7 +447,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -435,6 +456,9 @@ 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. @@ -447,7 +471,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -457,6 +480,9 @@ 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. @@ -469,7 +495,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -479,6 +504,9 @@ 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. @@ -491,7 +519,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -501,6 +528,9 @@ 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. @@ -513,7 +543,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -523,6 +552,9 @@ 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. @@ -535,7 +567,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -545,6 +576,9 @@ 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. @@ -557,7 +591,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -567,6 +600,9 @@ 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. @@ -579,7 +615,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -589,6 +624,9 @@ 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. @@ -601,7 +639,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -611,6 +648,9 @@ 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. @@ -623,7 +663,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -633,6 +672,9 @@ 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. @@ -645,7 +687,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -655,6 +696,9 @@ 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. @@ -667,7 +711,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -677,6 +720,9 @@ 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. @@ -689,7 +735,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -699,6 +744,9 @@ 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. @@ -711,7 +759,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -721,6 +768,9 @@ 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. @@ -733,7 +783,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -743,6 +792,9 @@ 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. @@ -755,7 +807,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -765,6 +816,9 @@ 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`. @@ -774,7 +828,6 @@ 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 @@ -784,6 +837,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -795,7 +851,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -805,13 +860,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -821,13 +878,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -837,13 +896,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -853,13 +914,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -869,13 +932,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -885,13 +950,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -901,13 +968,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -917,13 +986,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -933,13 +1004,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -949,13 +1022,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -965,13 +1040,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -981,13 +1058,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -997,13 +1076,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1013,13 +1094,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1029,13 +1112,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1045,6 +1130,9 @@ 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. @@ -1053,7 +1141,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1063,13 +1150,15 @@ 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 ("). ```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 @@ -1079,6 +1168,9 @@ 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. @@ -1087,7 +1179,6 @@ 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 @@ -1097,6 +1188,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -1124,7 +1218,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection 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 @@ -1134,6 +1227,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: @@ -1145,7 +1241,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1155,6 +1250,9 @@ Accept wildcard characters: False ``` ### -ExpansionServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExpansionServer parameter specifies the Exchange server that's used to expand the distribution group. The default value is blank ($null), which means expansion happens on the closest available Exchange server. If you specify an expansion server, and that server is unavailable, any messages that are sent to the distribution group can't be delivered. @@ -1170,7 +1268,6 @@ When you specify an expansion server, use the ExchangeLegacyDN. You can find thi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1180,6 +1277,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1192,7 +1292,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -1202,6 +1301,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1214,7 +1316,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -1224,6 +1325,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1236,7 +1340,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -1246,6 +1349,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1258,7 +1364,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -1268,6 +1373,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1280,7 +1388,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -1290,6 +1397,9 @@ Accept wildcard characters: False ``` ### -ForceMembershipRefresh + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill ForceMembershipRefresh Description }} @@ -1298,7 +1408,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1308,13 +1417,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 @@ -1324,6 +1435,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this dynamic distribution group. Although messages send on behalf of the group clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the group, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -1349,7 +1463,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -1359,6 +1472,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -1368,7 +1484,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -1378,6 +1493,9 @@ 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. @@ -1391,7 +1509,6 @@ 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 @@ -1401,6 +1518,9 @@ 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. @@ -1416,7 +1536,6 @@ You can specify multiple values separated by commas. When you use multiple value Type: WellKnownRecipientType 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 @@ -1426,6 +1545,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -1437,7 +1559,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -1447,6 +1568,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -1461,7 +1585,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -1471,6 +1594,9 @@ 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 dynamic group can only have one owner. The group owner is able to: - Modify the properties of the group @@ -1494,7 +1620,6 @@ The owner you specify for this parameter must be a mailbox, mail user or mail-en 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 @@ -1504,6 +1629,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxReceiveSize parameter specifies the maximum allowed email message size that can be sent to this group. @@ -1525,7 +1653,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1535,6 +1662,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxSendSize parameter specifies the maximum allowed email message size that can be sent from this group. @@ -1556,7 +1686,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1566,6 +1695,9 @@ 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 @@ -1585,7 +1717,6 @@ You need to use this parameter to specify at least one moderator when you set th 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 @@ -1595,6 +1726,9 @@ 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. @@ -1606,7 +1740,6 @@ 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 @@ -1616,13 +1749,15 @@ Accept wildcard characters: False ``` ### -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 ("). ```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 @@ -1632,13 +1767,15 @@ 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 @@ -1648,13 +1785,15 @@ Accept wildcard characters: False ``` ### -PhoneticDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1664,6 +1803,9 @@ 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. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but the email addresses of the group are no longer automatically updated by email address policies. @@ -1674,7 +1816,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm 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 @@ -1684,6 +1825,9 @@ 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 @@ -1699,7 +1843,6 @@ 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 @@ -1709,6 +1852,9 @@ 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. @@ -1724,7 +1870,6 @@ 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 @@ -1734,6 +1879,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1757,7 +1905,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1767,6 +1914,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1790,7 +1940,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1800,6 +1949,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1825,7 +1977,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1835,6 +1986,9 @@ Accept wildcard characters: False ``` ### -ReportToManagerEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owners of the group (defined by the ManagedBy property). Valid values are: - $true: Delivery status notifications are sent to the owners of the group. @@ -1846,7 +2000,6 @@ The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the r 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 @@ -1856,6 +2009,9 @@ Accept wildcard characters: False ``` ### -ReportToOriginatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are: - $true: Delivery status notifications are sent to the message senders. This is the default value. @@ -1867,7 +2023,6 @@ The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the r 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 @@ -1877,6 +2032,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, 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. @@ -1886,7 +2044,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -1896,6 +2053,9 @@ 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. @@ -1908,7 +2068,6 @@ 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 @@ -1918,6 +2077,9 @@ Accept wildcard characters: False ``` ### -SendOofMessageToOriginatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are: - $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender. This is the default value. @@ -1927,7 +2089,6 @@ The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of o 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 @@ -1937,6 +2098,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -1949,7 +2113,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -1959,6 +2122,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -1979,7 +2145,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1989,6 +2154,9 @@ Accept wildcard characters: False ``` ### -UpdateMemberCount + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill UpdateMemberCount Description }} @@ -1997,7 +2165,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2007,13 +2174,15 @@ 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 @@ -2023,6 +2192,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -2034,7 +2206,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md index 0f0aa7ab42..2d3dd41aa6 100644 --- a/exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-eopprotectionpolicyrule applicable: Exchange Online, Exchange Online Protection -title: Set-EOPProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-eopprotectionpolicyrule +schema: 2.0.0 +title: Set-EOPProtectionPolicyRule --- # Set-EOPProtectionPolicyRule @@ -63,6 +64,9 @@ This example removes all conditions and exceptions from the Standard preset secu ## 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 @@ -75,7 +79,6 @@ 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 @@ -85,13 +88,15 @@ 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 @@ -101,6 +106,9 @@ 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. @@ -110,7 +118,6 @@ 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 @@ -120,13 +127,15 @@ 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 @@ -136,6 +145,9 @@ 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 @@ -151,7 +163,6 @@ 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 @@ -161,6 +172,9 @@ 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 @@ -178,7 +192,6 @@ 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 @@ -188,6 +201,9 @@ Accept wildcard characters: False ``` ### -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. We highly recommend that you use the default rule names for clarity and consistency. @@ -196,7 +212,6 @@ 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: False Position: Named @@ -206,6 +221,9 @@ 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. @@ -216,7 +234,6 @@ You must use the default value for the rule. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -226,13 +243,15 @@ 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 @@ -242,6 +261,9 @@ 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 @@ -257,7 +279,6 @@ 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 @@ -267,6 +288,9 @@ 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 @@ -284,7 +308,6 @@ 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 @@ -294,13 +317,15 @@ 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/exchange/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md index df1c651b18..dac8a03da1 100644 --- a/exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ecpvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-EcpVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ecpvirtualdirectory +schema: 2.0.0 +title: Set-EcpVirtualDirectory --- # Set-EcpVirtualDirectory @@ -67,6 +68,9 @@ This example turns off the Internet access to the EAC on server named Server01. ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -81,7 +85,6 @@ To manage the first ECP virtual directory created in an Exchange organization, y Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -91,6 +94,9 @@ Accept wildcard characters: False ``` ### -AdfsAuthentication + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdfsAuthentication parameter specifies that the ECP virtual directory allows users to authenticate through Active Directory Federation Services (AD FS) authentication. This parameter accepts $true or $false. The default value is $false. The ADFS authentication settings for Set-OwaVirtualDirectory and Set-EcpVirtualDirectory are related. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $true before you can set the AdfsAuthentication parameter on Set-OwaVirtualDirectory to $true. Likewise, you need to set the AdfsAuthentication parameter on Set-OwaVirtualDirectory to $false before you can set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false. @@ -99,7 +105,6 @@ The ADFS authentication settings for Set-OwaVirtualDirectory and Set-EcpVirtualD Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -109,13 +114,15 @@ Accept wildcard characters: False ``` ### -AdminEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdminEnabled parameter specifies that the EAC isn't able to be accessed through the Internet. For more information, see [Turn off access to the Exchange admin center](https://learn.microsoft.com/Exchange/architecture/client-access/disable-exchange-admin-center-access). This parameter accepts $true or $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -125,6 +132,9 @@ 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. @@ -136,7 +146,6 @@ This parameter can be used with the FormsAuthentication parameter or with the Di Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,6 +155,9 @@ 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`. @@ -155,7 +167,6 @@ 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 @@ -165,6 +176,9 @@ 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. @@ -174,7 +188,6 @@ 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 @@ -184,13 +197,15 @@ 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 @@ -200,6 +215,9 @@ 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. @@ -212,7 +230,6 @@ 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 @@ -222,6 +239,9 @@ 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. @@ -231,7 +251,6 @@ 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 @@ -241,6 +260,9 @@ 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. @@ -253,7 +275,6 @@ 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 @@ -263,13 +284,15 @@ Accept wildcard characters: False ``` ### -ExternalAuthenticationMethods + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalAuthenticationMethods parameter specifies the authentication methods supported on the Exchange server from outside the firewall. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -279,6 +302,9 @@ 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 also 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. @@ -287,7 +313,6 @@ This setting is also important when Secure Sockets Layer (SSL) is used. You need Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,6 +322,9 @@ Accept wildcard characters: False ``` ### -FormsAuthentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FormsAuthentication parameter specifies whether forms-based authentication is enabled on the ECP virtual directory. Valid values are: - $true: Forms authentication is enabled. The BasicAuthentication parameter is set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. @@ -306,7 +334,6 @@ The FormsAuthentication parameter specifies whether forms-based authentication i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -316,13 +343,15 @@ Accept wildcard characters: False ``` ### -GzipLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GzipLevel parameter sets Gzip configuration information for the ECP virtual directory. ```yaml Type: GzipLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -332,6 +361,9 @@ 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 also 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. @@ -340,7 +372,6 @@ This setting is also important when SSL is used. You need to set this parameter Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -350,13 +381,15 @@ Accept wildcard characters: False ``` ### -OAuthAuthentication + +> Applicable: Exchange Server 2019 + {{ Fill OAuthAuthentication Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -366,13 +399,15 @@ Accept wildcard characters: False ``` ### -OwaOptionsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You may want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -382,13 +417,15 @@ 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 @@ -398,6 +435,9 @@ 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. @@ -407,7 +447,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md index e63e09bc66..7e21e0e163 100644 --- a/exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-edgesyncserviceconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-EdgeSyncServiceConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-edgesyncserviceconfig +schema: 2.0.0 +title: Set-EdgeSyncServiceConfig --- # Set-EdgeSyncServiceConfig @@ -65,13 +66,15 @@ The log files are kept for 3 days. ## 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 you want to configure. ```yaml Type: EdgeSyncServiceConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,6 +84,9 @@ Accept wildcard characters: False ``` ### -ConfigurationSyncInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConfigurationSyncInterval parameter specifies how frequently the Microsoft Exchange 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. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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`. @@ -108,7 +116,6 @@ 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 @@ -118,6 +125,9 @@ 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. @@ -126,7 +136,6 @@ 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 @@ -136,13 +145,15 @@ 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 @@ -152,6 +163,9 @@ 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. @@ -160,7 +174,6 @@ 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 @@ -170,6 +183,9 @@ 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 Microsoft Exchange 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. @@ -178,7 +194,6 @@ 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 @@ -188,6 +203,9 @@ 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. @@ -196,7 +214,6 @@ 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 @@ -206,13 +223,15 @@ Accept wildcard characters: False ``` ### -LogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogEnabled parameter specifies enables or disables the EdgeSyncLog. 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 @@ -222,6 +241,9 @@ 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,7 +255,6 @@ 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 @@ -243,6 +264,9 @@ 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. @@ -251,7 +275,6 @@ 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 @@ -261,6 +284,9 @@ Accept wildcard characters: False ``` ### -LogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogMaxDirectorySize 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: @@ -279,7 +305,6 @@ 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 @@ -289,6 +314,9 @@ 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: @@ -307,7 +335,6 @@ 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 @@ -317,13 +344,15 @@ Accept wildcard characters: False ``` ### -LogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogPath parameter specifies the disk location to store 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 @@ -333,13 +362,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a unique name for the EdgeSync service configuration. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -349,6 +380,9 @@ 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 Microsoft Exchange EdgeSync service can maintain an optional lock on the 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. @@ -357,7 +391,6 @@ 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 @@ -367,6 +400,9 @@ 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 Microsoft Exchange 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. @@ -375,7 +411,6 @@ 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 @@ -385,13 +420,15 @@ 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/exchange/Set-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md index 3d157d6042..2f356b19ab 100644 --- a/exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-emailaddresspolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-EmailAddressPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-emailaddresspolicy +schema: 2.0.0 +title: Set-EmailAddressPolicy --- # Set-EmailAddressPolicy @@ -96,6 +97,9 @@ In Exchange Online, this example modifies the existing email address policy name ## 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 modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -106,7 +110,6 @@ The Identity parameter specifies the email address policy that you want to modif 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: True Position: 1 @@ -116,6 +119,9 @@ 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. @@ -130,7 +136,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -140,6 +145,9 @@ 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. @@ -154,7 +162,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -164,6 +171,9 @@ 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. @@ -178,7 +188,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,6 +197,9 @@ 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. @@ -202,7 +214,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -212,6 +223,9 @@ 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. @@ -226,7 +240,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,6 +249,9 @@ 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. @@ -250,7 +266,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,6 +275,9 @@ 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. @@ -274,7 +292,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -284,6 +301,9 @@ 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. @@ -298,7 +318,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -308,6 +327,9 @@ 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. @@ -322,7 +344,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -332,6 +353,9 @@ 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. @@ -346,7 +370,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,6 +379,9 @@ 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. @@ -370,7 +396,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -380,6 +405,9 @@ 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. @@ -394,7 +422,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -404,6 +431,9 @@ 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. @@ -418,7 +448,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -428,6 +457,9 @@ 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. @@ -442,7 +474,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -452,6 +483,9 @@ 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. @@ -466,7 +500,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -476,6 +509,9 @@ 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. @@ -490,7 +526,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -500,6 +535,9 @@ 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. @@ -514,7 +552,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -524,6 +561,9 @@ 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. @@ -538,7 +578,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -548,6 +587,9 @@ 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`. @@ -557,7 +599,6 @@ 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 @@ -567,6 +608,9 @@ 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. @@ -584,7 +628,6 @@ Typically, this property is only populated by values after a migration from a pr Type: ProxyAddressTemplateCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -594,6 +637,9 @@ 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. @@ -602,7 +648,6 @@ 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 @@ -612,6 +657,9 @@ Accept wildcard characters: False ``` ### -EnabledEmailAddressTemplates + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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`: @@ -631,7 +679,6 @@ In Exchange Online PowerShell, if you use this parameter with the IncludeUnified Type: ProxyAddressTemplateCollection 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 @@ -641,6 +688,9 @@ Accept wildcard characters: False ``` ### -EnabledPrimarySMTPAddressTemplate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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`. @@ -653,7 +703,6 @@ In Exchange Online PowerShell, if you use this parameter with the IncludeUnified 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 @@ -663,13 +712,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 @@ -679,6 +730,9 @@ 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: @@ -696,7 +750,6 @@ You can specify multiple values separated by commas. When you use multiple value Type: WellKnownRecipientType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -706,13 +759,15 @@ Accept wildcard characters: False ``` ### -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 for 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, Exchange Online Protection Required: False Position: Named @@ -722,6 +777,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -732,7 +790,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -742,6 +799,9 @@ 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: @@ -757,7 +817,6 @@ 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 @@ -767,6 +826,9 @@ 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'"`. @@ -783,7 +845,6 @@ 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 @@ -793,13 +854,15 @@ 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/exchange/Set-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-EmailTenantSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md index 795f69bb1f..ec5127cbf2 100644 --- a/exchange/exchange-ps/exchange/Set-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-emailtenantsettings applicable: Exchange Online -title: Set-EmailTenantSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-emailtenantsettings +schema: 2.0.0 +title: Set-EmailTenantSettings --- # Set-EmailTenantSettings @@ -45,13 +46,15 @@ This example enables priority account protection in the organization. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the settings object that you want to modify. The only settings object in the organization is named Default. ```yaml Type: EmailTenantSettingsIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: 0 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,13 +85,15 @@ 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 @@ -96,6 +103,9 @@ Accept wildcard characters: False ``` ### -EnablePriorityAccountProtection + +> Applicable: Exchange Online + The EnablePriorityAccountProtection parameter enables or disable priority account protection in the organization. Valid values are: - $true: Priority account protection is enabled. @@ -105,7 +115,6 @@ The EnablePriorityAccountProtection parameter enables or disable priority accoun Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -115,13 +124,15 @@ Accept wildcard characters: False ``` ### -IgnoreDehydratedFlag + +> 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 @@ -131,13 +142,15 @@ 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/exchange/Set-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-EventLogLevel.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md index 4b819c2bb3..a2a673d2e0 100644 --- a/exchange/exchange-ps/exchange/Set-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-eventloglevel applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-EventLogLevel -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-eventloglevel +schema: 2.0.0 +title: Set-EventLogLevel --- # Set-EventLogLevel @@ -44,13 +45,15 @@ This example sets the event log level to High for the MSExchangeTransport\\SmtpR ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the event logging category for which you want to set the event logging level. ```yaml Type: ECIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -60,6 +63,9 @@ Accept wildcard characters: False ``` ### -Level + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Level parameter specifies the log level for the specific event logging category. The valid values are: - Lowest @@ -72,7 +78,6 @@ The Level parameter specifies the log level for the specific event logging categ Type: ECIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,13 +108,15 @@ 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/exchange/Set-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md index 77225894de..82e36e2b06 100644 --- a/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-eventsfromemailconfiguration applicable: Exchange Online -title: Set-EventsFromEmailConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-eventsfromemailconfiguration +schema: 2.0.0 +title: Set-EventsFromEmailConfiguration --- # Set-EventsFromEmailConfiguration @@ -71,13 +72,15 @@ This example resets Events from Email settings for the user. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the mailbox that you want to modify. You identify the mailbox by email address. ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -87,6 +90,9 @@ Accept wildcard characters: False ``` ### -CreateEventsFromEmailAsPrivate + +> Applicable: Exchange Online + The CreateEventsFromEmailAsPrivate parameter specifies whether to create the events discovered from messages as normal or private events. Valid values are: - $true: The events are crated as private events. This is the default value. @@ -96,7 +102,6 @@ The CreateEventsFromEmailAsPrivate parameter specifies whether to create the eve Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -106,13 +111,15 @@ Accept wildcard characters: False ``` ### -EventReservationProcessingLevel + +> Applicable: Exchange Online + This parameter has been deprecated and is no longer used. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -122,6 +129,9 @@ Accept wildcard characters: False ``` ### -FlightReservationProcessingLevel + +> Applicable: Exchange Online + The FlightReservationProcessingLevel parameter specifies whether flight reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are: - Disabled: Do not discover flight reservations from messages. @@ -134,7 +144,6 @@ Note that these values are case sensitive. Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -144,13 +153,15 @@ Accept wildcard characters: False ``` ### -FoodEstablishmentReservationProcessingLevel + +> Applicable: Exchange Online + This parameter has been deprecated and is no longer used. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -160,13 +171,15 @@ Accept wildcard characters: False ``` ### -InvoiceProcessingLevel + +> Applicable: Exchange Online + This parameter has been deprecated and is no longer used. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -176,6 +189,9 @@ Accept wildcard characters: False ``` ### -LodgingReservationProcessingLevel + +> Applicable: Exchange Online + The LodgingReservationProcessingLevel parameter specifies whether lodging reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are: - Disabled: Do not discover lodging reservations from messages. @@ -186,7 +202,6 @@ The LodgingReservationProcessingLevel parameter specifies whether lodging reserv Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -196,6 +211,9 @@ Accept wildcard characters: False ``` ### -ParcelDeliveryProcessingLevel + +> Applicable: Exchange Online + The ParcelDeliveryProcessingLevel parameter specifies whether parcel deliveries are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are: - Disabled: Do not discover parcel deliveries from messages. @@ -206,7 +224,6 @@ The ParcelDeliveryProcessingLevel parameter specifies whether parcel deliveries Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,6 +233,9 @@ Accept wildcard characters: False ``` ### -RentalCarReservationProcessingLevel + +> Applicable: Exchange Online + The RentalCarReservationProcessingLevel parameter specifies whether rental car reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are: - Disabled: Do not discover rental car reservations from messages. @@ -226,7 +246,6 @@ The RentalCarReservationProcessingLevel parameter specifies whether rental car r Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -236,13 +255,15 @@ Accept wildcard characters: False ``` ### -ResetSettings + +> Applicable: Exchange Online + The ResetSettings switch specifies whether to return all of the reservation discovery settings to their default values. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ResetSettings Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -252,13 +273,15 @@ Accept wildcard characters: False ``` ### -ServiceReservationProcessingLevel + +> Applicable: Exchange Online + This parameter has been deprecated and is no longer used. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md similarity index 82% rename from exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md index 69e2cfccc7..0ac25be6d4 100644 --- a/exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangeassistanceconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ExchangeAssistanceConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangeassistanceconfig +schema: 2.0.0 +title: Set-ExchangeAssistanceConfig --- # Set-ExchangeAssistanceConfig @@ -60,13 +61,15 @@ This example changes the Help location for the Exchange admin center. ## 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 @@ -76,13 +79,15 @@ Accept wildcard characters: False ``` ### -CommunityLinkDisplayEnabled + +> 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 @@ -92,13 +97,15 @@ Accept wildcard characters: False ``` ### -CommunityURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -108,6 +115,9 @@ 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`. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ Accept wildcard characters: False ``` ### -ControlPanelFeedbackEnabled + +> 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 @@ -143,13 +154,15 @@ Accept wildcard characters: False ``` ### -ControlPanelFeedbackURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,13 +172,15 @@ Accept wildcard characters: False ``` ### -ControlPanelHelpURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ControlPanelHelpURL parameter specifies the URL where help for the Exchange admin center (EAC) is hosted. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -175,6 +190,9 @@ 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,7 +201,6 @@ 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 @@ -193,6 +210,9 @@ Accept wildcard characters: False ``` ### -ExchangeHelpAppOnline + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExchangeHelpAppOnline specifies whether your organization uses the public help that's hosted by Microsoft. Valid values are: - $true: Your organization uses the help that's hosted by Microsoft. This is the default value. @@ -202,7 +222,6 @@ The ExchangeHelpAppOnline specifies whether your organization uses the public he Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -212,13 +231,15 @@ Accept wildcard characters: False ``` ### -ManagementConsoleFeedbackEnabled + +> 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 @@ -228,13 +249,15 @@ Accept wildcard characters: False ``` ### -ManagementConsoleFeedbackURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -244,13 +267,15 @@ Accept wildcard characters: False ``` ### -ManagementConsoleHelpURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ManagementConsoleHelpURL parameter specifies the URL where help for the Exchange Management Console (EMC) is hosted. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,13 +285,15 @@ Accept wildcard characters: False ``` ### -OWAFeedbackEnabled + +> 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 @@ -276,13 +303,15 @@ Accept wildcard characters: False ``` ### -OWAFeedbackURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -292,13 +321,15 @@ Accept wildcard characters: False ``` ### -OWAHelpURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OWAHelpURL parameter specifies the URL for where help for the standard version of Outlook on the web is hosted. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -308,13 +339,15 @@ Accept wildcard characters: False ``` ### -OWALightFeedbackEnabled + +> 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 @@ -324,13 +357,15 @@ Accept wildcard characters: False ``` ### -OWALightFeedbackURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -340,13 +375,15 @@ Accept wildcard characters: False ``` ### -OWALightHelpURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OWALightHelpURL parameter specifies the URL for where help for the light version of Outlook on the web is hosted. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,13 +393,15 @@ Accept wildcard characters: False ``` ### -PrivacyLinkDisplayEnabled + +> 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 @@ -372,13 +411,15 @@ Accept wildcard characters: False ``` ### -PrivacyStatementURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -388,13 +429,15 @@ 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/exchange/Set-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-ExchangeFeature.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md index f023153538..f468ff6934 100644 --- a/exchange/exchange-ps/exchange/Set-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md @@ -1,12 +1,14 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangefeature applicable: Exchange Server 2019 -title: Set-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/exchange/set-exchangefeature +schema: 2.0.0 +title: Set-ExchangeFeature --- # Set-ExchangeFeature @@ -61,6 +63,9 @@ This example blocks the features F1.1.1, F1.2.1, and F2.1.1 on the computer name ## 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 @@ -72,7 +77,6 @@ The Identity parameter specifies the Exchange server that you want to modify. Yo Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: True Position: 0 @@ -82,13 +86,15 @@ Accept wildcard characters: False ``` ### -Approve + +> Applicable: Exchange Server 2019 + The Approve switch approves the feature specified by the FeatureID parameter. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -98,13 +104,15 @@ Accept wildcard characters: False ``` ### -Block + +> Applicable: Exchange Server 2019 + The Block switch blocks the feature specified by the FeatureID parameter. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -114,6 +122,9 @@ 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`. @@ -123,7 +134,6 @@ 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 @@ -133,13 +143,15 @@ Accept wildcard characters: False ``` ### -FeatureID + +> Applicable: Exchange Server 2019 + The FeatureID parameter specifies the feature you want to control. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -149,13 +161,15 @@ 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/exchange/Set-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ExchangeServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md index b010016da0..bfc9c49def 100644 --- a/exchange/exchange-ps/exchange/Set-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangeserver applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ExchangeServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangeserver +schema: 2.0.0 +title: Set-ExchangeServer --- # Set-ExchangeServer @@ -74,6 +75,9 @@ This example removes an Exchange server from the Customer Experience Improvement ## 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 modify. You can use any value that uniquely identifies the server. For example: - Name @@ -85,7 +89,6 @@ The Identity parameter specifies the Exchange server that you want to modify. Yo Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -95,6 +98,9 @@ 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,7 +110,6 @@ 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 @@ -114,13 +119,15 @@ Accept wildcard characters: False ``` ### -CustomerFeedbackEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CustomerFeedbackEnabled parameter specifies whether the Exchange server is enrolled in the Microsoft Customer Experience Improvement Program (CEIP). The CEIP collects anonymous information about how you use Exchange and problems that you might encounter. If you decide not to participate in the CEIP, the servers are opted-out automatically. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,6 +137,9 @@ Accept wildcard characters: False ``` ### -DataCollectionEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The DataCollectionEnabled parameter specifies whether the EM Service will collect and send diagnostic data to Microsoft using OCS. Valid values are: - $true: The EM Service collects and sends diagnostic data to Microsoft using OCS. @@ -139,7 +149,6 @@ The DataCollectionEnabled parameter specifies whether the EM Service will collec Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -149,6 +158,9 @@ 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. @@ -157,7 +169,6 @@ 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 @@ -167,13 +178,15 @@ Accept wildcard characters: False ``` ### -ErrorReportingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ErrorReportingEnabled parameter specifies whether error reporting is enabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -183,6 +196,9 @@ Accept wildcard characters: False ``` ### -InternetWebProxy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternetWebProxy parameter specifies the web proxy server that the Exchange server uses to reach the internet. A valid value for this parameter is the URL of the web proxy server. In Exchange 2016 or later, to configure a list of servers that bypass the web proxy server and connect to the internet directly, use the InternetWebProxyBypassList parameter. @@ -191,7 +207,6 @@ In Exchange 2016 or later, to configure a list of servers that bypass the web pr Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -201,6 +216,9 @@ Accept wildcard characters: False ``` ### -InternetWebProxyBypassList + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The InternetWebProxyBypassList parameter specifies a list of servers that bypass the web proxy server specified by the InternetWebProxy parameter. You identify the servers by their FQDN (for example, server01.contoso.com). To enter multiple values and overwrite any existing FQDN entries, use the following syntax: @("host1.contoso.com","host2.contoso.com","host3.contoso.com"). @@ -211,7 +229,6 @@ The maximum number of servers you can enter with this parameter is 100. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -221,13 +238,15 @@ Accept wildcard characters: False ``` ### -MitigationsApplied + +> Applicable: Exchange Server 2016, Exchange Server 2019 + Do not use this parameter. The EM service uses this parameter to store and track mitigation status. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -237,6 +256,9 @@ Accept wildcard characters: False ``` ### -MitigationsBlocked + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The MitigationsBlocked parameter specifies a list of mitigations that are blocked. The Mitigation IDs present in this list are not applied by EM service in its hourly run. To enter multiple values and overwrite any existing Mitigation entries, use the following syntax: `@("Entry1","Entry2",..."EntryN")`. @@ -245,7 +267,6 @@ To enter multiple values and overwrite any existing Mitigation entries, use the Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,6 +276,9 @@ Accept wildcard characters: False ``` ### -MitigationsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The MitigationsEnabled parameter specifies whether the Exchange Emergency Mitigation service (EM service) automatically applies mitigations on the Exchange server. Valid values are: - $true: The EM Service automatically applies mitigations on the Exchange server. @@ -266,7 +290,6 @@ For more information, see [Exchange Emergency Mitigation (EM) service](https://l Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -276,13 +299,15 @@ Accept wildcard characters: False ``` ### -MonitoringGroup + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringGroup parameter specifies how to add your Exchange servers to monitoring groups. You can add your servers to an existing group or create a monitoring group based on location or deployment, or to partition monitoring responsibility among your servers. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -292,13 +317,15 @@ Accept wildcard characters: False ``` ### -ProductKey + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProductKey parameter specifies the server product key. ```yaml Type: ProductKey Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -308,13 +335,15 @@ Accept wildcard characters: False ``` ### -RingLevel + +> Applicable: Exchange Server 2019 + The RingLevel parameter specifies the server ring level that's used by the Feature Flighting feature. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -324,13 +353,15 @@ Accept wildcard characters: False ``` ### -StaticConfigDomainController + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The StaticConfigDomainController parameter specifies whether to configure a domain controller to be used by the server via Directory Service Access (DSAccess). ```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,13 +371,15 @@ Accept wildcard characters: False ``` ### -StaticDomainControllers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The StaticDomainControllers parameter specifies whether to configure a list of domain controllers to be used by the server via DSAccess. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,13 +389,15 @@ Accept wildcard characters: False ``` ### -StaticExcludedDomainControllers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The StaticExcludedDomainControllers parameter specifies whether to exclude a list of domain controllers from being used by the server. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -372,13 +407,15 @@ Accept wildcard characters: False ``` ### -StaticGlobalCatalogs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The StaticGlobalCatalogs parameter specifies whether to configure a list of global catalogs to be used by the server via DSAccess. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -388,13 +425,15 @@ 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/exchange/Set-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-ExchangeSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md index 436392e2c0..1d28260b3c 100644 --- a/exchange/exchange-ps/exchange/Set-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangesettings applicable: Exchange Server 2016, Exchange Server 2019 -title: Set-ExchangeSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-exchangesettings +schema: 2.0.0 +title: Set-ExchangeSettings --- # Set-ExchangeSettings @@ -207,6 +208,9 @@ This example allows users to see the results of Unified Audit Logging. This exam ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the existing Exchange settings object that contains the Exchange settings that you want to configure. The value of this parameter is the value of the Name parameter on the New-ExchangeSetting cmdlet when the Exchange settings object was created. @@ -215,7 +219,6 @@ The value of this parameter is the value of the Name parameter on the New-Exchan Type: ExchangeSettingsIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -225,13 +228,15 @@ Accept wildcard characters: False ``` ### -ClearHistory + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ClearHistory switch specifies that you want to clear the entries in the modification history for the Exchange setting object. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ClearHistory Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -241,6 +246,9 @@ Accept wildcard characters: False ``` ### -ConfigName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ConfigName parameter specifies the available Exchange setting that you want to add, remove, or update in the Exchange settings object. Valid values for this parameter are determined by the configuration schema that was specified by the Name parameter on the New-ExchangeSettings cmdlet. For add and update operations, you also need to use the ConfigValue parameter to specify the actual value for the setting. You can't use the ConfigName parameter with the ConfigPairs parameter. @@ -249,7 +257,6 @@ For add and update operations, you also need to use the ConfigValue parameter to Type: String Parameter Sets: UpdateSetting, RemoveSetting Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -259,15 +266,17 @@ Accept wildcard characters: False ``` ### -ConfigPairs + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ConfigName parameter specifies the available Exchange setting that you want to add, remove, or update in the Exchange settings object. Valid values for this parameter are determined by the configuration schema that was specified by the Name parameter on the New-ExchangeSettings cmdlet. The syntax for a value is `=`. You can separate multiple values separated by commas. You can't use the ConfigPairs parameter with the ConfigName or ConfigValue parameters. ```yaml Type: String[] -Parameter Sets: RemoveMultipleSettings, UpdateMultipleSettings +Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric, RemoveMultipleSettings, UpdateMultipleSettings Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -276,20 +285,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String[] -Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -ConfigValue -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019 -### -ConfigValue The ConfigValue parameter specifies the value for the Exchange setting that you specified with the ConfigName parameter. The values are determined by the type of setting (a number, a timespan, $true or $false, etc.). You can't use the ConfigValue parameter with the ConfigPairs parameter. @@ -298,7 +297,6 @@ You can't use the ConfigValue parameter with the ConfigPairs parameter. Type: String Parameter Sets: UpdateSetting Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -308,6 +306,9 @@ Accept wildcard characters: False ``` ### -CreateSettingsGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The CreateSettingsGroup switch specifies that you're creating an Exchange settings group, which is a group of related Exchange settings. You don't need to specify a value with this switch. Depending on how you want to configure the settings group, you use either the GroupName parameter or the SettingsGroup parameter to specify the name of the Exchange settings group. Choose carefully, because you can't rename an existing settings group. @@ -316,7 +317,6 @@ Depending on how you want to configure the settings group, you use either the Gr Type: SwitchParameter Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupAdvanced, CreateSettingsGroupGeneric Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -326,6 +326,9 @@ Accept wildcard characters: False ``` ### -ExpirationDate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ExpirationDate parameter specifies the end date/time of the Exchange settings that are defined by the specified Exchange settings group. 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". @@ -334,9 +337,8 @@ You can only use the ExpirationDate parameter with the CreateSettingsGroup or Up ```yaml Type: DateTime -Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric +Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric, UpdateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -345,20 +347,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: DateTime -Parameter Sets: UpdateSettingsGroup -Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 +### -GuidMatch -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2016, Exchange Server 2019 -### -GuidMatch The GuidMatch parameter specifies the scope of an Exchange settings group based on the GUID of the object (for example, the GUID of the mailbox database). This parameter is available for use with all Scope parameter values other than Forest. You use the GuidMatch parameter only when you create Exchange settings groups by using the CreateSettingsGroup switch with the GroupName parameter. @@ -369,7 +361,6 @@ You can't use this parameter with the GenericScopeName, GenericScopeValue, MaxVe Type: Guid Parameter Sets: CreateSettingsGroupGuid Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -379,13 +370,15 @@ Accept wildcard characters: False ``` ### -Reason + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Reason parameter specifies a description for why the Exchange setting or settings group was created or modified. 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 Required: True Position: Named @@ -395,6 +388,9 @@ Accept wildcard characters: False ``` ### -RemoveSetting + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RemoveSetting switch specifies that you're removing an existing Exchange setting from an Exchange settings object. You don't need to specify a value with this switch. You use the ConfigPairs parameter or the ConfigName parameter to specify the setting that you want to remove. @@ -403,7 +399,6 @@ You use the ConfigPairs parameter or the ConfigName parameter to specify the set Type: SwitchParameter Parameter Sets: RemoveSetting, RemoveMultipleSettings Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -413,6 +408,9 @@ Accept wildcard characters: False ``` ### -RemoveSettingsGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RemoveSettingsGroup switch specifies that you're removing an Exchange settings group. You don't need to specify a value with this switch. You use the GroupName parameter to specify the Exchange settings group that you want to remove. @@ -421,7 +419,6 @@ You use the GroupName parameter to specify the Exchange settings group that you Type: SwitchParameter Parameter Sets: RemoveSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -431,6 +428,9 @@ Accept wildcard characters: False ``` ### -SettingsGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The SettingsGroup parameter specifies an existing Exchange settings group that's used to create a new settings group, or modify an existing settings group. You can't use the SettingsGroup parameter with the GroupName parameter. @@ -439,7 +439,6 @@ You can't use the SettingsGroup parameter with the GroupName parameter. Type: String Parameter Sets: CreateSettingsGroupAdvanced, UpdateSettingsGroupAdvanced Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -449,6 +448,9 @@ Accept wildcard characters: False ``` ### -UpdateSetting + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The UpdateSetting switch specifies that you're updating an Exchange setting in an existing Exchange settings object. You don't need to specify a value with this switch. You use the ConfigPairs parameter or the ConfigName and ConfigValue parameters to configure the Exchange setting. @@ -457,7 +459,6 @@ You use the ConfigPairs parameter or the ConfigName and ConfigValue parameters t Type: SwitchParameter Parameter Sets: UpdateSetting, UpdateMultipleSettings Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -467,6 +468,9 @@ Accept wildcard characters: False ``` ### -UpdateSettingsGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The UpdateSettingsGroup switch specifies that you're modifying an Exchange settings group. You don't need to specify a value with this switch. Depending on how you want to configure the settings group, you use either the GroupName parameter or the SettingsGroup parameter to specify the Exchange settings group that you want to modify. @@ -475,7 +479,6 @@ Depending on how you want to configure the settings group, you use either the Gr Type: SwitchParameter Parameter Sets: UpdateSettingsGroup, UpdateSettingsGroupAdvanced Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -485,6 +488,9 @@ 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`. @@ -496,7 +502,6 @@ 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 Required: False Position: Named @@ -506,6 +511,9 @@ Accept wildcard characters: False ``` ### -Disable + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Disable switch specifies that the Exchange settings group is disabled. You don't need to specify a value with this switch. You can only use this switch with the CreateSettingsGroup switch. @@ -516,7 +524,6 @@ To use this switch to enable an Exchange settings group, use this exact syntax ` Type: SwitchParameter Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -526,6 +533,9 @@ Accept wildcard characters: False ``` ### -DisableGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The DisableGroup parameter specifies the name of the enabled Exchange settings group that you want to disable. If the value contains spaces, enclose the value in quotation marks ("). You can use the DisableGroup and EnableGroup parameters together in the same command to enable and disable different Exchange settings groups at the same time. @@ -534,7 +544,6 @@ You can use the DisableGroup and EnableGroup parameters together in the same com Type: String Parameter Sets: EnableSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -544,13 +553,15 @@ 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 @@ -560,6 +571,9 @@ Accept wildcard characters: False ``` ### -EnableGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The EnableGroup parameter specifies the name of the disabled Exchange settings group that you want to enable. If the value contains spaces, enclose the value in quotation marks ("). You can use the DisableGroup and EnableGroup parameters together in the same command to enable and disable different Exchange settings groups at the same time. @@ -568,7 +582,6 @@ You can use the DisableGroup and EnableGroup parameters together in the same com Type: String Parameter Sets: EnableSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -578,6 +591,9 @@ 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. @@ -586,7 +602,6 @@ 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 @@ -596,13 +611,15 @@ Accept wildcard characters: False ``` ### -GenericScopeName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The GenericScopeName parameter specifies the name of the scope. The available values are determined by the schema of the Exchange setting object. ```yaml Type: String Parameter Sets: CreateSettingsGroupGeneric Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -612,13 +629,15 @@ Accept wildcard characters: False ``` ### -GenericScopeValue + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The GenericScopeValue parameter specifies 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: CreateSettingsGroupGeneric Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -628,6 +647,9 @@ Accept wildcard characters: False ``` ### -GroupName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The GroupName parameter specifies the name of the Exchange settings group in group operations. For example: - Create Exchange settings groups and simultaneously configure the group scope and priority. @@ -641,7 +663,6 @@ If the value contains spaces, enclose the value in quotation marks ("). Type: String Parameter Sets: UpdateSetting, RemoveSetting, CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric, UpdateSettingsGroup, RemoveMultipleSettings, RemoveSettingsGroup, UpdateMultipleSettings Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -651,6 +672,9 @@ Accept wildcard characters: False ``` ### -MaxVersion + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The MaxVersion parameter specifies the scope of an Exchange settings group based on the version of the object (for example, the version of Exchange that's installed on the server). This parameter is available for use with all Scope parameter values other than Forest. You use the MaxVersion parameter together with the MinVersion parameter only when you create Exchange settings groups by using the CreateSettingsGroup switch with the GroupName parameter. @@ -661,7 +685,6 @@ You can't use this parameter with the GuidMatch, GenericScopeName, or GenericSco Type: String Parameter Sets: CreateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -671,6 +694,9 @@ Accept wildcard characters: False ``` ### -MinVersion + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The MinVersion parameter specifies the scope of an Exchange settings group based on the version of the object (for example, the version of Exchange that's installed on the server). This parameter is available for use with all Scope parameter values other than Forest. You use the MinVersion parameter together with the MaxVersion parameter only when you create Exchange settings groups by using the CreateSettingsGroup switch with the GroupName parameter. @@ -681,7 +707,6 @@ You can't use this parameter with GuidMatch, GenericScopeName, or GenericScopeVa Type: String Parameter Sets: CreateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -691,6 +716,9 @@ Accept wildcard characters: False ``` ### -NameMatch + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The NameMatch parameter specifies the scope of an Exchange settings group based on the name of the object (for example, the process name). This parameter is available for use with all Scope parameter values other than Forest. You use the NameMatch parameter only when you create Exchange settings groups by using the CreateSettingsGroup switch with the GroupName parameter. @@ -701,7 +729,6 @@ You can't use this parameter with the GuidMatch, GenericScopeName, or GenericSco Type: String Parameter Sets: CreateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -711,13 +738,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the priority of an Exchange settings group. The priority value for every group must be unique. A lower priority value indicates a higher priority. ```yaml Type: Int32 Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric, UpdateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -727,6 +756,9 @@ Accept wildcard characters: False ``` ### -Scope + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The Scope parameter specifies the scope of the Exchange settings object. Valid values are: - Dag @@ -742,7 +774,6 @@ The Scope parameter specifies the scope of the Exchange settings object. Valid v Type: ExchangeSettingsScope Parameter Sets: CreateSettingsGroup, CreateSettingsGroupGuid, CreateSettingsGroupGeneric Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -752,6 +783,9 @@ Accept wildcard characters: False ``` ### -ScopeFilter + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ScopeFilter parameter uses OPATH filter syntax to specify the scope of an Exchange settings group based. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"ServerRole -like 'Mailbox*'"`). - 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. @@ -771,7 +805,6 @@ You use this parameter only when you update Exchange settings groups by using th Type: String Parameter Sets: CreateSettingsGroup, UpdateSettingsGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -781,13 +814,15 @@ 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/exchange/Set-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md index 65ae3af9cb..baaac52073 100644 --- a/exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-exophishsimoverriderule applicable: Exchange Online -title: Set-ExoPhishSimOverrideRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-exophishsimoverriderule +schema: 2.0.0 +title: Set-ExoPhishSimOverrideRule --- # Set-ExoPhishSimOverrideRule @@ -57,6 +58,9 @@ This example modifies the specified phishing simulation override rule with the s ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the phishing simulation override rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -70,7 +74,6 @@ Use the Get-ExoPhishSimOverrideRule cmdlet to find the values. The name of the r Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -80,6 +83,9 @@ Accept wildcard characters: False ``` ### -AddDomains + +> Applicable: Exchange Online + The AddDomains parameter specifies an existing entry to add to the list of email domains that are used by the non-Microsoft phishing simulation. You can specify multiple values separated by commas. A maximum of 20 entries are allowed in the list. @@ -88,7 +94,6 @@ You can specify multiple values separated by commas. A maximum of 20 entries are Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -98,6 +103,9 @@ Accept wildcard characters: False ``` ### -AddSenderIpRanges + +> Applicable: Exchange Online + The AddSenderIpRanges parameter specifies an existing entry to add to the list of source IP addresses that are used by the non-Microsoft phishing simulation. Valid values are: - Single IP address: For example, 192.168.1.1. @@ -112,7 +120,6 @@ A maximum of 10 entries are allowed in the list. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -122,13 +129,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -138,6 +147,9 @@ 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,7 +159,6 @@ 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 @@ -157,13 +168,15 @@ 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 @@ -173,6 +186,9 @@ Accept wildcard characters: False ``` ### -RemoveDomains + +> Applicable: Exchange Online + The RemoveDomains parameter specifies an existing entry to remove from the list of email domains that are used by the non-Microsoft phishing simulation. You can specify multiple values separated by commas. @@ -181,7 +197,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -191,6 +206,9 @@ Accept wildcard characters: False ``` ### -RemoveSenderIpRanges + +> Applicable: Exchange Online + The RemoveSenderIpRanges parameter specifies an existing entry to remove from the list of source IP addresses that are used by the non-Microsoft phishing simulation. Valid values are: - Single IP address: For example, 192.168.1.1. @@ -203,7 +221,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -213,13 +230,15 @@ 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/exchange/Set-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md index 29ef4908ae..7a43e6a6d8 100644 --- a/exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/get-exosecopsoverriderule applicable: Exchange Online -title: set-ExoSecOpsOverrideRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/get-exosecopsoverriderule +schema: 2.0.0 +title: set-ExoSecOpsOverrideRule --- # Set-ExoSecOpsOverrideRule @@ -53,6 +54,9 @@ This example adds a comment to the specified SecOps mailbox override rule. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the SecOps override rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -66,7 +70,6 @@ Use the Get-ExoSecOpsMailboxRule cmdlet to find these values. The name of the ru Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -76,13 +79,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -92,6 +97,9 @@ 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`. @@ -101,7 +109,6 @@ 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 @@ -111,13 +118,15 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Set-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md similarity index 97% rename from exchange/exchange-ps/exchange/Set-ExternalInOutlook.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md index 83221e105b..590d279e29 100644 --- a/exchange/exchange-ps/exchange/Set-ExternalInOutlook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-externalinoutlook applicable: Exchange Online, Exchange Online Protection -title: Set-ExternalInOutlook -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-externalinoutlook +schema: 2.0.0 +title: Set-ExternalInOutlook --- # Set-ExternalInOutlook @@ -58,6 +59,9 @@ This example adds and removes the specified email addresses from the exception l ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the GUID of the external sender identification object that you want to modify. This parameter is optional and typically isn't needed, because the organization's GUID resolves automatically when you use this cmdlet. @@ -68,7 +72,6 @@ If you specify an invalid Identity value, the cmdlet still runs and changes the Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 0 @@ -78,6 +81,9 @@ Accept wildcard characters: False ``` ### -AllowList + +> Applicable: Exchange Online + The AllowList parameter specifies exceptions to external sender identification in supported versions of Outlook. Messages received from the specified senders or senders in the specified domains don't receive native External sender identification. The allow list uses the `5322.From` address (also known as the **From** address or P2 sender). Valid values are an individual domain (contoso.com), a domain and all subdomains (*.contoso.com) or email addresses (admin@contoso.com). @@ -94,7 +100,6 @@ The maximum number of entries is 50, and the total size of all entries can't exc Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -104,6 +109,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter enables or disables external sender identification in supported versions of Outlook. Valid values are: - $true: External sender identification in Outlook is enabled. An External icon is added in the area of the subject line of messages from external senders. To exempt specific senders or sender domains from this identification, use the AllowList parameter. @@ -115,7 +123,6 @@ After an admin enables this setting, it can take between 24 and 48 hours for use Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-FeatureConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-FeatureConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md index 775dd3b86a..a500507036 100644 --- a/exchange/exchange-ps/exchange/Set-FeatureConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md @@ -1,9 +1,11 @@ --- +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/exchange/set-featureconfiguration -applicable: Security & Compliance -title: Set-FeatureConfiguration schema: 2.0.0 +title: Set-FeatureConfiguration --- # Set-FeatureConfiguration @@ -62,6 +64,9 @@ This example updates a collection policy named "Microsoft Copilot collection pol ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the feature configuration that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -72,7 +77,6 @@ The Identity parameter specifies the feature configuration that you want to modi Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -82,13 +86,15 @@ 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 @@ -98,6 +104,9 @@ 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,7 +116,6 @@ 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 @@ -117,13 +125,15 @@ 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 @@ -133,6 +143,9 @@ Accept wildcard characters: False ``` ### -Mode + +> Applicable: Security & Compliance + The Mode parameter specifies feature configuration mode. Valid values are: - Enable: The feature configuration is enabled. @@ -142,7 +155,6 @@ The Mode parameter specifies feature configuration mode. Valid values are: Type: PolicyMode Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -152,13 +164,15 @@ 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: False Position: Named @@ -168,13 +182,15 @@ 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/exchange/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md index 92e99bb1fe..c24102f63e 100644 --- a/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-federatedorganizationidentifier applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-FederatedOrganizationIdentifier -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-federatedorganizationidentifier +schema: 2.0.0 +title: Set-FederatedOrganizationIdentifier --- # Set-FederatedOrganizationIdentifier @@ -68,13 +69,15 @@ This example enables the organization identifier. This enables federation for 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 federated organization identifier. ```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 @@ -84,13 +87,15 @@ Accept wildcard characters: False ``` ### -AccountNamespace + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AccountNamespace parameter specifies the federated domain to be used to establish the organization identifier with the Microsoft Federation Gateway. ```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: False Position: Named @@ -100,6 +105,9 @@ 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`. @@ -109,7 +117,6 @@ 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 @@ -119,13 +126,15 @@ Accept wildcard characters: False ``` ### -DefaultDomain + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DefaultDomain parameter specifies the federated domain used for delegation tokens issued by the Microsoft Federation Gateway for user accounts in the Exchange organization. If the DefaultDomain parameter isn't set, the primary SMTP domain for each user account is used in delegation tokens issued by the Microsoft Federation Gateway. Only a single domain or subdomain for the Exchange organization should be configured, and it applies to all delegation tokens issued for the Exchange organization, for example, contoso.com. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -135,13 +144,15 @@ Accept wildcard characters: False ``` ### -DelegationFederationTrust + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DelegationFederationTrust parameter specifies the identity of the federation trust to be used by the organization identifier. ```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: Named @@ -151,6 +162,9 @@ 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. @@ -159,7 +173,6 @@ 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,6 +182,9 @@ 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 the organization identifier is enabled. Valid values include $true or $false. Setting the parameter to $false disables federation. @@ -177,7 +193,6 @@ Setting the parameter to $false disables federation. 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 @@ -187,13 +202,15 @@ Accept wildcard characters: False ``` ### -OrganizationContact + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OrganizationContact parameter specifies the SMTP address of the federation contact. ```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 @@ -203,13 +220,15 @@ 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/exchange/Set-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-FederationTrust.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md index 5a6e6a3d8a..e2801878cc 100644 --- a/exchange/exchange-ps/exchange/Set-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-federationtrust applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-FederationTrust -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-federationtrust +schema: 2.0.0 +title: Set-FederationTrust --- # Set-FederationTrust @@ -88,6 +89,9 @@ Before you configure a federation trust to use the next certificate as the curre ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the federation trust being modified. **Note**: For Exchange Online organizations, use the value "Microsoft Entra authentication". @@ -96,7 +100,6 @@ The Identity parameter specifies the name of the federation trust being modified Type: FederationTrustIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -106,13 +109,15 @@ 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 federation organization identifier. ```yaml Type: String Parameter Sets: ApplicationUri Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -122,6 +127,9 @@ Accept wildcard characters: False ``` ### -PublishFederationCertificate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PublishFederationCertificate switch specifies the next certificate as the current certificate for the federation trust and publishes it to the Microsoft Federation Gateway. You don't need to specify a value with this switch. The certificate is used to encrypt tokens with the Microsoft Federation Gateway. @@ -132,7 +140,6 @@ Before setting the next certificate to be used as the current certificate, ensur Type: SwitchParameter Parameter Sets: PublishFederationCertificate Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -142,6 +149,9 @@ 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`. @@ -151,7 +161,6 @@ 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 @@ -161,13 +170,15 @@ 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 @@ -177,13 +188,15 @@ 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: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -193,13 +206,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a 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: False Position: Named @@ -209,13 +224,15 @@ Accept wildcard characters: False ``` ### -RefreshMetadata + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RefreshMetadata switch specifies that the metadata document and certificate is retrieved again from the Microsoft Federation Gateway. 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 @@ -225,13 +242,15 @@ 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 the X.509 certificate to be configured as the next certificate for the federation trust. After the certificate is deployed on all Exchange servers in the organization, you can use the PublishFederationCertificate switch to configure the trust to use this certificate. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,13 +260,15 @@ 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/exchange/Set-FilePlanPropertyAuthority.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md index 2c6319179c..fdd50a2e05 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertyauthority -applicable: Security & Compliance -title: Set-FilePlanPropertyAuthority schema: 2.0.0 +title: Set-FilePlanPropertyAuthority --- # Set-FilePlanPropertyAuthority @@ -39,6 +41,9 @@ This example modifies the display name for the custom file plan property authori ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property authority that you want to modify. You can use any value that uniquely identifies the authority. For example: - Name @@ -49,7 +54,6 @@ The Identity parameter specifies the custom file plan property authority that yo Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -59,6 +63,9 @@ 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. @@ -68,7 +75,6 @@ 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 @@ -78,13 +84,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of the file plan property authority. 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 @@ -94,13 +102,15 @@ 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/exchange/Set-FilePlanPropertyCategory.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md index c997f07927..48b4b0d8fd 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertycategory -applicable: Security & Compliance -title: Set-FilePlanPropertyCategory schema: 2.0.0 +title: Set-FilePlanPropertyCategory --- # Set-FilePlanPropertyCategory @@ -37,6 +39,9 @@ This example modifies the display name for the custom file plan property categor ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property category that you want to modify. You can use any value that uniquely identifies the category. For example: - Name @@ -47,7 +52,6 @@ The Identity parameter specifies the custom file plan property category that you Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -57,6 +61,9 @@ 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. @@ -66,7 +73,6 @@ 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 @@ -76,13 +82,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of the file plan property category. 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 @@ -92,13 +100,15 @@ 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/exchange/Set-FilePlanPropertyCitation.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md index 78ebda0733..6ebd3a5f32 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertycitation -applicable: Security & Compliance -title: Set-FilePlanPropertyCitation schema: 2.0.0 +title: Set-FilePlanPropertyCitation --- # Set-FilePlanPropertyCitation @@ -42,6 +44,9 @@ This example modifies the citation URL for the custom file plan property citatio ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property citation that you want to modify. You can use any value that uniquely identifies the citation. For example: - Name @@ -52,7 +57,6 @@ The Identity parameter specifies the custom file plan property citation that you Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -62,13 +66,15 @@ Accept wildcard characters: False ``` ### -CitationJurisdiction + +> 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: Named @@ -78,13 +84,15 @@ Accept wildcard characters: False ``` ### -CitationUrl + +> 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: Named @@ -94,6 +102,9 @@ 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,7 +114,6 @@ 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 @@ -113,13 +123,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of 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: Named @@ -129,13 +141,15 @@ 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/exchange/Set-FilePlanPropertyDepartment.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md index 40d312c5a8..211f642461 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertydepartment -applicable: Security & Compliance -title: Set-FilePlanPropertyDepartment schema: 2.0.0 +title: Set-FilePlanPropertyDepartment --- # Set-FilePlanPropertyDepartment @@ -44,6 +46,9 @@ This example modifies the display name for the custom file plan property departm ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property department that you want to modify. You can use any value that uniquely identifies the department. For example: - Name @@ -54,7 +59,6 @@ The Identity parameter specifies the custom file plan property department that y Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -64,6 +68,9 @@ 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. @@ -73,7 +80,6 @@ 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,13 +89,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of the file plan property department. 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 @@ -99,13 +107,15 @@ 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/exchange/Set-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md index 0be4986969..3e4b2deaa0 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertyreferenceid -applicable: Security & Compliance -title: Set-FilePlanPropertyReferenceId schema: 2.0.0 +title: Set-FilePlanPropertyReferenceId --- # Set-FilePlanPropertyReferenceId @@ -40,6 +42,9 @@ This example modifies the display name for the custom file plan property referen ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property reference ID that you want to modify. You can use any value that uniquely identifies the reference ID. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property reference ID that Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of the file plan property reference ID. 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 @@ -95,13 +103,15 @@ 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/exchange/Set-FilePlanPropertySubCategory.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md index 384fa72ff4..5abffefc7d 100644 --- a/exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md @@ -1,9 +1,11 @@ --- +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/exchange/set-fileplanpropertysubcategory -applicable: Security & Compliance -title: Set-FilePlanPropertySubCategory schema: 2.0.0 +title: Set-FilePlanPropertySubCategory --- # Set-FilePlanPropertySubCategory @@ -40,6 +42,9 @@ This example modifies the display name for the custom file plan property subcate ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the custom file plan property subcategory that you want to modify. You can use any value that uniquely identifies the subcategory. For example: - Name @@ -50,7 +55,6 @@ The Identity parameter specifies the custom file plan property subcategory that Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -60,6 +64,9 @@ 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. @@ -69,7 +76,6 @@ 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 @@ -79,13 +85,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name of the file plan property subcategory. 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 @@ -95,13 +103,15 @@ 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/exchange/Set-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-FocusedInbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md index daebaa21e2..59d7fc5d72 100644 --- a/exchange/exchange-ps/exchange/Set-FocusedInbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.Management-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-focusedinbox applicable: Exchange Online, Exchange Online Protection -title: Set-FocusedInbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.Management-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-focusedinbox +schema: 2.0.0 +title: Set-FocusedInbox --- # Set-FocusedInbox @@ -44,6 +45,9 @@ This example disables Focused Inbox for the mailbox of laura@contoso.com. ## 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 @@ -61,7 +65,6 @@ 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,6 +74,9 @@ Accept wildcard characters: False ``` ### -FocusedInboxOn + +> Applicable: Exchange Online, Exchange Online Protection + The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Valid values are: - $true: Focused Inbox is enabled. This is the default value. @@ -80,7 +86,6 @@ The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -90,13 +95,15 @@ 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/exchange/Set-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ForeignConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md index 5ee2d43be4..1a0064ed3f 100644 --- a/exchange/exchange-ps/exchange/Set-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-foreignconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ForeignConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-foreignconnector +schema: 2.0.0 +title: Set-ForeignConnector --- # Set-ForeignConnector @@ -56,6 +57,9 @@ This example configures a 10 MB message size limit on the existing Foreign conne ## 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 modify. The Identity parameter can take any of the following values for the Foreign connector object: - GUID @@ -66,7 +70,6 @@ The Identity parameter specifies the Foreign connector that you want to modify. Type: ForeignConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -76,6 +79,9 @@ 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. @@ -97,7 +103,6 @@ To add or remove one or more address space values without affecting any existing Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -107,13 +112,15 @@ 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,6 +130,9 @@ 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,7 +142,6 @@ 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 @@ -142,6 +151,9 @@ 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. @@ -150,7 +162,6 @@ 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 @@ -160,6 +171,9 @@ Accept wildcard characters: False ``` ### -DropDirectory + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DropDirectory parameter specifies the name of the Drop directory used by this Foreign connector. All outbound messages sent to address spaces defined by this Foreign connector are put in the specified Drop directory. The location of the Drop directory for each Foreign connector is controlled by the following two items: - RootDropDirectoryPath parameter in the Set-TransportService cmdlet: This option is used for all Foreign connectors that exist on the Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path or a Universal Naming Convention (UNC) path to a remote server. @@ -181,7 +195,6 @@ The Drop directory must have the following permissions assigned to it: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,6 +204,9 @@ Accept wildcard characters: False ``` ### -DropDirectoryQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DropDirectoryQuota parameter specifies the maximum size of all message files in the Drop directory. When the specified value is reached, no new message files can be copied into the Drop directory until the existing messages are delivered and deleted. When you enter a value, qualify the value with one of the following units: @@ -209,7 +225,6 @@ The valid input range for this parameter is from 1 through 2147483647 bytes. If Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -219,13 +234,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether to enable the Foreign connector. The valid values are $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 @@ -235,6 +252,9 @@ 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. @@ -243,7 +263,6 @@ 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 @@ -253,13 +272,15 @@ 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 @@ -269,6 +290,9 @@ 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 can pass through this Foreign connector. When you enter a value, qualify the value with one of the following units: @@ -287,7 +311,6 @@ If you enter a value of unlimited, no message size limit is imposed on this Fore Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -297,13 +320,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a descriptive 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: False Position: Named @@ -313,13 +338,15 @@ Accept wildcard characters: False ``` ### -RelayDsnRequired + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RelayDsnRequired parameter specifies whether a Relay delivery status notification (DSN) is required by the Foreign connector when messages are written to the Drop directory. The valid input values for this parameter are $true or $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 Required: False Position: Named @@ -329,6 +356,9 @@ 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 Mailbox servers running the Transport service provides fault tolerance and high availability if one of the servers fails. The default value of this parameter is the name of the Mailbox server on which this Foreign connector was first installed. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -339,7 +369,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -349,13 +378,15 @@ 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/exchange/Set-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-FrontendTransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md index 1332c4a436..4803709b5e 100644 --- a/exchange/exchange-ps/exchange/Set-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-frontendtransportservice applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-FrontendTransportService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-frontendtransportservice +schema: 2.0.0 +title: Set-FrontendTransportService --- # Set-FrontendTransportService @@ -92,13 +93,15 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server that you want to modify. ```yaml Type: FrontendTransportServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -108,13 +111,15 @@ Accept wildcard characters: False ``` ### -AgentLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,6 +129,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -134,7 +142,6 @@ Setting the value of the AgentLogMaxAge parameter to 00:00:00 prevents the autom Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -144,6 +151,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -162,7 +172,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,6 +181,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -190,7 +202,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -200,13 +211,15 @@ Accept wildcard characters: False ``` ### -AgentLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -216,6 +229,9 @@ Accept wildcard characters: False ``` ### -AntispamAgentsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Front End Transport service. You set this parameter by using a script. You shouldn't modify this parameter manually. @@ -224,7 +240,6 @@ You set this parameter by using a script. You shouldn't modify this parameter ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -234,6 +249,9 @@ 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`. @@ -243,7 +261,6 @@ 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 @@ -253,13 +270,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -269,6 +288,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. 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. @@ -279,7 +301,6 @@ For example, to specify 25 days for this parameter, use 25.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -289,6 +310,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: @@ -307,7 +331,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -317,6 +340,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -335,7 +361,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -345,13 +370,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -361,13 +388,15 @@ Accept wildcard characters: False ``` ### -DnsLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -377,6 +406,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -387,7 +419,6 @@ Setting the value of the DnsLogMaxAge parameter to 00:00:00 prevents the automat Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -397,6 +428,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB. When you enter a value, qualify the value with one of the following units: @@ -415,7 +449,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -425,6 +458,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -443,7 +479,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -453,13 +488,15 @@ Accept wildcard characters: False ``` ### -DnsLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks ("). ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -469,13 +506,15 @@ 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 @@ -485,13 +524,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -501,6 +542,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used. @@ -509,7 +553,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -519,13 +562,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSProtocolOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any. ```yaml Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -535,6 +580,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSServers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. You must separate IP addresses by using commas. The default value is an empty list ({}). If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the ExternalDNSServers parameter and its list of DNS servers isn't used. @@ -543,7 +591,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the Ext Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -553,13 +600,15 @@ Accept wildcard characters: False ``` ### -ExternalIPAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Front End Transport service. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -569,13 +618,15 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -585,6 +636,9 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used. @@ -593,7 +647,6 @@ If the value of the InternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -603,6 +656,9 @@ Accept wildcard characters: False ``` ### -InternalDNSProtocolOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly. The default value is Any. @@ -611,7 +667,6 @@ The default value is Any. Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -621,6 +676,9 @@ Accept wildcard characters: False ``` ### -InternalDNSServers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address and are separated by commas. The default value is any empty list ({}). If the InternalDNSAdapterGuid parameter is set, and the value of the InternalDNSAdapterEnabled parameter is set to $true, the InternalDNSServers parameter and its list of DNS servers isn't used. @@ -629,7 +687,6 @@ If the InternalDNSAdapterGuid parameter is set, and the value of the InternalDNS Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -639,6 +696,9 @@ Accept wildcard characters: False ``` ### -IntraOrgConnectorProtocolLoggingLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connector In the Front End Transport service. Valid values are: - None: Protocol logging is disabled for the intra-organization Send connector in the Front End Transport service. @@ -648,7 +708,6 @@ The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP pro Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -658,13 +717,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionRatePerMinute + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -674,6 +735,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Receive connectors in the Transport service on the server. Log files that are older than the specified value are automaticallydeleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -686,7 +750,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -696,6 +759,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Receive connectors in the Front End Transport service on the server. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -718,7 +784,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -728,6 +793,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Receive connectors in the Front End Transport service on the server. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -750,7 +818,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -760,6 +827,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for all Receive connectors in the Front End Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\ProtocolLog\\SmtpReceive. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for any Receive connector in the Front End Transport service. To disable protocol logging for Receive connectors, use the value None for the ProtocolLoggingLevel parameter on the Set-ReceiveConnector cmdlet for each Receive connector in the Front End Transport service. @@ -768,7 +838,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -778,6 +847,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxAge + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 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. @@ -788,7 +860,6 @@ For example, to specify 5 days for this parameter, use 5.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -798,6 +869,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxDirectorySize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -816,7 +890,6 @@ The valid input range for this parameter is from 1 through 9223372036854775807 b Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -826,13 +899,15 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\Routing. Setting this parameter to $null disables routing table logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -842,6 +917,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Send connectors in the Front End Transport service that have this server configured as a source server. Log files that are older than the specified value are deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -854,7 +932,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -864,6 +941,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Send connectors in the Front End Transport service that have this server configured as a source server. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -886,7 +966,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -896,6 +975,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all the Send connectors in the Front End Transport service that have this server configured as a source server. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -918,7 +1000,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -928,6 +1009,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogPath parameter specifies the location of the protocol log directory for all Send connectors in the Front End Transport service that have this server configured as a source server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\ProtocolLog\\SmtpSend. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for any Send connector in the Front End Transport service that has this server configured as a source server. To disable protocol logging for these Send connectors, use the value None for the following parameters: @@ -939,7 +1023,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -949,13 +1032,15 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryCount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -965,6 +1050,9 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Front End Transport service, the default value of the TransientFailureRetryInterval parameter 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. @@ -975,7 +1063,6 @@ For example, to specify 8 minutes for this parameter, use 00:08:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -985,13 +1072,15 @@ 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/exchange/Set-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-GlobalAddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md index b4bbb3747e..22142f3998 100644 --- a/exchange/exchange-ps/exchange/Set-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-globaladdresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-GlobalAddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-globaladdresslist +schema: 2.0.0 +title: Set-GlobalAddressList --- # Set-GlobalAddressList @@ -78,6 +79,9 @@ This example assigns a new name, GALwithNewName, to the GAL with the GUID 96d0c5 ## 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 modify. You can use any value that uniquely identifies the GAL. For example: - Name @@ -88,7 +92,6 @@ The Identity parameter specifies the global address list that you want to modify Type: GlobalAddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -98,6 +101,9 @@ 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. 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. @@ -110,7 +116,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -120,6 +125,9 @@ 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. @@ -132,7 +140,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -142,6 +149,9 @@ 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. @@ -154,7 +164,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -164,6 +173,9 @@ 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. @@ -176,7 +188,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -186,6 +197,9 @@ 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. @@ -198,7 +212,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -208,6 +221,9 @@ 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. @@ -220,7 +236,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -230,6 +245,9 @@ 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. @@ -242,7 +260,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -252,6 +269,9 @@ 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. @@ -264,7 +284,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -274,6 +293,9 @@ 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. @@ -286,7 +308,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -296,6 +317,9 @@ 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. @@ -308,7 +332,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -318,6 +341,9 @@ 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. @@ -330,7 +356,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -340,6 +365,9 @@ 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. @@ -352,7 +380,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -362,6 +389,9 @@ 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. @@ -374,7 +404,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -384,6 +413,9 @@ 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. @@ -396,7 +428,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -406,6 +437,9 @@ 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. @@ -418,7 +452,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -428,6 +461,9 @@ 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. @@ -440,7 +476,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -450,6 +485,9 @@ 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. @@ -462,7 +500,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -472,6 +509,9 @@ 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. @@ -484,7 +524,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -494,6 +533,9 @@ 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`. @@ -503,7 +545,6 @@ 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 @@ -513,6 +554,9 @@ 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. @@ -521,7 +565,6 @@ 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 @@ -531,6 +574,9 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch. @@ -539,7 +585,6 @@ The ForceUpgrade switch suppresses the confirmation message that appears if the Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -549,6 +594,9 @@ 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. @@ -564,7 +612,6 @@ You can specify multiple values separated by commas. When you use multiple value Type: WellKnownRecipientType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -574,13 +621,15 @@ Accept wildcard characters: False ``` ### -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 GAL. 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: False Position: Named @@ -590,6 +639,9 @@ 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: @@ -605,7 +657,6 @@ 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 @@ -615,6 +666,9 @@ Accept wildcard characters: False ``` ### -RecipientFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RecipientFilter parameter specifies an 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. @@ -630,7 +684,6 @@ 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 @@ -640,13 +693,15 @@ 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/exchange/Set-Group.md b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-Group.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Group.md index 25c66b6124..73ff7692c2 100644 --- a/exchange/exchange-ps/exchange/Set-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-group applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-Group -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-group +schema: 2.0.0 +title: Set-Group --- # Set-Group @@ -69,6 +70,9 @@ This example specifies that the group Human Resources is a hierarchical group an ## 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 @@ -80,7 +84,6 @@ The Identity parameter specifies the group that you want to modify. You can use Type: GroupIdParameter 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 @@ -90,6 +93,9 @@ 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: @@ -101,7 +107,6 @@ 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 @@ -111,6 +116,9 @@ 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`. @@ -120,7 +128,6 @@ 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 @@ -130,6 +137,9 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill Description Description }} @@ -138,7 +148,6 @@ 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 @@ -148,6 +157,9 @@ 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 ("). This parameter is meaningful only if the group is mail-enabled. @@ -156,7 +168,6 @@ This parameter is meaningful only if the group is mail-enabled. 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 @@ -166,6 +177,9 @@ 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. @@ -176,7 +190,6 @@ 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 @@ -186,6 +199,9 @@ 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. @@ -199,7 +215,6 @@ 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 @@ -209,13 +224,15 @@ Accept wildcard characters: False ``` ### -IsHierarchicalGroup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The IsHierarchicalGroup parameter specifies whether the group is part of a hierarchical address book. Valid values are $true or $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, Exchange Online Protection Required: False Position: Named @@ -225,6 +242,9 @@ 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 @@ -258,7 +278,6 @@ Owners that you specify with this parameter are not added as group members. You 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 @@ -268,13 +287,15 @@ Accept wildcard characters: False ``` ### -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 ("). ```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 @@ -284,13 +305,15 @@ 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 @@ -300,13 +323,15 @@ Accept wildcard characters: False ``` ### -PhoneticDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -316,13 +341,15 @@ Accept wildcard characters: False ``` ### -SeniorityIndex + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SeniorityIndex parameter specifies the order in which this group will display in a hierarchical address book. A group with a value of 2 will display higher in an address book than a group with a value of 1. ```yaml Type: Int32 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 @@ -332,6 +359,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -346,7 +376,6 @@ This parameter is meaningful only if the group is mail-enabled. 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 @@ -356,13 +385,15 @@ Accept wildcard characters: False ``` ### -Universal + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Universal switch changes the scope of the group from Global or DomainLocal to Universal. 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 @@ -372,13 +403,15 @@ 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 @@ -388,6 +421,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -399,7 +435,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md index d1f0720b66..dee18ea3c4 100644 --- a/exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-holdcompliancepolicy applicable: Security & Compliance -title: Set-HoldCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-holdcompliancepolicy +schema: 2.0.0 +title: Set-HoldCompliancePolicy --- # Set-HoldCompliancePolicy @@ -70,6 +71,9 @@ This example makes the following changes to the existing preservation policy nam ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the preservation policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -80,7 +84,6 @@ The Identity parameter specifies the preservation policy that you want to modify Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -90,6 +93,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -100,7 +106,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -110,6 +115,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes. Valid values are: - A mailbox @@ -128,7 +136,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -138,13 +145,15 @@ Accept wildcard characters: False ``` ### -AddPublicFolderLocation + +> Applicable: Security & Compliance + The AddPublicFolderLocation parameter specifies that you want to add all public folders to the preservation policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -154,6 +163,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocation + +> Applicable: Security & Compliance + The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites when you aren't using 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"`. @@ -164,7 +176,6 @@ SharePoint sites can't be added to the policy until they have been indexed. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -174,13 +185,15 @@ 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: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -190,6 +203,9 @@ 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`. @@ -199,7 +215,6 @@ 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 @@ -209,6 +224,9 @@ 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. @@ -218,7 +236,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -228,6 +245,9 @@ 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,7 +256,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -246,6 +265,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter specifies the existing mailboxes to remove from the policy. Valid values are: - A mailbox @@ -264,7 +286,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -274,13 +295,15 @@ Accept wildcard characters: False ``` ### -RemovePublicFolderLocation + +> Applicable: Security & Compliance + The RemovePublicFolderLocation parameter specifies that you want to remove all public folders from the preservation policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -290,6 +313,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocation + +> Applicable: Security & Compliance + The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites when you aren't using 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"`. @@ -298,7 +324,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -308,13 +333,15 @@ 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/exchange/Set-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-HoldComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md index e86f4d51b9..faafb800e9 100644 --- a/exchange/exchange-ps/exchange/Set-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-holdcompliancerule applicable: Security & Compliance -title: Set-HoldComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-holdcompliancerule +schema: 2.0.0 +title: Set-HoldComplianceRule --- # Set-HoldComplianceRule @@ -51,6 +52,9 @@ This example changes the hold duration for the existing preservation rule named ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the preservation rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the preservation rule that you want to modify. Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -71,13 +74,15 @@ 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 @@ -87,6 +92,9 @@ 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`. @@ -96,7 +104,6 @@ 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 @@ -106,6 +113,9 @@ 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". @@ -114,7 +124,6 @@ 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 @@ -124,6 +133,9 @@ 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". @@ -132,7 +144,6 @@ 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 @@ -142,6 +153,9 @@ 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). @@ -150,7 +164,6 @@ 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 @@ -160,13 +173,15 @@ 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 @@ -176,6 +191,9 @@ 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. @@ -185,7 +203,6 @@ The HoldContent parameter specifies the hold duration for the preservation rule. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -195,6 +212,9 @@ 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, Months or Years. - Days @@ -207,7 +227,6 @@ 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 @@ -217,13 +236,15 @@ 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/exchange/Set-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md index 8c66cec8fe..ebe3f75eb3 100644 --- a/exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedconnectionfilterpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-HostedConnectionFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedconnectionfilterpolicy +schema: 2.0.0 +title: Set-HostedConnectionFilterPolicy --- # Set-HostedConnectionFilterPolicy @@ -61,6 +62,9 @@ This example modifies the connection filter policy named Default with the follow ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the connection filter policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -73,7 +77,6 @@ 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: True Position: 1 @@ -83,13 +86,15 @@ 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 ("). The maximum length is 255 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -99,13 +104,15 @@ Accept wildcard characters: False ``` ### -ConfigurationXmlRaw + +> 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 @@ -115,6 +122,9 @@ 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`. @@ -124,7 +134,6 @@ 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 @@ -134,13 +143,15 @@ Accept wildcard characters: False ``` ### -EnableSafeList + +> 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 @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -IPAllowList + +> Applicable: Exchange Online, Exchange Online Protection + The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify won't be identified as spam, despite any other spam characteristics of the messages. Valid values are: - Single IP address: For example, 192.168.1.1. @@ -164,7 +178,6 @@ You can specify multiple IP addresses of the same type separated by commas. For Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -174,6 +187,9 @@ Accept wildcard characters: False ``` ### -IPBlockList + +> Applicable: Exchange Online, Exchange Online Protection + The IPBlockList parameter specifies IP addresses from which messages are never allowed. Messages from the IP addresses you specify are blocked without any further spam scanning. Valid values are: - Single IP address: For example, 192.168.1.1. @@ -188,7 +204,6 @@ You can specify multiple IP addresses of the same type separated by commas. For Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -198,13 +213,15 @@ Accept wildcard characters: False ``` ### -MakeDefault + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -214,13 +231,15 @@ 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/exchange/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md index d8cfd90e6b..126adcee18 100644 --- a/exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedcontentfilterpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-HostedContentFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedcontentfilterpolicy +schema: 2.0.0 +title: Set-HostedContentFilterPolicy --- # Set-HostedContentFilterPolicy @@ -102,6 +103,9 @@ This example modifies the spam filter policy named Contoso Executives with the f ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the spam filter policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -112,7 +116,6 @@ The Identity parameter specifies the spam filter policy that you want to modify. Type: HostedContentFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -122,6 +125,9 @@ 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 @@ -141,7 +147,6 @@ 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 @@ -151,13 +156,15 @@ 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 @@ -167,6 +174,9 @@ 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). @@ -179,7 +189,6 @@ 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 @@ -189,6 +198,9 @@ 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). @@ -201,7 +213,6 @@ 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 @@ -211,6 +222,9 @@ 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). @@ -223,7 +237,6 @@ 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 @@ -233,6 +246,9 @@ 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). @@ -245,7 +261,6 @@ 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 @@ -255,6 +270,9 @@ 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 @@ -271,7 +289,6 @@ 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 @@ -281,6 +298,9 @@ 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. @@ -295,7 +315,6 @@ 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 @@ -305,6 +324,9 @@ 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). @@ -313,7 +335,6 @@ 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 @@ -323,6 +344,9 @@ 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`. @@ -332,7 +356,6 @@ 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 @@ -342,13 +365,15 @@ 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 @@ -358,13 +383,15 @@ 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 @@ -374,6 +401,9 @@ 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. @@ -383,7 +413,6 @@ 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 @@ -393,6 +422,9 @@ 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. @@ -402,7 +434,6 @@ 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 @@ -412,13 +443,15 @@ 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 @@ -428,13 +461,15 @@ 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 @@ -444,13 +479,15 @@ 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 @@ -460,12 +497,14 @@ 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 @@ -475,13 +514,15 @@ 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 @@ -491,13 +532,15 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationLimit + +> 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 @@ -507,6 +550,9 @@ 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. @@ -516,7 +562,6 @@ 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 @@ -526,6 +571,9 @@ 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 @@ -542,7 +590,6 @@ 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 @@ -552,6 +599,9 @@ 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). @@ -565,7 +615,6 @@ 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 @@ -575,6 +624,9 @@ 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 @@ -591,7 +643,6 @@ 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 @@ -601,6 +652,9 @@ 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. @@ -611,7 +665,6 @@ 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 @@ -621,6 +674,9 @@ 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. @@ -631,7 +687,6 @@ 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 @@ -641,6 +696,9 @@ 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. @@ -651,7 +709,6 @@ 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 @@ -661,6 +718,9 @@ 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. @@ -671,7 +731,6 @@ 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 @@ -681,6 +740,9 @@ 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. @@ -690,7 +752,6 @@ 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 @@ -700,6 +761,9 @@ 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, HighConfidencePhish. @@ -713,7 +777,6 @@ 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 @@ -723,6 +786,9 @@ 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. @@ -739,7 +805,6 @@ To empty the list, use the value $null. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -749,6 +814,9 @@ Accept wildcard characters: False ``` ### -MakeDefault + +> Applicable: Exchange Online, Exchange Online Protection + The MakeDefault switch makes the specified spam filter policy the default spam filter policy. You don't need to specify a value with this switch. The default spam filter policy is applied to everyone (no corresponding spam filter rule), can't be renamed, and has the unmodifiable priority value Lowest (the default policy is always applied last). @@ -757,7 +825,6 @@ The default spam filter policy is applied to everyone (no corresponding spam fil Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -767,6 +834,9 @@ 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. @@ -777,7 +847,6 @@ 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 @@ -787,6 +856,9 @@ 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. @@ -797,7 +869,6 @@ 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 @@ -807,6 +878,9 @@ 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. @@ -817,7 +891,6 @@ 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 @@ -827,6 +900,9 @@ 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. @@ -837,7 +913,6 @@ 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 @@ -847,6 +922,9 @@ 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. @@ -857,7 +935,6 @@ 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 @@ -867,6 +944,9 @@ 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. @@ -876,7 +956,6 @@ 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 @@ -886,6 +965,9 @@ 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. @@ -896,7 +978,6 @@ 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 @@ -906,6 +987,9 @@ 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. @@ -915,7 +999,6 @@ 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 @@ -925,6 +1008,9 @@ 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. @@ -935,7 +1021,6 @@ 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 @@ -945,6 +1030,9 @@ 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. @@ -955,7 +1043,6 @@ 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 @@ -965,6 +1052,9 @@ 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. @@ -974,7 +1064,6 @@ 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 @@ -984,6 +1073,9 @@ 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. @@ -994,7 +1086,6 @@ 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 @@ -1004,6 +1095,9 @@ 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 @@ -1017,7 +1111,6 @@ 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 @@ -1027,6 +1120,9 @@ 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 @@ -1043,7 +1139,6 @@ 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 @@ -1053,6 +1148,9 @@ 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. @@ -1066,7 +1164,6 @@ 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 @@ -1076,6 +1173,9 @@ 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. @@ -1087,7 +1187,6 @@ 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 @@ -1097,6 +1196,9 @@ 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 @@ -1113,7 +1215,6 @@ 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 @@ -1123,6 +1224,9 @@ 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 @@ -1136,7 +1240,6 @@ 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 @@ -1146,6 +1249,9 @@ 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. @@ -1162,7 +1268,6 @@ To empty the list, use the value $null. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1172,6 +1277,9 @@ 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). @@ -1185,7 +1293,6 @@ 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 @@ -1195,6 +1302,9 @@ 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 @@ -1211,7 +1321,6 @@ 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 @@ -1221,6 +1330,9 @@ 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. @@ -1232,7 +1344,6 @@ 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 @@ -1242,6 +1353,9 @@ 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. @@ -1252,7 +1366,6 @@ 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 @@ -1262,6 +1375,9 @@ 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. @@ -1272,7 +1388,6 @@ 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 @@ -1282,13 +1397,15 @@ 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/exchange/Set-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md index 991cf73ca1..7319501685 100644 --- a/exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedcontentfilterrule applicable: Exchange Online, Exchange Online Protection -title: Set-HostedContentFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedcontentfilterrule +schema: 2.0.0 +title: Set-HostedContentFilterRule --- # Set-HostedContentFilterRule @@ -55,6 +56,9 @@ This example adds an exception to the 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 modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the spam filter rule that you want to modify. Y Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -75,13 +78,15 @@ 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 @@ -91,6 +96,9 @@ 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`. @@ -100,7 +108,6 @@ 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 @@ -110,13 +117,15 @@ 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 @@ -126,6 +135,9 @@ 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 @@ -141,7 +153,6 @@ 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 @@ -151,6 +162,9 @@ 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 @@ -168,7 +182,6 @@ 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 @@ -178,6 +191,9 @@ 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, you can specify the name, GUID, or distinguished name (DN) of the spam filter policy. @@ -188,7 +204,6 @@ You can't specify the default spam filter policy. And, you can't specify a spam Type: HostedContentFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -198,6 +213,9 @@ Accept wildcard characters: False ``` ### -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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. @@ -206,7 +224,6 @@ Don't use the following characters in the name value: `\ % & * + / = ? { } | < > Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -216,6 +233,9 @@ 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: @@ -230,7 +250,6 @@ 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 @@ -240,13 +259,15 @@ 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 @@ -256,6 +277,9 @@ 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 @@ -271,7 +295,6 @@ 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 @@ -281,6 +304,9 @@ 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 @@ -298,7 +324,6 @@ 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 @@ -308,13 +333,15 @@ 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/exchange/Set-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md index 5a570aaa15..6bfda40fca 100644 --- a/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedoutboundspamfilterpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-HostedOutboundSpamFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedoutboundspamfilterpolicy +schema: 2.0.0 +title: Set-HostedOutboundSpamFilterPolicy --- # Set-HostedOutboundSpamFilterPolicy @@ -55,6 +56,9 @@ This example configures the following settings in the outbound spam filter polic ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the outbound spam filter policy you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the outbound spam filter policy you want to mod Type: HostedOutboundSpamFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -75,6 +78,9 @@ 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. @@ -86,7 +92,6 @@ Type: OutboundRecipientLimitsExceededAction Parameter Sets: (All) Aliases: Accepted values: Alert, BlockUserForToday, BlockUser -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -96,13 +101,15 @@ 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 @@ -112,6 +119,9 @@ 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). @@ -125,7 +135,6 @@ Type: AutoForwardingMode Parameter Sets: (All) Aliases: Accepted values: Automatic, Off, On -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -135,6 +144,9 @@ 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. @@ -143,7 +155,6 @@ 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 @@ -153,6 +164,9 @@ 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. @@ -162,7 +176,6 @@ 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 @@ -172,6 +185,9 @@ 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`. @@ -181,7 +197,6 @@ 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 @@ -191,6 +206,9 @@ 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: @@ -202,7 +220,6 @@ 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 @@ -212,6 +229,9 @@ 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. @@ -222,7 +242,6 @@ 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 @@ -232,13 +251,15 @@ 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](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-1). ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -248,13 +269,15 @@ 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](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-1). ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -264,13 +287,15 @@ 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](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-1). ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -280,13 +305,15 @@ 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/exchange/Set-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md index fd8d912dd6..05a2696d50 100644 --- a/exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedoutboundspamfilterrule applicable: Exchange Online, Exchange Online Protection -title: Set-HostedOutboundSpamFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hostedoutboundspamfilterrule +schema: 2.0.0 +title: Set-HostedOutboundSpamFilterRule --- # Set-HostedOutboundSpamFilterRule @@ -52,6 +53,9 @@ This example adds an exception to the existing rule named Contoso Executives. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the outbound spam filter rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -62,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ 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 @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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 @@ -122,7 +132,6 @@ 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 @@ -132,6 +141,9 @@ 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 @@ -147,7 +159,6 @@ 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 @@ -157,13 +168,15 @@ 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 @@ -173,6 +186,9 @@ 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 @@ -188,7 +204,6 @@ 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 @@ -198,6 +213,9 @@ 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 @@ -213,7 +231,6 @@ 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 @@ -223,6 +240,9 @@ 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: @@ -237,7 +257,6 @@ 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: False Position: Named @@ -247,6 +266,9 @@ Accept wildcard characters: False ``` ### -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: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. @@ -255,7 +277,6 @@ Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -265,6 +286,9 @@ 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: @@ -279,7 +303,6 @@ 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 @@ -289,13 +312,15 @@ 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 @@ -305,13 +330,15 @@ 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/exchange/Set-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-HybridConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md index 7b0b227234..83e475593d 100644 --- a/exchange/exchange-ps/exchange/Set-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-hybridconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-HybridConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-hybridconfiguration +schema: 2.0.0 +title: Set-HybridConfiguration --- # Set-HybridConfiguration @@ -72,6 +73,9 @@ This example specifies that the hybrid deployment uses a defined TLS certificate ## PARAMETERS ### -ClientAccessServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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: @@ -86,7 +90,6 @@ You can specify multiple servers 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 @@ -96,6 +99,9 @@ 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,7 +111,6 @@ 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 @@ -115,13 +120,15 @@ 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,6 +138,9 @@ 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. @@ -139,7 +149,6 @@ 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 @@ -149,6 +158,9 @@ 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. @@ -157,7 +169,6 @@ 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 @@ -167,6 +178,9 @@ 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. @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter has been deprecated and is no longer used. There can be only one HybridConfiguration object in an Exchange organization. @@ -202,7 +218,6 @@ There can be only one HybridConfiguration object in an Exchange organization. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -212,13 +227,15 @@ 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 @@ -228,6 +245,9 @@ 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). @@ -243,7 +263,6 @@ The value of this parameter must be blank ($null) when you use the EdgeTransport Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -253,6 +272,9 @@ 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 be used as the certificate for hybrid deployment secure message transport. This certificate cannot be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter. @@ -261,7 +283,6 @@ The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -271,6 +292,9 @@ 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). @@ -286,7 +310,6 @@ The value of this parameter must be blank ($null) when you use the EdgeTransport Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -296,6 +319,9 @@ 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. @@ -306,7 +332,6 @@ 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 @@ -316,6 +341,9 @@ 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. @@ -329,7 +357,6 @@ 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 @@ -339,6 +366,9 @@ 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. @@ -351,7 +381,6 @@ You can specify multiple servers separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -361,13 +390,15 @@ 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 @@ -377,6 +408,9 @@ 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 externally accessible from the Internet on port 25. The accepted values for the EdgeTransportServers parameter are either the full or short computer name of an Edge Transport server, for example, either edge.corp.contoso.com or EDGE. Separate server names with a comma if defining more than one Edge Transport server. When configuring the EdgeTransportServers parameter, you must configure the ReceivingTransportServers and SendingTransportServers parameter values to $null. @@ -385,7 +419,6 @@ When configuring the EdgeTransportServers parameter, you must configure the Rece Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-IPAllowListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-IPAllowListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md index 0c7a6349a0..77c8120243 100644 --- a/exchange/exchange-ps/exchange/Set-IPAllowListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPAllowListConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistconfig +schema: 2.0.0 +title: Set-IPAllowListConfig --- # Set-IPAllowListConfig @@ -47,6 +48,9 @@ This example configures connection filtering to use the IP Allow list on message ## 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`. @@ -56,7 +60,6 @@ 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,6 +69,9 @@ 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. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the IP Allow list is used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. By default, the IP Allow list is used for content filtering. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -100,13 +107,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by the IP Allow list. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by the IP Allow list. ```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,13 +125,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by the IP Allow list. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by the IP Allow list. Authenticated partner messages aren't considered internal mail. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,13 +143,15 @@ 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/exchange/Set-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-IPAllowListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md index 4ede592a05..decf042112 100644 --- a/exchange/exchange-ps/exchange/Set-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPAllowListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistprovider +schema: 2.0.0 +title: Set-IPAllowListProvider --- # Set-IPAllowListProvider @@ -57,6 +58,9 @@ This example sets the priority to 1 for the existing IP Allow list provider name ## 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 modify. You can use any value that uniquely identifies the IP Allow list provider. For example: - Name @@ -67,7 +71,6 @@ The Identity parameter specifies the IP Allow list provider that you want to mod Type: IPAllowListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -77,13 +80,15 @@ 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 @@ -93,13 +98,15 @@ 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 @@ -109,6 +116,9 @@ 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`. @@ -118,7 +128,6 @@ 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 @@ -128,6 +137,9 @@ 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. @@ -136,7 +148,6 @@ 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 @@ -146,13 +157,15 @@ 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 agent queries the IP Allow list provider according to the priority set for this IP Allow list provider configuration. Valid input for this parameter is $true or $false. The default value is $true. By default, the Connection Filtering agent queries the IP Allow list provider according to the priority set for this IP Allow list provider configuration. ```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,6 +175,9 @@ 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. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -172,7 +188,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -182,13 +197,15 @@ 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: False Position: Named @@ -198,13 +215,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -214,6 +233,9 @@ 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've configured. 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 you've 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 added first is incremented by 1. @@ -222,7 +244,6 @@ 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 @@ -232,13 +253,15 @@ 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/exchange/Set-IPAllowListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md index 214711a0f1..7943a7f8e1 100644 --- a/exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistprovidersconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPAllowListProvidersConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipallowlistprovidersconfig +schema: 2.0.0 +title: Set-IPAllowListProvidersConfig --- # Set-IPAllowListProvidersConfig @@ -47,6 +48,9 @@ This example configures connection filtering to use IP Allow list providers on m ## 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`. @@ -56,7 +60,6 @@ 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,6 +69,9 @@ 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. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether IP Allow list providers are used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. The default value is $true. By default, IP Allow list providers are used for content filtering. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -100,13 +107,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by IP Allow list providers. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by IP Allow list providers. ```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,13 +125,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by IP Allow list providers. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by IP Allow list providers. Authenticated partner messages aren't considered internal mail. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,13 +143,15 @@ 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/exchange/Set-IPBlockListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-IPBlockListConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md index af8ccda55d..1c6c0c8a64 100644 --- a/exchange/exchange-ps/exchange/Set-IPBlockListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPBlockListConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistconfig +schema: 2.0.0 +title: Set-IPBlockListConfig --- # Set-IPBlockListConfig @@ -49,6 +50,9 @@ This example configures connection filtering to use the IP Block list on message ## 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`. @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ 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. @@ -76,7 +82,6 @@ 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 @@ -86,13 +91,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the IP Block list is used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. By default, the IP Block list is used for content filtering. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -102,13 +109,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by the IP Block list. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by the IP Block list. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,13 +127,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by the IP Block list. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by the IP Block list. Authenticated partner messages aren't considered internal mail. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -134,13 +145,15 @@ Accept wildcard characters: False ``` ### -MachineEntryRejectionResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MachineEntryRejectionResponse parameter specifies customized text in the non-delivery report (NDR) for messages that are blocked by connection filtering due to IP addresses in the IP Block list that were added by sender reputation. The value can't exceed 240 characters. If the value contains spaces, enclose the value in double quotation marks ("). ```yaml Type: AsciiString Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,13 +163,15 @@ Accept wildcard characters: False ``` ### -StaticEntryRejectionResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The StaticEntryRejectionResponse parameter specifies a customized text in the NDR for messages that are blocked by connection filtering due to IP addresses in the IP Block list. The value can't exceed 240 characters. If the value contains spaces, enclose the value in double quotation marks ("). ```yaml Type: AsciiString Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -166,13 +181,15 @@ 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/exchange/Set-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-IPBlockListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md index f7394da090..60f1eeddd7 100644 --- a/exchange/exchange-ps/exchange/Set-IPBlockListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPBlockListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistprovider +schema: 2.0.0 +title: Set-IPBlockListProvider --- # Set-IPBlockListProvider @@ -58,6 +59,9 @@ This example sets the priority value to 1 for the IP Block 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 Block list provider that you want to modify. You can use any value that uniquely identifies the IP Block list provider. For example: - Name @@ -68,7 +72,6 @@ The Identity parameter specifies the IP Block list provider that you want to mod Type: IPBlockListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -78,13 +81,15 @@ 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 @@ -94,13 +99,15 @@ 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 @@ -110,6 +117,9 @@ 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`. @@ -119,7 +129,6 @@ 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 @@ -129,6 +138,9 @@ 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. @@ -137,7 +149,6 @@ 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 @@ -147,13 +158,15 @@ 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 @@ -163,6 +176,9 @@ 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. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -173,7 +189,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -183,13 +198,15 @@ 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: False Position: Named @@ -199,13 +216,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -215,6 +234,9 @@ 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. @@ -223,7 +245,6 @@ 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 @@ -233,6 +254,9 @@ 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". @@ -241,7 +265,6 @@ 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 @@ -251,13 +274,15 @@ 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/exchange/Set-IPBlockListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md index 50419ac6d6..0e3d180b21 100644 --- a/exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistprovidersconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-IPBlockListProvidersConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ipblocklistprovidersconfig +schema: 2.0.0 +title: Set-IPBlockListProvidersConfig --- # Set-IPBlockListProvidersConfig @@ -58,6 +59,9 @@ This example makes the following changes to the list of bypassed recipients: ## PARAMETERS ### -BypassedRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedRecipients parameter specifies the email addresses of internal recipients that are exempted from filtering by IP Block list providers. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -68,7 +72,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -78,6 +81,9 @@ 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,7 +93,6 @@ 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,6 +102,9 @@ 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. @@ -105,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether IP Block list providers are used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. The default value is $true. By default, IP Block list providers are used for content filtering. ```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,13 +140,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by IP Block list providers. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by IP Bock list providers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,13 +158,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by IP Block list providers. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by IP Block list providers. Authenticated partner messages aren't considered internal mail. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -163,13 +176,15 @@ 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/exchange/Set-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-IRMConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md index 76f288110e..8fef1baf42 100644 --- a/exchange/exchange-ps/exchange/Set-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-irmconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-IRMConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-irmconfiguration +schema: 2.0.0 +title: Set-IRMConfiguration --- # Set-IRMConfiguration @@ -81,6 +82,9 @@ This example enables licensing for external messages. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The Identity parameter specifies the organization's IRM configuration object to modify. The valid value for this parameter is "ControlPoint Configuration". @@ -89,7 +93,6 @@ The Identity parameter specifies the organization's IRM configuration object to Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -99,6 +102,9 @@ Accept wildcard characters: False ``` ### -AutomaticServiceUpdateEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AutomaticServiceUpdateEnabled parameter specifies whether to allow the automatic addition of new features within Azure Information Protection for your cloud-based organization. Valid values are: @@ -110,7 +116,6 @@ The AutomaticServiceUpdateEnabled parameter specifies whether to allow the autom Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -120,6 +125,9 @@ Accept wildcard characters: False ``` ### -AzureRMSLicensingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AzureRMSLicensingEnabled parameter specifies whether the Exchange Online organization can to connect directly to Azure Rights Management. Valid values are: @@ -131,7 +139,6 @@ The AzureRMSLicensingEnabled parameter specifies whether the Exchange Online org Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -141,6 +148,9 @@ Accept wildcard characters: False ``` ### -ClientAccessServerEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ClientAccessServerEnabled parameter specifies whether Exchange Client Access servers are allowed to authenticate clients that do not have direct access to AD RMS (for example, Outlook on the web, Exchange ActiveSync or remote Outlook Anywhere clients). Valid values are: @@ -152,7 +162,6 @@ The ClientAccessServerEnabled parameter specifies whether Exchange Client Access Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -162,6 +171,9 @@ 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`. @@ -171,7 +183,6 @@ 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 @@ -181,6 +192,9 @@ Accept wildcard characters: False ``` ### -DecryptAttachmentForEncryptOnly + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The DecryptAttachmentForEncryptOnly parameter specifies whether mail recipients have unrestricted rights on the attachment or not for Encrypt-only mails sent using Microsoft Purview Message Encryption. Valid values are: @@ -194,7 +208,6 @@ This parameter replaces the deprecated DecryptAttachmentFromPortal parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -204,6 +217,9 @@ 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. @@ -212,7 +228,6 @@ 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 @@ -222,6 +237,9 @@ Accept wildcard characters: False ``` ### -EDiscoverySuperUserEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EDiscoverySuperUserEnabled parameter specifies whether members of the Discovery Management role group can access IRM-protected messages in a discovery mailbox that were returned by a discovery search. Valid values are: - $true: Members of the Discovery Management role group can access IRM-protected messages in discovery mailboxes. @@ -233,7 +251,6 @@ For more information about In-Place eDiscovery and IRM-protected messages, see [ 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 @@ -243,6 +260,9 @@ Accept wildcard characters: False ``` ### -EnablePdfEncryption + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EnablePdfEncryption parameter specifies whether to enable the encryption of PDF attachments using Microsoft Purview Message Encryption. Valid values are: @@ -254,7 +274,6 @@ The EnablePdfEncryption parameter specifies whether to enable the encryption of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -264,6 +283,9 @@ Accept wildcard characters: False ``` ### -EnablePortalTrackingLogs + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. **Note**: This parameter is available only in organizations with Microsoft Purview Advanced Message Encryption. For more information, see [Advanced Message Encryption](https://learn.microsoft.com/purview/ome-advanced-message-encryption). @@ -277,7 +299,6 @@ The EnablePortalTrackingLogs parameter specifies whether to turn on auditing for Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -287,6 +308,9 @@ Accept wildcard characters: False ``` ### -ExternalLicensingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExternalLicensingEnabled parameter specifies whether Exchange will try to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server will devote excessive resources to validating signatures and decrypting messages, even if the keys aren't valid. @@ -300,7 +324,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -310,6 +333,9 @@ 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. Use this switch to hide the confirmation prompt when you modify the InternalLicensingEnabled parameter. @@ -318,7 +344,6 @@ Use this switch to hide the confirmation prompt when you modify the InternalLice 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 @@ -328,6 +353,9 @@ Accept wildcard characters: False ``` ### -InternalLicensingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note**: In Exchange Online, this parameter affects both internal and external messages. In on-premises Exchange, this parameter only affects internal messages. The InternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to internal recipients. Valid values are: @@ -339,7 +367,6 @@ The InternalLicensingEnabled parameter specifies whether to enable IRM features 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 @@ -349,6 +376,9 @@ Accept wildcard characters: False ``` ### -JournalReportDecryptionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The JournalReportDecryptionEnabled parameter specifies whether to enable journal report decryption. Valid values are: - $true: Journal report encryption is enabled. A decrypted copy of the IRM-protected message is attached to the journal report. This is the default value. Note that journal report decryption requires additional configuration on AD RMS servers. For more information, see [Journal report decryption](https://learn.microsoft.com/exchange/journal-report-decryption-exchange-2013-help). @@ -358,7 +388,6 @@ The JournalReportDecryptionEnabled parameter specifies whether to enable journal 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 @@ -368,6 +397,9 @@ Accept wildcard characters: False ``` ### -LicensingLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LicensingLocation parameter specifies the RMS licensing URLs. You can specify multiple URL values separated by commas. Typically, in on-premises Exchange, you only need to use this parameter in cross-forest deployments of AD RMS licensing servers. @@ -378,7 +410,6 @@ Typically, in on-premises Exchange, you only need to use this parameter in cross 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 @@ -388,6 +419,9 @@ Accept wildcard characters: False ``` ### -RefreshServerCertificates + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RefreshServerCertificates switch clears all Rights Account Certificates (RACs), Computer Licensor Certificates (CLCs), and cached AD RMS templates from all Exchange servers in the organization. You don't need to specify a value with this switch. @@ -398,7 +432,6 @@ Clearing RACs, CLCs, and cached templates might be required during troubleshooti Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -408,6 +441,9 @@ Accept wildcard characters: False ``` ### -RejectIfRecipientHasNoRights + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RejectIfRecipientHasNoRights Description }} @@ -416,7 +452,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -426,6 +461,9 @@ Accept wildcard characters: False ``` ### -RMSOnlineKeySharingLocation + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RMSOnlineKeySharingLocation parameter specifies the Azure Rights Management URL that's used to get the trusted publishing domain (TPD) for the Exchange Online organization. @@ -434,7 +472,6 @@ The RMSOnlineKeySharingLocation parameter specifies the Azure Rights Management Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -444,6 +481,9 @@ Accept wildcard characters: False ``` ### -SearchEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SearchEnabled parameter specifies whether to enable searching of IRM-encrypted messages in Outlook on the web (formerly known as Outlook Web App). Valid values are: - $true: Searching IRM-encrypted messages in Outlook on the web is enabled. This is the default value. @@ -453,7 +493,6 @@ The SearchEnabled parameter specifies whether to enable searching of IRM-encrypt 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 @@ -463,6 +502,9 @@ Accept wildcard characters: False ``` ### -SimplifiedClientAccessDoNotForwardDisabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The SimplifiedClientAccessDoNotForwardDisabled parameter specifies whether to disable **Do not forward** in Outlook on the web. Valid values are: @@ -474,7 +516,6 @@ The SimplifiedClientAccessDoNotForwardDisabled parameter specifies whether to di Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -484,6 +525,9 @@ Accept wildcard characters: False ``` ### -SimplifiedClientAccessEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The SimplifiedClientAccessEnabled parameter specifies whether to enable the Protect button in Outlook on the web. Valid values are: @@ -495,7 +539,6 @@ The SimplifiedClientAccessEnabled parameter specifies whether to enable the Prot Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -505,6 +548,9 @@ Accept wildcard characters: False ``` ### -SimplifiedClientAccessEncryptOnlyDisabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The SimplifiedClientAccessEncryptOnlyDisabled parameter specifies whether to disable **Encrypt only** in Outlook on the web. Valid values are: @@ -516,7 +562,6 @@ The SimplifiedClientAccessEncryptOnlyDisabled parameter specifies whether to dis Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -526,6 +571,9 @@ Accept wildcard characters: False ``` ### -TransportDecryptionSetting + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TransportDecryptionSetting parameter specifies the transport decryption configuration. Valid values are: - Disabled: Transport decryption is disabled for internal and external messages. @@ -536,7 +584,6 @@ The TransportDecryptionSetting parameter specifies the transport decryption conf Type: TransportDecryptionSetting 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 @@ -546,13 +593,15 @@ 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/exchange/Set-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ImapSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md index d6a70cad13..7a84747e66 100644 --- a/exchange/exchange-ps/exchange/Set-ImapSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-imapsettings applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ImapSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-imapsettings +schema: 2.0.0 +title: Set-ImapSettings --- # Set-ImapSettings @@ -102,6 +103,9 @@ This example specifies the certificate that contains mail.contoso.com is used to ## PARAMETERS ### -AuthenticatedConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthenticatedConnectionTimeout parameter specifies the period of time to wait before closing an idle authenticated connection. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -112,7 +116,6 @@ Valid values are 00:00:30 to 1:00:00. The default setting is 00:30:00 (30 minute Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -122,13 +125,15 @@ Accept wildcard characters: False ``` ### -Banner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Banner parameter specifies the text string that's displayed to connecting IMAP4 clients. The default value is: The Microsoft Exchange IMAP4 service is ready. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,6 +143,9 @@ Accept wildcard characters: False ``` ### -CalendarItemRetrievalOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarItemRetrievalOption parameter specifies how calendar items are presented to IMAP4 clients. Valid values are: - 0 or iCalendar. This is the default value. @@ -151,7 +159,6 @@ If you specify 3 or Custom, you need to specify a value for the OwaServerUrl par Type: CalendarItemRetrievalOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -161,6 +168,9 @@ 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`. @@ -170,7 +180,6 @@ 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 @@ -180,13 +189,15 @@ 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 @@ -196,6 +207,9 @@ Accept wildcard characters: False ``` ### -EnableExactRFC822Size + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients. Valid values are: - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your IMAP4 clients. @@ -205,7 +219,6 @@ The EnableExactRFC822Size parameter specifies how message sizes are presented to Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -215,6 +228,9 @@ Accept wildcard characters: False ``` ### -EnableGSSAPIAndNTLMAuth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are: - $true: NTLM for IMAP4 connections is enabled. This is the default value. @@ -224,7 +240,6 @@ The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Inte Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -234,6 +249,9 @@ Accept wildcard characters: False ``` ### -EnforceCertificateErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnforceCertificateErrors parameter specifies whether to enforce valid Secure Sockets Layer (SSL) certificate validation failures. Valid values are: The default setting is $false. @@ -245,7 +263,6 @@ The default setting is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,6 +272,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used. Valid values are: - None: Extended Protection for Authentication isn't used. This is the default value. @@ -267,7 +287,6 @@ Extended Protection for Authentication enhances the protection and handling of c Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,6 +296,9 @@ Accept wildcard characters: False ``` ### -ExternalConnectionSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by external IMAP4 clients (IMAP4 connections from outside your corporate network). This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). @@ -293,7 +315,6 @@ The combination of encryption methods and ports that are specified for this para Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -303,6 +324,9 @@ Accept wildcard characters: False ``` ### -InternalConnectionSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by internal IMAP4 clients (IMAP4 connections from inside your corporate network). This setting is also used when a IMAP4 connection is forwarded to another Exchange server that's running the Microsoft Exchange IMAP4 service. This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). @@ -319,7 +343,6 @@ The combination of encryption methods and ports that are specified for this para Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -329,6 +352,9 @@ Accept wildcard characters: False ``` ### -LogFileLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogFileLocation parameter specifies the location for the IMAP4 protocol log files. The default location is %ExchangeInstallPath%Logging\\Imap4. This parameter is only meaningful when the ProtocolLogEnabled parameter value is $true. @@ -337,7 +363,6 @@ This parameter is only meaningful when the ProtocolLogEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -347,6 +372,9 @@ Accept wildcard characters: False ``` ### -LogFileRollOverSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogFileRollOverSettings parameter specifies how frequently IMAP4 protocol logging creates a new log file. Valid values are: - 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. @@ -360,7 +388,6 @@ This parameter is only meaningful when the LogPerFileSizeQuota parameter value i Type: LogFileRollOver Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -370,6 +397,9 @@ Accept wildcard characters: False ``` ### -LoginType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LoginType parameter specifies the authentication method for IMAP4 connections. Valid values are: - 1 or PlainTextLogin. @@ -380,7 +410,6 @@ The LoginType parameter specifies the authentication method for IMAP4 connection Type: LoginOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -390,6 +419,9 @@ Accept wildcard characters: False ``` ### -LogPerFileSizeQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogPerFileSizeQuota parameter specifies the maximum size of a IMAP4 protocol log file. When you enter a value, qualify the value with one of the following units: @@ -410,7 +442,6 @@ This parameter is only meaningful when the ProtocolLogEnabled parameter value is Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -420,13 +451,15 @@ Accept wildcard characters: False ``` ### -MaxCommandSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxCommandSize parameter specifies the maximum size in bytes of a single IMAP4 command. Valid values are from 1024 through 16384. The default value is 10240. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -436,13 +469,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionFromSingleIP + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionFromSingleIP parameter specifies the maximum number of IMAP4 connections that are accepted by the Exchange server from a single IP address. Valid values are from 1 through 2147483647. The default value is 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -452,13 +487,15 @@ Accept wildcard characters: False ``` ### -MaxConnections + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnections parameter specifies the maximum number of IMAP4 connections that are accepted by the Exchange server. Valid values are from 1 through 2147483647. The default value is 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -468,13 +505,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionsPerUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionsPerUser parameter specifies the maximum number of IMAP4 connections that are allowed for each user. Valid values are from 1 through 2147483647. The default value is 16. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -484,6 +523,9 @@ Accept wildcard characters: False ``` ### -MessageRetrievalMimeFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are: - 0 or TextOnly. @@ -498,7 +540,6 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages Type: MimeTextFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -508,13 +549,15 @@ Accept wildcard characters: False ``` ### -OwaServerUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaServerUrl parameter specifies the URL that's used to retrieve calendar information for instances of custom Outlook on the web calendar items. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -524,6 +567,9 @@ Accept wildcard characters: False ``` ### -PreAuthenticatedConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PreAuthenticatedConnectionTimeout parameter specifies the period of time to wait before closing an idle IMAP4 connection that isn't authenticated. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -534,7 +580,6 @@ Valid values are00:00:30 to 1:00:00. The default value is 00:01:00 (one minute). Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -544,6 +589,9 @@ Accept wildcard characters: False ``` ### -ProtocolLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLogEnabled parameter specifies whether to enable protocol logging for IMAP4. Valid values are: - $true: IMAP4 protocol logging is enabled. @@ -553,7 +601,6 @@ The ProtocolLogEnabled parameter specifies whether to enable protocol logging fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -563,13 +610,15 @@ Accept wildcard characters: False ``` ### -ProxyTargetPort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProxyTargetPort parameter specifies the port on the Microsoft Exchange IMAP4 Backend service that listens for client connections that are proxied from the Microsoft Exchange IMAP4 service. The default value is 1993. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -579,6 +628,9 @@ 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 @@ -592,7 +644,6 @@ 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 @@ -602,6 +653,9 @@ Accept wildcard characters: False ``` ### -ShowHiddenFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders are visible. Valid values are: - $true: Hidden folders are visible. @@ -611,7 +665,6 @@ The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -621,6 +674,9 @@ Accept wildcard characters: False ``` ### -SSLBindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SSLBindings parameter specifies the IP address and TCP port that's used for IMAP4 connection that's always encrypted by SSL/TLS. This parameter uses the syntax `IPv4OrIPv6Address:Port`. The default value is `[::]:993,0.0.0.0:993`. @@ -633,7 +689,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -643,6 +698,9 @@ Accept wildcard characters: False ``` ### -SuppressReadReceipt + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to IMAP4 clients that have the Send read receipts for messages I send setting configured in their IMAP4 email program. Valid values are: - $true: The sender receives a read receipt only when the recipient opens the message. @@ -652,7 +710,6 @@ The SuppressReadReceipt parameter specifies whether to stop duplicate read recei Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -662,6 +719,9 @@ Accept wildcard characters: False ``` ### -UnencryptedOrTLSBindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UnencryptedOrTLSBindings parameter specifies the IP address and TCP port that's used for unencrypted IMAP4 connections, or IMAP4 connections that are encrypted by using opportunistic TLS (STARTTLS) after the initial unencrypted protocol handshake. This parameter uses the syntax `IPv4OrIPv6Address:Port`. The default value is `[::]:143,0.0.0.0:143`. @@ -674,7 +734,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -684,13 +743,15 @@ 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 @@ -700,6 +761,9 @@ Accept wildcard characters: False ``` ### -X509CertificateName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X509CertificateName parameter specifies the certificate that's used for encrypting IMAP4 client connections. A valid value for this parameter is the FQDN from the ExternalConnectionSettings or InternalConnectionSettings parameters (for example, mail.contoso.com or mailbox01.contoso.com). @@ -712,7 +776,6 @@ If you use a wildcard certificate, you don't need to assign the certificate to t 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/exchange/Set-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-InboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md index 285ba184d1..4c07a6638b 100644 --- a/exchange/exchange-ps/exchange/Set-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-inboundconnector applicable: Exchange Online, Exchange Online Protection -title: Set-InboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-inboundconnector +schema: 2.0.0 +title: Set-InboundConnector --- # Set-InboundConnector @@ -69,13 +70,15 @@ Require that the TLS certificate that is used to encrypt communications contain ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the Inbound connector you want to change. ```yaml Type: InboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -85,6 +88,9 @@ 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. @@ -93,7 +99,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -103,6 +108,9 @@ 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. @@ -116,7 +124,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -126,13 +133,15 @@ 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 @@ -142,6 +151,9 @@ 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`. @@ -151,7 +163,6 @@ 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 @@ -161,6 +172,9 @@ 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. @@ -173,7 +187,6 @@ 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 @@ -183,6 +196,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values: - Partner: The connector services domains that are external to your organization. @@ -192,7 +208,6 @@ The ConnectorType parameter specifies a category for the domains that are servic Type: TenantConnectorType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -202,6 +217,9 @@ 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. @@ -214,7 +232,6 @@ 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,6 +241,9 @@ 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. @@ -233,7 +253,6 @@ 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 @@ -243,13 +262,15 @@ 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 @@ -259,13 +280,15 @@ 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 @@ -275,6 +298,9 @@ 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. @@ -283,7 +309,6 @@ 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 @@ -293,6 +318,9 @@ 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. @@ -302,7 +330,6 @@ 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 @@ -312,13 +339,15 @@ Accept wildcard characters: False ``` ### -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: False Position: Named @@ -328,6 +357,9 @@ 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 @@ -339,7 +371,6 @@ 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 @@ -349,6 +380,9 @@ 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. @@ -360,7 +394,6 @@ 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 @@ -370,6 +403,9 @@ 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. @@ -381,7 +417,6 @@ 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 @@ -391,13 +426,15 @@ 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 @@ -407,6 +444,9 @@ 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. @@ -415,7 +455,6 @@ You can specify multiple domains separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -425,6 +464,9 @@ 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. @@ -439,7 +481,6 @@ IPv6 addresses are not supported. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -449,13 +490,15 @@ 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 @@ -465,6 +508,9 @@ 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. @@ -481,7 +527,6 @@ 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 @@ -491,6 +536,9 @@ 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). This parameter works only for mail flow between two Microsoft 365 organizations, so no other parameters are used. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -501,7 +549,6 @@ 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 @@ -511,13 +558,15 @@ 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/exchange/Set-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-InboxRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md index fbbb29f2cb..c0d8cec05e 100644 --- a/exchange/exchange-ps/exchange/Set-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-inboxrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-InboxRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-inboxrule +schema: 2.0.0 +title: Set-InboxRule --- # Set-InboxRule @@ -113,6 +114,9 @@ This example modifies the action of the existing Inbox rule ProjectContoso. The ## 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 modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -124,7 +128,6 @@ The Identity parameter specifies the Inbox rule that you want to modify. 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 @@ -134,13 +137,15 @@ 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 @@ -150,6 +155,9 @@ 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). @@ -158,7 +166,6 @@ The categories that you specify for this parameter are defined in the mailbox (t 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 @@ -168,6 +175,9 @@ 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 @@ -203,7 +213,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -213,6 +222,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -227,7 +239,6 @@ The corresponding exception parameter to this condition is ExceptIfBodyContainsW 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 @@ -237,6 +248,9 @@ 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`. @@ -246,7 +260,6 @@ 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 @@ -256,6 +269,9 @@ 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: @@ -277,7 +293,6 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -287,6 +302,9 @@ 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 @@ -320,7 +338,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -330,6 +347,9 @@ 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. @@ -339,7 +359,6 @@ The DeleteMessage parameter specifies an action for the Inbox rule that sends me 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 @@ -349,6 +368,9 @@ 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. @@ -357,7 +379,6 @@ 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 @@ -367,6 +388,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -381,7 +405,6 @@ The corresponding condition parameter to this exception is BodyContainsWords. 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 @@ -391,6 +414,9 @@ 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 @@ -411,7 +437,6 @@ The corresponding condition parameter to this exception is FlaggedForAction. 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 @@ -421,6 +446,9 @@ 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 @@ -438,7 +466,6 @@ The corresponding condition parameter to this exception is From. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -448,6 +475,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -462,7 +492,6 @@ The corresponding condition parameter to this exception is FromAddressContainsWo 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 @@ -472,6 +501,9 @@ 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. @@ -483,7 +515,6 @@ The corresponding condition parameter to this exception is HasAttachment. 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 @@ -493,6 +524,9 @@ 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. @@ -501,7 +535,6 @@ The corresponding condition parameter to this exception is HasClassification. Type: MessageClassificationIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -511,6 +544,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -525,7 +561,6 @@ The corresponding condition parameter to this exception is HeaderContainsWords. 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 @@ -535,6 +570,9 @@ 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 @@ -555,7 +593,6 @@ The corresponding condition parameter to this exception is MessageTypeMatches. Type: InboxRuleMessageType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -565,6 +602,9 @@ 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. @@ -576,7 +616,6 @@ The corresponding condition parameter to this exception is MyNameInCcBox. 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 @@ -586,6 +625,9 @@ 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. @@ -597,7 +639,6 @@ The corresponding condition parameter to this exception is MyNameInToBox. 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 @@ -607,6 +648,9 @@ 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. @@ -618,7 +662,6 @@ The corresponding condition parameter to this exception is MyNameInToOrCcBox. 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 @@ -628,6 +671,9 @@ 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. @@ -639,7 +685,6 @@ The corresponding condition parameter to this exception is MyNameNotInToBox. 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 @@ -649,6 +694,9 @@ 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". @@ -659,7 +707,6 @@ The corresponding condition parameter to this exception is ReceivedAfterDate. Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -669,6 +716,9 @@ 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". @@ -679,7 +729,6 @@ The corresponding condition parameter to this exception is ReceivedBeforeDate. Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -689,6 +738,9 @@ 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. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -703,7 +755,6 @@ The corresponding condition parameter to this exception is RecipientAddressConta 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 @@ -713,6 +764,9 @@ 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. @@ -724,7 +778,6 @@ The corresponding condition parameter to this exception is SentOnlyToMe. 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 @@ -734,6 +787,9 @@ 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 @@ -751,7 +807,6 @@ The corresponding condition parameter to this exception is SentTo. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -761,6 +816,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -775,7 +833,6 @@ The corresponding condition parameter to this exception is SubjectContainsWords. 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 @@ -785,6 +842,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -799,7 +859,6 @@ The corresponding condition parameter to this exception is SubjectOrBodyContains 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 @@ -809,6 +868,9 @@ 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 @@ -821,7 +883,6 @@ The corresponding condition parameter to this exception is WithImportance. Type: Importance Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -831,6 +892,9 @@ 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: @@ -851,7 +915,6 @@ The corresponding condition parameter to this exception is WithinSizeRangeMaximu Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -861,6 +924,9 @@ 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: @@ -881,7 +947,6 @@ The corresponding condition parameter to this exception is WithinSizeRangeMinimu Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -891,6 +956,9 @@ 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 @@ -904,7 +972,6 @@ The corresponding condition parameter to this exception is WithSensitivity. Type: Sensitivity Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -914,6 +981,9 @@ 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 @@ -932,7 +1002,6 @@ The FlaggedForAction parameter specifies a condition for the Inbox rule that loo 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 @@ -942,6 +1011,9 @@ 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. @@ -950,7 +1022,6 @@ 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 @@ -960,6 +1031,9 @@ 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 @@ -975,7 +1049,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -985,6 +1058,9 @@ 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 @@ -1000,7 +1076,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1010,6 +1085,9 @@ 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 @@ -1027,7 +1105,6 @@ The corresponding exception parameter to this condition is ExceptIfFrom. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1037,6 +1114,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -1051,7 +1131,6 @@ The corresponding exception parameter to this condition is ExceptIfFromAddressCo 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 @@ -1061,6 +1140,9 @@ 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. @@ -1072,7 +1154,6 @@ The corresponding exception parameter to this condition is ExceptIfHasAttachment 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 @@ -1082,6 +1163,9 @@ 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. @@ -1090,7 +1174,6 @@ The corresponding exception parameter to this condition is ExceptIfHasClassifica Type: MessageClassificationIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1100,6 +1183,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -1114,7 +1200,6 @@ The corresponding exception parameter to this condition is ExceptIfHeaderContain 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 @@ -1124,6 +1209,9 @@ 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 @@ -1141,7 +1229,6 @@ 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 @@ -1151,6 +1238,9 @@ 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. @@ -1160,7 +1250,6 @@ The MarkAsRead parameter specifies an action for the Inbox rule that marks messa 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 @@ -1170,6 +1259,9 @@ 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 @@ -1180,7 +1272,6 @@ The MarkImportance parameter specifies an action for the Inbox rule that marks m Type: Importance Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1190,6 +1281,9 @@ 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 @@ -1210,7 +1304,6 @@ The corresponding exception parameter to this condition is ExceptIfMessageTypeMa Type: InboxRuleMessageType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1220,6 +1313,9 @@ 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: @@ -1241,7 +1337,6 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1251,6 +1346,9 @@ 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. @@ -1262,7 +1360,6 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInCcBox 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 @@ -1272,6 +1369,9 @@ 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. @@ -1283,7 +1383,6 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInToBox 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 @@ -1293,6 +1392,9 @@ 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. @@ -1304,7 +1406,6 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInToOrC 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 @@ -1314,6 +1415,9 @@ 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. @@ -1325,7 +1429,6 @@ The corresponding exception parameter to this condition is ExceptIfMyNameNotInTo 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 @@ -1335,13 +1438,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for 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: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1351,6 +1456,9 @@ 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. @@ -1360,7 +1468,6 @@ The PinMessage parameter specifies an action for the Inbox rule that pins messag Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1370,13 +1477,15 @@ 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: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1386,6 +1495,9 @@ 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". @@ -1396,7 +1508,6 @@ The corresponding exception parameter to this condition is ExceptIfReceivedAfter Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1406,6 +1517,9 @@ 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". @@ -1416,7 +1530,6 @@ The corresponding exception parameter to this condition is ExceptIfReceivedBefor Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1426,6 +1539,9 @@ 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. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -1440,7 +1556,6 @@ The corresponding exception parameter to this condition is ExceptIfRecipientAddr 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 @@ -1450,6 +1565,9 @@ 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 @@ -1465,7 +1583,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1475,6 +1592,9 @@ 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. @@ -1487,7 +1607,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1497,6 +1616,9 @@ 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. @@ -1508,7 +1630,6 @@ The corresponding exception parameter to this condition is ExceptIfSentOnlyToMe. 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 @@ -1518,6 +1639,9 @@ 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 @@ -1535,7 +1659,6 @@ The corresponding exception parameter to this condition is ExceptIfSentTo. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1545,6 +1668,9 @@ Accept wildcard characters: False ``` ### -SoftDeleteMessage + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SoftDeleteMessage Description }} @@ -1553,7 +1679,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1563,6 +1688,9 @@ 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. @@ -1572,7 +1700,6 @@ The StopProcessingRules parameter specifies an action for the Inbox rule that st 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 @@ -1582,6 +1709,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -1596,7 +1726,6 @@ The corresponding exception parameter to this condition is ExceptIfSubjectContai 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 @@ -1606,6 +1735,9 @@ 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 that overwrite any existing entries, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces. @@ -1620,7 +1752,6 @@ The corresponding exception parameter to this condition is ExceptIfSubjectOrBody 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 @@ -1630,13 +1761,15 @@ 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 @@ -1646,6 +1779,9 @@ 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 @@ -1658,7 +1794,6 @@ The corresponding exception parameter to this condition is ExceptIfWithImportanc Type: Importance Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1668,6 +1803,9 @@ 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: @@ -1688,7 +1826,6 @@ The corresponding exception parameter to this condition is ExceptIfWithinSizeRan Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1698,6 +1835,9 @@ 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: @@ -1718,7 +1858,6 @@ The corresponding exception parameter to this condition is ExceptIfWithinSizeRan Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1728,6 +1867,9 @@ 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 @@ -1741,7 +1883,6 @@ The corresponding exception parameter to this condition is ExceptIfWithSensitivi Type: Sensitivity 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/exchange/Set-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-InformationBarrierPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-InformationBarrierPolicy.md index 2fbe4dd044..ab086a847f 100644 --- a/exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-InformationBarrierPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-informationbarrierpolicy applicable: Security & Compliance -title: Set-InformationBarrierPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-informationbarrierpolicy +schema: 2.0.0 +title: Set-InformationBarrierPolicy --- # Set-InformationBarrierPolicy @@ -81,6 +82,9 @@ This example activates the specified inactive information barrier policy. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the information barrier policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -91,7 +95,6 @@ The Identity parameter specifies the information barrier policy that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -101,13 +104,15 @@ 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 @@ -117,13 +122,15 @@ 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 @@ -133,6 +140,9 @@ 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. @@ -141,7 +151,6 @@ 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 @@ -151,13 +160,15 @@ 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 @@ -167,6 +178,9 @@ 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"). @@ -177,7 +191,6 @@ You can't use this parameter with the SegmentsBlocked parameter. Type: MultiValuedProperty Parameter Sets: OrganizationSegmentsAllowed Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -187,13 +200,15 @@ 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: False Position: Named @@ -203,6 +218,9 @@ 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"). @@ -213,7 +231,6 @@ You can't use this parameter with the SegmentsAllowed parameter. Type: MultiValuedProperty Parameter Sets: OrganizationSegmentsBlocked Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -223,6 +240,9 @@ 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 @@ -233,7 +253,6 @@ Type: EopInformationBarrierPolicyState Parameter Sets: (All) Aliases: Accepted values: Inactive, Active -Applicable: Security & Compliance Required: False Position: Named @@ -243,13 +262,15 @@ 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/exchange/Set-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md index 5216746dff..d7251ebd07 100644 --- a/exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-intraorganizationconnector applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-IntraOrganizationConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-intraorganizationconnector +schema: 2.0.0 +title: Set-IntraOrganizationConnector --- # Set-IntraOrganizationConnector @@ -49,6 +50,9 @@ This example disables the Intra-Organization connector named "MainCloudConnector ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Identity parameter specifies the Intra-Organization connector that you want to modify. You can use any value that uniquely identifies the connector. For example: - Name @@ -59,7 +63,6 @@ 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, Exchange Online Protection Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 used for the Autodiscover service for the domain configured in the IntraOrganization Connector. This parameter is automatically populated with the TargetAutodiscoverEpr value from the Get-FederationInformation cmdlet for the defined domain. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -104,6 +111,9 @@ 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. @@ -112,7 +122,6 @@ 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,6 +131,9 @@ 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. @@ -130,7 +142,6 @@ 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 @@ -140,13 +151,15 @@ 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. The 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. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -156,6 +169,9 @@ 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. @@ -164,7 +180,6 @@ 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 @@ -174,13 +189,15 @@ 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/exchange/Set-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-JournalRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md index 3c8d9f1233..37bc6a4450 100644 --- a/exchange/exchange-ps/exchange/Set-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-journalrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-JournalRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-journalrule +schema: 2.0.0 +title: Set-JournalRule --- # Set-JournalRule @@ -56,6 +57,9 @@ This example modifies the journal email address for all journal rules. The Get-J ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the name or GUID of the rule you want to modify. The Identity parameter is a positional parameter. When using positional parameters in a command, you can omit the parameter label. @@ -64,7 +68,6 @@ The Identity parameter is a positional parameter. When using positional paramete 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 @@ -74,6 +77,9 @@ 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`. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ 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,7 +109,6 @@ 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,6 +118,9 @@ Accept wildcard characters: False ``` ### -JournalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The JournalEmailAddress parameter specifies a journal recipient. Journal reports for the specified rule are sent to the journal recipient. You can use any value that uniquely identifies the recipient. For example: - Name @@ -124,7 +134,6 @@ The JournalEmailAddress parameter specifies a journal recipient. Journal reports Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -134,13 +143,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the journal rule. The name of the rule can be up to 64 characters. ```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 @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -Recipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recipient parameter specifies the SMTP address of a mailbox, contact, or distribution group to journal. If you specify a distribution group, all recipients in that distribution group are journaled. All messages sent to or received from a recipient are journaled. To journal messages from all recipients, use the value $null for this parameter. @@ -158,7 +172,6 @@ To journal messages from all recipients, use the value $null for this parameter. 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 @@ -168,6 +181,9 @@ Accept wildcard characters: False ``` ### -Scope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Scope parameter specifies the scope of email messages to which the journal rule is applied. You can use the following values: - Global: Global rules process all email messages that pass through a Transport service. This includes email messages that were already processed by the external and internal rules. @@ -178,7 +194,6 @@ The Scope parameter specifies the scope of email messages to which the journal r Type: JournalRuleScope Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -188,13 +203,15 @@ 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/exchange/Set-Label.md b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-Label.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Label.md index 8424874e92..d33e751d3b 100644 --- a/exchange/exchange-ps/exchange/Set-Label.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/policy-and-compliance/set-label applicable: Security & Compliance -title: Set-Label -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/policy-and-compliance/set-label +schema: 2.0.0 +title: Set-Label --- # Set-Label @@ -125,6 +126,9 @@ This example removes the localized label name and label Tooltips for "Label1" in ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the sensitivity label that you want to modify. You can use any value that uniquely identifies the label. For example: - Name @@ -135,7 +139,6 @@ The Identity parameter specifies the sensitivity label that you want to modify. Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -145,6 +148,9 @@ Accept wildcard characters: False ``` ### -AdvancedSettings + +> Applicable: Security & Compliance + The AdvancedSettings parameter enables specific features and capabilities for a sensitivity label. Specify this parameter with the identity (name or GUID) of the sensitivity label, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value. @@ -177,7 +183,6 @@ For more information to help you configure advanced settings for a label, see [P Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -187,6 +192,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterAlignment + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterAlignment parameter specifies the footer alignment. Valid values are: - Left @@ -199,7 +207,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -209,6 +216,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterEnabled + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterEnabled parameter enables or disables the Apply Content Marking Footer action for the label. Valid values are: - $true: The Apply Content Marking Footer action is enabled. @@ -218,7 +228,6 @@ The ApplyContentMarkingFooterEnabled parameter enables or disables the Apply Con Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -228,6 +237,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontColor + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontColor parameter specifies the color of the footer text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -236,7 +248,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -246,6 +257,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontName + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontName parameter specifies the font of the footer text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -256,7 +270,6 @@ This parameter is supported only by the Azure Information Protection unified lab Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -266,6 +279,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterFontSize + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterFontSize parameter specifies the font size (in points) of the footer text. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -274,7 +290,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -284,6 +299,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterMargin + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterMargin parameter specifies the size (in points) of the footer margin. This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -294,7 +312,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -304,6 +321,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingFooterText + +> Applicable: Security & Compliance + The ApplyContentMarkingFooterText parameter specifies the footer text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyContentMarkingFooterEnabled parameter value is either $true or $false. @@ -312,7 +332,6 @@ This parameter is meaningful only when the ApplyContentMarkingFooterEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -322,6 +341,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderAlignment + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderAlignment parameter specifies the header alignment. Valid values are: - Left @@ -334,7 +356,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+ContentAlignment Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -344,6 +365,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderEnabled + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderEnabled parameter enables or disables the Apply Content Marking Header action for the label. Valid values are: - $true: The Apply Content Marking Header action is enabled. @@ -353,7 +377,6 @@ The ApplyContentMarkingHeaderEnabled parameter enables or disables the Apply Con Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -363,6 +386,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontColor + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontColor parameter specifies the color of the header text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -371,7 +397,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -381,6 +406,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontName + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontName parameter specifies the font of the header text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -389,7 +417,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -399,6 +426,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderFontSize + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderFontSize parameter specifies the font size (in points) of the header text. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -407,7 +437,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -417,6 +446,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderMargin + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderMargin parameter specifies the size (in points) of the header margin. This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -427,7 +459,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -437,6 +468,9 @@ Accept wildcard characters: False ``` ### -ApplyContentMarkingHeaderText + +> Applicable: Security & Compliance + The ApplyContentMarkingHeaderText parameter specifies the header text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled parameter value is either $true or $false. @@ -445,7 +479,6 @@ This parameter is meaningful only when the ApplyContentMarkingHeaderEnabled para Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -455,6 +488,9 @@ Accept wildcard characters: False ``` ### -ApplyDynamicWatermarkingEnabled + +> Applicable: Security & Compliance + **Note**: This parameter is Generally Available only for labels with admin-defined permissions. Support for label with user-defined permissions is currently in Public Preview, isn't available in all organizations, and is subject to change. The ApplyDynamicWatermarkingEnabled parameter enables dynamic watermarking for a specific label that applies encryption. Valid values are: @@ -468,7 +504,6 @@ You set the watermark text with the DynamicWatermarkDisplay parameter. For more Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -478,6 +513,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingEnabled + +> Applicable: Security & Compliance + The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarking Header action for the label. Valid values are: - $true: The Apply Watermarking Header action is enabled. @@ -487,7 +525,6 @@ The ApplyWaterMarkingEnabled parameter enables or disables the Apply Watermarkin Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -497,6 +534,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontColor + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontColor parameter specifies the color of the watermark text. This parameter accepts a hexadecimal color code value in the format `#xxxxxx`. The default value is `#000000`. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -505,7 +545,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -515,6 +554,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontName + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontName parameter specifies the font of the watermark text. If the value contains spaces, enclose the value in quotation marks ("). For example `"Courier New"`. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -523,7 +565,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -533,6 +574,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingFontSize + +> Applicable: Security & Compliance + The ApplyWaterMarkingFontSize parameter specifies the font size (in points) of the watermark text. This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -541,7 +585,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -551,6 +594,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingLayout + +> Applicable: Security & Compliance + The ApplyWaterMarkingLayout parameter specifies the watermark alignment. Valid values are: - Horizontal @@ -562,7 +608,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+WaterMarkingLayout Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -572,6 +617,9 @@ Accept wildcard characters: False ``` ### -ApplyWaterMarkingText + +> Applicable: Security & Compliance + The ApplyWaterMarkingText parameter specifies the watermark text. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter value is either $true or $false. @@ -580,7 +628,6 @@ This parameter is meaningful only when the ApplyWaterMarkingEnabled parameter va Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -590,13 +637,15 @@ Accept wildcard characters: False ``` ### -ColumnAssetCondition + +> 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 @@ -606,13 +655,15 @@ 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 @@ -622,13 +673,15 @@ Accept wildcard characters: False ``` ### -Conditions + +> Applicable: Security & Compliance + The Conditions parameter is used for automatic labeling of files and email for data in use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -638,6 +691,9 @@ 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`. @@ -647,7 +703,6 @@ 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 @@ -657,6 +712,9 @@ Accept wildcard characters: False ``` ### -ContentType + +> Applicable: Security & Compliance + The ContentType parameter specifies where the sensitivity label can be applied. Valid values are: - File @@ -673,7 +731,6 @@ Values can be combined, for example: "File, Email, PurviewAssets". Type: MipLabelContentType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -683,13 +740,15 @@ Accept wildcard characters: False ``` ### -DefaultContentLabel + +> Applicable: Security & Compliance + The DefaultContentLabel specifies a label that can be automatically applied to meetings created in a labeled Teams channel. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -699,13 +758,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Security & Compliance + The DisplayName parameter specifies the display name for the sensitivity label. The display name appears in any client that supports sensitivity labels. This includes Word, Excel, PowerPoint, Outlook, SharePoint, Teams, and Power BI. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -715,6 +776,9 @@ Accept wildcard characters: False ``` ### -DynamicWatermarkDisplay + +> Applicable: Security & Compliance + **Note**: This parameter is Generally Available only for labels with admin-defined permissions. Support for label with user-defined permissions is currently in Public Preview, isn't available in all organizations, and is subject to change. The DynamicWatermarkDisplay parameter specifies the watermark text to display for a given label. This parameter supports text and the following special tokens: @@ -730,7 +794,6 @@ This parameter is meaningful only when the ApplyDynamicWatermarkingEnabled param Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -740,6 +803,9 @@ Accept wildcard characters: False ``` ### -EncryptionContentExpiredOnDateInDaysOrNever + +> Applicable: Security & Compliance + The EncryptionContentExpiredOnDateInDaysOrNever parameter specifies when the encrypted content expires. Valid values are: - An integer (number of days) @@ -751,7 +817,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -761,6 +826,9 @@ Accept wildcard characters: False ``` ### -EncryptionDoNotForward + +> Applicable: Security & Compliance + The EncryptionDoNotForward parameter specifies whether the Do Not Forward template is applied. Valid values are: - $true: The Do Not Forward template is applied. @@ -772,7 +840,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -782,13 +849,15 @@ Accept wildcard characters: False ``` ### -EncryptionDoubleKeyEncryptionUrl + +> 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 @@ -798,6 +867,9 @@ Accept wildcard characters: False ``` ### -EncryptionEnabled + +> Applicable: Security & Compliance + The EncryptionEnabled parameter specifies whether encryption in enabled. Valid values are: - $true: Encryption is enabled. @@ -807,7 +879,6 @@ The EncryptionEnabled parameter specifies whether encryption in enabled. Valid v Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -817,6 +888,9 @@ Accept wildcard characters: False ``` ### -EncryptionEncryptOnly + +> Applicable: Security & Compliance + The EncryptionEncryptOnly parameter specifies whether the encrypt-only template is applied. Valid values are: - $true: The encrypt-only template is applied. @@ -828,7 +902,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -838,6 +911,9 @@ Accept wildcard characters: False ``` ### -EncryptionOfflineAccessDays + +> Applicable: Security & Compliance + The EncryptionOfflineAccessDays parameter specifies the number of days that offline access is allowed. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -846,7 +922,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -856,6 +931,9 @@ Accept wildcard characters: False ``` ### -EncryptionPromptUser + +> Applicable: Security & Compliance + The EncryptionPromptUser parameter specifies whether to set the label with user defined permission in Word, Excel, and PowerPoint. Valid values are: - $true: The label is set with user defined permissions in Word, Excel and PowerPoint. @@ -867,7 +945,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -877,6 +954,9 @@ Accept wildcard characters: False ``` ### -EncryptionProtectionType + +> Applicable: Security & Compliance + The EncryptionProtectionType parameter specifies the protection type for encryption. Valid values are: - Template @@ -889,7 +969,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: Microsoft.Office.CompliancePolicy.Tasks.FlattenLabelActionUtils+SupportedProtectionType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -899,6 +978,9 @@ Accept wildcard characters: False ``` ### -EncryptionRightsDefinitions + +> Applicable: Security & Compliance + The EncryptionRightsDefinitions parameter specifies the rights users have when accessing protected. This parameter uses the syntax `Identity1:Rights1,Rights2;Identity2:Rights3,Rights4`. For example, `john@contoso.com:VIEW,EDIT;microsoft.com:VIEW`. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false and the EncryptionProtectionType parameter value is Template. @@ -907,7 +989,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: EncryptionRightsDefinitionsParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -917,6 +998,9 @@ Accept wildcard characters: False ``` ### -EncryptionRightsUrl + +> Applicable: Security & Compliance + The EncryptionRightsUrl parameter specifies the URL for hold your own key (HYOK) protection. This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false. @@ -925,7 +1009,6 @@ This parameter is meaningful only when the EncryptionEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -935,13 +1018,15 @@ Accept wildcard characters: False ``` ### -LabelActions + +> Applicable: Security & Compliance + The LabelActions parameter is used to specify actions that can be performed on labels. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -951,6 +1036,9 @@ Accept wildcard characters: False ``` ### -LocaleSettings + +> Applicable: Security & Compliance + The LocaleSettings parameter specifies one or more localized label names and label Tooltips in different languages. Regions include all region codes supported in Office Client applications. Valid values use the following syntax (JSON): - Label display names: `{"localeKey":"DisplayName","Settings":[{"Key":"en-us","Value":"English display name"},{"Key":"de-de","Value":"Deutscher Anzeigename"},{"Key":"es-es","Value":"Nombre para mostrar en Español"}]}` @@ -962,7 +1050,6 @@ To remove a language, you need to enter an empty value for that language. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -972,13 +1059,15 @@ Accept wildcard characters: False ``` ### -MigrationId + +> 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 @@ -988,13 +1077,15 @@ Accept wildcard characters: False ``` ### -NextLabel + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1004,6 +1095,9 @@ Accept wildcard characters: False ``` ### -ParentId + +> Applicable: Security & Compliance + The ParentId parameter specifies the parent label that you want this label to be under (a sublabel). You can use any value that uniquely identifies the parent sensitivity label. For example: - Name @@ -1014,7 +1108,6 @@ The ParentId parameter specifies the parent label that you want this label to be Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1024,13 +1117,15 @@ Accept wildcard characters: False ``` ### -PreviousLabel + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1040,13 +1135,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Security & Compliance + The Priority parameter specifies a priority value for the sensitivity label that determines the order of label processing. A higher integer value indicates a higher priority. ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1056,13 +1153,15 @@ Accept wildcard characters: False ``` ### -SchematizedDataCondition + +> 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 @@ -1072,13 +1171,15 @@ Accept wildcard characters: False ``` ### -Setting + +> 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 @@ -1088,13 +1189,15 @@ Accept wildcard characters: False ``` ### -Settings + +> 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 @@ -1104,6 +1207,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowAccessToGuestUsers + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowAccessToGuestUsers parameter enables or disables access to guest users. Valid values are: - $true: Guest access is enabled. @@ -1115,7 +1221,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1125,6 +1230,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowEmailFromGuestUsers + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowEmailFromGuestUsers parameter enables or disables email from guest users. Valid values are: - $true: Email from guest users is enabled. @@ -1136,7 +1244,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1146,6 +1253,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowFullAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowFullAccess parameter enables or disables full access. Valid values are: - $true: Full access is enabled. @@ -1157,7 +1267,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1167,6 +1276,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionAllowLimitedAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionAllowLimitedAccess parameter enables or disables limited access. Valid values are: - $true: Limited access is enabled. @@ -1178,7 +1290,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1188,6 +1299,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionBlockAccess + +> Applicable: Security & Compliance + The SiteAndGroupProtectionBlockAccess parameter blocks access. Valid values are: - $true: Access is blocked. @@ -1199,7 +1313,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1209,6 +1322,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionEnabled + +> Applicable: Security & Compliance + The SiteAndGroupProtectionEnabled parameter enables or disables the Site and Group Protection action for the label. Valid values are: - $true: The Site and Group Protection action is enabled. @@ -1218,7 +1334,6 @@ The SiteAndGroupProtectionEnabled parameter enables or disables the Site and Gro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1228,13 +1343,15 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionLevel + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: SiteAndGroupProtectionLevelParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1244,6 +1361,9 @@ Accept wildcard characters: False ``` ### -SiteAndGroupProtectionPrivacy + +> Applicable: Security & Compliance + The SiteAndGroupProtectionPrivacy parameter specifies the privacy level for the labe. Valid values are: - Public @@ -1255,7 +1375,6 @@ This parameter is meaningful only when the SiteAndGroupProtectionEnabled paramet Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AccessType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1265,6 +1384,9 @@ Accept wildcard characters: False ``` ### -SiteExternalSharingControlType + +> Applicable: Security & Compliance + The SiteExternalSharingControlType parameter specifies the external user sharing setting for the label. Valid values are: - ExternalUserAndGuestSharing @@ -1283,7 +1405,6 @@ These correspond to the following settings through the admin center: Type: Microsoft.Office.CompliancePolicy.Tasks.SiteExternalSharingControlType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1293,6 +1414,9 @@ Accept wildcard characters: False ``` ### -TeamsAllowedPresenters + +> Applicable: Security & Compliance + The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Valid values are: - Everyone @@ -1305,7 +1429,6 @@ The TeamsAllowedPresenters parameter controls who can present in Teams meetings. Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.AllowedPresenters Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1315,6 +1438,9 @@ Accept wildcard characters: False ``` ### -TeamsAllowMeetingChat + +> Applicable: Security & Compliance + The TeamsAllowMeetingChat parameter controls whether chat is available in Teams meetings. Valid values are: - Enabled @@ -1326,7 +1452,6 @@ The TeamsAllowMeetingChat parameter controls whether chat is available in Teams Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.MeetingChatMode Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1336,13 +1461,15 @@ Accept wildcard characters: False ``` ### -TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch + +> Applicable: Security & Compliance + {{ Fill TeamsAllowPrivateTeamsToBeDiscoverableUsingSearch Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1352,6 +1479,9 @@ Accept wildcard characters: False ``` ### -TeamsBypassLobbyForDialInUsers + +> Applicable: Security & Compliance + The TeamsBypassLobbyForDialInUsers parameter controls the lobby experience for dial-in users who join Teams meetings. Valid values are: - $true: Dial in users bypass the lobby when joining Teams meetings. @@ -1362,7 +1492,6 @@ The TeamsBypassLobbyForDialInUsers parameter controls the lobby experience for d Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1372,13 +1501,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelProtectionEnabled + +> Applicable: Security & Compliance + {{ Fill TeamsChannelProtectionEnabled Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1388,13 +1519,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithExternalTenants + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithExternalTenants Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1404,13 +1537,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithPrivateTeamsOnly + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithPrivateTeamsOnly Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1420,13 +1555,15 @@ Accept wildcard characters: False ``` ### -TeamsChannelSharedWithSameLabelOnly + +> Applicable: Security & Compliance + {{ Fill TeamsChannelSharedWithSameLabelOnly Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1436,6 +1573,9 @@ Accept wildcard characters: False ``` ### -TeamsCopyRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsCopyRestrictionEnforced parameter controls whether chat messages in Teams meetings can be copied to the clipboard. Valid values are: - $true: Chat messages can be copied to the clipboard. @@ -1445,7 +1585,6 @@ The TeamsCopyRestrictionEnforced parameter controls whether chat messages in Tea Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1455,6 +1594,9 @@ Accept wildcard characters: False ``` ### -TeamsEndToEndEncryptionEnabled + +> Applicable: Security & Compliance + The TeamsEndToEndEncryptionEnabled parameter controls video stream encryption in Teams meetings. Valid values are: - $true: Video stream encryption is enabled. @@ -1465,7 +1607,6 @@ The TeamsEndToEndEncryptionEnabled parameter controls video stream encryption in Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1475,6 +1616,9 @@ Accept wildcard characters: False ``` ### -TeamsLobbyBypassScope + +> Applicable: Security & Compliance + The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Teams meetings. Valid values are: - Everyone @@ -1489,7 +1633,6 @@ The TeamsLobbyBypassScope parameter controls who bypasses the lobby when joining Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.LobbyBypassScope Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1499,6 +1642,9 @@ Accept wildcard characters: False ``` ### -TeamsLobbyRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsLobbyRestrictionEnforced parameter controls whether participants bypass the lobby when joining Teams meetings. Valid values are: - $true: Users bypass the lobby when joining Teams meetings. @@ -1509,7 +1655,6 @@ The TeamsLobbyRestrictionEnforced parameter controls whether participants bypass Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1519,6 +1664,9 @@ Accept wildcard characters: False ``` ### -TeamsPresentersRestrictionEnforced + +> Applicable: Security & Compliance + The TeamsPresentersRestrictionEnforced parameter controls whether presenter restrictions are enabled in Teams meetings. Valid values are: - $true: Presenter restrictions are enabled in Teams meetings. @@ -1529,7 +1677,6 @@ The TeamsPresentersRestrictionEnforced parameter controls whether presenter rest Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1539,6 +1686,9 @@ Accept wildcard characters: False ``` ### -TeamsProtectionEnabled + +> Applicable: Security & Compliance + The TeamsProtectionEnabled parameter controls whether Teams protection is enabled in Teams meetings. Valid values are: - $true: Teams protection is enabled in Teams meetings. @@ -1548,7 +1698,6 @@ The TeamsProtectionEnabled parameter controls whether Teams protection is enable Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1558,6 +1707,9 @@ Accept wildcard characters: False ``` ### -TeamsRecordAutomatically + +> Applicable: Security & Compliance + The TeamsRecordAutomatically parameter controls whether Teams meetings are automatically recorded after they start. Valid values are: - $true: Teams meetings are automatically recorded after they start. @@ -1568,7 +1720,6 @@ The TeamsRecordAutomatically parameter controls whether Teams meetings are autom Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1578,6 +1729,9 @@ Accept wildcard characters: False ``` ### -TeamsVideoWatermark + +> Applicable: Security & Compliance + The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams meetings. Valid values are: - None @@ -1589,7 +1743,6 @@ The TeamsVideoWatermark parameter controls whether a watermark is shown in Teams Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WaterMarkProtectionValues Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1599,6 +1752,9 @@ Accept wildcard characters: False ``` ### -TeamsWhoCanRecord + +> Applicable: Security & Compliance + The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid values are: - Organizer @@ -1610,7 +1766,6 @@ The TeamsWhoCanRecord parameter controls who can record Teams meetings. Valid va Type: Microsoft.Office.CompliancePolicy.PolicyConfiguration.WhoCanRecordOptions Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1620,13 +1775,15 @@ Accept wildcard characters: False ``` ### -Tooltip + +> Applicable: Security & Compliance + The ToolTip parameter specifies the default tooltip and sensitivity label description that's seen by users. It the value contains spaces, enclose the value in quotation marks ("). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1636,13 +1793,15 @@ 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/exchange/Set-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-LabelPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md index 5b190d2637..437999e803 100644 --- a/exchange/exchange-ps/exchange/Set-LabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-labelpolicy applicable: Security & Compliance -title: Set-LabelPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-labelpolicy +schema: 2.0.0 +title: Set-LabelPolicy --- # Set-LabelPolicy @@ -104,6 +105,9 @@ This example configures the specified advanced setting for the sensitivity label ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the policy that you want to view. You can use any value that uniquely identifies the policy. For example: - Name @@ -114,7 +118,6 @@ The Identity parameter specifies the policy that you want to view. You can use a Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -124,6 +127,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -134,7 +140,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -144,6 +149,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. A valid value is a mailbox. To specify the mailbox, you can use any value that uniquely identifies it. For example: @@ -159,7 +167,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -169,6 +176,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocationException + +> Applicable: Security & Compliance + The AddExchangeLocationException parameter specifies the mailboxes to add to the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. A valid value is a mailbox. To specify the mailbox, you can use any value that uniquely identifies it. For example: @@ -184,7 +194,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -194,6 +203,9 @@ Accept wildcard characters: False ``` ### -AddLabels + +> Applicable: Security & Compliance + The AddLabels parameter specifies the sensitivity labels that you want to add to the policy. You can use any value that uniquely identifies the label. For example: - Name @@ -206,7 +218,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -216,6 +227,9 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocation + +> Applicable: Security & Compliance + The AddModernGroupLocation parameter specifies the Microsoft 365 Groups to add to the list of included Microsoft 365 Groups. To identify the Microsoft 365 Group, you must use the primary SMTP 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"`. @@ -224,7 +238,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -234,13 +247,15 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -250,13 +265,15 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -266,13 +283,15 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -282,13 +301,15 @@ Accept wildcard characters: False ``` ### -AddPublicFolderLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -298,13 +319,15 @@ Accept wildcard characters: False ``` ### -AddSharePointLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -314,13 +337,15 @@ Accept wildcard characters: False ``` ### -AddSharePointLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -330,13 +355,15 @@ Accept wildcard characters: False ``` ### -AddSkypeLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -346,13 +373,15 @@ Accept wildcard characters: False ``` ### -AddSkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -362,6 +391,9 @@ Accept wildcard characters: False ``` ### -AdvancedSettings + +> Applicable: Security & Compliance + The AdvancedSettings parameter enables client-specific features and capabilities for the sensitivity label policy. Specify this parameter with the identity (name or GUID) of the policy, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value. @@ -398,7 +430,6 @@ Additionally, for Power BI: Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -408,13 +439,15 @@ 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: Identity, AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -424,6 +457,9 @@ 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`. @@ -433,7 +469,6 @@ 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 @@ -443,6 +478,9 @@ 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. @@ -451,7 +489,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -461,13 +498,15 @@ Accept wildcard characters: False ``` ### -MigrationId + +> 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 @@ -477,6 +516,9 @@ Accept wildcard characters: False ``` ### -NextLabelPolicy + +> Applicable: Security & Compliance + The NextLabelPolicy parameter updates the policy order so the policy that's specified by this parameter is after the current policy that you're modifying. You can use any value that uniquely identifies the policy. For example: - Name @@ -487,7 +529,6 @@ The NextLabelPolicy parameter updates the policy order so the policy that's spec Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -497,6 +538,9 @@ 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. @@ -505,7 +549,6 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -515,6 +558,9 @@ Accept wildcard characters: False ``` ### -PreviousLabelPolicy + +> Applicable: Security & Compliance + The PreviousLabelPolicy parameter updates the policy order so the policy that's specified by this parameter is before the current policy that you're modifying. You can use any value that uniquely identifies the policy. For example: - Name @@ -525,7 +571,6 @@ The PreviousLabelPolicy parameter updates the policy order so the policy that's Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -535,6 +580,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter specifies the mailboxes to remove from the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -553,7 +601,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -563,6 +610,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocationException + +> Applicable: Security & Compliance + The RemoveExchangeLocationException parameter specifies the mailboxes to remove from the list of excluded mailboxes when you're using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -581,7 +631,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -591,6 +640,9 @@ Accept wildcard characters: False ``` ### -RemoveLabels + +> Applicable: Security & Compliance + The RemoveLabels parameter specifies the sensitivity labels that you want to remove from the policy. You can use any value that uniquely identifies the label. For example: - Name @@ -603,7 +655,6 @@ 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 @@ -613,6 +664,9 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocation + +> Applicable: Security & Compliance + The RemoveModernGroupLocation parameter specifies the Microsoft 365 Groups to remove from the list of included groups. To identify the Microsoft 365 Group, you must use the primary SMTP 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"`. @@ -621,7 +675,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -631,13 +684,15 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -647,13 +702,15 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -663,13 +720,15 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -679,13 +738,15 @@ Accept wildcard characters: False ``` ### -RemovePublicFolderLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -695,13 +756,15 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -711,13 +774,15 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -727,13 +792,15 @@ Accept wildcard characters: False ``` ### -RemoveSkypeLocation + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -743,13 +810,15 @@ Accept wildcard characters: False ``` ### -RemoveSkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -759,13 +828,15 @@ Accept wildcard characters: False ``` ### -Setting + +> 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 @@ -775,13 +846,15 @@ Accept wildcard characters: False ``` ### -Settings + +> 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 @@ -791,13 +864,15 @@ 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/exchange/Set-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-LinkedUser.md rename to exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md index ab7afd569b..4667f93b53 100644 --- a/exchange/exchange-ps/exchange/Set-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-linkeduser applicable: Exchange Online, Exchange Online Protection -title: Set-LinkedUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-linkeduser +schema: 2.0.0 +title: Set-LinkedUser --- # Set-LinkedUser @@ -45,6 +46,9 @@ This example modifies the certificate subject for the linked user "GALSync-Servi ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the linked user. You can use any value that uniquely identifies the linked user, for example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the linked user. You can use any value that uni Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -64,13 +67,15 @@ Accept wildcard characters: False ``` ### -CertificateSubject + +> Applicable: Exchange Online + The CertificateSubject parameter specifies the value of the subject field of the user's digital certificate. The syntax of the CertificateSubject value is `X509:IssuerSubject`. The values of Issuer and Subject are required and must be in X.500 format. To remove the value of CertificateSubject, specify the value $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -80,6 +85,9 @@ 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,7 +97,6 @@ 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,13 +106,15 @@ 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/exchange/Set-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md index db10ad8518..9b51664fdf 100644 --- a/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-m365dataatrestencryptionpolicy applicable: Exchange Online, Exchange Online Protection -title: Set-M365DataAtRestEncryptionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-m365dataatrestencryptionpolicy +schema: 2.0.0 +title: Set-M365DataAtRestEncryptionPolicy --- # Set-M365DataAtRestEncryptionPolicy @@ -66,6 +67,9 @@ This example updates the Microsoft 365 data-at-rest encryption policy named Tena ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the data-at-rest encryption policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -76,7 +80,6 @@ The Identity parameter specifies the data-at-rest encryption policy that you wan Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -86,6 +89,9 @@ 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`. @@ -95,7 +101,6 @@ 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 @@ -105,13 +110,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Online + The Description parameter specifies an optional description for the policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -121,13 +128,15 @@ 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 @@ -137,6 +146,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online, Exchange Online Protection + The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -146,7 +158,6 @@ The Enabled parameter specifies whether the policy is enabled or disabled. Valid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -156,6 +167,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -164,7 +178,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: DCAdminPurgeKeyRequest, TenantAdminPurgeKeyRequest Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -174,13 +187,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the Microsoft 365 data-at-rest 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 @@ -190,13 +205,15 @@ Accept wildcard characters: False ``` ### -Refresh + +> Applicable: Exchange Online + Use the Refresh switch to update the Microsoft 365 data-at-rest encryption policy in Exchange Online after you rotate any of the associated keys in the Azure Key Vault. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: RefreshKey Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -206,13 +223,15 @@ 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/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md index d5a82bfdda..9f4b6e7539 100644 --- a/exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-m365dataatrestencryptionpolicyassignment applicable: Exchange Online -title: Set-M365DataAtRestEncryptionPolicyAssignment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-m365dataatrestencryptionpolicyassignment +schema: 2.0.0 +title: Set-M365DataAtRestEncryptionPolicyAssignment --- # Set-M365DataAtRestEncryptionPolicyAssignment @@ -39,6 +40,9 @@ This example assigns the Microsoft 365 data-at-rest encryption policy named Cont ## PARAMETERS ### -DataEncryptionPolicy + +> Applicable: Exchange Online + The DataEncryptionPolicy parameter specifies the Microsoft 365 data-at-rest encryption policy. You can use any value that uniquely identifies the policy. For example: - Name @@ -49,7 +53,6 @@ The DataEncryptionPolicy parameter specifies the Microsoft 365 data-at-rest encr Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Set-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-MailContact.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md index e699c9dec7..bb3921dbe4 100644 --- a/exchange/exchange-ps/exchange/Set-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailcontact applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailContact -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailcontact +schema: 2.0.0 +title: Set-MailContact --- # Set-MailContact @@ -106,6 +107,9 @@ This example sets John Rodman's external email address to john@contoso.com. ## 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 modify. You can use any value that uniquely identifies the mail contact. For example: - Name @@ -119,7 +123,6 @@ The Identity parameter specifies the mail contact that you want to modify. You c Type: MailContactIdParameter 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,6 +132,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -152,7 +158,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -162,6 +167,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -185,7 +193,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -195,6 +202,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -220,7 +230,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -230,6 +239,9 @@ 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: @@ -254,7 +266,6 @@ 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 @@ -264,6 +275,9 @@ 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: @@ -283,7 +297,6 @@ 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 @@ -293,6 +306,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -314,7 +330,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -324,6 +339,9 @@ 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`. @@ -333,7 +351,6 @@ 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 @@ -343,6 +360,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -354,7 +374,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -364,13 +383,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -380,13 +401,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -396,13 +419,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -412,13 +437,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -428,13 +455,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -444,13 +473,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -460,13 +491,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -476,13 +509,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -492,13 +527,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -508,13 +545,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -524,13 +563,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -540,13 +581,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -556,13 +599,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -572,13 +617,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -588,13 +635,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -604,13 +653,15 @@ 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 mail contact. The display name is visible in the Exchange admin center (EAC) 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -620,6 +671,9 @@ 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. @@ -628,7 +682,6 @@ 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 @@ -638,6 +691,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -665,7 +721,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection 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 @@ -675,6 +730,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: @@ -686,7 +744,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -696,6 +753,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -708,7 +768,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -718,6 +777,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -730,7 +792,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -740,6 +801,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -752,7 +816,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -762,6 +825,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -774,7 +840,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -784,6 +849,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -796,7 +864,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -806,6 +873,9 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -816,7 +886,6 @@ When you use the ExternalEmailAddress parameter to change the external email add Type: ProxyAddress 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 @@ -826,13 +895,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 @@ -842,6 +913,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail contact. Although messages sent on behalf of the mail contact clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the mail contact, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -867,7 +941,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -877,6 +950,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -886,7 +962,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -896,6 +971,9 @@ 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. @@ -909,7 +987,6 @@ 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 @@ -919,6 +996,9 @@ Accept wildcard characters: False ``` ### -MacAttachmentFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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) @@ -935,7 +1015,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -945,6 +1024,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -956,7 +1038,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -966,6 +1047,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -980,7 +1064,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -990,6 +1073,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail contact. Messages larger than the maximum size are rejected. @@ -1013,7 +1099,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1023,6 +1108,9 @@ Accept wildcard characters: False ``` ### -MaxRecipientPerMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxRecipientPerMessage parameter specifies the maximum number of recipients allowed in messages sent by the mail contact. @@ -1035,7 +1123,6 @@ The value unlimited indicates the maximum number of recipients per message for t Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1045,6 +1132,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail contact. @@ -1068,7 +1158,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1078,6 +1167,9 @@ Accept wildcard characters: False ``` ### -MessageBodyFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -1093,7 +1185,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1103,6 +1194,9 @@ Accept wildcard characters: False ``` ### -MessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -1119,7 +1213,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1129,6 +1222,9 @@ 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 @@ -1148,7 +1244,6 @@ You need to use this parameter to specify at least one moderator when you set th 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 @@ -1158,6 +1253,9 @@ 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. @@ -1169,7 +1267,6 @@ 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 @@ -1179,13 +1276,15 @@ Accept wildcard characters: False ``` ### -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 mail contact. 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, Exchange Online Protection Required: False Position: Named @@ -1195,6 +1294,9 @@ 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. @@ -1209,7 +1311,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1219,6 +1320,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1242,7 +1346,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1252,6 +1355,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1275,7 +1381,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1285,6 +1390,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1310,7 +1418,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1320,6 +1427,9 @@ Accept wildcard characters: False ``` ### -RemovePicture + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemovePicture switch removes the picture from the mail contact. You don't need to specify a value with this switch. @@ -1330,7 +1440,6 @@ You can add a picture to a mail contact by using the Import-RecipientDataPropert Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1340,6 +1449,9 @@ Accept wildcard characters: False ``` ### -RemoveSpokenName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveSpokenName switch removes the spoken name from the mail contact. You don't need to specify a value with this switch. @@ -1350,7 +1462,6 @@ You can add a sound file to a mail contact by using the Import-RecipientDataProp Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1360,6 +1471,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, 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. @@ -1369,7 +1483,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -1379,6 +1492,9 @@ Accept wildcard characters: False ``` ### -SecondaryAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SecondaryAddress parameter specifies the secondary address that's used by the Unified Messaging (UM)-enabled mail contact. @@ -1387,7 +1503,6 @@ The SecondaryAddress parameter specifies the secondary address that's used by th Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1397,6 +1512,9 @@ Accept wildcard characters: False ``` ### -SecondaryDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This parameter is provided to create a secondary proxy address. @@ -1405,7 +1523,6 @@ The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1415,6 +1532,9 @@ 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. @@ -1427,7 +1547,6 @@ 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 @@ -1437,6 +1556,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -1449,7 +1571,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -1459,6 +1580,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -1479,7 +1603,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1489,6 +1612,9 @@ Accept wildcard characters: False ``` ### -UseMapiRichTextFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UseMapiRichTextFormat parameter specifies what to do with messages that are sent to the mail user or mail contact in MAPI rich text format, also known as Outlook Rich Text or Transport Neutral Encapsulation Format (TNEF). Valid values are: - Always: TNEF is used for all messages sent to the mail user or mail contact. @@ -1501,7 +1627,6 @@ The default value is UseDefaultSettings. Type: UseMapiRichTextFormat 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 @@ -1511,6 +1636,9 @@ Accept wildcard characters: False ``` ### -UsePreferMessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -1520,7 +1648,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1530,6 +1657,9 @@ Accept wildcard characters: False ``` ### -UserCertificate + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The UserCertificate parameter specifies the digital certificate used to sign a user's email messages. @@ -1538,7 +1668,6 @@ The UserCertificate parameter specifies the digital certificate used to sign a u Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1548,6 +1677,9 @@ Accept wildcard characters: False ``` ### -UserSMimeCertificate + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The UserSMimeCertificate parameter specifies the S/MIME certificate that's used to sign a user's email messages. @@ -1556,7 +1688,6 @@ The UserSMimeCertificate parameter specifies the S/MIME certificate that's used Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1566,13 +1697,15 @@ 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 @@ -1582,6 +1715,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -1593,7 +1729,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailPublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md index 8dd27b3503..87946cf3e7 100644 --- a/exchange/exchange-ps/exchange/Set-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailpublicfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailPublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailpublicfolder +schema: 2.0.0 +title: Set-MailPublicFolder --- # Set-MailPublicFolder @@ -120,6 +121,9 @@ This example removes the secondary email address MyPublicFolder@fabrikam.com fro ## 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 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. @@ -128,7 +132,6 @@ You can omit the parameter label so that only the public folder name or GUID is Type: MailPublicFolderIdParameter 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 @@ -138,6 +141,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -161,7 +167,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -171,6 +176,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -194,7 +202,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -204,6 +211,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -229,7 +239,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -239,6 +248,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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: @@ -263,7 +275,6 @@ 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 Required: False Position: Named @@ -273,6 +284,9 @@ Accept wildcard characters: False ``` ### -ArbitrationMailbox + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The ArbitrationMailbox parameter specifies the mailbox used to manage the moderation process. You can use any value that uniquely identifies the mailbox. For example: @@ -292,7 +306,6 @@ The ArbitrationMailbox parameter specifies the mailbox used to manage the modera Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -302,6 +315,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -323,7 +339,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -333,6 +348,9 @@ 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`. @@ -342,7 +360,6 @@ 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 @@ -352,6 +369,9 @@ Accept wildcard characters: False ``` ### -Contacts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Contacts parameter specifies the contacts for the public folder. Contacts are persons about whom you can save several types of information, such as addresses, telephone numbers, and web page URLs. Valid values for this parameter are recipients in your organization. You can use any value that uniquely identifies the recipient. For example: @@ -369,7 +389,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -379,13 +398,15 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010 + The CreateDTMFMap parameter specifies that a dual tone multi-frequency (DTMF) map be created for the user. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -395,13 +416,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -411,13 +434,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -427,13 +452,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -443,13 +470,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -459,13 +488,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -475,13 +506,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -491,13 +524,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -507,13 +542,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -523,13 +560,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -539,13 +578,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -555,13 +596,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -571,13 +614,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -587,13 +632,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -603,13 +650,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -619,13 +668,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -635,6 +686,9 @@ Accept wildcard characters: False ``` ### -DeliverToMailboxAndForward + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress or ForwardingSmtpAddress parameters. Valid values are: - $true: Messages are delivered to this public folder and forwarded to the specified recipient or email address. @@ -646,7 +700,6 @@ The default value is $false. The value of this parameter is meaningful only if y 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 @@ -656,13 +709,15 @@ 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 Public Folder Proxy object. 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, Exchange Online Required: False Position: Named @@ -672,6 +727,9 @@ 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. @@ -680,7 +738,6 @@ 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 @@ -690,6 +747,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -717,7 +777,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -727,6 +786,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: - $true: Email address policies are applied to this recipient. This is the default value. @@ -736,7 +798,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address 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 @@ -746,13 +807,15 @@ Accept wildcard characters: False ``` ### -EntryId + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EntryId parameter specifies the EntryID value for the public folder. You use this parameter to correct an existing EntryID that points to a folder that can't be found. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -762,6 +825,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -774,7 +840,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -784,6 +849,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -796,7 +864,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -806,6 +873,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -818,7 +888,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -828,6 +897,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -840,7 +912,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -850,6 +921,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -862,7 +936,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -872,13 +945,15 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalEmailAddress parameter specifies an email address outside the organization. ```yaml Type: ProxyAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -888,6 +963,9 @@ Accept wildcard characters: False ``` ### -ForwardingAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForwardingAddress parameter specifies a forwarding address for messages that are sent to this public folder. A valid value for this parameter is a recipient in your organization. You can use any value that uniquely identifies the recipient. For example: - Name @@ -908,7 +986,6 @@ The default value is blank ($null), which means no forwarding recipient is confi Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -918,6 +995,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this public folder. Although messages sent on behalf of the mail user clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the public folder, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -943,7 +1023,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -953,6 +1032,9 @@ 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 this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -962,7 +1044,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -972,6 +1053,9 @@ 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: @@ -983,7 +1067,6 @@ 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 @@ -993,6 +1076,9 @@ Accept wildcard characters: False ``` ### -IgnoreMissingFolderLink + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enabled public folder from a specific validation check that's used during a public folder migration. Valid values are: - $true: Skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the public folder is ignored, and the public folder migration can continue. @@ -1002,7 +1088,6 @@ The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enab Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1012,6 +1097,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -1023,7 +1111,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -1033,6 +1120,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -1047,7 +1137,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -1057,6 +1146,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the public folder. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -1076,7 +1168,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify 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 @@ -1086,6 +1177,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxSendSize parameter specifies the maximum size of a message that can be sent by the public folder. When you enter a value, qualify the value with one of the following units: @@ -1105,7 +1199,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify 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 @@ -1115,6 +1208,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 @@ -1134,7 +1230,6 @@ You need to use this parameter to specify at least one moderator when you set 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 @@ -1144,6 +1239,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -1155,7 +1253,6 @@ 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 Required: False Position: Named @@ -1165,13 +1262,15 @@ Accept wildcard characters: False ``` ### -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 public folder. 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: False Position: Named @@ -1181,13 +1280,15 @@ Accept wildcard characters: False ``` ### -OnPremisesObjectId + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The OnPremisesObjectId parameter specifies the ObjectID (GUID) value of the mail-enabled public folder from the on-premises environment. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1197,13 +1298,15 @@ Accept wildcard characters: False ``` ### -PhoneticDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. 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, Exchange Online Required: False Position: Named @@ -1213,6 +1316,9 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but the email addresses of the public folder are no longer automatically updated by email address policies. @@ -1223,7 +1329,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm 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 @@ -1233,6 +1338,9 @@ Accept wildcard characters: False ``` ### -PublicFolderType + +> Applicable: Exchange Server 2010 + The PublicFolderType parameter specifies which of the following four types is assigned to the public folder: - GeneralPurpose @@ -1244,7 +1352,6 @@ The PublicFolderType parameter specifies which of the following four types is as Type: PublicFolderType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1254,6 +1361,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1277,7 +1387,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1287,6 +1396,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1310,7 +1422,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1320,6 +1431,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1345,7 +1459,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1355,6 +1468,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -1364,7 +1480,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -1374,6 +1489,9 @@ Accept wildcard characters: False ``` ### -SendModerationNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -1386,7 +1504,6 @@ 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 Required: False Position: Named @@ -1396,6 +1513,9 @@ 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 @@ -1409,7 +1529,6 @@ 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 @@ -1419,6 +1538,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -1431,7 +1553,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -1441,6 +1562,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The UMDtmfMap parameter specifies if you want to create a user-defined DTMF map for the UM-enabled user. @@ -1449,7 +1573,6 @@ The UMDtmfMap parameter specifies if you want to create a user-defined DTMF map Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1459,13 +1582,15 @@ 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 @@ -1475,6 +1600,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -1486,7 +1614,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-MailUser.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md index ab267d41fa..af76eaa84e 100644 --- a/exchange/exchange-ps/exchange/Set-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailuser applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailuser +schema: 2.0.0 +title: Set-MailUser --- # Set-MailUser @@ -958,6 +959,9 @@ This example modifies the external email address for the mail user named John Wo ## 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 modify. You can use any value that uniquely identifies the mail user. For example: - Name @@ -971,7 +975,6 @@ The Identity parameter specifies the mail user that you want to modify. You can Type: MailUserIdParameter 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 @@ -981,6 +984,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1004,7 +1010,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1014,6 +1019,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1037,7 +1045,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1047,6 +1054,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -1072,7 +1082,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1082,6 +1091,9 @@ 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: @@ -1106,7 +1118,6 @@ 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 @@ -1116,6 +1127,9 @@ 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: @@ -1135,7 +1149,6 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t Type: MailboxIdParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1145,13 +1158,15 @@ Accept wildcard characters: False ``` ### -ArchiveGuid + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: Guid 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 @@ -1161,6 +1176,9 @@ Accept wildcard characters: False ``` ### -ArchiveName + +> 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. @@ -1169,7 +1187,6 @@ This parameter is reserved for internal Microsoft use. Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1179,6 +1196,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -1200,7 +1220,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -1210,6 +1229,9 @@ 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`. @@ -1219,7 +1241,6 @@ 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 @@ -1229,6 +1250,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -1240,7 +1264,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1250,13 +1273,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1266,13 +1291,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1282,13 +1309,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1298,13 +1327,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1314,13 +1345,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1330,13 +1363,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1346,13 +1381,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1362,13 +1399,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1378,13 +1417,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1394,13 +1435,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1410,13 +1453,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1426,13 +1471,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1442,13 +1489,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1458,13 +1507,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1474,13 +1525,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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, Exchange Online Protection Required: False Position: Named @@ -1490,6 +1543,9 @@ Accept wildcard characters: False ``` ### -DataEncryptionPolicy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the mail user. You can use any value that uniquely identifies the policy. For example: @@ -1504,7 +1560,6 @@ You can use the Get-DataEncryptionPolicy cmdlet to view the available policies. Type: DataEncryptionPolicyIdParameter Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1514,13 +1569,15 @@ 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 mail user. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1530,6 +1587,9 @@ 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. @@ -1538,7 +1598,6 @@ 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 @@ -1548,6 +1607,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -1575,7 +1637,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection 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 @@ -1585,6 +1646,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: @@ -1596,7 +1660,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1606,6 +1669,9 @@ Accept wildcard characters: False ``` ### -EnableLitigationHoldForMigration + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EnableLitigationHoldForMigration switch is used in cross-tenant mailbox migrations to increase the quota on the Recoverable Items folder to 100 GB (and also enable Litigation Hold) prior to migration. You don't need to specify a value with this switch. @@ -1616,7 +1682,6 @@ This feature is not available in hybrid tenants. Type: SwitchParameter Parameter Sets: EnableLitigationHoldForMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -1626,13 +1691,15 @@ Accept wildcard characters: False ``` ### -ExchangeGuid + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: Guid 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 @@ -1642,6 +1709,9 @@ Accept wildcard characters: False ``` ### -ExcludeFromAllOrgHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The ExcludeFromAllOrgHolds switch specifies whether to exclude the soft-deleted mail user from all organization-wide Microsoft 365 retention policies. You don't need to specify a value with this switch. @@ -1656,7 +1726,6 @@ When you use this switch, use one of the following values to uniquely identify t Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1666,6 +1735,9 @@ Accept wildcard characters: False ``` ### -ExcludeFromOrgHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill ExcludeFromOrgHolds Description }} @@ -1674,7 +1746,6 @@ This parameter is available only in the cloud-based service. Type: String[] Parameter Sets: ExcludeFromOrgHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1684,6 +1755,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1696,7 +1770,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -1706,6 +1779,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1718,7 +1794,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -1728,6 +1803,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1740,7 +1818,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -1750,6 +1827,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1762,7 +1842,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -1772,6 +1851,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -1784,7 +1866,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -1794,6 +1875,9 @@ Accept wildcard characters: False ``` ### -ExternalEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -1804,7 +1888,6 @@ When you use the ExternalEmailAddress parameter to change the external email add Type: ProxyAddress 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 @@ -1814,6 +1897,9 @@ Accept wildcard characters: False ``` ### -FederatedIdentity + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The FederatedIdentity parameter associates an on-premises Active Directory user with a user in the cloud. @@ -1822,7 +1908,6 @@ The FederatedIdentity parameter associates an on-premises Active Directory user Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1832,13 +1917,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 @@ -1848,6 +1935,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail user. Although messages sent on behalf of the mail user clearly show the sender in the From field (` on behalf of `, replies to these messages are delivered to the mail user, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -1873,7 +1963,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -1883,6 +1972,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -1892,7 +1984,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -1902,6 +1993,9 @@ 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. @@ -1910,7 +2004,6 @@ The HVEAccount switch specifies that this mail user account is specifically used Type: SwitchParameter Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Position: Named Default value: None @@ -1920,6 +2013,9 @@ 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. @@ -1933,7 +2029,6 @@ This switch enables the command to access Active Directory objects that aren't c Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1943,6 +2038,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -1951,7 +2049,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service 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 @@ -1961,6 +2058,9 @@ Accept wildcard characters: False ``` ### -JournalArchiveAddress + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -1969,7 +2069,6 @@ This parameter is reserved for internal Microsoft use. Type: SmtpAddress Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1979,6 +2078,9 @@ 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. @@ -1987,7 +2089,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1997,6 +2098,9 @@ Accept wildcard characters: False ``` ### -MacAttachmentFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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) @@ -2013,7 +2117,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2023,6 +2126,9 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2031,7 +2137,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2041,6 +2146,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -2052,7 +2160,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -2062,6 +2169,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -2076,7 +2186,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -2086,6 +2195,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail user. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -2105,7 +2217,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2115,6 +2226,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail user. When you enter a value, qualify the value with one of the following units: @@ -2134,7 +2248,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2144,6 +2257,9 @@ Accept wildcard characters: False ``` ### -MessageBodyFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -2159,7 +2275,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2169,6 +2284,9 @@ Accept wildcard characters: False ``` ### -MessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text @@ -2185,7 +2303,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2195,6 +2312,9 @@ Accept wildcard characters: False ``` ### -MicrosoftOnlineServicesID + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The MicrosoftOnlineServicesID parameter specifies the user ID for the object. This parameter only applies to objects in the cloud-based service. It isn't available for on-premises deployments. @@ -2203,7 +2323,6 @@ The MicrosoftOnlineServicesID parameter specifies the user ID for the object. Th Type: SmtpAddress Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2213,6 +2332,9 @@ 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 @@ -2232,7 +2354,6 @@ You need to use this parameter to specify at least one moderator when you set th 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 @@ -2242,6 +2363,9 @@ 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. @@ -2253,7 +2377,6 @@ 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 @@ -2263,13 +2386,15 @@ Accept wildcard characters: False ``` ### -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 mail user. 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, Exchange Online Protection Required: False Position: Named @@ -2279,6 +2404,9 @@ Accept wildcard characters: False ``` ### -Password + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The Password parameter allows users to change their own password. You can use the following methods as a value for this parameter: @@ -2293,7 +2421,6 @@ You can't use this parameter to change another user's password (the parameter is Type: SecureString Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2303,6 +2430,9 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only in on-premises Exchange. The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. @@ -2317,7 +2447,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm 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 @@ -2327,6 +2456,9 @@ Accept wildcard characters: False ``` ### -RecalculateInactiveMailUser + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RecalculateInactiveMailUser Description }} @@ -2335,7 +2467,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RecalculateInactiveMailUser Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2345,6 +2476,9 @@ Accept wildcard characters: False ``` ### -RecipientLimits + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The RecipientLimits parameter specifies the maximum number of recipients allowed in messages sent by the mail user. @@ -2357,7 +2491,6 @@ The value unlimited indicates the maximum number of recipients per message for t 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 @@ -2367,6 +2500,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder for a mail user that has a corresponding remote mailbox or remote archive mailbox in the cloud-based service. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages. @@ -2389,7 +2525,6 @@ The RecoverableItemsQuota value must be greater than or equal to the Recoverable Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2399,6 +2534,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for a mail user that has a corresponding remote mailbox or remote archive mailbox in the cloud-based service. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log. @@ -2421,7 +2559,6 @@ The RecoverableItemsQuota value must be greater than or equal to the Recoverable Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2431,6 +2568,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -2454,7 +2594,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -2464,6 +2603,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -2487,7 +2629,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -2497,6 +2638,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -2522,7 +2666,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -2532,6 +2675,9 @@ Accept wildcard characters: False ``` ### -RemoveComplianceTagHoldApplied + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveComplianceTagHoldApplied Description }} @@ -2540,7 +2686,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RemoveComplianceTagHoldApplied Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2550,6 +2695,9 @@ Accept wildcard characters: False ``` ### -RemoveDelayHoldApplied + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveDelayHoldApplied Description }} @@ -2558,7 +2706,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RemoveDelayHoldApplied Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2568,6 +2715,9 @@ Accept wildcard characters: False ``` ### -RemoveDelayReleaseHoldApplied + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveDelayReleaseHoldApplied Description }} @@ -2576,7 +2726,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RemoveDelayReleaseHoldApplied Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2586,6 +2735,9 @@ Accept wildcard characters: False ``` ### -RemoveDisabledArchive + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RemoveDisabledArchive switch specifies whether to remove the disabled archive that's associated with the mail user. You don't need to specify a value with this switch. @@ -2594,7 +2746,6 @@ The RemoveDisabledArchive switch specifies whether to remove the disabled archiv Type: SwitchParameter Parameter Sets: RemoveDisabledArchive Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2604,6 +2755,9 @@ Accept wildcard characters: False ``` ### -RemoveLitigationHoldEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RemoveLitigationHoldEnabled switch specifies whether to remove litigation hold from all mailbox locations of a mail user, including online archive, in an Exchange hybrid environment. You don't need to specify a value with this switch. @@ -2614,7 +2768,6 @@ This switch is useful in scenarios where admins can't permanently delete mail us Type: SwitchParameter Parameter Sets: RemoveLitigationHoldEnabled Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2624,6 +2777,9 @@ Accept wildcard characters: False ``` ### -RemoveMailboxProvisioningConstraint + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveMailboxProvisioningConstraint Description }} @@ -2632,7 +2788,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds, UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2642,6 +2797,9 @@ Accept wildcard characters: False ``` ### -RemoveOrphanedHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveOrphanedHolds Description }} @@ -2650,7 +2808,6 @@ This parameter is available only in the cloud-based service. Type: String[] Parameter Sets: RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2660,6 +2817,9 @@ Accept wildcard characters: False ``` ### -RemovePicture + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemovePicture switch removes the picture from the mail user. You don't need to specify a value with this switch. @@ -2670,7 +2830,6 @@ You can add a picture to a mail user by using the Import-RecipientDataProperty c Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2680,6 +2839,9 @@ Accept wildcard characters: False ``` ### -RemoveSpokenName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveSpokenName switch removes the spoken name from the mail user. You don't need to specify a value with this switch. @@ -2690,7 +2852,6 @@ You can add a sound file to a mail user by using the Import-RecipientDataPropert Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2700,6 +2861,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, 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. @@ -2709,7 +2873,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -2719,6 +2882,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The ResetPasswordOnNextLogon parameter allows users to require themselves to change their password the next time they log on. Valid values are: @@ -2732,7 +2898,6 @@ You can't use this parameter to require another user to change their password (t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2742,6 +2907,9 @@ 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). The maximum length is 20 characters. @@ -2750,7 +2918,6 @@ The SamAccountName parameter (also known as the pre-Windows 2000 user account or Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2760,6 +2927,9 @@ Accept wildcard characters: False ``` ### -SecondaryAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Online Protection + This parameter is available only in on-premises Exchange. The SecondaryAddress parameter specifies the secondary address used by the Unified Messaging (UM)-enabled user. @@ -2768,7 +2938,6 @@ The SecondaryAddress parameter specifies the secondary address used by the Unifi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Online Protection Required: False Position: Named @@ -2778,6 +2947,9 @@ Accept wildcard characters: False ``` ### -SecondaryDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This parameter is provided to create a secondary proxy address. @@ -2786,7 +2958,6 @@ The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2796,6 +2967,9 @@ 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. @@ -2808,7 +2982,6 @@ 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 @@ -2818,6 +2991,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -2830,7 +3006,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -2840,6 +3015,9 @@ Accept wildcard characters: False ``` ### -SkipDualWrite + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in Exchange 2016 or later. This parameter is reserved for internal Microsoft use. @@ -2848,7 +3026,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2858,6 +3035,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -2878,7 +3058,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2888,6 +3067,9 @@ Accept wildcard characters: False ``` ### -UnblockForwardSyncPostCrossTenantMigration + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill UnblockForwardSyncPostCrossTenantMigration Description }} @@ -2896,7 +3078,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: UnblockForwardSyncPostCrossTenantMigration Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -2906,6 +3087,9 @@ Accept wildcard characters: False ``` ### -UseMapiRichTextFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UseMapiRichTextFormat parameter specifies what to do with messages that are sent to the mail user or mail contact in MAPI rich text format, also known as Outlook Rich Text or Transport Neutral Encapsulation Format (TNEF). Valid values are: - Always: TNEF is used for all messages sent to the mail user or mail contact. @@ -2918,7 +3102,6 @@ The default value is UseDefaultSettings. Type: UseMapiRichTextFormat 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 @@ -2928,6 +3111,9 @@ Accept wildcard characters: False ``` ### -UsePreferMessageFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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. @@ -2937,7 +3123,6 @@ 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2947,13 +3132,15 @@ Accept wildcard characters: False ``` ### -UserCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UserCertificate parameter specifies the digital certificate used to sign a user's email messages. ```yaml 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 @@ -2963,6 +3150,9 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. @@ -2971,7 +3161,6 @@ The UserPrincipalName parameter specifies the logon name for the user account. T Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2981,13 +3170,15 @@ Accept wildcard characters: False ``` ### -UserSMimeCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UserSMimeCertificate parameter specifies the S/MIME certificate that's used to sign a user's email messages. ```yaml 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 @@ -2997,13 +3188,15 @@ 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 @@ -3013,6 +3206,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -3024,7 +3220,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-Mailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md index f24e40f01c..1b1ed8a3ff 100644 --- a/exchange/exchange-ps/exchange/Set-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-Mailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailbox +schema: 2.0.0 +title: Set-Mailbox --- # Set-Mailbox @@ -1190,6 +1191,9 @@ In Exchange Online, this example removes the delay hold that's applied to Asraf' ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -1207,7 +1211,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us 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 @@ -1217,6 +1220,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1240,7 +1246,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1250,6 +1255,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1273,7 +1281,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1283,6 +1290,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -1308,7 +1318,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -1318,6 +1327,9 @@ Accept wildcard characters: False ``` ### -AccountDisabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only in the cloud-based service. The AccountDisabled parameter specifies whether to disable the account that's associated with the mailbox. Valid values are: @@ -1329,7 +1341,6 @@ The AccountDisabled parameter specifies whether to disable the account that's as Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1339,6 +1350,9 @@ Accept wildcard characters: False ``` ### -AddressBookPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 @@ -1351,7 +1365,6 @@ For more information about address book policies, see [Address book policies in Type: AddressBookMailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1361,6 +1374,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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: @@ -1385,7 +1401,6 @@ 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 Required: False Position: Named @@ -1395,6 +1410,9 @@ Accept wildcard characters: False ``` ### -AntispamBypassEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AntispamBypassEnabled parameter specifies whether to skip anti-spam processing on the mailbox. Valid values are: @@ -1406,7 +1424,6 @@ The AntispamBypassEnabled parameter specifies whether to skip anti-spam processi Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1416,6 +1433,9 @@ Accept wildcard characters: False ``` ### -ApplyMandatoryProperties + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplyMandatoryProperties switch specifies whether to update the msExchVersion attribute of the mailbox. You don't need to specify a value with this switch. You might need to use this switch to fix inaccessible mailboxes or mailboxes that were created in previous versions of Exchange. @@ -1424,7 +1444,6 @@ You might need to use this switch to fix inaccessible mailboxes or mailboxes 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 @@ -1434,6 +1453,9 @@ 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 modify arbitration mailboxes. You don't need to specify a value with this switch. @@ -1446,7 +1468,6 @@ To modify arbitration mailboxes that are used to store audit log settings or dat Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1456,6 +1477,9 @@ 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: @@ -1475,7 +1499,6 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t Type: MailboxIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1485,6 +1508,9 @@ 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: @@ -1497,7 +1523,6 @@ The ArchiveDatabase parameter specifies the Exchange database that contains the Type: DatabaseIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1507,6 +1532,9 @@ 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. @@ -1517,7 +1545,6 @@ Only use this parameter if the archive is hosted in the cloud-based service. Type: SmtpDomain Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1527,6 +1554,9 @@ Accept wildcard characters: False ``` ### -ArchiveName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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, the following default values are used based on the version of Exchange: @@ -1543,7 +1573,6 @@ In Outlook in Exchange Online, the value of this parameter is ignored. The name 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 @@ -1553,6 +1582,9 @@ Accept wildcard characters: False ``` ### -ArchiveQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ArchiveQuota parameter specifies the maximum size for the user's archive mailbox. If the archive mailbox reaches or exceeds this size, it no longer accepts messages. @@ -1573,7 +1605,6 @@ The ArchiveQuota value must be greater than or equal to the ArchiveWarningQuota Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1583,6 +1614,9 @@ Accept wildcard characters: False ``` ### -ArchiveStatus + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This cmdlet is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1591,7 +1625,6 @@ This parameter is reserved for internal Microsoft use. Type: ArchiveStatusFlags Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1601,6 +1634,9 @@ Accept wildcard characters: False ``` ### -ArchiveWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ArchiveWarningQuota parameter specifies the warning threshold for the size of the user's archive mailbox. If the archive mailbox reaches or exceeds this size, the user receives a descriptive warning message. @@ -1621,7 +1657,6 @@ The ArchiveWarningQuota value must be less than or equal to the ArchiveQuota val Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1631,6 +1666,9 @@ Accept wildcard characters: False ``` ### -AttributesToClear + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1639,7 +1677,6 @@ This parameter is reserved for internal Microsoft use. Type: SetMailbox+ClearableADAttributes[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1649,6 +1686,9 @@ Accept wildcard characters: False ``` ### -AuditAdmin + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditAdmin parameter specifies the mailbox operations to log for administrators as part of mailbox audit logging. Valid values are: - None @@ -1682,7 +1722,6 @@ The AuditEnabled parameter must be set to $true to enable mailbox audit logging. 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 @@ -1692,6 +1731,9 @@ Accept wildcard characters: False ``` ### -AuditDelegate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditDelegate parameter specifies the mailbox operations to log for delegate users as part of mailbox audit logging. Valid values are: - None @@ -1722,7 +1764,6 @@ The AuditEnabled parameter must be set to $true to enable mailbox audit logging. 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 @@ -1732,6 +1773,9 @@ Accept wildcard characters: False ``` ### -AuditEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditEnabled parameter specifies whether to enable or disable mailbox audit logging for the mailbox. If auditing is enabled, actions specified in the AuditAdmin, AuditDelegate, and AuditOwner parameters are logged. Valid values are: - $true: Mailbox audit logging is enabled. @@ -1743,7 +1787,6 @@ The AuditEnabled parameter specifies whether to enable or disable mailbox audit 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 @@ -1753,6 +1796,9 @@ 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 modify audit log mailboxes. You don't need to specify a value with this switch. @@ -1765,7 +1811,6 @@ To modify other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1775,6 +1820,9 @@ Accept wildcard characters: False ``` ### -AuditLogAgeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditLogAgeLimit parameter specifies the maximum age of audit log entries for the mailbox. Log entries older than the specified value are removed. The default value is 90 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. @@ -1785,7 +1833,6 @@ For example, to specify 60 days for this parameter, use 60.00:00:00. Setting thi Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1795,6 +1842,9 @@ Accept wildcard characters: False ``` ### -AuditOwner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditOwner parameter specifies the mailbox operations to log for mailbox owners as part of mailbox audit logging. Valid values include: - None (This is the default value in Exchange 2010, Exchange 2013, and Exchange 2016.) @@ -1826,7 +1876,6 @@ The AuditEnabled parameter must be set to $true to enable mailbox audit logging. 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 @@ -1836,6 +1885,9 @@ 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 modify auxiliary audit log mailboxes. You don't need to specify a value with this switch. @@ -1848,7 +1900,6 @@ To modify other types of arbitration mailboxes, don't use this switch. Instead, Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1858,6 +1909,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -1879,7 +1933,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. 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 @@ -1889,6 +1942,9 @@ Accept wildcard characters: False ``` ### -CalendarLoggingQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CalendarLoggingQuota parameter specifies the maximum size of the log in the Recoverable Items folder of the mailbox that stores changes to calendar items. When the log exceeds this size, calendar logging is disabled until messaging records management (MRM) removes older calendar logs to free up more space. @@ -1913,7 +1969,6 @@ When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $ Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1923,6 +1978,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairDisabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CalendarRepairDisabled parameter specifies whether to prevent calendar items in the mailbox from being repaired by the Calendar Repair Assistant. Valid values are: - $true: The Calendar Repair Assistant doesn't repair calendar items in the mailbox. @@ -1932,7 +1990,6 @@ The CalendarRepairDisabled parameter specifies whether to prevent calendar items 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 @@ -1942,6 +1999,9 @@ Accept wildcard characters: False ``` ### -CalendarVersionStoreDisabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar changes in the mailbox from being logged. Valid values are: - $true: Changes to a calendar item aren't recorded. @@ -1951,7 +2011,6 @@ The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar 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 @@ -1961,6 +2020,9 @@ Accept wildcard characters: False ``` ### -ClearThrottlingPolicyAssignment + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ClearThrottlingPolicyAssignment switch specifies whether to clear any throttling policy assignments for the mailbox. You don't need to specify a value with this switch. @@ -1971,7 +2033,6 @@ Admins can contact Microsoft Support to assign a throttling policy to a mailbox, Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1981,6 +2042,9 @@ Accept wildcard characters: False ``` ### -ClientExtensions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) will be installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox. @@ -1991,7 +2055,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2001,6 +2064,9 @@ 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`. @@ -2010,7 +2076,6 @@ 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 @@ -2020,6 +2085,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -2031,7 +2099,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2041,13 +2108,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2057,13 +2126,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2073,13 +2144,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2089,13 +2162,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2105,13 +2180,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2121,13 +2198,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2137,13 +2216,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2153,13 +2234,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2169,13 +2252,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2185,13 +2270,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2201,13 +2288,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2217,13 +2306,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2233,13 +2324,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2249,13 +2342,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2265,13 +2360,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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: False Position: Named @@ -2281,6 +2378,9 @@ 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 mailbox database that contains the mailbox. You can use any value that uniquely identifies the database. For example: @@ -2295,7 +2395,6 @@ Use the Get-MailboxDatabase cmdlet to see the available mailbox databases. Type: DatabaseIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2305,6 +2404,9 @@ Accept wildcard characters: False ``` ### -DataEncryptionPolicy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example: @@ -2319,7 +2421,6 @@ You can use the Get-DataEncryptionPolicy cmdlet to view the available policies. Type: DataEncryptionPolicyIdParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2329,6 +2430,9 @@ Accept wildcard characters: False ``` ### -DefaultAuditSet + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DefaultAuditSet parameter specifies whether to revert the mailbox operations that are logged in the mailbox audit log back to the set of default operations for the specified logon type. Valid values are: @@ -2343,7 +2447,6 @@ With on-by-default mailbox auditing in the cloud-based service, a set of mailbox Type: MultiValuedProperty Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2353,6 +2456,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderMailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderMailbox parameter assigns a specific public folder mailbox to the user. You can use any value that uniquely identifies the public folder mailbox. For example: - Name @@ -2368,7 +2474,6 @@ By default, the public folder mailbox used by a user is automatically selected b Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2378,6 +2483,9 @@ Accept wildcard characters: False ``` ### -DeliverToMailboxAndForward + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress or ForwardingSmtpAddress parameters. Valid values are: - $true: Messages are delivered to this mailbox and forwarded to the specified recipient or email address. @@ -2389,7 +2497,6 @@ The default value is $false. The value of this parameter is meaningful only if y 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 @@ -2399,6 +2506,9 @@ Accept wildcard characters: False ``` ### -DisableThrottling + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are: @@ -2410,7 +2520,6 @@ The DisableThrottling parameter enables or disables sender rate throttling for t Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2420,13 +2529,15 @@ 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 mailbox. The display name is visible in the Exchange admin center, in address lists, and in 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, Exchange Online Required: False Position: Named @@ -2436,6 +2547,9 @@ 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. @@ -2444,7 +2558,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2454,6 +2567,9 @@ Accept wildcard characters: False ``` ### -DowngradeHighPriorityMessagesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DowngradeHighPriorityMessagesEnabled parameter specifies whether to prevent the mailbox from sending high priority messages to an X.400 mail system. Valid values are: @@ -2465,7 +2581,6 @@ The DowngradeHighPriorityMessagesEnabled parameter specifies whether to prevent Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2475,6 +2590,9 @@ Accept wildcard characters: False ``` ### -DumpsterMessagesPerFolderCountReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DumpsterMessagesPerFolderCountReceiveQuota parameter specifies the maximum number of messages that can be contained in each folder in the Recoverable Items folder (called the dumpster in previous versions of Exchange). When a folder exceeds this limit, it can't store new messages. For example, if the Deletions folder in the Recoverable Items folder has exceeded the message count limit and the mailbox owner attempts to permanently delete items from their mailbox, the deletion will fail. @@ -2485,7 +2603,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2495,6 +2612,9 @@ Accept wildcard characters: False ``` ### -DumpsterMessagesPerFolderCountWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DumpsterMessagesPerFolderCountWarningQuota parameters specifies the number of messages that each folder in the Recoverable Items folder (called the dumpster in previous versions of Exchange) can hold before Exchange sends a warning message to the mailbox owner and logs an event to the application event log. When this quota is reached, warning messages and logged events occur once a day. @@ -2505,7 +2625,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2515,6 +2634,9 @@ Accept wildcard characters: False ``` ### -ElcProcessingDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to prevent the Managed Folder Assistant from processing the mailbox. Valid values are: @@ -2526,7 +2648,6 @@ The ElcProcessingDisabled parameter specifies whether to prevent the Managed Fol Type: Boolean Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2536,6 +2657,9 @@ Accept wildcard characters: False ``` ### -EmailAddressDisplayNames + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill EmailAddressDisplayNames Description }} @@ -2544,7 +2668,6 @@ This parameter is available only in the cloud-based service. Type: MultiValuedProperty Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2554,6 +2677,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -2581,7 +2707,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2591,6 +2716,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: @@ -2602,7 +2730,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2612,6 +2739,9 @@ Accept wildcard characters: False ``` ### -EnableRoomMailboxAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The EnableRoomMailboxAccount parameter specifies whether to enable the disabled user account that's associated with this room mailbox. Valid values are: @@ -2627,7 +2757,6 @@ A room mailbox in Exchange Online is created with associated an account that has Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2637,6 +2766,9 @@ Accept wildcard characters: False ``` ### -EndDateForRetentionHold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EndDateForRetentionHold parameter specifies the end date for retention hold for messaging records management (MRM). To use this parameter, you need to set the RetentionHoldEnabled parameter to the value $true. **Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RentionHoldEnabled_ will still be $true on the mailbox after the specified date, but MRM will start processing mailbox items as normal. @@ -2647,7 +2779,6 @@ 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, Exchange Online Required: False Position: Named @@ -2657,6 +2788,9 @@ Accept wildcard characters: False ``` ### -EnforcedTimestamps + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill EnforcedTimestamps Description }} @@ -2665,7 +2799,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2675,6 +2808,9 @@ Accept wildcard characters: False ``` ### -ExcludeFromAllOrgHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in Exchange Online. The ExcludeFromAllOrgHolds switch excludes the mailbox from all organization-wide Microsoft 365 retention policies. This switch can only be used for inactive mailboxes. You don't need to specify a value with this switch. @@ -2685,7 +2821,6 @@ When you use this switch, use the DistinguishedName or ExchangeGuid property val Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2695,6 +2830,9 @@ Accept wildcard characters: False ``` ### -ExcludeFromOrgHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in Exchange Online. The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'. @@ -2707,7 +2845,6 @@ When you use this parameter, use the DistinguishedName or ExchangeGuid property Type: String[] Parameter Sets: ExcludeFromOrgHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2717,6 +2854,9 @@ Accept wildcard characters: False ``` ### -ExtendedPropertiesCountQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExtendedPropertiesCountQuota property is used to configure the Named Properties and NonMAPI Named Properties quotas for a mailbox. This should typically only be done if you are experiencing QuotaExceededException or MapiExceptionNamedPropsQuotaExceeded errors. @@ -2725,7 +2865,6 @@ The ExtendedPropertiesCountQuota property is used to configure the Named Propert Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2735,6 +2874,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -2747,7 +2889,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 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 @@ -2757,6 +2898,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -2769,7 +2913,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 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 @@ -2779,6 +2922,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -2791,7 +2937,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 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 @@ -2801,6 +2946,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -2813,7 +2961,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 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 @@ -2823,6 +2970,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -2835,7 +2985,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 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 @@ -2845,6 +2994,9 @@ Accept wildcard characters: False ``` ### -ExternalOofOptions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalOofOptions parameter specifies the automatic replies or Out of Office (also known OOF) message options that are available for the mailbox. Valid values are: - External: Automatic replies can be configured for external senders. This is the default value. @@ -2854,7 +3006,6 @@ The ExternalOofOptions parameter specifies the automatic replies or Out of Offic Type: ExternalOofOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2864,6 +3015,9 @@ Accept wildcard characters: False ``` ### -FolderHierarchyChildrenCountReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner won't be able to create a new subfolder when this limit is reached. @@ -2874,7 +3028,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2884,6 +3037,9 @@ Accept wildcard characters: False ``` ### -FolderHierarchyChildrenCountWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FolderHierarchyChildrenCountWarningQuota parameter specifies the number of subfolders that can be created in a mailbox folder before Exchange sends a warning message to the mailbox owner and logs an event to the application event log. When this quota is reached, warning messages and logged events occur once a day. @@ -2894,7 +3050,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2904,6 +3059,9 @@ Accept wildcard characters: False ``` ### -FolderHierarchyDepthReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner won't be able to create another level in the folder hierarchy of the mailbox folder when this limit is reached. @@ -2914,7 +3072,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2924,6 +3081,9 @@ Accept wildcard characters: False ``` ### -FolderHierarchyDepthWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FolderHierarchyDepthWarningQuota parameter specifies the number of levels in the folder hierarchy of a mailbox folder that can be created before Exchange sends a warning message to the mailbox owner and logs an event to the application event log. When this quota is reached, warning messages and logged events occur once a day. @@ -2934,7 +3094,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2944,6 +3103,9 @@ Accept wildcard characters: False ``` ### -FoldersCountReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, no new folders will be able to be created. @@ -2954,7 +3116,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2964,6 +3125,9 @@ Accept wildcard characters: False ``` ### -FoldersCountWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The FoldersCountWarningQuota parameter is used to display a warning message that the folder hierarchy is full when the value specified for this parameter is reached. This parameter is typically used for public folder mailboxes. @@ -2974,7 +3138,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2984,6 +3147,9 @@ 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. @@ -2992,7 +3158,6 @@ 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 Required: False Position: Named @@ -3002,6 +3167,9 @@ Accept wildcard characters: False ``` ### -ForwardingAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForwardingAddress parameter specifies a forwarding address in your organization for messages that are sent to this mailbox. You can use any value that uniquely identifies the internal recipient. For example: - Name @@ -3024,7 +3192,6 @@ If you configure values for both the ForwardingAddress and ForwardingSmtpAddress Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3034,6 +3201,9 @@ Accept wildcard characters: False ``` ### -ForwardingSmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForwardingSmtpAddress parameter specifies a forwarding SMTP address for messages that are sent to this mailbox. Typically, you use this parameter to specify external email addresses that aren't validated. How messages are delivered and forwarded is controlled by the DeliverToMailboxAndForward parameter. @@ -3049,7 +3219,6 @@ If you configure values for both the ForwardingAddress and ForwardingSmtpAddress Type: ProxyAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3059,6 +3228,9 @@ Accept wildcard characters: False ``` ### -GMGen + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GMGen parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for group metrics generation for the organization. In MailTips, group metrics information is used to indicate the number of recipients in a message or whether recipients are outside your organization. You can use this parameter only on an arbitration mailbox. @@ -3069,7 +3241,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3079,6 +3250,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mailbox. Although messages send on behalf of the mailbox clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the mailbox, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -3104,7 +3278,6 @@ By default, this parameter is blank, which means no one else has permission to s 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 @@ -3114,6 +3287,9 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't need to specify a value with this switch. @@ -3122,7 +3298,6 @@ The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't ne Type: MailboxIdParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3132,6 +3307,9 @@ 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 this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -3141,7 +3319,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is 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 @@ -3151,6 +3328,9 @@ 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. @@ -3164,7 +3344,6 @@ This switch enables the command to access Active Directory objects that aren't c Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3174,6 +3353,9 @@ Accept wildcard characters: False ``` ### -ImListMigrationCompleted + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ImListMigrationCompleted parameter specifies whether a user's Lync or Skype for Business contact list is stored in their mailbox. @@ -3191,7 +3373,6 @@ If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's L Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3201,6 +3382,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -3209,7 +3393,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service 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 @@ -3219,6 +3402,9 @@ Accept wildcard characters: False ``` ### -InactiveMailbox + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The InactiveMailbox switch specifies that the mailbox is an inactive mailbox. You don't need to specify a value with this switch. @@ -3235,7 +3421,6 @@ You can't use this switch to modify other properties on inactive mailboxes. Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3245,6 +3430,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromServingHierarchy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox. You should use this parameter only during public folder migrations. Don't use this parameter once the initial migration validation is complete. @@ -3253,7 +3441,6 @@ You should use this parameter only during public folder migrations. Don't use th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3263,6 +3450,9 @@ Accept wildcard characters: False ``` ### -IsHierarchyReady + +> 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. @@ -3271,7 +3461,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3281,6 +3470,9 @@ Accept wildcard characters: False ``` ### -IsHierarchySyncEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -3289,7 +3481,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3299,6 +3490,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -3321,7 +3515,6 @@ In on-premises Exchange, the default value of this parameter is unlimited. When 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 @@ -3331,6 +3524,9 @@ Accept wildcard characters: False ``` ### -JournalArchiveAddress + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -3339,7 +3535,6 @@ This parameter is reserved for internal Microsoft use. Type: SmtpAddress Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3349,6 +3544,9 @@ Accept wildcard characters: False ``` ### -Languages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Languages parameter specifies the language preferences for this mailbox, in order of preference. Several Exchange components display information to a mailbox user in the preferred language, if that language is supported. Some of those components include quota messages, non-delivery reports (NDRs), the Outlook on the web user interface, and Unified Messaging (UM) voice prompts. 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). @@ -3361,7 +3559,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -3371,6 +3568,9 @@ 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 specified by the LinkedDomainController parameter. @@ -3381,7 +3581,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3391,6 +3590,9 @@ 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. @@ -3399,7 +3601,6 @@ The LinkedDomainController parameter specifies the domain controller in the fore Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3409,6 +3610,9 @@ 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: @@ -3422,7 +3626,6 @@ The LinkedMasterAccount parameter specifies the master account in the forest whe Type: UserIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3432,6 +3635,9 @@ Accept wildcard characters: False ``` ### -LitigationHoldDate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LitigationHoldDate parameter specifies the date that the mailbox is placed on litigation hold. The parameter is populated automatically when you place a mailbox on litigation hold. The date you specify can be used for informational or reporting purposes. When you use the LitigationHoldEnabled parameter to place the mailbox on litigation hold, you can specify any date using the LitigationHoldDate parameter. However, the mailbox is actually placed on litigation hold when you run the command to place the mailbox on litigation hold. @@ -3440,7 +3646,6 @@ When you use the LitigationHoldEnabled parameter to place the mailbox on litigat Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3450,6 +3655,9 @@ Accept wildcard characters: False ``` ### -LitigationHoldDuration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LitigationHoldDuration parameter specifies how long mailbox items are held if the mailbox is placed on litigation hold. The duration is calculated from the date a mailbox item is received or created. A valid value is an integer that represents the number of days, or the value unlimited. The default value is unlimited, which means items are held indefinitely or until the hold is removed. @@ -3458,7 +3666,6 @@ A valid value is an integer that represents the number of days, or the value unl 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 @@ -3468,6 +3675,9 @@ Accept wildcard characters: False ``` ### -LitigationHoldEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are: - $true: The mailbox is on litigation hold. @@ -3481,7 +3691,6 @@ Placing public folder mailboxes on Litigation Hold isn't supported. To place pub 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 @@ -3491,13 +3700,15 @@ Accept wildcard characters: False ``` ### -LitigationHoldOwner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LitigationHoldOwner parameter specifies the user who placed the mailbox on litigation hold. If you don't use this parameter when you place the mailbox on litigation hold, the value is populated automatically. If you use this parameter when you place the mailbox on litigation hold, you can specify a text value. If the value contains spaces, include the value in quotation marks ("). You can use this value for informational and reporting purposes. ```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 @@ -3507,6 +3718,9 @@ Accept wildcard characters: False ``` ### -MailboxMessagesPerFolderCountReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is an available only in on-premises Exchange. The MailboxMessagesPerFolderCountReceiveQuota parameter specifies the maximum number of messages for a mailbox folder. When this limit is reached, the folder can't receive new messages. @@ -3519,7 +3733,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3529,6 +3742,9 @@ Accept wildcard characters: False ``` ### -MailboxMessagesPerFolderCountWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is an available only in on-premises Exchange. The MailboxMessagesPerFolderCountWarningQuota parameter specifies the number of messages that a mailbox folder can hold before Exchange sends a warning message to the mailbox owner and logs an event to the application event log. When this quota is reached, warning messages and logged events occur once a day. @@ -3541,7 +3757,6 @@ To see the current value of this property, run the command `Get-MailboxStatistic Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3551,6 +3766,9 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments. @@ -3563,7 +3781,6 @@ To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the Type: String Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3573,6 +3790,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -3584,7 +3804,6 @@ When you add a MailTip to a recipient, two things happen: 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 @@ -3594,6 +3813,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -3608,7 +3830,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo 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 @@ -3618,6 +3839,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicy + +> Applicable: Exchange Server 2010 + This parameter is functional only in Exchange Server 2010. The ManagedFolderMailboxPolicy parameter specifies a managed folder mailbox policy that controls MRM for the mailbox. If the parameter is set to $null, Exchange removes the managed folder mailbox policy from the mailbox but any managed folders in the mailbox remain. @@ -3626,7 +3850,6 @@ The ManagedFolderMailboxPolicy parameter specifies a managed folder mailbox poli Type: MailboxPolicyIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -3636,6 +3859,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderMailboxPolicyAllowed + +> Applicable: Exchange Server 2010 + This parameter is functional only in Exchange Server 2010. The ManagedFolderMailboxPolicyAllowed switch bypasses the warning that MRM features aren't supported for clients running versions of Outlook earlier than Outlook 2007. You don't need to specify a value with this switch. @@ -3648,7 +3874,6 @@ Although Outlook 2003 Service Pack 3 clients are supported, they have limited MR Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -3658,6 +3883,9 @@ Accept wildcard characters: False ``` ### -Management + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Management parameter specifies whether the arbitration mailbox (also call an organization mailbox) is used to manage mailbox moves and mailbox migrations. You can use this parameter only on an arbitration mailbox. @@ -3668,7 +3896,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3678,6 +3905,9 @@ Accept wildcard characters: False ``` ### -MaxBlockedSenders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxBlockedSenders parameter specifies the maximum number of senders that can be included in the blocked senders list. Blocked senders are senders that are considered junk senders by the mailbox and are used in junk email rules. This parameter is validated only when the junk email rules are updated using Outlook on the web or Exchange Web Services. @@ -3686,7 +3916,6 @@ The MaxBlockedSenders parameter specifies the maximum number of senders that can Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3696,6 +3925,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mailbox. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -3721,7 +3953,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify 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 @@ -3731,6 +3962,9 @@ Accept wildcard characters: False ``` ### -MaxSafeSenders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxSafeSenders parameter specifies the maximum number of senders that can be included in the safe senders list. Safe senders are senders that are trusted by the mailbox and are used in junk email rules. This parameter is validated only when the junk email rules are updated using cloud-based organizations or services. @@ -3739,7 +3973,6 @@ The MaxSafeSenders parameter specifies the maximum number of senders that can be Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3749,6 +3982,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mailbox. When you enter a value, qualify the value with one of the following units: @@ -3774,7 +4010,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify 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 @@ -3784,6 +4019,9 @@ Accept wildcard characters: False ``` ### -MessageCopyForSendOnBehalfEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: Previously, this parameter was available only for shared mailboxes. In Exchange Online or Exchange 2016 CU6 or later, this parameter is also available for user mailboxes. This parameter is not available for linked user mailboxes. The MessageCopyForSendOnBehalfEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send on behalf of" permission. Valid values are: @@ -3797,7 +4035,6 @@ You give users permission to send on behalf of a mailbox by using the GrantSendO Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3807,6 +4044,9 @@ Accept wildcard characters: False ``` ### -MessageCopyForSentAsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: Previously, this parameter was available only for shared mailboxes. In Exchange Online or Exchange 2016 CU6 or later, this parameter is also available for user mailboxes. This parameter is not available for linked user mailboxes. The MessageCopyForSentAsEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send as" permission. Valid values are: @@ -3822,7 +4062,6 @@ In on-premises Exchange, you give a user permission to send as a mailbox by runn Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3832,6 +4071,9 @@ Accept wildcard characters: False ``` ### -MessageCopyForSMTPClientSubmissionEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MessageCopyForSMTPClientSubmissionEnabled parameter specifies whether to copy the sender for messages that are sent using SMTP client submission (SMTP AUTH). Valid values are: @@ -3843,7 +4085,6 @@ The MessageCopyForSMTPClientSubmissionEnabled parameter specifies whether to cop Type: Boolean Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3853,6 +4094,9 @@ Accept wildcard characters: False ``` ### -MessageTracking + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MessageTracking parameter specifies whether the arbitration mailbox (also called an organization mailbox) is the anchor mailbox that's used for cross-organizational message tracking scenarios. By default, the message tracking organizational capability is assigned to the arbitration mailbox named SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}. You can use this parameter only on an arbitration mailbox. @@ -3863,7 +4107,6 @@ Valid values are$true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: FalseNamed Position: @@ -3873,6 +4116,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingReadStatusEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MessageTrackingReadStatusEnabled parameter specifies whether to include detailed information in delivery reports for messages sent to the mailbox. Valid values are: - $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This is the default value. @@ -3882,7 +4128,6 @@ The MessageTrackingReadStatusEnabled parameter specifies whether to include deta 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 @@ -3892,6 +4137,9 @@ Accept wildcard characters: False ``` ### -MicrosoftOnlineServicesID + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MicrosoftOnlineServicesID parameter specifies the Microsoft work or school account for the mailbox (for example, lila@contoso.onmicrosoft.com). @@ -3900,7 +4148,6 @@ The MicrosoftOnlineServicesID parameter specifies the Microsoft work or school a Type: SmtpAddress Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3910,6 +4157,9 @@ Accept wildcard characters: False ``` ### -Migration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Migration switch is required to modify migration mailboxes. You don't need to specify a value with this switch. @@ -3918,7 +4168,6 @@ The Migration switch is required to modify migration mailboxes. You don't need t Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3928,6 +4177,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 @@ -3947,7 +4199,6 @@ You need to use this parameter to specify at least one moderator when you set 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 @@ -3957,6 +4208,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -3968,7 +4222,6 @@ 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 Required: False Position: Named @@ -3978,6 +4231,9 @@ Accept wildcard characters: False ``` ### -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 mailbox. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). In the cloud-based service, many special characters aren't allowed in the Name value (for example, ö, ü, or ä). For more information, see [Error when you try to create a username that contains a special character in Microsoft 365](https://learn.microsoft.com/office/troubleshoot/office-suite-issues/username-contains-special-character). @@ -3986,7 +4242,6 @@ In the cloud-based service, many special characters aren't allowed in the Name v 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 @@ -3996,6 +4251,9 @@ Accept wildcard characters: False ``` ### -NewPassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The NewPassword parameter is used with the OldPassword parameter when a user changes their own password in Outlook on the web. By default, the NewPassword and OldPassword parameters are also available to members of the Help Desk and Organization Management role groups via the User Options role. However, administrators use the Password parameter to reset a user's password, because that parameter doesn't require the user's current password. @@ -4010,7 +4268,6 @@ You can use the following methods as a value for this parameter: Type: SecureString Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4020,6 +4277,9 @@ Accept wildcard characters: False ``` ### -NonCompliantDevices + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill NonCompliantDevices Description }} @@ -4028,7 +4288,6 @@ This parameter is available only in the cloud-based service. Type: MultiValuedProperty Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4038,6 +4297,9 @@ Accept wildcard characters: False ``` ### -OABGen + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The OABGen parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for offline address book (OAB) file generation and storage for the organization. OAB requests are sent to the server where this arbitration mailbox is located. You can use this parameter only on an arbitration mailbox. @@ -4048,7 +4310,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4058,13 +4319,15 @@ Accept wildcard characters: False ``` ### -Office + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Office parameter specifies the user's physical office name or number. ```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 @@ -4074,6 +4337,9 @@ Accept wildcard characters: False ``` ### -OfflineAddressBook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The OfflineAddressBook parameter specifies the offline address book (OAB) that's associated with the mailbox. You can use any value that uniquely identifies the OAB. For example: @@ -4088,7 +4354,6 @@ Use the Get-OfflineAddressBook cmdlet to see the available offline address books Type: OfflineAddressBookIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4098,6 +4363,9 @@ Accept wildcard characters: False ``` ### -OldPassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The OldPassword parameter is used with the NewPassword parameter when a user changes their own password in Outlook on the web. By default, the NewPassword and OldPassword parameters are also available to members of the Help Desk and Organization Management role groups via the User Options role. However, administrators typically use the Password parameter to reset a user's password, because that parameter doesn't require the user's current password. @@ -4112,7 +4380,6 @@ You can use the following methods as a value for this parameter: Type: SecureString Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4122,6 +4389,9 @@ Accept wildcard characters: False ``` ### -OMEncryption + +> 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. @@ -4130,7 +4400,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4140,6 +4409,9 @@ Accept wildcard characters: False ``` ### -OMEncryptionStore + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. PARAMVALUE: Boolean @@ -4148,7 +4420,6 @@ PARAMVALUE: Boolean Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4158,6 +4429,9 @@ Accept wildcard characters: False ``` ### -Password + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Password parameter resets the password of the user account that's associated with the mailbox to the value you specify. To use this parameter on a mailbox other than your own, consider the following options: - Exchange Online: You can't use this parameter to change another user's password. Use the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. @@ -4173,7 +4447,6 @@ You can use the following methods as a value for this parameter: Type: SecureString Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4183,6 +4456,9 @@ 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. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. @@ -4195,7 +4471,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm Type: SmtpAddress Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4205,6 +4480,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send new messages, and the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -4227,7 +4505,6 @@ In on-premises Exchange, the default value of this parameter is unlimited. When 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 @@ -4237,6 +4514,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendReceiveQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -4259,7 +4539,6 @@ In on-premises Exchange, the default value of this parameter is unlimited. When 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 @@ -4269,6 +4548,9 @@ Accept wildcard characters: False ``` ### -ProvisionedForOfficeGraph + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -4277,7 +4559,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -4287,6 +4568,9 @@ Accept wildcard characters: False ``` ### -PstProvider + +> 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. @@ -4295,7 +4579,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4305,6 +4588,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolder switch is required to modify public folder mailboxes. 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. @@ -4313,7 +4599,6 @@ 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 @@ -4323,6 +4608,9 @@ Accept wildcard characters: False ``` ### -QueryBaseDN + +> 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. @@ -4331,7 +4619,6 @@ This parameter is reserved for internal Microsoft use. Type: OrganizationalUnitIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4341,6 +4628,9 @@ Accept wildcard characters: False ``` ### -RecalculateInactiveMailbox + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RecalculateInactiveMailbox switch specifies whether to recalculate the hold status of an inactive mailbox. You don't need to specify a value with this switch. @@ -4353,7 +4643,6 @@ You use this switch with the InactiveMailbox switch and the Identity parameter ( Type: SwitchParameter Parameter Sets: RecalculateInactiveMailbox Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4363,6 +4652,9 @@ Accept wildcard characters: False ``` ### -RecipientLimits + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RecipientLimits parameter specifies the maximum number of recipients allowed in messages sent by the mailbox. In on-premises Exchange, a valid value is an integer or the value unlimited. The default value is unlimited, which indicates the maximum number of recipients per message for the mailbox is controlled elsewhere (for example, organization, server, or connector limits). @@ -4373,7 +4665,6 @@ In the cloud-based service, a valid value is an integer from 1 to 1000. The defa Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4383,6 +4674,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder of the mailbox. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages. @@ -4407,7 +4701,6 @@ When the UseDatabaseQuotaDefaults parameter is set to the value $true (the defau Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4417,6 +4710,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for the mailbox. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log. @@ -4441,7 +4737,6 @@ When the UseDatabaseQuotaDefaults parameter is set to the value $true (the defau Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4451,6 +4746,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -4474,7 +4772,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -4484,6 +4781,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -4507,7 +4807,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -4517,6 +4816,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -4542,7 +4844,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce 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 @@ -4552,6 +4853,9 @@ Accept wildcard characters: False ``` ### -RemoteRecipientType + +> 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. @@ -4560,7 +4864,6 @@ This parameter is reserved for internal Microsoft use. Type: RemoteRecipientType Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4570,6 +4873,9 @@ Accept wildcard characters: False ``` ### -RemoveDelayHoldApplied + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RemoveDelayHoldApplied switch specifies whether to remove delay holds on email-related data (generated by Outlook or Outlook on the web) from the mailbox. You don't need to specify a value with this switch. @@ -4583,7 +4889,6 @@ For more information, see [Managing mailboxes on delay hold](https://learn.micro Type: SwitchParameter Parameter Sets: RemoveDelayHoldApplied Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4593,6 +4898,9 @@ Accept wildcard characters: False ``` ### -RemoveDelayReleaseHoldApplied + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RemoveDelayReleaseHoldApplied switch specifies whether to remove delay holds on cloud data generated by non-Exchange apps (such as Teams, Forms, and Viva Engage) from the mailbox. Data generated by a non-Exchange cloud-based app is typically stored in a hidden folder in the mailbox. You don't need to specify a value with this switch. @@ -4607,7 +4915,6 @@ For more information, see [Managing mailboxes on delay hold](https://learn.micro Type: SwitchParameter Parameter Sets: RemoveDelayReleaseHoldApplied Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -4617,6 +4924,9 @@ Accept wildcard characters: False ``` ### -RemoveDisabledArchive + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The RemoveDisabledArchive switch specifies whether to remove the disabled archive that's associated with the mailbox. You don't need to specify a value with this switch. @@ -4625,7 +4935,6 @@ The RemoveDisabledArchive switch specifies whether to remove the disabled archiv Type: SwitchParameter Parameter Sets: RemoveDisabledArchive Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -4635,6 +4944,9 @@ Accept wildcard characters: False ``` ### -RemoveMailboxProvisioningConstraint + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill RemoveMailboxProvisioningConstraint Description }} @@ -4643,7 +4955,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4653,6 +4964,9 @@ Accept wildcard characters: False ``` ### -RemoveManagedFolderAndPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveManagedFolderAndPolicy switch specifies whether to remove all MRM policies and attributes from a mailbox. You don't need to specify a value with this switch. @@ -4661,7 +4975,6 @@ The RemoveManagedFolderAndPolicy switch specifies whether to remove all MRM poli Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4671,6 +4984,9 @@ Accept wildcard characters: False ``` ### -RemoveOrphanedHolds + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RemoveOrphanedHolds parameter is used to remove the mailbox (typically, an inactive mailbox) from In-Place Holds that no longer exist, but are still applied to the mailbox. You identify the In-Place Hold by using its GUID value. You can specify multiple GUID values separated by commas. @@ -4683,7 +4999,6 @@ In an Exchange hybrid deployment, In-Place Holds that are created in the on-prem Type: String[] Parameter Sets: RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4693,6 +5008,9 @@ Accept wildcard characters: False ``` ### -RemovePicture + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemovePicture switch specifies whether to remove the picture from the mailbox. You don't need to specify a value with this switch. @@ -4703,7 +5021,6 @@ You can add a picture to a mailbox by using the Import-RecipientDataProperty cmd Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4713,6 +5030,9 @@ Accept wildcard characters: False ``` ### -RemoveSpokenName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RemoveSpokenName parameter specifies whether to remove the spoken name from the mailbox. You don't need to specify a value with this switch. @@ -4723,7 +5043,6 @@ You can add a sound file to a mailbox by using the Import-RecipientDataProperty Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4733,6 +5052,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -4742,7 +5064,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes 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 @@ -4752,6 +5073,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are: @@ -4765,7 +5089,6 @@ In Exchange Online, administrators can require users to reset their password the Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4775,13 +5098,15 @@ Accept wildcard characters: False ``` ### -ResourceCapacity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResourceCapacity parameter specifies the capacity of the resource mailbox. For example, you can use this parameter to identify the number of seats in a conference room (room mailbox) or in a vehicle (equipment mailbox). A valid value is an integer. ```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 @@ -4791,6 +5116,9 @@ Accept wildcard characters: False ``` ### -ResourceCustom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResourceCustom parameter specifies one or more custom resource properties to add to the resource mailbox. You can use this parameter only on resource mailboxes. You use the Set-ResourceConfig and Get-ResourceConfig cmdlets to create and view custom resource properties. @@ -4805,7 +5133,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -4815,6 +5142,9 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsFor + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetainDeletedItemsFor parameter specifies the length of time to keep soft-deleted items for the mailbox. Soft-deleted items are items that have been deleted by using any of these methods: - Deleting items from the Deleted Items folder. @@ -4837,7 +5167,6 @@ In on-premises Exchange, when the UseDatabaseQuotaDefaults parameter on the mail Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4847,6 +5176,9 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsUntilBackup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: @@ -4862,7 +5194,6 @@ For more information, see [Recoverable Items folder in Exchange Server](https:// Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -4872,6 +5203,9 @@ Accept wildcard characters: False ``` ### -RetentionComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RetentionComment parameter specifies a comment that's displayed in Outlook regarding the user's retention hold status. In on-premises Exchange, you can only use this parameter if the RetentionHoldEnabled parameter is set to $true. @@ -4884,7 +5218,6 @@ This comment should be localized to the user's preferred language. If the commen 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 @@ -4894,6 +5227,9 @@ Accept wildcard characters: False ``` ### -RetentionHoldEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionHoldEnabled parameter specifies whether the mailbox is placed on retention hold. Placing the mailbox on retention hold temporarily suspends the processing of retention policies or managed folder mailbox policies for the mailbox (for example, when the user is on vacation). Valid values are: - $true: The mailbox is placed on retention hold. Retention policies and managed folder policies are suspended for the mailbox, and purging items from the mailbox isn't possible (even using MFCMapi). @@ -4905,7 +5241,6 @@ To set the start date for retention hold, use the StartDateForRetentionHold para 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 @@ -4915,6 +5250,9 @@ Accept wildcard characters: False ``` ### -RetentionPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionPolicy parameter specifies the retention policy that you want applied to this mailbox. You can use any value that uniquely identifies the policy. For example: - Name @@ -4929,7 +5267,6 @@ Use the Get-RetentionPolicy cmdlet to see the available retention policies. Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4939,6 +5276,9 @@ Accept wildcard characters: False ``` ### -RetentionUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RetentionUrl parameter specifies the URL or an external web page with additional details about the organization's messaging retention policies. This URL can be used to expose details regarding retention policies in general, which is usually a customized legal or IT website for the company. @@ -4947,7 +5287,6 @@ This URL can be used to expose details regarding retention policies in general, 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 @@ -4957,6 +5296,9 @@ Accept wildcard characters: False ``` ### -RoleAssignmentPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RoleAssignmentPolicy parameter specifies the role assignment policy that's assigned to the mailbox. You can use any value that uniquely identifies the role assignment policy. For example: - Name @@ -4971,7 +5313,6 @@ Use the Get-RoleAssignmentPolicy cmdlet to see the available role assignment pol Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -4981,6 +5322,9 @@ Accept wildcard characters: False ``` ### -RoomMailboxPassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. Use the RoomMailboxPassword parameter to configure the password for the account that's associated with the room mailbox when that account is enabled and able to log in (the EnableRoomMailboxAccount parameter is set to the value $true). @@ -5005,7 +5349,6 @@ To configure the password for a room mailbox account in Exchange Online, use the Type: SecureString Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5015,6 +5358,9 @@ Accept wildcard characters: False ``` ### -RulesQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RulesQuota parameter specifies the limit for the size of Inbox rules for the mailbox. When you enter a value, qualify the value with one of the following: A valid value is a number from 32 to 256 kilobytes (32768 to 262144 bytes). When you enter a value, qualify the value with one of the following units: @@ -5034,7 +5380,6 @@ The quota for Inbox rules applies only to enabled rules. There is no restriction Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5044,6 +5389,9 @@ 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). The maximum length is 20 characters. @@ -5052,7 +5400,6 @@ The SamAccountName parameter (also known as the pre-Windows 2000 user account or Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5062,6 +5409,9 @@ Accept wildcard characters: False ``` ### -SchedulerAssistant + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SchedulerAssistant Description }} @@ -5070,7 +5420,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -5080,6 +5429,9 @@ Accept wildcard characters: False ``` ### -SCLDeleteEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLDeleteEnabled parameter specifies whether to silently delete messages that meet or exceed the spam confidence level (SCL) specified by the SCLDeleteThreshold parameter. Valid values are: @@ -5092,7 +5444,6 @@ The SCLDeleteEnabled parameter specifies whether to silently delete messages tha Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5102,6 +5453,9 @@ Accept wildcard characters: False ``` ### -SCLDeleteThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLDeleteThreshold parameter specifies the SCL delete threshold. When the SCLDeleteEnabled parameter is set to $true, messages with an SCL greater than or equal to the specified value are silently deleted. @@ -5112,7 +5466,6 @@ A valid value is an integer from 0 through 9. This value should be greater than Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5122,6 +5475,9 @@ Accept wildcard characters: False ``` ### -SCLJunkEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLJunkEnabled parameter specifies whether messages that exceed(not meet) the SCL specified by the SCLJunkThreshold parameter are moved to the Junk Email folder. Valid values are: @@ -5134,7 +5490,6 @@ The SCLJunkEnabled parameter specifies whether messages that exceed(not meet) th Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5144,6 +5499,9 @@ Accept wildcard characters: False ``` ### -SCLJunkThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLJunkThreshold parameter specifies the SCL Junk Email folder threshold. When the SCLJunkEnabled parameter is set to $true, messages with an SCL greater than (not equal to) the specified value are moved to the Junk Email folder. @@ -5154,7 +5512,6 @@ A valid value is an integer from 0 through 9. This value should be less than the Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5164,6 +5521,9 @@ Accept wildcard characters: False ``` ### -SCLQuarantineEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLQuarantineEnabled parameter specifies whether messages that meet or exceed the SCL specified by the SCLQuarantineThreshold parameter are quarantined. If a message is quarantined, it's sent to the quarantine mailbox where administrators can review it. Valid values are: @@ -5178,7 +5538,6 @@ To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](h Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5188,6 +5547,9 @@ Accept wildcard characters: False ``` ### -SCLQuarantineThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLQuarantineThreshold parameter specifies the SCL quarantine threshold. When the SCLQuarantineEnabled parameter is set to $true, messages with an SCL greater than or equal to the specified value are quarantined. @@ -5198,7 +5560,6 @@ A valid value is an integer from 0 through 9. This value should be less than the Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5208,6 +5569,9 @@ Accept wildcard characters: False ``` ### -SCLRejectEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLRejectEnabled parameter specifies whether messages that meet or exceed the SCL specified by the SCLRejectThreshold parameter are rejected. Valid values are: @@ -5220,7 +5584,6 @@ The SCLRejectEnabled parameter specifies whether messages that meet or exceed th Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5230,6 +5593,9 @@ Accept wildcard characters: False ``` ### -SCLRejectThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLRejectThreshold parameter specifies the SCL reject threshold. When the SCLRejectEnabled parameter is set to $true, messages with an SCL greater than or equal to the specified value are rejected, and an NDR is sent to the sender. @@ -5240,7 +5606,6 @@ A valid value is an integer from 0 through 9. This value should be less than the Type: Int32 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5250,6 +5615,9 @@ Accept wildcard characters: False ``` ### -SecondaryAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SecondaryAddress parameter specifies the secondary address used by the UM-enabled user. @@ -5258,7 +5626,6 @@ The SecondaryAddress parameter specifies the secondary address used by the UM-en Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5268,6 +5635,9 @@ Accept wildcard characters: False ``` ### -SecondaryDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This parameter is provided to create a secondary proxy address. @@ -5276,7 +5646,6 @@ The SecondaryDialPlan parameter specifies a secondary UM dial plan to use. This Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5286,6 +5655,9 @@ Accept wildcard characters: False ``` ### -SendModerationNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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. @@ -5298,7 +5670,6 @@ 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 Required: False Position: Named @@ -5308,6 +5679,9 @@ Accept wildcard characters: False ``` ### -SharingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SharingPolicy parameter specifies the sharing policy that's assigned to the mailbox. You can use any value that uniquely identifies the sharing policy. For example: - Name @@ -5320,7 +5694,6 @@ Use the Get-SharingPolicy cmdlet to see the available sharing policies. Type: SharingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5330,6 +5703,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -5342,7 +5718,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -5352,6 +5727,9 @@ Accept wildcard characters: False ``` ### -SingleItemRecoveryEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are: - $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This is the default value in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery). @@ -5361,7 +5739,6 @@ The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recover 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 @@ -5371,6 +5748,9 @@ Accept wildcard characters: False ``` ### -SkipDualWrite + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange This parameter is reserved for internal Microsoft use. @@ -5379,7 +5759,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5389,6 +5768,9 @@ Accept wildcard characters: False ``` ### -StartDateForRetentionHold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartDateForRetentionHold parameter specifies the start date for the retention hold that's placed on the mailbox. 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". @@ -5399,7 +5781,6 @@ To use this parameter, you need to set the RetentionHoldEnabled parameter to val Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5409,13 +5790,15 @@ Accept wildcard characters: False ``` ### -StsRefreshTokensValidFrom + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5425,6 +5808,9 @@ Accept wildcard characters: False ``` ### -SystemMessageSizeShutoffQuota + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -5433,7 +5819,6 @@ This parameter is reserved for internal Microsoft use. Type: Int64 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5443,6 +5828,9 @@ Accept wildcard characters: False ``` ### -SystemMessageSizeWarningQuota + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -5451,7 +5839,6 @@ This parameter is reserved for internal Microsoft use. Type: Int64 Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5461,6 +5848,9 @@ Accept wildcard characters: False ``` ### -ThrottlingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ThrottlingPolicy parameter specifies the throttling policy that's assigned to the mailbox. You can use any value that uniquely identifies the throttling policy. For example: @@ -5475,7 +5865,6 @@ Use the Get-ThrottlingPolicy cmdlet to see the available throttling policies. Type: ThrottlingPolicyIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5485,6 +5874,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Type parameter specifies the mailbox type for the mailbox. Valid values are: - Equipment @@ -5498,7 +5890,6 @@ The Type parameter specifies the mailbox type for the mailbox. Valid values are: Type: ConvertibleMailboxSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -5508,6 +5899,9 @@ Accept wildcard characters: False ``` ### -UMDataStorage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDataStorage parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used to store UM call data records and UM custom prompts. This capability can be assigned to only one arbitration mailbox for the organization. You can use this parameter only on an arbitration mailbox. @@ -5518,7 +5912,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5528,6 +5921,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -5548,7 +5944,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5558,6 +5953,9 @@ Accept wildcard characters: False ``` ### -UMGrammar + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars will be generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox. @@ -5568,7 +5966,6 @@ Valid values are $true or $false. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5578,6 +5975,9 @@ Accept wildcard characters: False ``` ### -UpdateEnforcedTimestamp + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill UpdateEnforcedTimestamp Description }} @@ -5586,7 +5986,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: RecalculateInactiveMailbox, RemoveDelayHoldApplied, RemoveDisabledArchive, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RemoveDelayReleaseHoldApplied, RemoveOrphanedHolds Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -5596,6 +5995,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseQuotaDefaults + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseDatabaseQuotaDefaults parameter specifies whether applicable quotas for the mailbox are determined by the quota values on the mailbox or the corresponding quota values on the mailbox database (not all mailbox quotas are configurable on the mailbox database). Valid values are: - $true: The mailbox uses the applicable quota values that are configured on the mailbox database. Any corresponding quotas that are configured on the mailbox are ignored. In on-premises Exchange, this is the default value. @@ -5614,7 +6016,6 @@ The following quotas are affected by this parameter: 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 @@ -5624,6 +6025,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseRetentionDefaults + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The UseDatabaseRetentionDefaults parameter specifies whether the retention settings for items in the Recoverable Items folder in the mailbox are determined by the settings on the mailbox or the corresponding settings on the mailbox database. Valid values are: @@ -5645,7 +6049,6 @@ The following retention settings are affected by this parameter: 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 @@ -5655,13 +6058,15 @@ Accept wildcard characters: False ``` ### -UserCertificate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserCertificate parameter specifies the digital certificate used to sign a user's email messages. ```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 @@ -5671,6 +6076,9 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. @@ -5679,7 +6087,6 @@ The UserPrincipalName parameter specifies the logon name for the user account. T Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -5689,13 +6096,15 @@ Accept wildcard characters: False ``` ### -UserSMimeCertificate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserSMimeCertificate parameter specifies the S/MIME certificate that's used to sign a user's email messages. ```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 @@ -5705,13 +6114,15 @@ 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 @@ -5721,6 +6132,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -5732,7 +6146,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md index bf087d92fa..caa8a36b12 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxauditbypassassociation applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxAuditBypassAssociation -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxauditbypassassociation +schema: 2.0.0 +title: Set-MailboxAuditBypassAssociation --- # Set-MailboxAuditBypassAssociation @@ -54,13 +55,15 @@ This example removes the bypass association for the Svc-MyApplication account. ## 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 user or computer account to be bypassed from mailbox audit logging. ```yaml Type: MailboxAuditBypassAssociationIdParameter 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 @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -AuditBypassEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AuditBypassEnabled parameter specifies whether audit bypass is enabled for the user or computer. Valid values include the following: - $true: Enables mailbox audit logging bypass @@ -79,7 +85,6 @@ The AuditBypassEnabled parameter specifies whether audit bypass is enabled for t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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,7 +126,6 @@ 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 @@ -126,13 +135,15 @@ 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/exchange/Set-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md index 24d0f4377e..228bc2f6c2 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md @@ -1,13 +1,14 @@ --- +applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection +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/exchange/set-mailboxautoreplyconfiguration -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxAutoReplyConfiguration schema: 2.0.0 search.appverid: MET150 -author: chrisda -ms.author: chrisda -ms.reviewer: +title: Set-MailboxAutoReplyConfiguration --- # Set-MailboxAutoReplyConfiguration @@ -67,6 +68,9 @@ This example configures Automatic Replies for Tony's mailbox to be sent, specifi ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -84,7 +88,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us 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 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -AutoDeclineFutureRequestsWhenOOF + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The AutoDeclineFutureRequestsWhenOOF parameter specifies whether to automatically decline new meeting requests that are sent to the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: @@ -107,7 +113,6 @@ You can use this parameter only when the AutoReplyState parameter is set to Sche Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -117,6 +122,9 @@ Accept wildcard characters: False ``` ### -AutoReplyState + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are: - Enabled: Automatic Replies are sent for the mailbox. @@ -132,7 +140,6 @@ The Enabled and Scheduled values require these additional settings: Type: OofState Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -142,6 +149,9 @@ 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`. @@ -151,7 +161,6 @@ 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 @@ -161,6 +170,9 @@ Accept wildcard characters: False ``` ### -CreateOOFEvent + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The CreateOOFEvent parameter specifies whether to create a calendar event that corresponds to the scheduled time period when Automatic Replies are being sent for the mailbox. Valid values are: @@ -172,7 +184,6 @@ The CreateOOFEvent parameter specifies whether to create a calendar event that c Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -182,6 +193,9 @@ Accept wildcard characters: False ``` ### -DeclineAllEventsForScheduledOOF + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The DeclineAllEventsForScheduledOOF parameter specifies whether to decline all existing calendar events in the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: @@ -197,7 +211,6 @@ You can't use this parameter with the EventsToDeleteIDs parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -207,6 +220,9 @@ Accept wildcard characters: False ``` ### -DeclineEventsForScheduledOOF + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The DeclineEventsForScheduledOOF parameter specifies whether it's possible to decline existing calendar events in the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are: @@ -223,7 +239,6 @@ You can use this parameter only when the AutoReplyState parameter is set to Sche Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -233,6 +248,9 @@ Accept wildcard characters: False ``` ### -DeclineMeetingMessage + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The DeclineMeetingMessage parameter specifies the text in the message when meetings requests that are sent to the mailbox are automatically declined. For example: @@ -248,7 +266,6 @@ To clear the value of this parameter, use the value $null. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -258,6 +275,9 @@ 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. @@ -266,7 +286,6 @@ 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 @@ -276,6 +295,9 @@ Accept wildcard characters: False ``` ### -EndTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EndTime parameter specifies the end date and time that Automatic Replies are sent for the mailbox. You use this parameter only when the AutoReplyState parameter is set to Scheduled, and the value of this parameter is meaningful only when AutoReplyState is Scheduled. 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". @@ -284,7 +306,6 @@ 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, Exchange Online Required: False Position: Named @@ -294,6 +315,9 @@ Accept wildcard characters: False ``` ### -EventsToDeleteIDs + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The EventsToDeleteIDs parameter specifies the calendar events to delete from the mailbox when the DeclineEventsForScheduledOOF parameter is set to $true. @@ -306,7 +330,6 @@ You can't use this parameter with the DeclineAllEventsForScheduledOOF parameter. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -316,6 +339,9 @@ Accept wildcard characters: False ``` ### -ExternalAudience + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalAudience parameter specifies whether Automatic Replies are sent to external senders. Valid values are: - None: Automatic Replies aren't sent to any external senders. @@ -328,7 +354,6 @@ The value of this parameter is meaningful only when the AutoReplyState parameter Type: ExternalAudience Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -338,6 +363,9 @@ Accept wildcard characters: False ``` ### -ExternalMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalMessage parameter specifies the Automatic Replies message that's sent to external senders or senders outside the organization. If the value contains spaces, enclose the value in quotation marks ("). HTML tags are automatically added to the text. For example, if you enter the text, "I'm on vacation", the value automatically becomes: `I'm on vacation`. Additional HTML tags are supported if you enclose the value in quotation marks. For example, `"I'm on vacation. I'll respond when I return."`. @@ -353,7 +381,6 @@ To clear the value of this parameter when it's no longer required (for example, 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 @@ -363,6 +390,9 @@ 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: @@ -374,7 +404,6 @@ 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 @@ -384,6 +413,9 @@ Accept wildcard characters: False ``` ### -InternalMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalMessage parameter specifies the Automatic Replies message that's sent to internal senders or senders within the organization. If the value contains spaces, enclose the value in quotation marks ("). HTML tags are automatically added to the text. For example, if you enter the text: "I'm on vacation", the value automatically becomes: `I'm on vacation`. Additional HTML tags are supported if you enclose the value in quotation marks. For example, `"I'm on vacation. Please contact my manager."`. @@ -396,7 +428,6 @@ To clear the value of this parameter when it's no longer required (for example, 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 @@ -406,6 +437,9 @@ Accept wildcard characters: False ``` ### -OOFEventSubject + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The OOFEventSubject parameter specifies the subject for the calendar event that's automatically created when the CreateOOFEvent parameter is set to $true. @@ -416,7 +450,6 @@ If the value contains spaces, enclose the value in quotation marks ("). To clear Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -426,6 +459,9 @@ Accept wildcard characters: False ``` ### -StartTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartTime parameter specifies the start date and time that Automatic Replies are sent for the specified mailbox. You use this parameter only when the AutoReplyState parameter is set to Scheduled, and the value of this parameter is meaningful only when AutoReplyState is Scheduled. 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". @@ -434,7 +470,6 @@ 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, Exchange Online Required: False Position: Named @@ -444,13 +479,15 @@ 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/exchange/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md index 78d43a57d3..86389e1f41 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxcalendarconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxCalendarConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxcalendarconfiguration +schema: 2.0.0 +title: Set-MailboxCalendarConfiguration --- # Set-MailboxCalendarConfiguration @@ -185,6 +186,9 @@ This example sets the working day's starting hour to 7 A.M. for the calendar of ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -202,7 +206,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -212,13 +215,15 @@ Accept wildcard characters: False ``` ### -AgendaMailEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -228,6 +233,9 @@ Accept wildcard characters: False ``` ### -AgendaMailIntroductionEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AgendaMailIntroductionEnabled Description }} @@ -236,7 +244,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -246,6 +253,9 @@ Accept wildcard characters: False ``` ### -AgendaPaneEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -254,7 +264,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -264,6 +273,9 @@ Accept wildcard characters: False ``` ### -AutoDeclineWhenBusy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AutoDeclineWhenBusy Description }} @@ -272,7 +284,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -282,6 +293,9 @@ Accept wildcard characters: False ``` ### -CalendarFeedsPreferredLanguage + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The CalendarFeedsPreferredLanguage parameter specifies the preferred language for calendar feeds. A valid value is an ISO 639-1 lowercase two-letter language code (for example, en for English). @@ -290,7 +304,6 @@ The CalendarFeedsPreferredLanguage parameter specifies the preferred language fo Type: String Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -300,6 +313,9 @@ Accept wildcard characters: False ``` ### -CalendarFeedsPreferredRegion + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The CalendarFeedsPreferredRegion specifies the preferred region for calendar feeds. A valid value is an ISO 3166-1 two-letter country code (for example, AU for Australia). @@ -310,7 +326,6 @@ A reference for two-letter country codes is available at [Country Codes List](ht Type: String Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -320,6 +335,9 @@ Accept wildcard characters: False ``` ### -CalendarFeedsRootPageId + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The CalendarFeedsRootPageId parameter specifies the root page ID for calendar feeds. @@ -328,7 +346,6 @@ The CalendarFeedsRootPageId parameter specifies the root page ID for calendar fe Type: String Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -338,6 +355,9 @@ 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`. @@ -347,7 +367,6 @@ 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 @@ -357,6 +376,9 @@ Accept wildcard characters: False ``` ### -ConversationalSchedulingEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are: - $true: Conversational scheduling is enabled. This is the default value. @@ -366,7 +388,6 @@ The ConversationalSchedulingEnabled parameter specifies whether to enable or dis Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -376,6 +397,9 @@ Accept wildcard characters: False ``` ### -CreateEventsFromEmailAsPrivate + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The CreateEventsFromEmailAsPrivate parameter specifies whether to create events from email messages as Normal or Private. Valid values are: @@ -387,7 +411,6 @@ The CreateEventsFromEmailAsPrivate parameter specifies whether to create events Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -397,13 +420,15 @@ Accept wildcard characters: False ``` ### -DailyAgendaMailSchedule + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: AgendaMailSchedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -413,13 +438,15 @@ Accept wildcard characters: False ``` ### -DefaultMeetingDuration + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -429,6 +456,9 @@ Accept wildcard characters: False ``` ### -DefaultMinutesToReduceLongEventsBy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DefaultMinutesToReduceLongEventsBy Description }} @@ -437,7 +467,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -447,6 +476,9 @@ Accept wildcard characters: False ``` ### -DefaultMinutesToReduceShortEventsBy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DefaultMinutesToReduceShortEventsBy Description }} @@ -455,7 +487,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -465,6 +496,9 @@ Accept wildcard characters: False ``` ### -DefaultOnlineMeetingProvider + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DefaultOnlineMeetingProvider parameter specifies the default provider for online meetings. Valid values are: @@ -490,7 +524,6 @@ The DefaultOnlineMeetingProvider parameter specifies the default provider for on Type: OnlineMeetingProviderType Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -500,6 +533,9 @@ Accept wildcard characters: False ``` ### -DefaultReminderTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultReminderTime parameter specifies the length of time before a meeting or appointment when the reminder is first displayed. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -529,7 +565,6 @@ This parameter is ignored when the RemindersEnabled parameter is set to $false. Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -539,6 +574,9 @@ Accept wildcard characters: False ``` ### -DeleteMeetingRequestOnRespond + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DeleteMeetingRequestOnRespond Description }} @@ -547,7 +585,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -557,6 +594,9 @@ Accept wildcard characters: False ``` ### -DiningEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DiningEventsFromEmailEnabled parameter specifies whether to create dining reservation events from email messages. Valid values are: @@ -570,7 +610,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -580,6 +619,9 @@ 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. @@ -588,7 +630,6 @@ 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 @@ -598,6 +639,9 @@ Accept wildcard characters: False ``` ### -EntertainmentEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EntertainmentEventsFromEmailEnabled parameter specifies whether to create entertainment reservation events from email messages. Valid values are: @@ -611,7 +655,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -621,6 +664,9 @@ Accept wildcard characters: False ``` ### -EventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EventsFromEmailEnabled parameter specifies whether to enable events to be created from email messages. Valid values are: @@ -641,7 +687,6 @@ When this setting is enabled, you can enable or disable creating specific types Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -651,6 +696,9 @@ Accept wildcard characters: False ``` ### -FirstWeekOfYear + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FirstWeekOfYear parameter specifies the first week of the year. Valid values are: - FirstDay: Week numbers start on the first day of the year. This is the default value. @@ -664,7 +712,6 @@ You configure the first day of the week by using the WeekStartDay parameter. Type: FirstWeekRules Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -674,6 +721,9 @@ Accept wildcard characters: False ``` ### -FlightEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FlightEventsFromEmailEnabled parameter specifies whether to create flight reservation events from email messages. Valid values are: @@ -687,7 +737,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -697,6 +746,9 @@ Accept wildcard characters: False ``` ### -HotelEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The HotelEventsFromEmailEnabled parameter specifies whether to create hotel reservation events from email messages. Valid values are: @@ -710,7 +762,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -720,6 +771,9 @@ Accept wildcard characters: False ``` ### -InvoiceEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The InvoiceEventsFromEmailEnabled parameter specifies whether to allow creating invoices from email messages. Valid values are: @@ -731,7 +785,6 @@ The InvoiceEventsFromEmailEnabled parameter specifies whether to allow creating Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -741,6 +794,9 @@ Accept wildcard characters: False ``` ### -LocationDetailsInFreeBusy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The LocationDetailsInFreeBusy parameter specifies the level of work location information that's returned as part of a user's availability. Work location information is visible across several Microsoft 365 application experiences, and the level of location information that's shown to other users in the organization is controlled by this parameter. Valid values are: @@ -753,7 +809,6 @@ The LocationDetailsInFreeBusy parameter specifies the level of work location inf Type: LocationDetailsPermissionInFreeBusy Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -763,6 +818,9 @@ Accept wildcard characters: False ``` ### -MailboxLocation + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill MailboxLocation Description }} @@ -771,7 +829,6 @@ This parameter is available only in the cloud-based service. Type: MailboxLocationIdParameter Parameter Sets: MailboxLocation Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -781,6 +838,9 @@ Accept wildcard characters: False ``` ### -OnlineMeetingsByDefaultEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value will be ignored. Eventually, this parameter will override the Outlook-configured setting. @@ -797,7 +857,6 @@ Setting this parameter enables the display of the **Add online meeting to all me Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -807,6 +866,9 @@ Accept wildcard characters: False ``` ### -PackageDeliveryEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PackageDeliveryEventsFromEmailEnabled parameter specifies whether to create package delivery events from email messages. Valid values are: @@ -820,7 +882,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -830,6 +891,9 @@ Accept wildcard characters: False ``` ### -PreserveDeclinedMeetings + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill PreserveDeclinedMeetings Description }} @@ -838,7 +902,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -848,6 +911,9 @@ Accept wildcard characters: False ``` ### -RemindersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are: - $true: Reminders are enabled. This is the default value. @@ -859,7 +925,6 @@ When the reminder is first displayed is controlled by the DefaultReminderTime pa 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 @@ -869,6 +934,9 @@ Accept wildcard characters: False ``` ### -ReminderSoundEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReminderSoundEnabled parameter specifies whether a sound is played along with the reminder. Valid values are: - $true: A sound is played with the reminder. This is the default value. @@ -880,7 +948,6 @@ This parameter is ignored when the RemindersEnabled parameter is set to $false. 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 @@ -890,6 +957,9 @@ Accept wildcard characters: False ``` ### -RentalCarEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The RentalCarEventsFromEmailEnabled parameter specifies whether to create rental car reservation events from email messages. Valid values are: @@ -903,7 +973,6 @@ This parameter is meaningful only when the EventsFromEmailEnabled parameter is s Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -913,6 +982,9 @@ Accept wildcard characters: False ``` ### -ServiceAppointmentEventsFromEmailEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ServiceAppointmentEventsFromEmailEnabled Description }} @@ -921,7 +993,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -931,6 +1002,9 @@ Accept wildcard characters: False ``` ### -ShortenEventScopeDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ShortenEventScopeDefault Description }} @@ -939,7 +1013,6 @@ This parameter is available only in the cloud-based service. Type: ShortenEventScopeOption Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -949,6 +1022,9 @@ Accept wildcard characters: False ``` ### -ShowWeekNumbers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowWeekNumbers parameter specifies whether the week number is displayed in the Outlook on the web calendar. Valid values are: - $true: The week number is displayed. @@ -958,7 +1034,6 @@ The ShowWeekNumbers parameter specifies whether the week number is displayed in 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 @@ -968,13 +1043,15 @@ Accept wildcard characters: False ``` ### -SkipAgendaMailOnFreeDays + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -984,6 +1061,9 @@ Accept wildcard characters: False ``` ### -TimeIncrement + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are: - FifteenMinutes @@ -993,7 +1073,6 @@ The TimeIncrement parameter specifies the scale that the Outlook on the web cale Type: HourIncrement Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1003,6 +1082,9 @@ Accept wildcard characters: False ``` ### -UseBrightCalendarColorThemeInOwa + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light colors or bright colors for the calendar in Outlook on the web. Valid values are: - $true: Use bright colors in the calendar. @@ -1012,7 +1094,6 @@ The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light co Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1022,6 +1103,9 @@ Accept wildcard characters: False ``` ### -WeatherEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WeatherEnabled specifies whether weather is displayed in the calendar in Outlook on the web. Valid values are: @@ -1034,7 +1118,6 @@ The WeatherEnabled specifies whether weather is displayed in the calendar in Out Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1044,6 +1127,9 @@ Accept wildcard characters: False ``` ### -WeatherLocationBookmark + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WeatherLocationBookmark parameter specifies the default weather information that's displayed in the calendar in Outlook on the web. This parameter is based on an index value of the configured weather locations. The first weather location has the index value 0, the second weather location has the index value 1, and so on. @@ -1054,7 +1140,6 @@ A valid value for this parameter depends on the number of weather locations that Type: Int32 Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1064,6 +1149,9 @@ Accept wildcard characters: False ``` ### -WeatherLocations + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WeatherLocations parameter specifies one or more locations to display the weather for in the calendar in Outlook on the web. @@ -1082,7 +1170,6 @@ You can configure a maximum of 5 weather locations. Type: MultiValuedProperty Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1092,6 +1179,9 @@ Accept wildcard characters: False ``` ### -WeatherUnit + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WeatherUnit parameter specifies the temperature scale that's used to display the weather in the calendar in Outlook on the web. Valid values are: @@ -1104,7 +1194,6 @@ The WeatherUnit parameter specifies the temperature scale that's used to display Type: WeatherTemperatureUnit Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1114,6 +1203,9 @@ Accept wildcard characters: False ``` ### -WeekStartDay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WeekStartDay parameter specifies the first day of the week. Valid values are: - Sunday (This is the default value) @@ -1128,7 +1220,6 @@ The WeekStartDay parameter specifies the first day of the week. Valid values are Type: DayOfWeek Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1138,13 +1229,15 @@ 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 @@ -1154,6 +1247,9 @@ Accept wildcard characters: False ``` ### -WorkDays + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkDays parameter specifies the work days in the calendar. Valid values are: - None @@ -1174,7 +1270,6 @@ You can specify multiple values separated by commas, but redundant values are ig Type: DaysOfWeek Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1184,6 +1279,9 @@ Accept wildcard characters: False ``` ### -WorkingHoursEndTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkingHoursEndTime parameter specifies the time that the work day ends. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1194,7 +1292,6 @@ The default value is 17:00:00 (5:00 P.M.). Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1204,6 +1301,9 @@ Accept wildcard characters: False ``` ### -WorkingHoursStartTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkingHoursStartTime parameter specifies the time that the work day starts. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1214,7 +1314,6 @@ The default value is 08:00:00(8:00 A.M.). Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1224,6 +1323,9 @@ Accept wildcard characters: False ``` ### -WorkingHoursTimeZone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WorkingHoursTimeZone parameter specifies the time zone that's used by the WorkingHoursStartTime and WorkingHoursEndTime parameters. A valid value for this parameter is a supported time zone key name (for example, "Pacific Standard Time"). @@ -1236,7 +1338,6 @@ 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 @@ -1246,6 +1347,9 @@ Accept wildcard characters: False ``` ### -WorkspaceUserEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill WorkspaceUserEnabled Description }} @@ -1254,7 +1358,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md index 7a30ee7341..78d1d63851 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxcalendarfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxCalendarFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxcalendarfolder +schema: 2.0.0 +title: Set-MailboxCalendarFolder --- # Set-MailboxCalendarFolder @@ -66,6 +67,9 @@ This example enables the calendar in Kai's mailbox to be searchable on the web. ## 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 calendar folder that you want to modify. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: @@ -87,7 +91,6 @@ 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, Exchange Online Protection Required: True Position: 1 @@ -97,6 +100,9 @@ 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,7 +112,6 @@ 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,6 +121,9 @@ Accept wildcard characters: False ``` ### -DetailLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DetailLevel parameter specifies the level of calendar detail that's published and available to anonymous users. Valid values are: - AvailabilityOnly (default) @@ -128,7 +136,6 @@ This parameter is meaningful only when the PublishEnabled parameter value is $tr Type: DetailLevelEnumType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -138,6 +145,9 @@ 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. @@ -146,7 +156,6 @@ 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,6 +165,9 @@ Accept wildcard characters: False ``` ### -PublishDateRangeFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublishDateRangeFrom parameter specifies the start date of calendar information to publish (past information). Valid values are: - OneDay @@ -172,7 +184,6 @@ This parameter is meaningful only when the PublishEnabled parameter value is $tr Type: DateRangeEnumType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -182,6 +193,9 @@ Accept wildcard characters: False ``` ### -PublishDateRangeTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublishDateRangeTo parameter specifies the end date of calendar information to publish (future information). Valid values are: - OneDay @@ -198,7 +212,6 @@ This parameter is meaningful only when the PublishEnabled parameter value is $tr Type: DateRangeEnumType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -208,6 +221,9 @@ Accept wildcard characters: False ``` ### -PublishEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are: - $true: The calendar information is published. @@ -217,7 +233,6 @@ The PublishEnabled parameter specifies whether to publish the specified calendar 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,13 +242,15 @@ Accept wildcard characters: False ``` ### -ResetUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that has been published without being publicly searchable. 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 @@ -243,6 +260,9 @@ Accept wildcard characters: False ``` ### -SearchableUrlEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web. - $true: The published calendar URL is discoverable on the web. @@ -254,7 +274,6 @@ This parameter is meaningful only when the PublishEnabled parameter value is $tr 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 @@ -264,13 +283,15 @@ Accept wildcard characters: False ``` ### -SetAsSharingSource + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SetAsSharingSource switch specifies whether to set the calendar folder as a sharing source. 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 @@ -280,6 +301,9 @@ Accept wildcard characters: False ``` ### -SharedCalendarSyncStartDate + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. **Note**: This parameter is supported only for shared calendars that have been upgraded as described in [Calendar sharing in Microsoft 365](https://support.microsoft.com/office/365-b576ecc3-0945-4d75-85f1-5efafb8a37b4), and is not applicable to any other type of calendar or mailbox folder. @@ -302,7 +326,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -312,6 +335,9 @@ Accept wildcard characters: False ``` ### -UseHttps + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseHttps switch specifies whether to use HTTPS for the published URL of the calendar folder. You don't need to specify a value with this switch. This switch is meaningful only when the PublishEnabled parameter value is $true. @@ -320,7 +346,6 @@ This switch is meaningful only when the PublishEnabled parameter value is $true. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -330,13 +355,15 @@ 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/exchange/Set-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MailboxDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md index bf3cb3151f..520715886b 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxdatabase applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MailboxDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxdatabase +schema: 2.0.0 +title: Set-MailboxDatabase --- # Set-MailboxDatabase @@ -85,6 +86,9 @@ For more information about RPC access through Client Access servers, see [Set-Rp ## 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 modify. You can use any value that uniquely identifies the database. For example: - Name @@ -95,7 +99,6 @@ The Identity parameter specifies the mailbox database that you want to modify. Y Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -105,6 +108,9 @@ Accept wildcard characters: False ``` ### -AllowFileRestore + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowFileRestore parameter specifies whether to allow a database to be restored from a backup. Valid values are: - $true: You can replace an existing database with a newly-created database. You can mount a database that doesn't match the database entry in Active Directory. @@ -114,7 +120,6 @@ The AllowFileRestore parameter specifies whether to allow a database to be resto Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,6 +129,9 @@ Accept wildcard characters: False ``` ### -AutoDagExcludeFromMonitoring + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mailbox database from the ServerOneCopyMonitor, which alerts an administrator when a replicated database has only one healthy copy available. Valid values are: - $true: No alert is issued when there's only one healthy copy of the replicated database. @@ -133,7 +141,6 @@ The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mai Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -143,13 +150,15 @@ Accept wildcard characters: False ``` ### -AutoDatabaseMountDial + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: AutoDatabaseMountDial Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,6 +168,9 @@ Accept wildcard characters: False ``` ### -BackgroundDatabaseMaintenance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. Valid values are: - $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This is the default value. @@ -168,7 +180,6 @@ The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Sto Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -178,6 +189,9 @@ Accept wildcard characters: False ``` ### -CalendarLoggingQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarLoggingQuota parameter specifies the maximum size of the log in the Recoverable Items folder of the mailbox that stores changes to calendar items. When the log exceeds this size, calendar logging is disabled until messaging records management (MRM) removes older calendar logs to free up more space. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 6 gigabytes (6442450944 bytes). @@ -200,7 +214,6 @@ This setting applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -210,6 +223,9 @@ Accept wildcard characters: False ``` ### -CircularLoggingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CircularLoggingEnabled parameter specifies whether circular logging is enabled for the database. Valid values are: - $true: Circular logging is enabled. @@ -221,7 +237,6 @@ For more information about circular logging, see [Exchange Native Data Protectio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -231,6 +246,9 @@ 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`. @@ -240,7 +258,6 @@ 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 @@ -250,13 +267,15 @@ Accept wildcard characters: False ``` ### -DatabaseGroup + +> Applicable: 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -266,6 +285,9 @@ Accept wildcard characters: False ``` ### -DataMoveReplicationConstraint + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DataMoveReplicationConstraint parameter specifies the throttling behavior for high availability mailbox moves. Valid values are: - None: Moves shouldn't be throttled to ensure high availability. Use this setting if the database isn't part of a database availability group (DAG). @@ -283,7 +305,6 @@ Any value other than None enables the Microsoft Exchange Mailbox Replication ser Type: DataMoveReplicationConstraintParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,6 +314,9 @@ Accept wildcard characters: False ``` ### -DeletedItemRetention + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeletedItemRetention parameter specifies the length of time to keep deleted items in the Recoverable Items\\Deletions folder in mailboxes. Items are moved to this folder when the user deletes items from the Deleted Items folder, empties the Deleted Items folder, or deletes items by using Shift+Delete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. @@ -307,7 +331,6 @@ For more information, see [Recoverable Items folder in Exchange Server](https:// Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -317,13 +340,15 @@ 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 @@ -333,6 +358,9 @@ Accept wildcard characters: False ``` ### -EventHistoryRetentionPeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EventHistoryRetentionPeriod parameter specifies the length of time to keep event data. This event data is stored in the event history table in the Exchange store. It includes information about changes to various objects in the mailbox database. You can use this parameter to prevent the event history table from becoming too large and using too much disk space. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -343,7 +371,6 @@ Valid values are 00:00:01 to 30.00:00:00. The default value is 7.00:00:00 (7 day Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -353,6 +380,9 @@ Accept wildcard characters: False ``` ### -IndexEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange 2016 or earlier. The IndexEnabled parameter specifies whether Exchange Search indexes the mailbox database. Valid values are: @@ -364,7 +394,6 @@ The IndexEnabled parameter specifies whether Exchange Search indexes the mailbox Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -374,13 +403,15 @@ Accept wildcard characters: False ``` ### -IsExcludedFromInitialProvisioning + +> 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 @@ -390,6 +421,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioning + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. @@ -401,7 +435,6 @@ The value is automatically set to $true when you set the IsExcludedFromProvision Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -411,6 +444,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioningByOperator + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The IIsExcludedFromProvisioningByOperator parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: @@ -427,7 +463,6 @@ Note that setting this parameter to the value $true has these additional effects Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -437,6 +472,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioningDueToLogicalCorruption + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromProvisioningDueToLogicalCorruption parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: @@ -454,7 +492,6 @@ Note that setting this parameter to the value $true has these additional effects Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -464,6 +501,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioningReason + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromProvisioningReason parameter specifies the reason why you excluded the mailbox database from the mailbox provisioning load balancer. If the value contains spaces, enclose the value in quotation marks ("). The value must contain at least 10 characters. This parameter requires a value when you set any of the following parameters to $true: @@ -476,7 +516,6 @@ This parameter requires a value when you set any of the following parameters to Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -486,6 +525,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -506,7 +548,6 @@ This setting applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -516,6 +557,9 @@ Accept wildcard characters: False ``` ### -IsSuspendedFromProvisioning + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsSuspendedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are: - $true: Indicates that you don't want the exclusion to be permanent. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database. @@ -530,7 +574,6 @@ Note that setting this parameter to the value $true has these additional effects Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -540,6 +583,9 @@ Accept wildcard characters: False ``` ### -JournalRecipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The JournalRecipient parameter specifies the journal recipient to use for per-database journaling for all mailboxes on the database. You can use any value that uniquely identifies the recipient. For example: - Name @@ -553,7 +599,6 @@ The JournalRecipient parameter specifies the journal recipient to use for per-da Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -563,6 +608,9 @@ Accept wildcard characters: False ``` ### -MailboxRetention + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxRetention parameter specifies the length of time to keep deleted mailboxes before they are permanently deleted or purged. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -573,7 +621,6 @@ Valid values are 00:00:00 to 24855.03:14:07. The default value is 30.00:00:00 (3 Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -583,6 +630,9 @@ Accept wildcard characters: False ``` ### -MaintenanceSchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The MaintenanceSchedule parameter specifies when maintenance will be performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks. @@ -611,7 +661,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -621,6 +670,9 @@ Accept wildcard characters: False ``` ### -MetaCacheDatabaseMaxCapacityInBytes + +> Applicable: Exchange Server 2019 + The MetaCacheDatabaseMaxCapacityInBytes parameter specifies the size of the metacache database in bytes. To convert gigabytes to bytes, multiply the value by 1024^3. For terabytes to bytes, multiply by 1024^4. The default value is blank ($null). @@ -629,7 +681,6 @@ The default value is blank ($null). Type: Int64 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -639,6 +690,9 @@ Accept wildcard characters: False ``` ### -MountAtStartup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MountAtStartup parameter specifies whether to mount the mailbox database when the Microsoft Exchange Information Store service starts. Valid values are: - $true: The database is mounted when the service starts. This is the default value. @@ -648,7 +702,6 @@ The MountAtStartup parameter specifies whether to mount the mailbox database whe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -658,13 +711,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the mailbox database. 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 Required: False Position: Named @@ -674,6 +729,9 @@ Accept wildcard characters: False ``` ### -OfflineAddressBook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OfflineAddressBook parameter specifies the offline address book that's associated with the mailbox database. You can use any value that uniquely identifies the offline address book. For example: - Name @@ -686,7 +744,6 @@ By default, this setting is blank ($null). Type: OfflineAddressBookIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -696,6 +753,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send new messages, and the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -716,7 +776,6 @@ This settings applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -726,6 +785,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendReceiveQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -746,7 +808,6 @@ This setting applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -756,6 +817,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The PublicFolderDatabase parameter specifies the associated public folder database for this mailbox database. You can use any value that uniquely identifies the public folder database. For example: @@ -768,7 +832,6 @@ The PublicFolderDatabase parameter specifies the associated public folder databa Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -778,6 +841,9 @@ Accept wildcard characters: False ``` ### -QuotaNotificationSchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The QuotaNotificationSchedule parameter specifies when quota messages are sent to mailboxes that have reached one of the quota values. @@ -806,7 +872,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -816,6 +881,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder of the mailbox. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). @@ -838,7 +906,6 @@ This settings applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -848,6 +915,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for the mailbox. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). @@ -870,7 +940,6 @@ This settings applies to all mailboxes in the database that don't have their own Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -880,6 +949,9 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsUntilBackup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are: - $true: Deleted items in mailboxes are kept until the next mailbox database backup. This value could effectively override the deleted DeletedItemRetention and RecoverableItemsQuota parameter values. @@ -898,7 +970,6 @@ For more information, see [Recoverable Items folder in Exchange Server](https:// Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -908,6 +979,9 @@ Accept wildcard characters: False ``` ### -RpcClientAccessServer + +> Applicable: Exchange Server 2010 + This parameter is functional only in Exchange Server 2010. The RpcClientAccessServer parameter specifies the Client Access server or Client Access server array through which RPC clients (for example, Microsoft Office Outlook 2007 clients) access their mailboxes. This feature is supported for all versions of Outlook. @@ -918,7 +992,6 @@ When connecting with Outlook 2003 clients, RPC encryption is disabled by default Type: ClientAccessServerOrArrayIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -928,13 +1001,15 @@ 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/exchange/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md index 7a63396766..58f90b6153 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxdatabasecopy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MailboxDatabaseCopy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxdatabasecopy +schema: 2.0.0 +title: Set-MailboxDatabaseCopy --- # Set-MailboxDatabaseCopy @@ -57,13 +58,15 @@ This example configures an activation preference of 3 for the copy of the databa ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the database whose copy is being modified. ```yaml Type: DatabaseCopyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -73,13 +76,15 @@ 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 database availability group (DAG) when using the RedistributeActiveDatabases.ps1 script. The value for the ActivationPreference parameter is a number equal to or greater than 1, where 1 is at the top of the preference order. The position number can't be larger than the number of database 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 @@ -89,6 +94,9 @@ 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,7 +106,6 @@ 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,13 +115,15 @@ 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,6 +133,9 @@ 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 should wait before replaying log files that have been copied to the passive database copy. Setting this parameter to a value greater than 0 creates a lagged 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. @@ -136,7 +148,6 @@ For example, to specify a 14-day replay lag period, enter 14.00:00:00. The defau Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,6 +157,9 @@ 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 should wait before truncating log files that have replayed into the passive 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. @@ -156,7 +170,6 @@ 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 @@ -166,13 +179,15 @@ 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 @@ -182,13 +197,15 @@ Accept wildcard characters: False ``` ### -DatabaseCopyAutoActivationPolicy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: DatabaseCopyAutoActivationPolicyType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -198,6 +215,9 @@ 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. @@ -210,7 +230,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Set-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md index 400403f687..89c8ae6e25 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxexportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MailboxExportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxexportrequest +schema: 2.0.0 +title: Set-MailboxExportRequest --- # Set-MailboxExportRequest @@ -70,13 +71,15 @@ This example changes the second export request Ayla\\MailboxExport1 to accept up ## 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 specify a name for the export request, use the following syntax: `Alias\Name`. ```yaml Type: MailboxExportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -86,6 +89,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -96,7 +102,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -106,6 +111,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -116,7 +124,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -126,13 +133,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BatchName parameter specifies the name of the batch. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,6 +151,9 @@ 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`. @@ -151,7 +163,6 @@ 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 @@ -161,13 +172,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value is 30 days. ```yaml Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -177,13 +190,15 @@ 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,13 +208,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -209,6 +226,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -224,7 +244,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -234,6 +253,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lowest @@ -249,7 +271,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -259,6 +280,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RehomeRequest switch tells the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the mailbox that's being exported. You don't need to specify a value with this switch. This switch is used primarily for debugging purposes. @@ -267,7 +291,6 @@ This switch is used primarily for debugging purposes. Type: SwitchParameter Parameter Sets: Rehome Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -277,13 +300,15 @@ Accept wildcard characters: False ``` ### -RemoteCredential + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: PSCredential Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,13 +318,15 @@ Accept wildcard characters: False ``` ### -RemoteHostName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Fqdn Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -309,13 +336,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SkipMerging parameter specifies steps in the export that should be skipped. This parameter is used primarily for debugging purposes. ```yaml Type: SkippableMergeComponent[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -325,6 +354,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -338,7 +370,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -348,13 +379,15 @@ 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/exchange/Set-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md index 52df63f5f3..115c4262f6 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxFolderPermission -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission +schema: 2.0.0 +title: Set-MailboxFolderPermission --- # Set-MailboxFolderPermission @@ -82,6 +83,9 @@ In Exchange Online, this example changes an existing user's permissions to Edito ## 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: @@ -103,7 +107,6 @@ 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 @@ -113,6 +116,9 @@ 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 modify for the user on the mailbox folder. The values that you specify replace the existing permissions for the user on the folder. You can specify individual folder permissions or roles, which are combinations of permissions. You can specify multiple permissions and roles separated by commas. @@ -153,7 +159,6 @@ 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 @@ -163,6 +168,9 @@ 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 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: @@ -183,7 +191,6 @@ 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 @@ -193,6 +200,9 @@ 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`. @@ -202,7 +212,6 @@ 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 @@ -212,6 +221,9 @@ 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. @@ -220,7 +232,6 @@ 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 @@ -230,6 +241,9 @@ 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 modify their calendar permissions. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: @@ -248,7 +262,6 @@ 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 @@ -258,6 +271,9 @@ 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: @@ -272,7 +288,6 @@ You can specify multiple values separated by commas. Type: MailboxFolderPermissionFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -282,13 +297,15 @@ 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/exchange/Set-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md index aab760df38..c6c24ae026 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxirmaccess applicable: Exchange Online -title: Set-MailboxIRMAccess -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxirmaccess +schema: 2.0.0 +title: Set-MailboxIRMAccess --- # Set-MailboxIRMAccess @@ -42,6 +43,9 @@ This example prevents delegate Chris from reading IRM-protected messages in Lyne ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example - Name @@ -59,7 +63,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -AccessLevel + +> Applicable: Exchange Online + The AccessLevel parameter specifies what delegates can do to IRM-protected messages in the mailbox that's specified by the Identity parameter. The only value for this parameter is Block, which means you can only use this cmdlet to block delegate access to IRM-protected messages in the mailbox. @@ -80,7 +86,6 @@ Type: IRMAccessLevel Parameter Sets: (All) Aliases: Accepted values: Block -Applicable: Exchange Online Required: True Position: Named @@ -90,6 +95,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Online + **Note**: Delegates that you specify with this parameter must already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-recipients). The User parameter specifies the delegate who is blocked from reading IRM-protected messages in the mailbox. The delegate must be a user mailbox or a mail user. You can use any value that uniquely identifies the delegate. For example: @@ -109,7 +117,6 @@ The User parameter specifies the delegate who is blocked from reading IRM-protec Type: SecurityPrincipalIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Set-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md index 07b606b809..968e032c91 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboximportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MailboxImportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboximportrequest +schema: 2.0.0 +title: Set-MailboxImportRequest --- # Set-MailboxImportRequest @@ -78,13 +79,15 @@ This example finds all import requests that have a status of Suspended, and then ## 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 for the import request with the New-MailboxImportRequest cmdlet, use the following syntax: `Alias\Name`. ```yaml Type: MailboxImportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -AzureSharedAccessSignatureToken + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -102,7 +108,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AzureImportRequest Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -112,6 +117,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later or Exchange Online, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -122,7 +130,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -132,6 +139,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -144,7 +154,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -154,13 +163,15 @@ 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 of the batch. ```yaml 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 @@ -170,13 +181,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -186,6 +199,9 @@ 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,7 +211,6 @@ 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 @@ -205,6 +220,9 @@ 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. @@ -213,7 +231,6 @@ 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 @@ -223,6 +240,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -231,7 +251,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,6 +260,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -258,7 +280,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -268,6 +289,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: @@ -285,7 +309,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -295,6 +318,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RehomeRequest parameter tells the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the mailbox being imported. You don't need to specify a value with this switch. @@ -305,7 +331,6 @@ This switch is used primarily for debugging purposes. Type: SwitchParameter Parameter Sets: Rehome Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -315,6 +340,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -328,7 +356,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -338,6 +365,9 @@ Accept wildcard characters: False ``` ### -SkipInitialConnectionValidation + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service This parameter is reserved for internal Microsoft use. @@ -346,7 +376,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -356,13 +385,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies the steps in the import that should be skipped. This parameter is used primarily for debugging purposes. ```yaml Type: SkippableMergeComponent[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -372,6 +403,9 @@ Accept wildcard characters: False ``` ### -SkippedItemApprovalTime + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service This parameter is reserved for internal Microsoft use. @@ -380,7 +414,6 @@ This parameter is reserved for internal Microsoft use. Type: System.DateTime Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -390,13 +423,15 @@ 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/exchange/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md index 5c32a37cd8..49b3367d4f 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxjunkemailconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxJunkEmailConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxjunkemailconfiguration +schema: 2.0.0 +title: Set-MailboxJunkEmailConfiguration --- # Set-MailboxJunkEmailConfiguration @@ -81,6 +82,9 @@ This example identifies mailboxes where contacts are treated as trusted senders ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -98,7 +102,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us 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 @@ -108,6 +111,9 @@ Accept wildcard characters: False ``` ### -BlockedSendersAndDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BlockedSendersAndDomains parameter specifies the Blocked Senders list, which is a list of sender email addresses and domains whose messages are automatically sent to the Junk Email folder. This parameter corresponds to the Outlook on the web setting: Move email from these senders or domains to my Junk Email folder. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -118,7 +124,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -128,6 +133,9 @@ 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`. @@ -137,7 +145,6 @@ 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 @@ -147,6 +154,9 @@ Accept wildcard characters: False ``` ### -ContactsTrusted + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ContactsTrusted parameter specifies whether the contacts in the Contacts folder are treated as trusted senders. This parameter corresponds to the Outlook on the web setting: Trust email from my contacts. Valid values are: - $true: Messages from contacts in the Contacts folder that reach the mailbox are never delivered to the Junk Email folder, regardless of the content. @@ -156,7 +166,6 @@ The ContactsTrusted parameter specifies whether the contacts in the Contacts fol 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 @@ -166,6 +175,9 @@ 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,7 +186,6 @@ 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 @@ -184,6 +195,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter enables or disables the junk email rule on the mailbox (a hidden Inbox rule named Junk E-mail Rule). Valid values are: - $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This is the default value. @@ -209,7 +223,6 @@ The state of the junk email rule on the mailbox doesn't affect the client-side j 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 @@ -219,6 +232,9 @@ Accept wildcard characters: False ``` ### -FailOnError + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill FailOnError Description }} @@ -227,7 +243,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -237,6 +252,9 @@ 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: @@ -248,7 +266,6 @@ 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 @@ -258,6 +275,9 @@ Accept wildcard characters: False ``` ### -SenderScreeningEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SenderScreeningEnabled Description }} @@ -266,7 +286,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -276,6 +295,9 @@ Accept wildcard characters: False ``` ### -TrustedListsOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TrustedListsOnly parameter specifies that only messages from senders in the Safe Senders list are delivered to the Inbox. All other messages are treated as junk email. This parameter corresponds to the Outlook on the web setting: Don't trust email unless it comes from someone in my Safe Senders and Recipients list. Valid values are: - $true: Only messages from email address or domain entries in the Safe Senders list and the Safe Recipients list are delivered to the Inbox. All other messages are automatically delivered to the Junk Email folder. @@ -285,7 +307,6 @@ The TrustedListsOnly parameter specifies that only messages from senders in the 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 @@ -295,13 +316,15 @@ Accept wildcard characters: False ``` ### -TrustedRecipientsAndDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -311,6 +334,9 @@ Accept wildcard characters: False ``` ### -TrustedSendersAndDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TrustedSendersAndDomains parameter specifies the Safe Senders list and Safe Recipients list, which are lists of email addresses and domains. Messages from these senders that reach the mailbox are never delivered to the Junk Email folder, regardless of the content. This parameter corresponds to the Outlook on the web setting: Don't move email from these senders or domains to my Junk Email folder. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -329,7 +355,6 @@ To empty the list of email addresses and domains, use the value $null. 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 @@ -339,13 +364,15 @@ 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/exchange/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md index 047f4af452..2edf3c6576 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxmessageconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxMessageConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxmessageconfiguration +schema: 2.0.0 +title: Set-MailboxMessageConfiguration --- # Set-MailboxMessageConfiguration @@ -114,6 +115,9 @@ This example sets the compose email message form to always show the Bcc field in ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -131,7 +135,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us 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 @@ -141,6 +144,9 @@ Accept wildcard characters: False ``` ### -AfterMoveOrDeleteBehavior + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AfterMoveOrDeleteBehavior parameter specifies the behavior after moving or deleting an email item in Outlook on the web. You can use the following values: - OpenPreviousItem @@ -153,7 +159,6 @@ The default value is OpenNextItem. Type: AfterMoveOrDeleteBehavior Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -163,6 +168,9 @@ Accept wildcard characters: False ``` ### -AlwaysShowBcc + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AlwaysShowBcc parameter shows or hides the blind carbon copy (Bcc) field when the user creates messages in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -171,7 +179,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -181,6 +188,9 @@ Accept wildcard characters: False ``` ### -AlwaysShowFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AlwaysShowFrom parameter shows or hides the From field when the user creates messages in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -189,7 +199,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -199,6 +208,9 @@ Accept wildcard characters: False ``` ### -AutoAddSignature + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet. The AutoAddSignature parameter specifies whether to automatically add signatures to new email messages created in Outlook on the web. Valid values are: @@ -212,7 +224,6 @@ The email signature specified by the SignatureText parameter is added to plain t 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 @@ -222,6 +233,9 @@ Accept wildcard characters: False ``` ### -AutoAddSignatureOnMobile + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet. The AutoAddSignatureOnMobile parameter automatically adds the signature specified by the SignatureTextOnMobile parameter to messages when the user creates messages in Outlook on the web for devices. @@ -232,7 +246,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -242,6 +255,9 @@ Accept wildcard characters: False ``` ### -AutoAddSignatureOnReply + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoAddSignature parameter specifies whether to automatically add signatures to reply email messages created in Outlook on the web. Valid values are: - $true: Email signatures are automatically added to reply messages. @@ -253,7 +269,6 @@ The email signature specified by the SignatureText parameter is added to plain t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -263,6 +278,9 @@ Accept wildcard characters: False ``` ### -CheckForForgottenAttachments + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CheckForForgottenAttachments parameter shows or hides the attachment warning prompt when the user creates messages in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $true. @@ -273,7 +291,6 @@ For example, the user creates a message that includes the text "Please see the a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -283,6 +300,9 @@ Accept wildcard characters: False ``` ### -CheckForReportJunkDialog + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill CheckForReportJunkDialog Description }} @@ -291,7 +311,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -301,6 +320,9 @@ 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`. @@ -310,7 +332,6 @@ 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 @@ -320,6 +341,9 @@ Accept wildcard characters: False ``` ### -ConversationSortOrder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConversationSortOrder parameter specifies the sorting of messages in the reading pane in Conversation view for the user in Outlook on the web. You can use the following values: - Chronological @@ -336,7 +360,6 @@ The default value is ChronologicalNewestOnTop. Type: ConversationSortOrder Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -346,6 +369,9 @@ Accept wildcard characters: False ``` ### -DefaultFontColor + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultFontColor parameter specifies the default text color when the user creates messages in Outlook on the web. This parameter accepts a hexadecimal color code value in the format #xxxxxx. The default value is #000000. If the string value is unrecognized, the browser application uses a default font color to display the text. @@ -354,7 +380,6 @@ If the string value is unrecognized, the browser application uses a default font 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 @@ -364,6 +389,9 @@ Accept wildcard characters: False ``` ### -DefaultFontFlags + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultFontFlags parameter specifies the default text effect when the user creates messages in Outlook on the web. You can use the following values: - Normal @@ -378,7 +406,6 @@ The default value is Normal. Type: FontFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -388,6 +415,9 @@ Accept wildcard characters: False ``` ### -DefaultFontName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultFontName parameter specifies the default font when the user creates messages in Outlook on the web. The default value is Calibri. If the font name value is unrecognized, the browser application uses a default font to display the text. @@ -396,7 +426,6 @@ The default value is Calibri. If the font name value is unrecognized, the browse 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 @@ -406,6 +435,9 @@ Accept wildcard characters: False ``` ### -DefaultFontSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultFontSize parameter specifies the default text size when the user creates messages in Outlook on the web. Valid input for this parameter is an integer between 1 and 7. The default value is 3, which corresponds to a 12 point font size. @@ -414,7 +446,6 @@ Valid input for this parameter is an integer between 1 and 7. The default value 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 @@ -424,13 +455,15 @@ Accept wildcard characters: False ``` ### -DefaultFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultFormat parameter specifies the default message format when the user creates messages in Outlook on the web. Accepted values are Html and PlainText. The default value is Html. ```yaml Type: MailFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -440,6 +473,9 @@ Accept wildcard characters: False ``` ### -DefaultSignature + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DefaultSignature Description }} @@ -448,7 +484,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -458,6 +493,9 @@ Accept wildcard characters: False ``` ### -DefaultSignatureOnReply + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DefaultSignatureOnReply Description }} @@ -466,7 +504,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -476,6 +513,9 @@ Accept wildcard characters: False ``` ### -DeleteSignatureName + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DeleteSignatureName Description }} @@ -484,7 +524,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -494,6 +533,9 @@ Accept wildcard characters: False ``` ### -DisplayDensityMode + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill DisplayDensityMode Description }} @@ -502,7 +544,6 @@ This parameter is available only in the cloud-based service. Type: DisplayDensityMode Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -512,6 +553,9 @@ 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. @@ -520,7 +564,6 @@ 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 @@ -530,6 +573,9 @@ Accept wildcard characters: False ``` ### -EchoGroupMessageBackToSubscribedSender + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EchoGroupMessageBackToSubscribedSender parameter controls whether subscribed members of Microsoft 365 Groups receive copies of messages that they send to those Groups. Valid values are: @@ -541,7 +587,6 @@ The EchoGroupMessageBackToSubscribedSender parameter controls whether subscribed Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -551,6 +596,9 @@ Accept wildcard characters: False ``` ### -EmailComposeMode + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The EmailComposeMode parameter specifies how the user creates messages in Outlook on the web. You can use the following values: @@ -562,7 +610,6 @@ The EmailComposeMode parameter specifies how the user creates messages in Outloo Type: EmailComposeMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -572,6 +619,9 @@ Accept wildcard characters: False ``` ### -EmptyDeletedItemsOnLogoff + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EmptyDeletedItemsOnLogoff parameter specifies whether to delete items from the Deleted Items folder when the user logs out of Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -580,7 +630,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -590,6 +639,9 @@ Accept wildcard characters: False ``` ### -FavoritesBitFlags + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill FavoritesBitFlags Description }} @@ -598,7 +650,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -608,6 +659,9 @@ Accept wildcard characters: False ``` ### -GlobalReadingPanePosition + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange 2016 or later. It doesn't work in Exchange Online. The GlobalReadingPanePosition specifies the default location of the reading pane in Outlook on the web. Valid values are: @@ -620,7 +674,6 @@ The GlobalReadingPanePosition specifies the default location of the reading pane Type: MailReadingPanePosition Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -630,6 +683,9 @@ Accept wildcard characters: False ``` ### -HideDeletedItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The HideDeletedItems parameter shows or hides deleted messages in Conversation view for the user in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -638,7 +694,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -648,6 +703,9 @@ 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: @@ -659,7 +717,6 @@ 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 @@ -669,6 +726,9 @@ Accept wildcard characters: False ``` ### -IsDarkModeTheme + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IsDarkModeTheme Description }} @@ -677,7 +737,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -687,6 +746,9 @@ Accept wildcard characters: False ``` ### -IsFavoritesFolderTreeCollapsed + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the Favorites folder tree by default in Outlook on the web. Valid values are: - $true: The Favorites folder tree is collapsed by default. @@ -696,7 +758,6 @@ The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the F Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -706,6 +767,9 @@ Accept wildcard characters: False ``` ### -IsFocusedInboxEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill IsFocusedInboxEnabled Description }} @@ -714,7 +778,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -724,6 +787,9 @@ Accept wildcard characters: False ``` ### -IsMailRootFolderTreeCollapsed + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Mail root folder tree by default in Outlook on the web. Valid values are: - $true: The Mail root folder tree is collapsed by default. @@ -733,7 +799,6 @@ The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -743,6 +808,9 @@ Accept wildcard characters: False ``` ### -IsReplyAllTheDefaultResponse + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the default response for messages in Outlook on the web. Valid values are: - $true: Reply All is the default response option for messages in the reading pane. This is the default value. @@ -752,7 +820,6 @@ The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the de Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -762,6 +829,9 @@ Accept wildcard characters: False ``` ### -LinkPreviewEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is enabled for the user in Outlook on the web. Valid values are: - $true: Link preview of URLs in email messages is enabled for the user. This is the default value. @@ -773,7 +843,6 @@ This parameter depends on the value of the LinkPreviewEnabled parameter on the S Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -783,6 +852,9 @@ Accept wildcard characters: False ``` ### -MailFolderPaneExpanded + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is expanded by default in Outlook on the web. Valid values are: - $true: The Mail folder pane is expanded by default. This is the default value. @@ -792,7 +864,6 @@ The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -802,6 +873,9 @@ Accept wildcard characters: False ``` ### -MailSendUndoInterval + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MailSendUndoInterval Description }} @@ -810,7 +884,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -820,6 +893,9 @@ Accept wildcard characters: False ``` ### -ManuallyPickCertificate + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ManuallyPickCertificate Description }} @@ -828,7 +904,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -838,6 +913,9 @@ Accept wildcard characters: False ``` ### -NavigationBarWidth + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill NavigationBarWidth Description }} @@ -846,7 +924,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -856,6 +933,9 @@ Accept wildcard characters: False ``` ### -NavigationPaneViewOption + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are: - Default: This is the default value @@ -868,7 +948,6 @@ The NavigationPaneViewOption parameter specifies the default navigation pane vie Type: NavigationPaneView Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -878,6 +957,9 @@ Accept wildcard characters: False ``` ### -NewEnabledPonts + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill NewEnabledPonts Description }} @@ -886,7 +968,6 @@ This parameter is available only in the cloud-based service. Type: PontType Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -896,6 +977,9 @@ Accept wildcard characters: False ``` ### -NewItemNotification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NewItemNotification parameter specifies how to provide notification for the arrival of new items for the user in Outlook on the web. You can use the following values: - Sound @@ -911,7 +995,6 @@ The default value is All. Type: NewItemNotification Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -921,6 +1004,9 @@ Accept wildcard characters: False ``` ### -PreferAccessibleContent + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are: - $true: Prefer accessible content. @@ -930,7 +1016,6 @@ The PreferAccessibleContent parameter specifies whether to prefer accessible con Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -940,6 +1025,9 @@ Accept wildcard characters: False ``` ### -PreviewMarkAsReadBehavior + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreviewMarkAsReadBehavior parameter specifies the options for marking an item as Read in the reading pane for the user in Outlook on the web. You can use the following values: - Delayed: This value uses the delay interval specified by the PreviewMarkAsReadDelaytime parameter. @@ -952,7 +1040,6 @@ The default value is OnSelectionChange. Type: PreviewMarkAsReadBehavior Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -962,6 +1049,9 @@ Accept wildcard characters: False ``` ### -PreviewMarkAsReadDelaytime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreviewMarkAsReadDelaytime parameter specifies the time in seconds to wait before marking an item as Read for the user in Outlook on the web. Valid input for this parameter is an integer between 0 and 30. The default value is 5 seconds. @@ -972,7 +1062,6 @@ This parameter is meaningful only if you set the PreviewMarkAsReadBehavior param 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 @@ -982,6 +1071,9 @@ Accept wildcard characters: False ``` ### -ReadReceiptResponse + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReadReceiptResponse parameter specifies how to respond to requests for read receipts for the user in Outlook on the web. You can use the following values: - DoNotAutomaticallySend @@ -994,7 +1086,6 @@ The default value is DoNotAutomaticallySend. Type: ReadReceiptResponse Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1004,6 +1095,9 @@ Accept wildcard characters: False ``` ### -ReportJunkSelected + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ReportJunkSelected Description }} @@ -1012,7 +1106,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1022,6 +1115,9 @@ Accept wildcard characters: False ``` ### -SendAddressDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SendAddressDefault parameter specifies the default From email address when the user has POP, IMAP, or Hotmail subscriptions configured on their mailbox. Users can override the default From address when they create an email message in Outlook on the web. @@ -1043,7 +1139,6 @@ You can find the available values for SendAddressDefault on a mailbox by running Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1053,6 +1148,9 @@ Accept wildcard characters: False ``` ### -ShowConversationAsTree + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowConversationAsTree parameter specifies how to sort messages in the list view in an expanded conversation for the user in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -1061,7 +1159,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -1071,6 +1168,9 @@ Accept wildcard characters: False ``` ### -ShowInlinePreviews + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ShowInlinePreviews Description }} @@ -1079,7 +1179,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1089,6 +1188,9 @@ Accept wildcard characters: False ``` ### -ShowNotificationBar + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ShowNotificationBar Description }} @@ -1097,7 +1199,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1107,6 +1208,9 @@ Accept wildcard characters: False ``` ### -ShowPreviewTextInListView + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowPreviewTextInListView parameter specifies whether to show preview text for messages in list view in Outlook on the web. Valid values are: - $true: Show preview text for messages in list view. This is the default value. @@ -1116,7 +1220,6 @@ The ShowPreviewTextInListView parameter specifies whether to show preview text f Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1126,6 +1229,9 @@ Accept wildcard characters: False ``` ### -ShowReadingPaneOnFirstLoad + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading pane when the user opens in Outlook on the web for the first time. Valid values are: - $true: Show the reading pane when the user opens Outlook on the web for the first time. @@ -1135,7 +1241,6 @@ The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading p Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1145,6 +1250,9 @@ Accept wildcard characters: False ``` ### -ShowSenderOnTopInListView + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowSenderOnTopInListView parameter specifies whether to show the message sender on top in list view in Outlook on the web. Valid values are: - $true: Show the message sender on top in list view. This is the default value. @@ -1154,7 +1262,6 @@ The ShowSenderOnTopInListView parameter specifies whether to show the message se Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1164,6 +1271,9 @@ Accept wildcard characters: False ``` ### -ShowUpNext + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ShowUpNext parameter specifies whether the next upcoming event should be shown above the mail list view in Outlook on the web. Valid values are: - $true: Show the next upcoming event above the mail list view. This is the default value. @@ -1173,7 +1283,6 @@ The ShowUpNext parameter specifies whether the next upcoming event should be sho Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1183,6 +1292,9 @@ Accept wildcard characters: False ``` ### -SignatureHtml + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet. The SignatureHtml parameter specifies the email signature that's available to the user in HTML-formatted messages in Outlook on the web. You can use plain text or text with HTML tags. However, any JavaScript code is removed. @@ -1193,7 +1305,6 @@ To automatically add this email signature to HTML-formatted messages created by 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 @@ -1203,6 +1314,9 @@ Accept wildcard characters: False ``` ### -SignatureHtmlBody + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SignatureHtmlBody Description }} @@ -1211,7 +1325,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1221,6 +1334,9 @@ Accept wildcard characters: False ``` ### -SignatureName + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SignatureName Description }} @@ -1229,7 +1345,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1239,6 +1354,9 @@ Accept wildcard characters: False ``` ### -SignatureText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet. The SignatureText parameter specifies the email signature that's available to the user in plain text messages in Outlook on the web. This parameter supports all Unicode characters. @@ -1249,7 +1367,6 @@ To automatically add the email signature to plain text messages created by the 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 @@ -1259,6 +1376,9 @@ Accept wildcard characters: False ``` ### -SignatureTextOnMobile + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet. The SignatureTextOnMobile parameter specifies the email signature that's available in messages created by the user in Outlook on the web for devices. This parameter supports all Unicode characters. @@ -1269,7 +1389,6 @@ To automatically add the email signature to messages created by the user in Outl Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1279,6 +1398,9 @@ Accept wildcard characters: False ``` ### -SigningCertificateId + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SigningCertificateId Description }} @@ -1287,7 +1409,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1297,6 +1418,9 @@ Accept wildcard characters: False ``` ### -SigningCertificateSubject + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SigningCertificateSubject Description }} @@ -1305,7 +1429,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1315,6 +1438,9 @@ Accept wildcard characters: False ``` ### -SmimeEncrypt + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SmimeEncrypt Description }} @@ -1323,7 +1449,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1333,6 +1458,9 @@ Accept wildcard characters: False ``` ### -SmimeSign + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SmimeSign Description }} @@ -1341,7 +1469,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1351,6 +1478,9 @@ Accept wildcard characters: False ``` ### -UseDefaultSignatureOnMobile + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseDefaultSignatureOnMobile parameter specifies whether to add the default email signature to messages created by the user in Outlook on the web for devices. The user configures the default signature in Outlook. Valid input for this parameter is $true or $false. The default value is $false. @@ -1359,7 +1489,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1369,6 +1498,9 @@ Accept wildcard characters: False ``` ### -WebSuggestedRepliesEnabledForUser + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill WebSuggestedRepliesEnabledForUser Description }} @@ -1377,7 +1509,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1387,13 +1518,15 @@ 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/exchange/Set-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-MailboxPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md index 96b60c149b..bc9856e2e7 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxplan applicable: Exchange Online, Exchange Online Protection -title: Set-MailboxPlan -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxplan +schema: 2.0.0 +title: Set-MailboxPlan --- # Set-MailboxPlan @@ -59,6 +60,9 @@ This example lowers the default mailbox quotas in the mailbox plan named Exchang ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the mailbox plan that you want to modify. You can use any value that uniquely identifies the mailbox plan. For example: - Name @@ -71,7 +75,6 @@ The Identity parameter specifies the mailbox plan that you want to modify. You c Type: MailboxPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -81,6 +84,9 @@ 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,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -108,7 +116,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -118,6 +125,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Online + The IsDefault switch specifies that the mailbox plan is the default mailbox plan. You don't need to specify a value with this switch. New and newly-enabled mailboxes receive the settings in the default mailbox plan. @@ -126,7 +136,6 @@ New and newly-enabled mailboxes receive the settings in the default mailbox plan Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -136,6 +145,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Online + The IssueWarningQuota parameter specifies the warning threshold for the size of the mailboxes that are created or enabled using the mailbox plan. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -156,7 +168,6 @@ The maximum value is determined by the mailbox plan. You can lower the value, an Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -166,6 +177,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Online + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mailbox. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -188,7 +202,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -198,6 +211,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Online + The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mailbox. When you enter a value, qualify the value with one of the following units: @@ -220,7 +236,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -230,6 +245,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendQuota + +> Applicable: Exchange Online + The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send new messages, and the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -250,7 +268,6 @@ The maximum value is determined by the mailbox plan. You can lower the value, an Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -260,6 +277,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendReceiveQuota + +> Applicable: Exchange Online + The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -280,7 +300,6 @@ The maximum value is determined by the mailbox plan. You can lower the value, bu Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -290,13 +309,15 @@ Accept wildcard characters: False ``` ### -RecipientLimits + +> 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 @@ -306,6 +327,9 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsFor + +> Applicable: Exchange Online + The RetainDeletedItemsFor parameter specifies the length of time to keep soft-deleted items for the mailbox. Soft-deleted items are items that have been deleted by using any of these methods: - Deleting items from the Deleted Items folder. @@ -324,7 +348,6 @@ The default value is 14 days (14.00:00:00). In Exchange Online, you can increase Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -334,6 +357,9 @@ Accept wildcard characters: False ``` ### -RetentionPolicy + +> Applicable: Exchange Online + The RetentionPolicy parameter specifies the retention policy that's applied to new mailboxes that you create. You can use any value that uniquely identifies the policy. For example: - Name @@ -358,7 +384,6 @@ For more information, see [Mailbox plans in Exchange Online](https://learn.micro Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -368,6 +393,9 @@ Accept wildcard characters: False ``` ### -RoleAssignmentPolicy + +> Applicable: Exchange Online + The RoleAssignmentPolicy parameter specifies the role assignment policy that's applied to the mailbox. You can use any value that uniquely identifies the role assignment policy. For example: - Name @@ -382,7 +410,6 @@ To see the available role assignment policies, use the Get-RoleAssignmentPolicy Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -392,13 +419,15 @@ 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/exchange/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md index ef75fd3f02..e5f0c7bc3f 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxregionalconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxRegionalConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxregionalconfiguration +schema: 2.0.0 +title: Set-MailboxRegionalConfiguration --- # Set-MailboxRegionalConfiguration @@ -104,6 +105,9 @@ This example sets Megan Bowen mailbox language to Spanish Argentina, sets the da ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -121,7 +125,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: Default, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -131,6 +134,9 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill Archive Description }} @@ -139,7 +145,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -149,6 +154,9 @@ 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`. @@ -158,7 +166,6 @@ 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,6 +175,9 @@ Accept wildcard characters: False ``` ### -DateFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DateFormat parameter specifies a valid date format based on the current or specified language for the mailbox. For example, if the language is set to en-US, valid DateFormat parameter values include: - M/d/yyyy: This is the default value for en-US. @@ -184,7 +194,6 @@ For more information about the date format strings, see [Standard Date and Time 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 @@ -194,6 +203,9 @@ 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. @@ -202,7 +214,6 @@ 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 @@ -212,6 +223,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Language parameter specifies the language for the mailbox. 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). @@ -220,7 +234,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -230,6 +243,9 @@ Accept wildcard characters: False ``` ### -MailboxLocation + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill MailboxLocation Description }} @@ -238,7 +254,6 @@ This parameter is available only in the cloud-based service. Type: MailboxLocationIdParameter Parameter Sets: MailboxLocation Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -248,13 +263,15 @@ Accept wildcard characters: False ``` ### -LocalizeDefaultFolderName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LocalizeDefaultFolderName switch localizes the default folder names of the mailbox in the current or specified language. 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 @@ -264,6 +281,9 @@ Accept wildcard characters: False ``` ### -TimeFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TimeFormat parameter specifies a valid time format based on the current or specified language value for the mailbox. For example, if the language is set to en-us, valid TimeFormat parameter values include: - h:mm tt: This is the default value for en-US. @@ -277,7 +297,6 @@ For more information about the time format strings, see [Standard Date and Time 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 @@ -287,6 +306,9 @@ Accept wildcard characters: False ``` ### -TimeZone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TimeZone parameter specifies the time zone for the mailbox. A valid value for this parameter is a supported time zone key name (for example, "Pacific Standard Time"). @@ -299,7 +321,6 @@ 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 @@ -309,6 +330,9 @@ Accept wildcard characters: False ``` ### -UseCustomRouting + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill UseCustomRouting Description }} @@ -317,7 +341,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: Identity, MailboxLocation Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -327,13 +350,15 @@ 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/exchange/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md index a874cb3a60..349056e2a3 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxrestorerequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxRestoreRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxrestorerequest +schema: 2.0.0 +title: Set-MailboxRestoreRequest --- # Set-MailboxRestoreRequest @@ -81,6 +82,9 @@ This example changes the first restore request for Kweku's mailbox to skip 100 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 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). @@ -89,7 +93,6 @@ If you didn't specify a name for the restore request when it was created, Exchan Type: MailboxRestoreRequestIdParameter 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 @@ -99,6 +102,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later or Exchange Online, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -109,7 +115,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -119,6 +124,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -131,7 +139,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -141,6 +148,9 @@ 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 of the batch. Use this parameter to change, create, or remove a batch name. To remove a batch name, set the BatchName parameter value to an empty string or to null, for example, -BatchName "" or -BatchName $null. @@ -149,7 +159,6 @@ To remove a batch name, set the BatchName parameter value to an empty string or 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 @@ -159,13 +168,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the status of a completed restore request is set to Completed. If this parameter is set to a value of 0, the status is cleared immediately instead of changing it to Completed. ```yaml Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -175,6 +186,9 @@ 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`. @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2010, 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. @@ -202,7 +218,6 @@ 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, Exchange Online Required: False Position: Named @@ -212,6 +227,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -220,7 +238,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -230,6 +247,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -247,7 +267,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -257,6 +276,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: @@ -274,7 +296,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -284,6 +305,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The RehomeRequest switch moves the mailbox restore request to a different mailbox database. You don't need to specify a value with this switch. @@ -294,7 +318,6 @@ Use this switch to edit a mailbox restore request in the case where the source m Type: SwitchParameter Parameter Sets: Rehome Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -304,13 +327,15 @@ Accept wildcard characters: False ``` ### -RemoteHostName + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -320,6 +345,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -333,7 +361,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -343,6 +370,9 @@ Accept wildcard characters: False ``` ### -SkipInitialConnectionValidation + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -351,7 +381,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -361,6 +390,9 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values: - FolderACLs @@ -374,7 +406,6 @@ Use this parameter only if a restore request fails because of folder rules, fold Type: SkippableMergeComponent[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -384,6 +415,9 @@ Accept wildcard characters: False ``` ### -SkippedItemApprovalTime + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -392,7 +426,6 @@ This parameter is reserved for internal Microsoft use. Type: DateTime Parameter Sets: Identity, Rehome Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -402,6 +435,9 @@ Accept wildcard characters: False ``` ### -SourceWlmLevel + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SourceWlmLevel Description }} @@ -410,7 +446,6 @@ This parameter is available only in the cloud-based service. Type: WlmLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -420,6 +455,9 @@ Accept wildcard characters: False ``` ### -TargetWlmLevel + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill TargetWlmLevel Description }} @@ -428,7 +466,6 @@ This parameter is available only in the cloud-based service. Type: WlmLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -438,13 +475,15 @@ 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/exchange/Set-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md index ee2ec50572..4847b28fba 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxsearch +schema: 2.0.0 +title: Set-MailboxSearch --- # Set-Mailboxsearch @@ -87,13 +88,15 @@ In on-premises Exchange, this example adds all public folders to the existing ma ## 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 mailbox search that you want to modify. If the value contains spaces, enclose the value in quotation marks ("). ```yaml Type: SearchObjectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -103,6 +106,9 @@ Accept wildcard characters: False ``` ### -AllPublicFolderSources + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are: - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). @@ -112,7 +118,6 @@ The AllPublicFolderSources parameter specifies whether to include all public fol Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -122,6 +127,9 @@ Accept wildcard characters: False ``` ### -AllSourceMailboxes + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are: - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]). @@ -131,7 +139,6 @@ The AllSourceMailboxes parameter specifies whether to include all mailboxes in t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -141,6 +148,9 @@ 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`. @@ -150,7 +160,6 @@ 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 @@ -160,13 +169,15 @@ 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 search. 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, Exchange Online Required: False Position: Named @@ -176,6 +187,9 @@ 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,7 +198,6 @@ 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,6 +207,9 @@ Accept wildcard characters: False ``` ### -DoNotIncludeArchive + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The DoNotIncludeArchive switch excludes items in the user's Archive mailbox from mailbox searches. You don't need to specify a value with this switch. @@ -204,7 +220,6 @@ By default, items in the user's Archive mailbox are included in mailbox searches Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -214,6 +229,9 @@ Accept wildcard characters: False ``` ### -EndDate + +> Applicable: Exchange Server 2010, 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". @@ -224,7 +242,6 @@ To clear the end date, use the value $null. Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -234,13 +251,15 @@ Accept wildcard characters: False ``` ### -EstimateOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EstimateOnly switch provides only an estimate of the number of items that will be returned without copying message to the target 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 @@ -250,6 +269,9 @@ Accept wildcard characters: False ``` ### -ExcludeDuplicateMessages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExcludeDuplicateMessages parameter eliminates duplication of messages across mailboxes in an In-Place eDiscovery search. Valid values are: - $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value. @@ -259,7 +281,6 @@ The ExcludeDuplicateMessages parameter eliminates duplication of messages across 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 @@ -269,6 +290,9 @@ 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. Use this to switch to hide the confirmation prompt that indicates the previous search results will be removed from the target mailbox, and that the search will be restarted. @@ -277,7 +301,6 @@ Use this to switch to hide the confirmation prompt that indicates the previous s 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 @@ -287,13 +310,15 @@ Accept wildcard characters: False ``` ### -IncludeKeywordStatistics + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeKeywordStatistics switch returns keyword statistics (number of instances for each keyword). 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 @@ -303,6 +328,9 @@ Accept wildcard characters: False ``` ### -IncludeUnsearchableItems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncludeUnsearchableItems parameter specifies whether items that couldn't be indexed by Exchange Search should be included in the results. Valid values are: - $true: Unsearchable items are included in the results. @@ -314,7 +342,6 @@ Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you 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 @@ -324,6 +351,9 @@ Accept wildcard characters: False ``` ### -InPlaceHoldEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are: - $true: In-Place Hold is enabled on the search results. @@ -337,7 +367,6 @@ If you attempt to place a hold but don't specify mailboxes using the SourceMailb 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 @@ -347,6 +376,9 @@ Accept wildcard characters: False ``` ### -ItemHoldPeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all items or the mailbox items that are returned in the search query results). You use this parameter with the InPlaceHoldEnabled parameter to set an In-Place Hold. The duration is calculated from the time the item is received or created in the mailbox. Valid values are: - An integer. @@ -356,7 +388,6 @@ The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold 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 @@ -366,6 +397,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Language parameter specifies a locale for the mailbox 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). @@ -374,7 +408,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -384,6 +417,9 @@ Accept wildcard characters: False ``` ### -LogLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LogLevel parameter specifies a logging level for the mailbox search. Valid values are: - Basic: Basic details of the search are kept. This is the default value. @@ -394,7 +430,6 @@ The LogLevel parameter specifies a logging level for the mailbox search. Valid v Type: LoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -404,6 +439,9 @@ Accept wildcard characters: False ``` ### -MessageTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MessageTypes parameter specifies the message types to include in the search query. Valid values are: - Contacts @@ -423,7 +461,6 @@ The default value is blank ($null), which means all message types are included. Type: KindKeyword[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -433,6 +470,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the search. If the value contains spaces, enclose the value in quotation marks ("). The value of this parameter is used to create the top-level folder that holds the search results in the target mailbox that's specified by the TargetMailbox parameter. @@ -441,7 +481,6 @@ The value of this parameter is used to create the top-level folder that holds th 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 @@ -451,6 +490,9 @@ Accept wildcard characters: False ``` ### -Recipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Recipients parameter specifies one or more recipients include in the search query. Messages that have the specified recipients in the To, Cc, and Bcc fields are returned in the search results. You can specify multiple recipients separated by commas. If the value contains spaces, enclose the value in quotation marks ("). @@ -461,7 +503,6 @@ To clear the recipients, use the value $null. 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 @@ -471,6 +512,9 @@ Accept wildcard characters: False ``` ### -SearchDumpster + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The SearchDumpster parameter specifies whether the dumpster is searched. The dumpster is a storage area in the mailbox where deleted items are temporarily stored after being deleted or removed from the Deleted Items folder, or after being hard-deleted and before being purged from the mailbox based on Deleted Item Retention settings. @@ -481,7 +525,6 @@ Set the value to $true to enable searching the dumpster, or set to $false to dis Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -491,6 +534,9 @@ Accept wildcard characters: False ``` ### -SearchQuery + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SearchQuery parameter specifies keywords for the search query 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). If you use this parameter with other search query parameters, the query combines these parameters by using the AND operator. @@ -507,7 +553,6 @@ The other search query parameters are: 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 @@ -517,6 +562,9 @@ Accept wildcard characters: False ``` ### -Senders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Senders parameter specifies one or more senders to include in the search query. Messages that have the specified sender are returned in the search results. Senders can include users, distribution groups (messages sent by members of the group), SMTP addresses, or domains. You can specify multiple senders separated by commas. If the value contains spaces, enclose the value in quotation marks ("). @@ -527,7 +575,6 @@ To clear the senders, use the value $null. 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 @@ -537,6 +584,9 @@ Accept wildcard characters: False ``` ### -SourceMailboxes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceMailboxes parameter specifies the mailboxes to be searched. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -561,7 +611,6 @@ To enable In-Place Hold on the search results, you need to set the AllSourceMail Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -571,6 +620,9 @@ Accept wildcard characters: False ``` ### -StartDate + +> Applicable: Exchange Server 2010, 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". @@ -581,7 +633,6 @@ To clear start date, use the value $null. Type: ExDateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -591,13 +642,15 @@ Accept wildcard characters: False ``` ### -StatisticsStartIndex + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StatisticsStartIndex parameter is used by the Exchange admin center (EAC) to retrieve keyword statistics in a paged operation. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -607,6 +660,9 @@ Accept wildcard characters: False ``` ### -StatusMailRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StatusMailRecipients parameter specifies one or more recipients to receive a status email message upon completion of the search. You can use any value that uniquely identifies the recipient. For example: - Name @@ -622,7 +678,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -632,6 +687,9 @@ 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 destination mailbox where the search results are copied. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -649,7 +707,6 @@ The TargetMailbox parameter specifies the destination mailbox where the search r 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 @@ -659,13 +716,15 @@ 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/exchange/Set-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md index fc78cfa732..9f66f9399d 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxsentitemsconfiguration applicable: Exchange Server 2010 -title: Set-MailboxSentItemsConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxsentitemsconfiguration +schema: 2.0.0 +title: Set-MailboxSentItemsConfiguration --- # Set-MailboxSentItemsConfiguration @@ -47,6 +48,9 @@ This example configures the shared mailbox named "Customer Support Feedback" so ## PARAMETERS ### -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`. @@ -56,7 +60,6 @@ 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 @@ -66,13 +69,15 @@ 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 @@ -82,6 +87,9 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the mailbox whose Sent Items configuration you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ Accept wildcard characters: False ``` ### -SendAsItemsCopiedTo + +> Applicable: Exchange Server 2010 + The SendAsItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send As permission are saved. Valid values are: - Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. @@ -118,7 +128,6 @@ The SendAsItemsCopiedTo parameter specifies where messages that are sent from th Type: SentItemsCopiedTo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -128,6 +137,9 @@ Accept wildcard characters: False ``` ### -SendOnBehalfOfItemsCopiedTo + +> Applicable: Exchange Server 2010 + The SendOnBehalfOfItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send On Behalf Of permission are saved. Valid values are: - Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value. @@ -137,7 +149,6 @@ The SendOnBehalfOfItemsCopiedTo parameter specifies where messages that are sent Type: SentItemsCopiedTo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -147,13 +158,15 @@ 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/exchange/Set-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-MailboxServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md index 1e8ce40d3a..7fdfbaf24e 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxserver applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MailboxServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxserver +schema: 2.0.0 +title: Set-MailboxServer --- # Set-MailboxServer @@ -193,6 +194,9 @@ In Exchange 2010, this example throttles the TopN Words Assistant and the Unifie ## 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 modify. You can use any value that uniquely identifies the server. For example: - Name @@ -203,7 +207,6 @@ The Identity parameter specifies the Mailbox server that you want to modify. You Type: MailboxServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -213,13 +216,15 @@ Accept wildcard characters: False ``` ### -AutoDagServerConfigured + +> 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 @@ -229,6 +234,9 @@ Accept wildcard characters: False ``` ### -AutoDatabaseMountDial + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDatabaseMountDial parameter specifies the automatic database mount behavior for a continuous replication environment after a database failover on the Mailbox server. You can use the following values: - BestAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and mounts the database. @@ -241,7 +249,6 @@ The default value is GoodAvailability. If you specify either BestAvailability or Type: AutoDatabaseMountDial Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -251,6 +258,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairIntervalEndWindow + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairIntervalEndWindow parameter specifies the number of days into the future to repair calendar items in mailboxes on the Mailbox server. The default value in Exchange 2016 and Exchange 2019 is 7. This value means the Calendar Repair Assistant repairs meetings in calendars up to 7 days from now. Meetings that are scheduled to occur more than 7 days in the future aren't repaired. @@ -261,7 +271,6 @@ The default value in Exchange 2013 and Exchange 2010 is 30. This value means the Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -271,6 +280,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairLogDirectorySizeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairLogDirectorySizeLimit parameter specifies the maximum size of calendar repair log directory on the Mailbox server. When the directory reaches its maximum size, the server deletes the oldest log files first. Calendar repair log files begin with the name prefix CRA. The maximum size of the calendar repair log directory is calculated as the total size of all log files that have the CRA name prefix. Other files aren't counted in the total directory size calculation. Renaming old log files or copying other files into the calendar repair log directory could cause the directory to exceed its specified maximum size. @@ -293,7 +305,6 @@ If you enter the value unlimited, no size limit is imposed on the calendar repai Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -303,6 +314,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairLogEnabled parameter specifies whether the Calendar Repair Attendant logs items that it repairs on the Mailbox server. The repair log doesn't contain failed repair attempts. Valid input for this parameter is $true or $false. The default value is $true. @@ -318,7 +332,6 @@ The value of this parameter affects the following parameters: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -328,6 +341,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairLogFileAgeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairLogFileAgeLimit parameter specifies the calendar repair log maximum file age on the Mailbox server. Log files older than the specified value are deleted. The default value is 10 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. @@ -338,7 +354,6 @@ For example, to specify 30 days, enter 30.00:00:00. The value 00:00:00 prevents Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -348,13 +363,15 @@ Accept wildcard characters: False ``` ### -CalendarRepairLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairLogPath parameter specifies the location of the calendar repair log files on the Mailbox server. The default value is %ExchangeInstallPath%Logging\\Calendar Repair Assistant. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -364,13 +381,15 @@ Accept wildcard characters: False ``` ### -CalendarRepairLogSubjectLoggingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairLogSubjectLoggingEnabled parameter specifies whether to include the subject of repaired calendar items in the calendar repair log on the Mailbox server. 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 @@ -380,13 +399,15 @@ Accept wildcard characters: False ``` ### -CalendarRepairMissingItemFixDisabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant won't fix missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $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 Required: False Position: Named @@ -396,13 +417,15 @@ Accept wildcard characters: False ``` ### -CalendarRepairMode + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarRepairMode parameter specifies the Calendar Repair Assistant mode on the Mailbox server. Valid values for this parameter are ValidateOnly or RepairAndValidate. The default value is RepairAndValidate. ```yaml Type: CalendarRepairType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -412,6 +435,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairSchedule + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CalendarRepairSchedule parameter specifies the intervals each week during which the Calendar Repair Assistant applies checks for calendar failures. @@ -441,7 +467,6 @@ Here are some examples: Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -451,6 +476,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Calendar Repair Assistant. The default value is 1 day. @@ -465,7 +493,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -475,6 +502,9 @@ Accept wildcard characters: False ``` ### -CalendarRepairWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server will be identified as needing work completed on them. The default value is 1 day. @@ -487,7 +517,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -497,6 +526,9 @@ 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`. @@ -506,7 +538,6 @@ 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 @@ -516,6 +547,9 @@ Accept wildcard characters: False ``` ### -DarTaskStoreTimeBasedAssistantWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -524,7 +558,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -534,6 +567,9 @@ Accept wildcard characters: False ``` ### -DarTaskStoreTimeBasedAssistantWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -542,7 +578,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -552,6 +587,9 @@ Accept wildcard characters: False ``` ### -DatabaseCopyActivationDisabledAndMoveNow + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It will also immediately move any mounted databases on the server to other servers if copies exist and are healthy. Valid input for this parameter is $true or $false. The default value is $false. @@ -562,7 +600,6 @@ Setting this parameter to $true won't cause databases to move to a server that h Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -572,6 +609,9 @@ Accept wildcard characters: False ``` ### -DatabaseCopyAutoActivationPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic activation available for mailbox database copies on the specified Mailbox server. Valid values for this parameter are: - Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access is not impacted. @@ -582,7 +622,6 @@ The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic a Type: DatabaseCopyAutoActivationPolicyType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -592,6 +631,9 @@ Accept wildcard characters: False ``` ### -DirectoryProcessorWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -600,7 +642,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -610,6 +651,9 @@ Accept wildcard characters: False ``` ### -DirectoryProcessorWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -618,7 +662,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -628,13 +671,15 @@ 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 @@ -644,13 +689,15 @@ Accept wildcard characters: False ``` ### -FaultZone + +> Applicable: 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -660,6 +707,9 @@ Accept wildcard characters: False ``` ### -FolderLogForManagedFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The FolderLogForManagedFoldersEnabled parameter specifies whether managed folder logging is enabled on the Mailbox server. Valid input for this parameter is$true or $false. The default value is $false. @@ -680,7 +730,6 @@ The value of this parameter affects the following parameters: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -690,6 +739,9 @@ Accept wildcard characters: False ``` ### -ForceGroupMetricsGeneration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceGroupMetricsGeneration parameter specifies that group metrics information must be generated on the Mailbox server regardless of whether that server generates an offline address book (OAB). Valid input for this parameter is $true or $false. The default value is $false. By default, group metrics are generated only on servers that generate OABs. Group metrics information is used by MailTips to inform senders about how many recipients their messages will be sent to. You need to set this parameter to $true if your organization doesn't generate OABs and you want the group metrics data to be available. @@ -698,7 +750,6 @@ By default, group metrics are generated only on servers that generate OABs. Grou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -708,6 +759,9 @@ Accept wildcard characters: False ``` ### -GroupMailboxWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -716,7 +770,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -726,6 +779,9 @@ Accept wildcard characters: False ``` ### -GroupMailboxWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -734,7 +790,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -744,6 +799,9 @@ Accept wildcard characters: False ``` ### -GroupMetricsGenerationTime + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The GroupMetricsGenerationTime parameter specifies the time of day when group metrics data is generated on a Mailbox server. You must use the 24-hour clock notation (HH:MM) when specifying the generation time. @@ -752,7 +810,6 @@ The GroupMetricsGenerationTime parameter specifies the time of day when group me Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -762,6 +819,9 @@ Accept wildcard characters: False ``` ### -InferenceDataCollectionWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -770,7 +830,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -780,6 +839,9 @@ Accept wildcard characters: False ``` ### -InferenceDataCollectionWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -788,7 +850,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -798,6 +859,9 @@ Accept wildcard characters: False ``` ### -InferenceTrainingWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -806,7 +870,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -816,6 +879,9 @@ Accept wildcard characters: False ``` ### -InferenceTrainingWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -824,7 +890,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -834,6 +899,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogEnabled parameter enables or disables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: @@ -845,7 +913,6 @@ The IrmLogEnabled parameter enables or disables logging of Information Rights Ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -855,6 +922,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. The default value is 30 days. @@ -867,7 +937,6 @@ Setting the value of the IrmLogMaxAge parameter to 00:00:00 prevents the automat Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -877,6 +946,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 megabytes (MB). When you enter a value, qualify the value with one of the following units: @@ -895,7 +967,6 @@ The valid input range for either parameter is from 1 through 9223372036854775807 Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -905,6 +976,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -921,7 +995,6 @@ Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize para Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -931,6 +1004,9 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\ v14\\Logging\\IRMLogs. @@ -941,7 +1017,6 @@ If you set the value of the IrmLogPath parameter to $null, you effectively disab Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -951,6 +1026,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromProvisioning + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid input for this parameter is $true or $false. The default value is $false. If you specify$true, the server won't be used for provisioning a new OAB or for moving existing OABs. @@ -959,7 +1037,6 @@ If you specify$true, the server won't be used for provisioning a new OAB or for Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -969,6 +1046,9 @@ Accept wildcard characters: False ``` ### -JournalingLogForManagedFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The JournalingLogForManagedFoldersEnabled parameter specifies whether journaling activity is recorded in the managed folder log on the Mailbox server.Valid input for this parameter is$true or $false. The default value is $false. If you specify $true, information about messages that were journaled in managed folders is logged. The managed folder log directory is specified by the LogPathForManagedFolders parameter. @@ -977,7 +1057,6 @@ If you specify $true, information about messages that were journaled in managed Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -987,6 +1066,9 @@ Accept wildcard characters: False ``` ### -JunkEmailOptionsCommitterWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -995,7 +1077,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1005,6 +1086,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Locale parameter specifies the locale of the Mailbox server. A locale is a collection of language-related user preferences such as writing system, calendar, and date format. The following are examples: - en-US (English - United States) @@ -1021,7 +1105,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1031,6 +1114,9 @@ Accept wildcard characters: False ``` ### -LogDirectorySizeLimitForManagedFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The LogDirectorySizeLimitForManagedFolders parameter specifies the maximum size of all managed folder logs from a single mailbox database in the managed folder log directory on the Mailbox server. When a set of log files reaches its maximum size, the server deletes the oldest log files first. @@ -1053,7 +1139,6 @@ The default value is unlimited, which means no size limit is imposed on the mana Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1063,6 +1148,9 @@ Accept wildcard characters: False ``` ### -LogFileAgeLimitForManagedFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The LogFileAgeLimitForManagedFolders parameter specifies how long to retain managed folder logs on the Mailbox server. Log files older than the specified value are deleted. @@ -1075,7 +1163,6 @@ For example, to specify a 30 days, enter 30.00:00:00. The default value is 00:00 Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1085,6 +1172,9 @@ Accept wildcard characters: False ``` ### -LogFileSizeLimitForManagedFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The LogFileSizeLimitForManagedFolders parameter specifies the maximum size for each managed folder log file on the Mailbox server. When a log file reaches its maximum size, a new log file is created. The default value is 10 megabytes (MB). @@ -1105,7 +1195,6 @@ If you enter the value unlimited, no size limit is imposed on a managed folder l Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1115,6 +1204,9 @@ Accept wildcard characters: False ``` ### -LogPathForManagedFolders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The LogPathForManagedFolders parameter specifies the location of the managed folder log files on the Mailbox server. The default value is %ExchangeInstallPath%Logging\\ Managed Folder Assistant. @@ -1123,7 +1215,6 @@ The LogPathForManagedFolders parameter specifies the location of the managed fol Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1133,6 +1224,9 @@ Accept wildcard characters: False ``` ### -MailboxAssociationReplicationWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1141,7 +1235,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1151,6 +1244,9 @@ Accept wildcard characters: False ``` ### -MailboxAssociationReplicationWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1159,7 +1255,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1169,6 +1264,9 @@ Accept wildcard characters: False ``` ### -MailboxProcessorWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The MailboxProcessorWorkCycle parameter specifies how often to scan for locked mailboxes on the Mailbox server. The default value is 1 day. @@ -1179,7 +1277,6 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hou Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1189,6 +1286,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderAssistantSchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **Note**: Although this parameter is available in Exchange 2016 and Exchange 2019, it's only used for coexistence with previous versions of Exchange. For more information, see [Configure and run the Managed Folder Assistant in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/configure-managed-folder-assistant). The ManagedFolderAssistantSchedule parameter specifies the intervals each week during which the Managed Folder Assistant applies messaging records management (MRM) settings to managed folders in mailboxes on the Mailbox server. @@ -1220,7 +1320,6 @@ If the Managed Folder Assistant doesn't finish processing the mailboxes on the s Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1230,6 +1329,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be processed by the Managed Folder Assistant. The default value is 1 day. @@ -1244,7 +1346,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed F Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1254,6 +1355,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. @@ -1268,7 +1372,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1278,13 +1381,15 @@ Accept wildcard characters: False ``` ### -MAPIEncryptionRequired + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MAPIEncryptionRequired parameter specifies whether Exchange blocks MAPI client connections to the Mailbox server that don't use encrypted remote procedure calls (RPCs). Valid input for this parameter is$true or $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 Required: False Position: Named @@ -1294,6 +1399,9 @@ Accept wildcard characters: False ``` ### -MaximumActiveDatabases + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaximumActiveDatabases parameter specifies the maximum number of databases that can be mounted on the Mailbox server. When the maximum number is reached, the database copies on the server won't be activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server won't allow databases to be mounted. @@ -1304,7 +1412,6 @@ The default value is blank ($null), which means no maximum value is configured. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1314,6 +1421,9 @@ Accept wildcard characters: False ``` ### -MaximumPreferredActiveDatabases + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaximumPreferredActiveDatabases parameter specifies a preferred maximum number of databases that theMailbox server should have. This value is different from the actual maximum, which is configured using the MaximumActiveDatabases parameter. The value of MaximumPreferredActiveDatabases is only honored during best copy and server selection, database and server switchovers, and when rebalancing the DAG. The default value is blank ($null), which means no maximum value is configured. @@ -1322,7 +1432,6 @@ The default value is blank ($null), which means no maximum value is configured. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1332,6 +1441,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogEnabled parameter specifies whether message tracking is enabled. The default value is $true. @@ -1340,7 +1452,6 @@ The MessageTrackingLogEnabled parameter specifies whether message tracking is en Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1350,6 +1461,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxAge + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogMaxAge parameter specifies the message tracking log maximum file age. Log files older than the specified value are deleted. The default value is 30 days. @@ -1362,7 +1476,6 @@ The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1372,6 +1485,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxDirectorySize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogMaxDirectorySize parameter specifies the maximum size of the message tracking log directory. When the maximum directory size is reached, the server deletes the oldest log files first. @@ -1394,7 +1510,6 @@ Unqualified values are treated as bytes. The value of the MessageTrackingLogMaxF Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1404,6 +1519,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxFileSize + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the message tracking log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1419,7 +1537,6 @@ Unqualified values are treated as bytes. The value of the MessageTrackingLogMaxF Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1429,6 +1546,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogPath + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogPath parameter specifies the location of the message tracking logs. The default location is C:\\Program Files\\Microsoft\\Exchange Server TransportRoles\\Logs\\MessageTracking. If you set the value of the MessageTrackingLogPath parameter to $null, you effectively disable message tracking. However, if you set the value of the MessageTrackingLogPath parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true, event log errors occur. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter. @@ -1437,7 +1557,6 @@ The MessageTrackingLogPath parameter specifies the location of the message track Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1447,6 +1566,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogSubjectLoggingEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MessageTrackingLogSubjectLoggingEnabled parameter specifies if the message subject should be included in the message tracking log. The default value is $true. @@ -1455,7 +1577,6 @@ The MessageTrackingLogSubjectLoggingEnabled parameter specifies if the message s Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1465,13 +1586,15 @@ Accept wildcard characters: False ``` ### -MigrationLogFilePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1481,13 +1604,15 @@ Accept wildcard characters: False ``` ### -MigrationLogLoggingLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MigrationEventType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1497,13 +1622,15 @@ Accept wildcard characters: False ``` ### -MigrationLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1513,13 +1640,15 @@ Accept wildcard characters: False ``` ### -MigrationLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1529,13 +1658,15 @@ Accept wildcard characters: False ``` ### -MigrationLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1545,6 +1676,9 @@ Accept wildcard characters: False ``` ### -OABGeneratorWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server will be processed. The default value is 8 hours. @@ -1557,7 +1691,6 @@ For example, to specify 16 hours for this parameter, use 16:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1567,6 +1700,9 @@ Accept wildcard characters: False ``` ### -OABGeneratorWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The OABGeneratorWorkCycleCheckpoint parameter specifies the time span at which to run OAB generation on the Mailbox server. The default value is 1 hour. @@ -1579,7 +1715,6 @@ For example, to specify 2 hours for this parameter, use 02:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1589,6 +1724,9 @@ Accept wildcard characters: False ``` ### -PeopleCentricTriageWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1597,7 +1735,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1607,6 +1744,9 @@ Accept wildcard characters: False ``` ### -PeopleCentricTriageWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1615,7 +1755,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1625,6 +1764,9 @@ Accept wildcard characters: False ``` ### -PeopleRelevanceWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1633,7 +1775,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1643,6 +1784,9 @@ Accept wildcard characters: False ``` ### -PeopleRelevanceWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1651,7 +1795,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1661,6 +1804,9 @@ Accept wildcard characters: False ``` ### -ProbeTimeBasedAssistantWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1669,7 +1815,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1679,6 +1824,9 @@ Accept wildcard characters: False ``` ### -ProbeTimeBasedAssistantWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1687,7 +1835,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1697,6 +1844,9 @@ Accept wildcard characters: False ``` ### -PublicFolderWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The PublicFolderWorkCycle parameter is used by the public folder assistant to determine how often the mailboxes in a database are processed by the assistant on the Mailbox server. The default value is 1 day. @@ -1707,7 +1857,6 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hou Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1717,6 +1866,9 @@ Accept wildcard characters: False ``` ### -PublicFolderWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The PublicFolderWorkCycleCheckpoint determines how often the mailbox list for a database is evaluated on the Mailbox server. The processing speed is also calculated. The default value is 1 day. @@ -1727,7 +1879,6 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hou Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1737,6 +1888,9 @@ Accept wildcard characters: False ``` ### -RetentionLogForManagedFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The RetentionLogForManagedFoldersEnabled parameter specifies whether retention policy activity is recorded in the managed folder log on the Mailbox server. Valid input for this parameter is$true or $false. The default value is $false. @@ -1747,7 +1901,6 @@ If you specify $true, information about messages in managed folders that have be Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1757,6 +1910,9 @@ Accept wildcard characters: False ``` ### -SearchIndexRepairTimeBasedAssistantWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1765,7 +1921,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1775,6 +1930,9 @@ Accept wildcard characters: False ``` ### -SearchIndexRepairTimeBasedAssistantWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1783,7 +1941,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1793,6 +1950,9 @@ Accept wildcard characters: False ``` ### -SharePointSignalStoreWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1801,7 +1961,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1811,6 +1970,9 @@ Accept wildcard characters: False ``` ### -SharePointSignalStoreWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -1819,7 +1981,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1829,6 +1990,9 @@ Accept wildcard characters: False ``` ### -SharingPolicySchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SharingPolicySchedule parameter specifies the intervals each week during which the sharing policy runs on the Mailbox server. The Sharing Policy Assistant checks permissions on shared calendar items and contact folders in users' mailboxes against the assigned sharing policy. The assistant lowers or removes permissions according to the policy. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can specify multiple schedules separated by commas: `"Schedule1","Schedule2",..."ScheduleN"`. @@ -1856,7 +2020,6 @@ Here are some examples: Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1866,6 +2029,9 @@ Accept wildcard characters: False ``` ### -SharingPolicyWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Sharing Policy Assistant. The default value is 1 day. @@ -1880,7 +2046,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing P Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1890,6 +2055,9 @@ Accept wildcard characters: False ``` ### -SharingPolicyWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. @@ -1904,7 +2072,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing P Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1914,6 +2081,9 @@ Accept wildcard characters: False ``` ### -SharingSyncWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours. @@ -1928,7 +2098,6 @@ For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sy Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1938,6 +2107,9 @@ Accept wildcard characters: False ``` ### -SharingSyncWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 3 hours. @@ -1952,7 +2124,6 @@ For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sy Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1962,6 +2133,9 @@ Accept wildcard characters: False ``` ### -SiteMailboxWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server will be processed. The default value is 6 hours. @@ -1974,7 +2148,6 @@ For example, to specify 8 hours for this parameter, use 08:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -1984,6 +2157,9 @@ Accept wildcard characters: False ``` ### -SiteMailboxWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. The SiteMailboxWorkCycleCheckpoint parameter specifies the time span at which to refresh the site mailbox workcycle on the Mailbox server. The default value is 6 hours. @@ -1996,7 +2172,6 @@ For example, to specify 8 hours for this parameter, use 08:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2006,6 +2181,9 @@ Accept wildcard characters: False ``` ### -StoreDsMaintenanceWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2014,7 +2192,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2024,6 +2201,9 @@ Accept wildcard characters: False ``` ### -StoreDsMaintenanceWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2032,7 +2212,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2042,6 +2221,9 @@ Accept wildcard characters: False ``` ### -StoreIntegrityCheckWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2050,7 +2232,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2060,6 +2241,9 @@ Accept wildcard characters: False ``` ### -StoreIntegrityCheckWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2068,7 +2252,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2078,6 +2261,9 @@ Accept wildcard characters: False ``` ### -StoreMaintenanceWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2086,7 +2272,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2096,6 +2281,9 @@ Accept wildcard characters: False ``` ### -StoreMaintenanceWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2104,7 +2292,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2114,6 +2301,9 @@ Accept wildcard characters: False ``` ### -StoreScheduledIntegrityCheckWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2122,7 +2312,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2132,6 +2321,9 @@ Accept wildcard characters: False ``` ### -StoreScheduledIntegrityCheckWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2140,7 +2332,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2150,6 +2341,9 @@ Accept wildcard characters: False ``` ### -StoreUrgentMaintenanceWorkCycle + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2158,7 +2352,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2168,6 +2361,9 @@ Accept wildcard characters: False ``` ### -StoreUrgentMaintenanceWorkCycleCheckpoint + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -2176,7 +2372,6 @@ This parameter is reserved for internal Microsoft use. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -2186,6 +2381,9 @@ Accept wildcard characters: False ``` ### -SubjectLogForManagedFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1). The SubjectLogForManagedFoldersEnabled parameter specifies whether to include the subject of messages in the managed folder logs on the Mailbox server. Valid input for this parameter is$true or $false. The default value is $false. @@ -2196,7 +2394,6 @@ By default, the subject of messages is blank in the managed folder log. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2206,13 +2403,15 @@ Accept wildcard characters: False ``` ### -SubmissionServerOverrideList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2222,6 +2421,9 @@ Accept wildcard characters: False ``` ### -TopNWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server will be scanned by the TopN Words Assistant. The default value is 7 days. @@ -2236,7 +2438,6 @@ For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Wo Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2246,6 +2447,9 @@ Accept wildcard characters: False ``` ### -TopNWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day. @@ -2260,7 +2464,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Word Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2270,6 +2473,9 @@ Accept wildcard characters: False ``` ### -UMReportingWorkCycle + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be scanned by the Unified Messaging Reporting Assistant. The default value is 1 day. @@ -2286,7 +2492,6 @@ Changing the default work cycle for this assistant might impact the performance Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2296,6 +2501,9 @@ Accept wildcard characters: False ``` ### -UMReportingWorkCycleCheckpoint + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be marked by processing. The default value is 1 day. @@ -2308,7 +2516,6 @@ For example, to specify 2 days for this parameter, use 2.00:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2318,6 +2525,9 @@ Accept wildcard characters: False ``` ### -WacDiscoveryEndpoint + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The WacDiscoveryEndpoint parameter specifies the discovery endpoint for Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) for all mailboxes on the server. For example, `https://oos.internal.contoso.com/hosting/discovery`. Office Online Server enables users to view supported file attachments in Outlook on the web (formerly known as Outlook Web App). @@ -2326,7 +2536,6 @@ Office Online Server enables users to view supported file attachments in Outlook Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2336,13 +2545,15 @@ 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/exchange/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md index 975a5bcb45..e59201c886 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxspellingconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MailboxSpellingConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxspellingconfiguration +schema: 2.0.0 +title: Set-MailboxSpellingConfiguration --- # Set-MailboxSpellingConfiguration @@ -54,6 +55,9 @@ This example sets the spelling checker to ignore words containing numbers for me ## 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -71,7 +75,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us 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 @@ -81,13 +84,15 @@ Accept wildcard characters: False ``` ### -CheckBeforeSend + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CheckBeforeSend parameter specifies whether Outlook on the web checks the spelling for every message when the user clicks Send in the new message form. Valid values are$true or $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 @@ -97,6 +102,9 @@ 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,7 +114,6 @@ 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,6 +123,9 @@ Accept wildcard characters: False ``` ### -DictionaryLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DictionaryLanguage parameter specifies the dictionary language to use when the spelling checker checks the spelling in messages. Valid values are: - Arabic @@ -144,7 +154,6 @@ The DictionaryLanguage parameter specifies the dictionary language to use when t Type: SpellCheckerSupportedLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -154,6 +163,9 @@ 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. @@ -162,7 +174,6 @@ 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 @@ -172,13 +183,15 @@ Accept wildcard characters: False ``` ### -IgnoreMixedDigits + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IgnoreMixedDigits parameter specifies whether the spelling checker ignores words that contain numbers. Valid values are $true or $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 @@ -188,6 +201,9 @@ Accept wildcard characters: False ``` ### -IgnoreUppercase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IgnoreUppercase parameter specifies whether the spelling checker ignores words that contain only uppercase letters, for example, acronyms. Valid values are $true or $false. The default value is $false. @@ -196,7 +212,6 @@ Valid values are $true or $false. The default value is $false. 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 @@ -206,13 +221,15 @@ 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/exchange/Set-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MailboxTransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md index ae787b004f..fa803911be 100644 --- a/exchange/exchange-ps/exchange/Set-MailboxTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxtransportservice applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MailboxTransportService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mailboxtransportservice +schema: 2.0.0 +title: Set-MailboxTransportService --- # Set-MailboxTransportService @@ -85,13 +86,15 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server that you want to modify. ```yaml Type: MailboxTransportServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -101,6 +104,9 @@ 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`. @@ -110,7 +116,6 @@ 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 @@ -120,13 +125,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,6 +143,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. 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. @@ -146,7 +156,6 @@ For example, to specify 25 days for this parameter, use 25.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -156,6 +165,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: @@ -174,7 +186,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -184,6 +195,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -202,7 +216,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -212,13 +225,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -228,6 +243,9 @@ Accept wildcard characters: False ``` ### -ContentConversionTracingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service or in the Mailbox Transport service on the Mailbox server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of email messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows: - Administrators: Full Control @@ -238,7 +256,6 @@ The ContentConversionTracingEnabled parameter specifies whether content conversi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -248,13 +265,15 @@ 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 @@ -264,13 +283,15 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryAgentLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryAgentLogEnabled parameter specifies whether the agent log for the Mailbox Transport Delivery service is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -280,6 +301,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryAgentLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryAgentLogMaxAge parameter specifies the maximum age for the agent log file of the Mailbox Transport Delivery service. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -290,7 +314,6 @@ Setting the value of the MailboxDeliveryAgentLogMaxAge parameter to 00:00:00 pre Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -300,6 +323,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryAgentLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryAgentLogMaxDirectorySize parameter specifies the maximum size of all Mailbox Transport Delivery service agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -318,7 +344,6 @@ The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -328,6 +353,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryAgentLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryAgentLogMaxFileSize parameter specifies the maximum size of each agent log file for the Mailbox Transport Delivery service. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -346,7 +374,6 @@ The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,13 +383,15 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryAgentLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryAgentLogPath parameter specifies the default agent log directory location for the Mailbox Transport Delivery service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\AgentLog\\Delivery. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the MailboxDeliveryAgentLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -372,13 +401,15 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryConnectorMaxInboundConnection + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryConnectorMaxInboundConnection parameter specifies the maximum number of inbound connections for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. The default value is 5000. If you enter the value unlimited, no connection limit is imposed on the mailbox delivery Receive connector. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -388,6 +419,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryConnectorProtocolLoggingLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: - None: Protocol logging is disabled for the mailbox delivery Receive connector. This is the default value. @@ -397,7 +431,6 @@ The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables S Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -407,6 +440,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryConnectorSmtpUtf8Enabled + +> Applicable: Exchange Server 2019 + The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address internationalization (EAI) support for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are: - $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This is the default value @@ -416,7 +452,6 @@ The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -426,13 +461,15 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryThrottlingLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryThrottlingLogEnabled parameter specifies whether the mailbox delivery throttling log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -442,6 +479,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryThrottlingLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryThrottlingLogMaxAge parameter specifies the maximum age for the mailbox delivery throttling log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -452,7 +492,6 @@ Setting the value of the MailboxDeliveryThrottlingLogMaxAge parameter to 00:00:0 Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -462,6 +501,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryThrottlingLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryThrottlingLogMaxDirectorySize parameter specifies the maximum size of all mailbox delivery throttling logs in the mailbox delivery throttling log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 200 MB. When you enter a value, qualify the value with one of the following units: @@ -480,7 +522,6 @@ The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -490,6 +531,9 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryThrottlingLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryThrottlingLogMaxFileSize parameter specifies the maximum size of each mailbox delivery throttling log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -508,7 +552,6 @@ The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -518,13 +561,15 @@ Accept wildcard characters: False ``` ### -MailboxDeliveryThrottlingLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxDeliveryThrottlingLogPath parameter specifies the default mailbox delivery throttling log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Throttling\\Delivery. Setting the value of this parameter to $null disables mailbox delivery throttling logging. However, setting this parameter to $null when the value of the MailboxDeliveryThrottlingLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -534,13 +579,15 @@ Accept wildcard characters: False ``` ### -MailboxSubmissionAgentLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxSubmissionAgentLogEnabled parameter specifies whether the agent log is enabled for the Mailbox Transport Submission service. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -550,6 +597,9 @@ Accept wildcard characters: False ``` ### -MailboxSubmissionAgentLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxSubmissionAgentLogMaxAge parameter specifies the maximum age for the agent log file of the Mailbox Transport Submission service. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -560,7 +610,6 @@ Setting the value of the MailboxSubmissionAgentLogMaxAge parameter to 00:00:00 p Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -570,6 +619,9 @@ Accept wildcard characters: False ``` ### -MailboxSubmissionAgentLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxSubmissionAgentLogMaxDirectorySize parameter specifies the maximum size of all Mailbox Transport Submission service agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -588,7 +640,6 @@ The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less tha Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -598,6 +649,9 @@ Accept wildcard characters: False ``` ### -MailboxSubmissionAgentLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxSubmissionAgentLogMaxFileSize parameter specifies the maximum size of each agent log file for the Mailbox Transport Submission service. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -616,7 +670,6 @@ The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less tha Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -626,13 +679,15 @@ Accept wildcard characters: False ``` ### -MailboxSubmissionAgentLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxSubmissionAgentLogPath parameter specifies the default agent log directory location for the Mailbox Transport Submission service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\AgentLog\\Submission. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the MailboxSubmissionAgentLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -642,13 +697,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxDeliveries + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -658,13 +715,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxSubmissions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -674,13 +733,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -690,6 +751,9 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\PipelineTracing. The path must be local to the Exchange server. Setting this parameter to the value $null disables pipeline tracing. However, setting this parameter to $null when the value of the PipelineTracingEnabled attribute is $true generates event log errors. The preferred method to disable pipeline tracing is to use the PipelineTracingEnabled parameter. @@ -704,7 +768,6 @@ Pipeline tracing captures the complete contents of email messages to the path sp Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -714,13 +777,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingSenderAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -730,6 +795,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Log files that are older than the specified value are automatically deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -744,7 +812,6 @@ This parameter is only meaningful when the MailboxDeliveryConnectorProtocolLoggi Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -754,6 +821,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -776,7 +846,6 @@ This parameter is only meaningful when the MailboxDeliveryConnectorProtocolLoggi Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -786,6 +855,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -808,7 +880,6 @@ This parameter is only meaningful when the MailboxDeliveryConnectorProtocolLoggi Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -818,6 +889,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\ProtocolLog\\SmtpReceive. The log files are automatically stored in the Delivery subdirectory. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for the mailbox delivery Receive connector. To disable protocol logging for this connector, use the value None for the MailboxDeliveryConnectorProtocolLoggingLevel parameter. @@ -826,7 +900,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -836,6 +909,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxAge + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 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. @@ -846,7 +922,6 @@ For example, to specify 5 days for this parameter, use 5.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -856,6 +931,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxDirectorySize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -874,7 +952,6 @@ The valid input range for this parameter is from 1 through 9223372036854775807 b Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -884,13 +961,15 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\Routing. Setting this parameter to $null disables routing table logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -900,6 +979,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. Log files that are older than the specified value are automatically deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -912,7 +994,6 @@ This parameter is only meaningful when the IntraOrgConnectorProtocolLoggingLevel Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -922,6 +1003,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -944,7 +1028,6 @@ This parameter is only meaningful when the IntraOrgConnectorProtocolLoggingLevel Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -954,6 +1037,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -976,7 +1062,6 @@ This parameter is only meaningful when the IntraOrgConnectorProtocolLoggingLevel Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -986,6 +1071,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogPath parameter specifies the location of the protocol log directory for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\ProtocolLog\\SmtpSend. Log files are automatically stored in the following subdirectories: - Submission: Protocol log files for the intra-organization Send connector in the Mailbox Transport Submission service. @@ -997,7 +1085,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1007,13 +1094,15 @@ 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/exchange/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md index 97910b18d9..9b9b096dd7 100644 --- a/exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilterpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MalwareFilterPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilterpolicy +schema: 2.0.0 +title: Set-MalwareFilterPolicy --- # Set-MalwareFilterPolicy @@ -102,6 +103,9 @@ The last two commands remove the seventh file type that's displayed in the list. ## 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 you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -112,7 +116,6 @@ The Identity parameter specifies the malware filter policy you want to modify. Y Type: MalwareFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -122,6 +125,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Action parameter specifies the action to take when malware is detected in a message. Valid values are: @@ -134,7 +140,6 @@ The Action parameter specifies the action to take when malware is detected in a Type: MalwareFilteringAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -144,13 +149,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -160,6 +167,9 @@ Accept wildcard characters: False ``` ### -BypassInboundMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are: @@ -171,7 +181,6 @@ The BypassInboundMessages parameter enables or disables malware filtering on inc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,6 +190,9 @@ Accept wildcard characters: False ``` ### -BypassOutboundMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are: @@ -192,7 +204,6 @@ The BypassOutboundMessages parameter enables or disables malware filtering on ou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -202,6 +213,9 @@ 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`. @@ -211,7 +225,6 @@ 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 @@ -221,6 +234,9 @@ Accept wildcard characters: False ``` ### -CustomAlertText + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CustomAlertText parameter specifies the custom text to use in the replacement attachment named Malware Alert Text.txt. If the value contains spaces, enclose the value in quotation marks ("). @@ -231,7 +247,6 @@ This parameter is meaningful only when the value of the Action parameter is Dele Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,6 +256,9 @@ Accept wildcard characters: False ``` ### -CustomExternalBody + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -252,7 +270,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -262,6 +279,9 @@ Accept wildcard characters: False ``` ### -CustomExternalSubject + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomExternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -273,7 +293,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -283,6 +302,9 @@ Accept wildcard characters: False ``` ### -CustomFromAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomFromAddress parameter specifies the custom From address to use in notification messages for malware detections in messages from internal or external senders. This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -296,7 +318,6 @@ This parameter is meaningful only when the value of the CustomNotifications para Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -306,6 +327,9 @@ Accept wildcard characters: False ``` ### -CustomFromName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomFromName parameter specifies the custom From name to use in notification messages for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -319,7 +343,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -329,6 +352,9 @@ Accept wildcard characters: False ``` ### -CustomInternalBody + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomInternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -340,7 +366,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -350,6 +375,9 @@ Accept wildcard characters: False ``` ### -CustomInternalSubject + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomInternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the CustomNotifications parameter is $true, and the value of at least one of the following parameters is also $true: @@ -361,7 +389,6 @@ This parameter is meaningful only when the value of the CustomNotifications para 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 @@ -371,6 +398,9 @@ Accept wildcard characters: False ``` ### -CustomNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CustomNotifications parameter enables or disables the customization of notification messages for malware detections. Valid values are: - $true: Replace the default values used in notification messages with the values of the CustomFromAddress, CustomFromName, CustomExternalSubject, CustomExternalBody, CustomInternalSubject and CustomInternalBody parameters. @@ -387,7 +417,6 @@ This parameter is meaningful only when the value of at least one of the followin 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 @@ -397,6 +426,9 @@ 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. @@ -405,7 +437,6 @@ 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 @@ -415,6 +446,9 @@ Accept wildcard characters: False ``` ### -EnableExternalSenderAdminNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter. @@ -426,7 +460,6 @@ The EnableExternalSenderAdminNotifications parameter enables or disables sending 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 @@ -436,6 +469,9 @@ Accept wildcard characters: False ``` ### -EnableExternalSenderNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are: @@ -447,7 +483,6 @@ The EnableExternalSenderNotifications parameter enables or disables sending noti Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -457,6 +492,9 @@ Accept wildcard characters: False ``` ### -EnableFileFilter + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are: @@ -472,7 +510,6 @@ You specify the action for detected files using the FileTypeAction parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -482,6 +519,9 @@ Accept wildcard characters: False ``` ### -EnableInternalSenderAdminNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are: - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter. @@ -493,7 +533,6 @@ The EnableInternalSenderAdminNotifications parameter enables or disables sending 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 @@ -503,6 +542,9 @@ Accept wildcard characters: False ``` ### -EnableInternalSenderNotifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are: @@ -514,7 +556,6 @@ The EnableInternalSenderNotifications parameter enables or disables sending noti Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -524,6 +565,9 @@ Accept wildcard characters: False ``` ### -ExternalSenderAdminAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ExternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from external senders. This parameter is meaningful only if the value of the EnableExternalSenderAdminNotifications parameter is $true. @@ -532,7 +576,6 @@ This parameter is meaningful only if the value of the EnableExternalSenderAdminN Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -542,6 +585,9 @@ Accept wildcard characters: False ``` ### -FileTypeAction + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are: @@ -555,7 +601,6 @@ This parameter is meaningful only when the value of the EnableFileFilter paramet Type: FileTypeFilteringAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -565,6 +610,9 @@ Accept wildcard characters: False ``` ### -FileTypes + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The FileTypes parameter specifies the file types that are automatically blocked by the common attachments filter, regardless of content. The default values are: @@ -583,7 +631,6 @@ To add or remove file types without affecting the other file type entries, see t Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -593,6 +640,9 @@ Accept wildcard characters: False ``` ### -InternalSenderAdminAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The InternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from internal senders. This parameter is meaningful only if the value of the EnableInternalSenderAdminNotifications parameter is $true. @@ -601,7 +651,6 @@ This parameter is meaningful only if the value of the EnableInternalSenderAdminN Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -611,13 +660,15 @@ Accept wildcard characters: False ``` ### -IsPolicyOverrideApplied + +> 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 @@ -627,6 +678,9 @@ Accept wildcard characters: False ``` ### -MakeDefault + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MakeDefault switch makes this malware filter policy the default policy. You don't need to specify a value with this switch. The default malware filter policy has no recipient filters (is applied to everyone) and has the Priority value Lowest. @@ -635,7 +689,6 @@ The default malware filter policy has no recipient filters (is applied to everyo 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 @@ -645,6 +698,9 @@ Accept wildcard characters: False ``` ### -QuarantineTag + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The QuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as malware. You can use any value that uniquely identifies the quarantine policy. For example: @@ -663,7 +719,6 @@ 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 @@ -673,13 +728,15 @@ 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 @@ -689,6 +746,9 @@ Accept wildcard characters: False ``` ### -ZapEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are: @@ -700,7 +760,6 @@ The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malw Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-MalwareFilterRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md index 9589a6fc72..0d2bb814bc 100644 --- a/exchange/exchange-ps/exchange/Set-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilterrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MalwareFilterRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilterrule +schema: 2.0.0 +title: Set-MalwareFilterRule --- # Set-MalwareFilterRule @@ -56,13 +57,15 @@ This example adds an exception to the malware 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 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: True Position: 1 @@ -72,13 +75,15 @@ Accept wildcard characters: False ``` ### -Comments + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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,7 +125,6 @@ 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,13 +134,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -141,6 +152,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -156,7 +170,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -166,6 +179,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -183,7 +199,6 @@ If you remove the group after you create the rule, no exception is made for mess Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -193,6 +208,9 @@ Accept wildcard characters: False ``` ### -MalwareFilterPolicy + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule. You can use any value that uniquely identifies the policy. For example: @@ -207,7 +225,6 @@ You can't specify the default malware filter policy, and you can't specify a pol Type: MalwareFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -217,13 +234,15 @@ Accept wildcard characters: False ``` ### -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 malware filter rule. ```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 @@ -233,6 +252,9 @@ 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: @@ -247,7 +269,6 @@ 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 @@ -257,13 +278,15 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -273,6 +296,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -288,7 +314,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -298,6 +323,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, 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 @@ -315,7 +343,6 @@ If you remove the group after you create the rule, no action is taken on message Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -325,13 +352,15 @@ 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/exchange/Set-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md index b524b8fc9c..809cb98cd1 100644 --- a/exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilteringserver applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MalwareFilteringServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-malwarefilteringserver +schema: 2.0.0 +title: Set-MalwareFilteringServer --- # Set-MalwareFilteringServer @@ -57,6 +58,9 @@ This example sets the following Malware agent settings on the Mailbox server nam ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server where you want to configure the anti-malware settings. You can use any value that uniquely identifies the server. For example: - Name @@ -68,7 +72,6 @@ The Identity parameter specifies the server where you want to configure the anti Type: MalwareFilteringServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -78,13 +81,15 @@ Accept wildcard characters: False ``` ### -BypassFiltering + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassFiltering parameter temporarily bypasses malware filtering without disabling the Malware agent on the server. The Malware agent is still active, and the agent is still called for every message, but no malware filtering is actually performed. This allows you to temporarily disable and then enable malware filtering on the server without disrupting mail flow by restarting the Microsoft Exchange Transport service. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -94,6 +99,9 @@ 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`. @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ Accept wildcard characters: False ``` ### -DeferAttempts + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeferAttempts parameter specifies the maximum number of times to defer a message that can't be scanned by the Malware agent. Valid input for this parameter is an integer between 1 and 5. The default value is 3. After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt will occur in 1 hour, the next retry attempt will occur 2 hours after that, the next retry attempt will occur 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender. @@ -121,7 +131,6 @@ After the maximum number of deferrals is reached, the action taken by the Malwar Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,6 +140,9 @@ Accept wildcard characters: False ``` ### -DeferWaitTime + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeferWaitTime parameter specifies the time period in minutes to increase the interval to resubmit messages for malware filtering in an effort to reduce the workload on the server. For example, the first retry after the original failed scan occurs after the interval specified by the DeferWaitTime parameter. The second retry after the first retry occurs after two times the value of the DeferWaitTime parameter. The third retry after the second retry occurs after three times the value of the DeferWaitTime parameter and so on. The maximum number of retries is controlled by the DeferAttempts parameter. @@ -141,7 +153,6 @@ Valid input for this parameter is an integer between 0 and 15. The default value Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -151,6 +162,9 @@ 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. @@ -159,7 +173,6 @@ 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 @@ -169,6 +182,9 @@ Accept wildcard characters: False ``` ### -ForceRescan + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceRescan parameter specifies that messages should be scanned by the malware agent, even if the message was already scanned by cloud-based protection. Valid values are: - $true: Messages from cloud-based organizations are scanned by the malware agent. @@ -178,7 +194,6 @@ The ForceRescan parameter specifies that messages should be scanned by the malwa Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,13 +203,15 @@ Accept wildcard characters: False ``` ### -MinimumSuccessfulEngineScans + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -204,13 +221,15 @@ Accept wildcard characters: False ``` ### -PrimaryUpdatePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PrimaryUpdatePath parameter specifies where to download malware scanning engine updates. The default value is `http://forefrontdl.microsoft.com/server/scanengineupdate`. The location specified by the PrimaryUpdatePath parameter is always tried first. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -220,13 +239,15 @@ Accept wildcard characters: False ``` ### -ScanErrorAction + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ScanErrorAction parameter specifies the action to take when a message can't be scanned by the malware filter. Valid values for this parameter are Block or Allow. The default value is Block. ```yaml Type: MalwareScanErrorAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,13 +257,15 @@ Accept wildcard characters: False ``` ### -ScanTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ScanTimeout parameter specifies the timeout interval in seconds for messages that can't be scanned by the malware filter. Valid input for this parameter is an integer between 10 and 900. The default value is 300 (5 minutes). ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -252,6 +275,9 @@ Accept wildcard characters: False ``` ### -SecondaryUpdatePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SecondaryUpdatePath parameter specifies an alternate download location for malware scanning engine updates. The default values is blank ($null). This means no alternate download location is specified. The alternate download location is used when the location specified by the PrimaryUpdatePath parameter is unavailable for the time period specified by the UpdateTimeout parameter. On the next malware scanning engine update, the location specified by the PrimaryUpdate path parameter is tried first. @@ -260,7 +286,6 @@ The alternate download location is used when the location specified by the Prima Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -270,13 +295,15 @@ Accept wildcard characters: False ``` ### -UpdateFrequency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UpdateFrequency parameter specifies the frequency interval in minutes to check for malware scanning engine updates. Valid input for this parameter is an integer between 1 and 38880 (27 days). The default value is 60 (one hour). The locations to check for updates are specified by the PrimaryUpdatePath and SecondaryUpdatePath parameters. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -286,6 +313,9 @@ Accept wildcard characters: False ``` ### -UpdateTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UpdateTimeout parameter specifies the timeout interval in seconds to use when checking for malware scanning engine updates. Valid input for this parameter is an integer between 60 and 300. The default value is 150 seconds (2.5 minutes). If the location specified by the PrimaryUpdatePath parameter is unavailable for the time period specified by the UpdateTimeout parameter value, the location specified by the SecondaryUpdatePath parameter is used. @@ -294,7 +324,6 @@ If the location specified by the PrimaryUpdatePath parameter is unavailable for Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -304,13 +333,15 @@ 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/exchange/Set-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-ManagedContentSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md index 9606389193..96f526d75c 100644 --- a/exchange/exchange-ps/exchange/Set-ManagedContentSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managedcontentsettings applicable: Exchange Server 2010 -title: Set-ManagedContentSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedcontentsettings +schema: 2.0.0 +title: Set-ManagedContentSettings --- # Set-ManagedContentSettings @@ -57,13 +58,15 @@ This example specifies the address of the journaling recipient that's the destin ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed content settings. ```yaml Type: ELCContentSettingsIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -73,6 +76,9 @@ Accept wildcard characters: False ``` ### -AddressForJournaling + +> Applicable: Exchange Server 2010 + The AddressForJournaling parameter specifies the journaling recipient where journaled messages are sent. You can use any value that uniquely identifies the recipient. For example: - Name @@ -86,7 +92,6 @@ The AddressForJournaling parameter specifies the journaling recipient where jour Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -96,6 +101,9 @@ Accept wildcard characters: False ``` ### -AgeLimitForRetention + +> Applicable: Exchange Server 2010 + The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date that the item was delivered or the date that an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. @@ -104,7 +112,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -114,6 +121,9 @@ 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`. @@ -123,7 +133,6 @@ 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 @@ -133,13 +142,15 @@ 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 @@ -149,13 +160,15 @@ Accept wildcard characters: False ``` ### -JournalingEnabled + +> Applicable: Exchange Server 2010 + The JournalingEnabled parameter specifies that journaling is enabled when it's set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -165,13 +178,15 @@ Accept wildcard characters: False ``` ### -LabelForJournaling + +> Applicable: Exchange Server 2010 + The LabelForJournaling parameter specifies a label that's attached to an item. This label is used by the destination store to determine the content of the item and enforce the appropriate policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -181,6 +196,9 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling + +> Applicable: Exchange Server 2010 + The MessageFormatForJournaling parameter specifies the format in which an item should be journaled in. You can use the following values: - UseMsg Microsoft Outlook .MSG format @@ -190,7 +208,6 @@ The MessageFormatForJournaling parameter specifies the format in which an item s Type: JournalingFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -200,13 +217,15 @@ Accept wildcard characters: False ``` ### -MoveToDestinationFolder + +> Applicable: Exchange Server 2010 + The MoveToDestinationFolder parameter specifies the name of the destination folder for a retention action. ```yaml Type: ELCFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -216,13 +235,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies a unique name for the managed content settings. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -232,6 +253,9 @@ Accept wildcard characters: False ``` ### -RetentionAction + +> Applicable: Exchange Server 2010 + The RetentionAction parameter specifies one of the following actions to take when an item reaches its retention age limit, specified by the AgeLimitForRetention parameter. The following retention actions can be used: - Mark as past retention limit @@ -246,7 +270,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -256,13 +279,15 @@ Accept wildcard characters: False ``` ### -RetentionEnabled + +> Applicable: Exchange Server 2010 + The RetentionEnabled parameter specifies that retention is enabled when it's set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -272,6 +297,9 @@ Accept wildcard characters: False ``` ### -TriggerForRetention + +> Applicable: Exchange Server 2010 + The TriggerForRetention parameter specifies the date that's considered as the start date of the retention period. An item can reach its retention limit a specific number of days after the item was delivered or after it was moved into a specific folder. Valid values include: @@ -285,7 +313,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionDateType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -295,13 +322,15 @@ 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/exchange/Set-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-ManagedFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md index aef4960fcd..2a3d1446c8 100644 --- a/exchange/exchange-ps/exchange/Set-ManagedFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfolder applicable: Exchange Server 2010 -title: Set-ManagedFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfolder +schema: 2.0.0 +title: Set-ManagedFolder --- # Set-ManagedFolder @@ -55,13 +56,15 @@ This example sets the storage quota for the managed folder MyManagedFolder to 10 ## 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: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -71,13 +74,15 @@ Accept wildcard characters: False ``` ### -BaseFolderOnly + +> Applicable: Exchange Server 2010 + The BaseFolderOnly parameter specifies whether the managed content settings should be applied only to the managed folder or to the folder and all its subfolders. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -87,13 +92,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010 + The Comment parameter specifies the default administrator comment to be displayed with the folder in Microsoft Office Outlook 2007. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -103,6 +110,9 @@ 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`. @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ 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 @@ -138,13 +149,15 @@ Accept wildcard characters: False ``` ### -FolderName + +> Applicable: Exchange Server 2010 + The FolderName parameter specifies the name of the folder object as it appears in users' mailboxes. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -154,13 +167,15 @@ Accept wildcard characters: False ``` ### -LocalizedComment + +> Applicable: Exchange Server 2010 + The LocalizedComment parameter specifies localized administrator comments and their languages. Localized comments are displayed instead of the default comment when the language setting of any client that displays comments matches a language specified for this parameter value. Comments must be in the form ISOLanguageCode:Comment, for example, -LocalizedComment EN-US:"This is a localized comment in U.S. English." ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -170,13 +185,15 @@ Accept wildcard characters: False ``` ### -LocalizedFolderName + +> Applicable: Exchange Server 2010 + The LocalizedFolderName parameter specifies localized folder names and their languages. Localized folder names are displayed instead of the default folder name when the language setting of Outlook 2007 matches a language specified for this parameter value. Comments must be in the form ISOLanguageCode:Comment, for example, -LocalizedFolderName EN-US:"This is a localized folder name in U.S. English." ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -186,13 +203,15 @@ Accept wildcard characters: False ``` ### -MustDisplayCommentEnabled + +> Applicable: Exchange Server 2010 + The MustDisplayCommentEnabled parameter specifies whether to set a flag that's used by any client that displays comments and accepts this setting. If this parameter is set to $true, a flag is set that prevents users from minimizing a folder comment, which is visible in Outlook 2007 only. If the parameter isn't present or is set to $false, users can minimize the comment. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -202,13 +221,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies a unique name for the content settings. The Name parameter doesn't appear in users' mailboxes. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -218,13 +239,15 @@ Accept wildcard characters: False ``` ### -StorageQuota + +> Applicable: Exchange Server 2010 + The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -234,13 +257,15 @@ 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/exchange/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md index 4e82b118b4..16870daaf5 100644 --- a/exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfoldermailboxpolicy applicable: Exchange Server 2010 -title: Set-ManagedFolderMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managedfoldermailboxpolicy +schema: 2.0.0 +title: Set-ManagedFolderMailboxPolicy --- # Set-ManagedFolderMailboxPolicy @@ -54,13 +55,15 @@ This example links the managed custom folders Custom Folder 1 and Custom Folder ## 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: True Position: 1 @@ -70,6 +73,9 @@ 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`. @@ -79,7 +85,6 @@ 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 @@ -89,13 +94,15 @@ 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,13 +112,15 @@ Accept wildcard characters: False ``` ### -ManagedFolderLinks + +> Applicable: Exchange Server 2010 + The ManagedFolderLinks parameter specifies managed folders to which the managed folder mailbox policy is to be linked. The managed folders that you link to a policy appear in all mailboxes to which the policy is applied. ```yaml Type: ELCFolderIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -121,13 +130,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies a unique name for the policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -137,13 +148,15 @@ 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/exchange/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md index 44d3d2ad77..b9ece947fa 100644 --- a/exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managementroleassignment applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-ManagementRoleAssignment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managementroleassignment +schema: 2.0.0 +title: Set-ManagementRoleAssignment --- # Set-ManagementRoleAssignment @@ -140,13 +141,15 @@ This example restricts the Distribution Groups\_Cairns Admins role assignment us ## 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 role assignment to modify. If the name of the management role contains spaces, enclose it in quotation marks ("). ```yaml Type: RoleAssignmentIdParameter 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 @@ -156,6 +159,9 @@ 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 specifies the administrative unit to scope the role assignment to. @@ -168,7 +174,6 @@ You can't use this parameter with any of the other scope parameters. Type: AdministrativeUnitIdParameter Parameter Sets: RecipientAdministrativeUnitScope Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -178,6 +183,9 @@ Accept wildcard characters: False ``` ### -RecipientGroupScope + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RecipientGroupScope parameter specifies a group to consider for scoping the role assignment. Individual members of the specified group (not nested groups) are considered as in scope for the assignment. You can use any value that uniquely identifies the group: Name, DistinguishedName, GUID, or DisplayName. @@ -186,7 +194,6 @@ The RecipientGroupScope parameter specifies a group to consider for scoping the Type: GroupIdParameter Parameter Sets: RecipientGroupScope Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -196,6 +203,9 @@ 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`. @@ -205,7 +215,6 @@ 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 @@ -215,6 +224,9 @@ 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 specifies the existing configuration management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks ("). @@ -227,7 +239,6 @@ To remove a scope, specify a value of $null. Type: ManagementScopeIdParameter Parameter Sets: RelativeRecipientWriteScope, CustomRecipientWriteScope, RecipientOrganizationalUnitScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -237,6 +248,9 @@ 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 specifies the existing recipient-based management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks ("). If you use the CustomRecipientWriteScope parameter, you can't use the RecipientOrganizationalUnitScope, RecipientRelativeWriteScope, or ExclusiveRecipientWriteScope parameters, and any configured OU or predefined scope on the role assignment is overwritten. @@ -247,7 +261,6 @@ To remove a scope, specify a value of $null. Type: ManagementScopeIdParameter Parameter Sets: CustomRecipientWriteScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -257,6 +270,9 @@ Accept wildcard characters: False ``` ### -CustomResourceScope + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The CustomResourceScope parameter specifies the custom management scope to associate with this management role assignment. You can use any value that uniquely identifies the management scope. For example: @@ -273,7 +289,6 @@ You use this parameter with the App parameter to assign permissions to service p Type: ManagementScopeIdParameter Parameter Sets: App Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -283,6 +298,9 @@ 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. @@ -291,7 +309,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: RelativeRecipientWriteScope, CustomRecipientWriteScope, RecipientOrganizationalUnitScope, ExclusiveScope, RecipientAdministrativeUnitScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -301,13 +318,15 @@ 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 the management role assignment is enabled or disabled. 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 @@ -317,6 +336,9 @@ 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 specifies the existing configuration exclusive management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks ("). @@ -329,7 +351,6 @@ To remove a scope, specify a value of $null. Type: ManagementScopeIdParameter Parameter Sets: ExclusiveScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -339,6 +360,9 @@ 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 specifies the existing recipient-based exclusive management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks ("). If you use the ExclusiveRecipientWriteScope parameter, you can't use the CustomRecipientWriteScope, RecipientOrganizationalUnitScope, or RecipientRelativeWriteScope parameters and any configured OU or predefined scope on the role assignment is overwritten. @@ -349,7 +373,6 @@ To remove a scope, specify a value of $null. Type: ManagementScopeIdParameter Parameter Sets: ExclusiveScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -359,6 +382,9 @@ 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. @@ -369,7 +395,6 @@ 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 @@ -379,6 +404,9 @@ 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 specifies the OU to scope the new role assignment to. If the OU name contains spaces, enclose the domain and OU in quotation marks ("). If you use the RecipientOrganizationalUnitScope parameter, you can't use the CustomRecipientWriteScope, ExclusiveRecipientWriteScope, or RecipientRelativeWriteScope parameters and any predefined scopes or custom scopes on the role assignment are overwritten. @@ -389,7 +417,6 @@ To specify an OU, use the syntax: domain/ou. To remove an OU, specify a value of Type: OrganizationalUnitIdParameter Parameter Sets: RecipientOrganizationalUnitScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -399,6 +426,9 @@ Accept wildcard characters: False ``` ### -RecipientRelativeWriteScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRelativeWriteScope parameter specifies the type of restriction to apply to a recipient scope. If you use the RecipientRelativeWriteScope parameter, you can't use the CustomRecipientWriteScope, ExclusiveRecipientWriteScope, or RecipientOrganizationalUnitScope parameters. @@ -411,7 +441,6 @@ Even though the NotApplicable, OU, MyDirectReports, CustomRecipientScope, MyExec Type: RecipientWriteScopeType Parameter Sets: RelativeRecipientWriteScope Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -421,13 +450,15 @@ 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/exchange/Set-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md index ee811f9b5f..50cd8123bb 100644 --- a/exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managementroleentry applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-ManagementRoleEntry -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managementroleentry +schema: 2.0.0 +title: Set-ManagementRoleEntry --- # Set-ManagementRoleEntry @@ -73,6 +74,9 @@ In on-premises Exchange, this example adds the Location parameter to the Mailbox ## 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 modify. 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). @@ -83,7 +87,6 @@ If the role entry name contains spaces, enclose it 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 @@ -93,6 +96,9 @@ Accept wildcard characters: False ``` ### -AddParameter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AddParameter switch specifies that you're adding parameters to the specified role entry. You don't need to specify a value with this switch. Use the Parameters parameter to specify the parameters to add. @@ -103,7 +109,6 @@ You can't use the AddParameter switch and the RemoveParameter switch together 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 @@ -113,6 +118,9 @@ 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`. @@ -122,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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,7 +150,6 @@ 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,6 +159,9 @@ 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. @@ -160,7 +172,6 @@ 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 @@ -170,6 +181,9 @@ 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 added to or removed from the role entry. The Parameters parameter has the following modes: @@ -184,7 +198,6 @@ You can specify multiple parameters, separated with commas. 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 @@ -194,6 +207,9 @@ Accept wildcard characters: False ``` ### -RemoveParameter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RemoveParameter switch specifies that you're removing parameters to the specified role entry. You don't need to specify a value with this switch. Use the Parameters parameter to specify the parameters to remove. @@ -204,7 +220,6 @@ You can't use the AddParameter switch and the RemoveParameter switch together 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 @@ -214,6 +229,9 @@ 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). @@ -226,7 +244,6 @@ Unscoped top-level management roles can only contain custom scripts or non-Excha Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,13 +253,15 @@ 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/exchange/Set-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ManagementScope.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md index 7d84c230ae..30541e78d8 100644 --- a/exchange/exchange-ps/exchange/Set-ManagementScope.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-managementscope applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-ManagementScope -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-managementscope +schema: 2.0.0 +title: Set-ManagementScope --- # Set-ManagementScope @@ -88,13 +89,15 @@ This example changes the Active Directory site used in the server restriction fi ## 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 modify. If the 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: True Position: 1 @@ -104,6 +107,9 @@ Accept wildcard characters: False ``` ### -DatabaseRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DatabaseRestrictionFilter parameter uses OPATH filter syntax to specify the databases that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. @@ -123,7 +129,6 @@ You can't use this parameter with the RecipientRestrictionFilter, ServerRestrict Type: String Parameter Sets: DatabaseFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -133,6 +138,9 @@ Accept wildcard characters: False ``` ### -ServerRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ServerRestrictionFilter parameter uses OPATH filter syntax to specify the servers that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`. @@ -152,7 +160,6 @@ You can't use this parameter wit the RecipientRestrictionFilter, RecipientRoot, Type: String Parameter Sets: ServerFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -162,6 +169,9 @@ 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`. @@ -171,7 +181,6 @@ 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 @@ -181,6 +190,9 @@ 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. @@ -189,7 +201,6 @@ 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 @@ -199,6 +210,9 @@ 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. @@ -209,7 +223,6 @@ 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 @@ -219,13 +232,15 @@ Accept wildcard characters: False ``` ### -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 management scope. The management scope name can be a maximum of 64 characters. If the name contains spaces, enclose it 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 @@ -235,6 +250,9 @@ Accept wildcard characters: False ``` ### -RecipientRestrictionFilter + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"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. @@ -252,7 +270,6 @@ You can't use this parameter with the DatabaseRestrictionFilter, DatabaseList, S Type: String Parameter Sets: RecipientFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -262,6 +279,9 @@ Accept wildcard characters: False ``` ### -RecipientRoot + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an 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 @@ -275,7 +295,6 @@ You can't use this parameter with the ServerRestrictionFilter or DatabaseRestric Type: OrganizationalUnitIdParameter Parameter Sets: RecipientFilter Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -285,13 +304,15 @@ 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/exchange/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md index ec322afd70..e132263692 100644 --- a/exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mapivirtualdirectory applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-MapiVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mapivirtualdirectory +schema: 2.0.0 +title: Set-MapiVirtualDirectory --- # Set-MapiVirtualDirectory @@ -53,6 +54,9 @@ This example makes the following configuration changes to the MAPI virtual direc ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the MAPI virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -65,7 +69,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -75,6 +78,9 @@ Accept wildcard characters: False ``` ### -ApplyDefaults + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ApplyDefaults switch specifies whether to apply the correct defaults to the related internal IIS application settings. Typically, this switch is used only by Exchange Setup during the installation of Exchange Cumulative Updates or Service Packs and you shouldn't need to use it. This switch doesn't affect the values you configure by using the IISAuthenticationMethods, InternalUrl or ExternalUrl parameters. @@ -83,7 +89,6 @@ This switch doesn't affect the values you configure by using the IISAuthenticati Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -93,6 +98,9 @@ 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`. @@ -102,7 +110,6 @@ 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 @@ -112,13 +119,15 @@ 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,6 +137,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags + +> Applicable: 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. @@ -140,7 +152,6 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList + +> Applicable: 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. @@ -159,7 +173,6 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -169,6 +182,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking + +> Applicable: 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. @@ -181,7 +197,6 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,6 +206,9 @@ Accept wildcard characters: False ``` ### -ExternalUrl + +> Applicable: 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 enforces the Secure Sockets Layer (SSL) protocol and uses the default SSL port. Valid input for this parameter uses the syntax `https:///mapi`(for example, `https://external.contoso.com/mapi`). @@ -201,7 +219,6 @@ When you use the InternalUrl or ExternalUrl parameters, you need to specify one Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -211,6 +228,9 @@ Accept wildcard characters: False ``` ### -IISAuthenticationMethods + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values are: - Basic @@ -228,7 +248,6 @@ For more information about the different authentication methods, see [Understand Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,6 +257,9 @@ Accept wildcard characters: False ``` ### -InternalUrl + +> Applicable: 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 enforces the Secure Sockets Layer (SSL) protocol and uses the default SSL port. Valid input for this parameter uses the syntax `https:///mapi` (for example, `https://internal.contoso.com/mapi`). @@ -248,7 +270,6 @@ When you use the InternalUrl or ExternalUrl parameters, you need to specify one Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -258,13 +279,15 @@ 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/exchange/Set-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-MessageClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md index 4c48abce78..9adc298201 100644 --- a/exchange/exchange-ps/exchange/Set-MessageClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-messageclassification applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MessageClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-messageclassification +schema: 2.0.0 +title: Set-MessageClassification --- # Set-MessageClassification @@ -54,6 +55,9 @@ This example makes the following configuration changes to the message classifica ## 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 message classification that you want to modify. You can use any value that uniquely identifies the message classification. For example: - Name @@ -64,7 +68,6 @@ The Identity parameter specifies the message classification that you want to mod Type: MessageClassificationIdParameter 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 @@ -74,6 +77,9 @@ Accept wildcard characters: False ``` ### -ClassificationID + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ClassificationID parameter specifies the classification ID (GUID) of an existing message classification that you want to import and use in your Exchange organization. Use this parameter if you're configuring message classifications that span two Exchange forests in the same organization. To find the ClassificationID value of the message classification, replace `` with the name of the message classification and run the following command: `Get-MessageClassification -Identity ""`. @@ -82,7 +88,6 @@ To find the ClassificationID value of the message classification, replace ` 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,7 +109,6 @@ 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 @@ -111,6 +118,9 @@ 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 title of the message classification that's displayed in Outlook and selected by users. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks ("). The message classification XML file must be present on the sender's computer for the display name to be displayed. @@ -119,7 +129,6 @@ The message classification XML file must be present on the sender's computer for 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 @@ -129,6 +138,9 @@ Accept wildcard characters: False ``` ### -DisplayPrecedence + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are: - Highest @@ -147,7 +159,6 @@ Although Outlook only lets a user specify a single classification for a message, Type: ClassificationDisplayPrecedenceLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -157,6 +168,9 @@ 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. @@ -167,7 +181,6 @@ 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 @@ -177,13 +190,15 @@ Accept wildcard characters: False ``` ### -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 message classification. 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: False Position: Named @@ -193,6 +208,9 @@ Accept wildcard characters: False ``` ### -PermissionMenuVisible + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are: - $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value. @@ -202,7 +220,6 @@ The PermissionMenuVisible parameter specifies whether the values that you entere 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 @@ -212,13 +229,15 @@ Accept wildcard characters: False ``` ### -RecipientDescription + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RecipientDescription parameter specifies the detailed text that's shown to Outlook recipient when they receive a message that has the message classification applied. The maximum length is 1024 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: False Position: Named @@ -228,6 +247,9 @@ Accept wildcard characters: False ``` ### -RetainClassificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetainClassificationEnabled parameter specifies whether the message classification should persist with the message if the message is forwarded or replied to. The default value is $true. @@ -236,7 +258,6 @@ The default value is $true. 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 @@ -246,13 +267,15 @@ Accept wildcard characters: False ``` ### -SenderDescription + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SenderDescription parameter specifies the detailed text that's shown to Outlook senders when they select a message classification to apply to a message before they send the message. The maximum length is 1024 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: False Position: Named @@ -262,13 +285,15 @@ 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/exchange/Set-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md index 17981b8c20..9644ba5296 100644 --- a/exchange/exchange-ps/exchange/Set-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationbatch applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MigrationBatch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationbatch +schema: 2.0.0 +title: Set-MigrationBatch --- # Set-MigrationBatch @@ -75,6 +76,9 @@ This example updates MigrationBatch01 by approving all of the skipped items for ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the migration batch that you want to modify. You can use any value that uniquely identifies the migration batch. For example: - Name (the Identity property value) @@ -84,7 +88,6 @@ The Identity parameter specifies the migration batch that you want to modify. Yo Type: MigrationBatchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -AddUsers + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AddUsers Description }} @@ -102,7 +108,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -112,6 +117,9 @@ Accept wildcard characters: False ``` ### -AllowIncrementalSyncs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are: @@ -123,7 +131,6 @@ The AllowIncrementalSyncs parameter specifies whether to enable or disable incre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -133,6 +140,9 @@ Accept wildcard characters: False ``` ### -AllowUnknownColumnsInCsv + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are: - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration. @@ -142,7 +152,6 @@ The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -152,6 +161,9 @@ Accept wildcard characters: False ``` ### -ApproveSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. @@ -164,7 +176,6 @@ For more information about maximum message size values, see the following topic Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -174,6 +185,9 @@ Accept wildcard characters: False ``` ### -AutoRetryCount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AutoRetryCount parameter specifies the number of attempts to restart the migration batch to migrate mailboxes that encountered errors. @@ -182,7 +196,6 @@ The AutoRetryCount parameter specifies the number of attempts to restart the mig Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -192,6 +205,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. @@ -202,7 +218,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -212,6 +227,9 @@ Accept wildcard characters: False ``` ### -CompleteAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter. @@ -227,7 +245,6 @@ In Exchange Online PowerShell, if you specify a date/time value without a time z Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -237,6 +254,9 @@ 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`. @@ -246,7 +266,6 @@ 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 @@ -256,6 +275,9 @@ Accept wildcard characters: False ``` ### -CSVData + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CSVData parameter specifies the CSV file that contains information about the user mailboxes to be moved or migrated. The required attributes in the header row of the CSV file vary depending on the type of migration. 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`). @@ -266,7 +288,6 @@ 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 @@ -276,6 +297,9 @@ 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. @@ -284,7 +308,6 @@ 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 @@ -294,6 +317,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -309,7 +335,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -319,6 +344,9 @@ Accept wildcard characters: False ``` ### -MoveOptions + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MoveOptions parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. Don't use this parameter with the SkipMoving parameter. @@ -327,7 +355,6 @@ Don't use this parameter with the SkipMoving parameter. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -337,6 +364,9 @@ Accept wildcard characters: False ``` ### -NotificationEmails + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NotificationEmails parameter specifies one or more email addresses that migration status reports are sent to. If you don't use this parameter, the status report isn't sent. @@ -347,7 +377,6 @@ To enter multiple values and overwrite any existing entries, use the following s Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -357,6 +386,9 @@ 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. @@ -365,7 +397,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -375,6 +406,9 @@ Accept wildcard characters: False ``` ### -ReportInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails. By default, emailed reports are sent every 24 hours for a batch. Setting this value to 0 indicates that reports should never be sent for this batch. @@ -385,7 +419,6 @@ This parameter should only be used in the cloud-based service. Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -395,13 +428,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipMerging parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -411,6 +446,9 @@ Accept wildcard characters: False ``` ### -SkipMoving + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -419,7 +457,6 @@ The SkipMoving parameter specifies the stages of the migration that you want to Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -429,13 +466,15 @@ Accept wildcard characters: False ``` ### -SkipReports + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipReports switch specifies that you want to skip automatic reporting for the migration. You don't need to specify a value with this switch. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -445,6 +484,9 @@ Accept wildcard characters: False ``` ### -SourcePublicFolderDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SourcePublicFolderDatabase parameter specifies the source public folder database that's used in a public folder migration. You can use any value that uniquely identifies the database. For example: @@ -457,7 +499,6 @@ The SourcePublicFolderDatabase parameter specifies the source public folder data Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -467,6 +508,9 @@ Accept wildcard characters: False ``` ### -StartAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for users within the batch won't start until the date/time you specify with this 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". @@ -480,7 +524,6 @@ In Exchange Online PowerShell, if you specify a date/time value without a time z Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -490,6 +533,9 @@ Accept wildcard characters: False ``` ### -SyncNow + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SyncNow switch starts an immediate sync for users that have already reached Synced status, but doesn't resume any Failed users. You don't need to specify a value with this switch. You can use this switch to speed up onboarding moves by using the switch just before the completion of the move. For IMAP migrations, you can use this switch after MX record switchover. @@ -498,7 +544,6 @@ You can use this switch to speed up onboarding moves by using the switch just be Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -508,6 +553,9 @@ Accept wildcard characters: False ``` ### -Update + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Update switch sets the Update flag on the migration batch. You don't need to specify a value with this switch. The Update flag triggers the Migration Service to reapply all of the settings from the endpoint, batch, and user to the migration process. @@ -516,7 +564,6 @@ The Update flag triggers the Migration Service to reapply all of the settings fr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -526,13 +573,15 @@ 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/exchange/Set-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-MigrationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md index 99bb6f912b..376eb44b8f 100644 --- a/exchange/exchange-ps/exchange/Set-MigrationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MigrationConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationconfig +schema: 2.0.0 +title: Set-MigrationConfig --- # Set-MigrationConfig @@ -54,6 +55,9 @@ This example sets the migration system to only allow 100 concurrent migrations. ## PARAMETERS ### -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`. @@ -63,7 +67,6 @@ 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 @@ -73,6 +76,9 @@ 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. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ Accept wildcard characters: False ``` ### -Features + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Features parameter specifies the set of features to enable for the migration system. Use one of the following values: @@ -104,7 +112,6 @@ The Features parameter specifies the set of features to enable for the migration Type: MigrationFeature Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -114,6 +121,9 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMigrations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxConcurrentMigrations parameter specifies the maximum number of active migrations that your organization can run at any specific time. @@ -122,7 +132,6 @@ The MaxConcurrentMigrations parameter specifies the maximum number of active mig Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,6 +141,9 @@ Accept wildcard characters: False ``` ### -MaxNumberOfBatches + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxNumberOfBatches parameter specifies the maximum number of batches that your organization can migrate at any time. @@ -140,7 +152,6 @@ The MaxNumberOfBatches parameter specifies the maximum number of batches that yo Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,6 +161,9 @@ 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,7 +172,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -168,13 +181,15 @@ 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/exchange/Set-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-MigrationEndpoint.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md index cade570874..d578ee8430 100644 --- a/exchange/exchange-ps/exchange/Set-MigrationEndpoint.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationendpoint applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MigrationEndpoint -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationendpoint +schema: 2.0.0 +title: Set-MigrationEndpoint --- # Set-MigrationEndpoint @@ -87,13 +88,15 @@ This example changes the MaxConcurrentMigrations setting to 10 on the Onboarding ## 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 configure. ```yaml Type: MigrationEndpointIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -103,6 +106,9 @@ Accept wildcard characters: False ``` ### -AcceptUntrustedCertificates + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AcceptUntrustedCertificates Description }} @@ -111,7 +117,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -121,6 +126,9 @@ Accept wildcard characters: False ``` ### -ApplicationId + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ApplicationId Description }} @@ -129,7 +137,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -139,6 +146,9 @@ Accept wildcard characters: False ``` ### -AppSecretKeyVaultUrl + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AppSecretKeyVaultUrl Description }} @@ -147,7 +157,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -157,6 +166,9 @@ Accept wildcard characters: False ``` ### -Authentication + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Authentication parameter specifies the authentication method used by the remote mail server. @@ -165,7 +177,6 @@ The Authentication parameter specifies the authentication method used by the rem Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -175,6 +186,9 @@ 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`. @@ -184,7 +198,6 @@ 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 @@ -194,6 +207,9 @@ Accept wildcard characters: False ``` ### -Credentials + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Credentials parameter specifies the username and password for connecting to the remote endpoint. Credentials should be used when creating either a staged or cutover Exchange endpoint or a RemoteMove endpoint. 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). @@ -202,7 +218,6 @@ 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, Exchange Online Required: False Position: Named @@ -212,6 +227,9 @@ 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. @@ -220,7 +238,6 @@ 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 @@ -230,6 +247,9 @@ Accept wildcard characters: False ``` ### -ExchangeServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeServer parameter specifies the on-premises source Exchange server for cutover and staged migrations. This parameter is applicable only to staged and cutover Exchange endpoints which don't use Autodiscovery. @@ -238,7 +258,6 @@ The ExchangeServer parameter specifies the on-premises source Exchange server fo Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -248,6 +267,9 @@ Accept wildcard characters: False ``` ### -MailboxPermission + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxPermission parameter specifies what permissions should be used to access the source mailbox during OutlookAnywhere onboarding (Staged Exchange Migration and Cutover Exchange Migration). This parameter is not for non-OutlookAnywhere migrations. @@ -261,7 +283,6 @@ The account specified must have the following permissions: Type: MigrationMailboxPermission Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -271,13 +292,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentIncrementalSyncs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxConcurrentIncrementalSyncs parameter specifies the maximum number of incremental syncs allowed for this endpoint at a specified time. This value must be less or equal to MaxConcurrentMigrations parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -287,13 +310,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMigrations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that will be migrated for this endpoint at a specified time. This parameter is applicable for all migration types. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -303,6 +328,9 @@ Accept wildcard characters: False ``` ### -NspiServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The NspiServer parameter specifies the FQDN of the remote Name Service Provider Interface (NSPI) server. This parameter is only applicable to staged and cutover Exchange endpoints that don't use Autodiscovery. @@ -311,7 +339,6 @@ The NspiServer parameter specifies the FQDN of the remote Name Service Provider Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -321,6 +348,9 @@ 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. @@ -329,7 +359,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -339,6 +368,9 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration, the Port parameter specifies the TCP port number used by the migration process to connect to the remote server. @@ -347,7 +379,6 @@ For an IMAP migration, the Port parameter specifies the TCP port number used by Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -357,6 +388,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabaseServerLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -365,7 +399,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -375,6 +408,9 @@ Accept wildcard characters: False ``` ### -RemoteServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteServer parameter specifies the remote server depending on the protocol type for moves: - Exchange server moves: The FQDN of an Exchange server that has the Client Access role installed, a Client Access server array, or a group of Client Access servers that are located behind a supported network load balancer. @@ -384,7 +420,6 @@ The RemoteServer parameter specifies the remote server depending on the protocol Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -394,6 +429,9 @@ Accept wildcard characters: False ``` ### -RpcProxyServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For a staged Exchange migration, the RpcProxyServer parameter specifies the FQDN of the RPC proxy server for the on-premises Exchange server. This parameter is only applicable to staged and cutover Exchange endpoints that don't use Autodiscovery @@ -402,7 +440,6 @@ For a staged Exchange migration, the RpcProxyServer parameter specifies the FQDN Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -412,6 +449,9 @@ Accept wildcard characters: False ``` ### -Security + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl. @@ -420,7 +460,6 @@ For an IMAP migration, the Security parameter specifies the encryption method us Type: IMAPSecurityMechanism Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -430,6 +469,9 @@ Accept wildcard characters: False ``` ### -ServiceAccountKeyFileData + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. @@ -440,7 +482,6 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -450,13 +491,15 @@ Accept wildcard characters: False ``` ### -SkipVerification + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SkipVerification switch skips verifying that the remote server is reachable when creating a migration endpoint. 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 @@ -466,6 +509,9 @@ Accept wildcard characters: False ``` ### -SourceMailboxLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Use the LegacyExchangeDN for the on-premises test mailbox as the value for this parameter. The cmdlet tries to access this mailbox using the credentials for the administrator account on the target server. @@ -474,7 +520,6 @@ The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Us Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -484,6 +529,9 @@ Accept wildcard characters: False ``` ### -TestMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The TestMailbox parameter specifies a mailbox on the target server. Use the primary SMTP address as the value for this parameter. The cmdlet tries to access this mailbox using the credentials for the administrator account on the target server. @@ -492,7 +540,6 @@ The TestMailbox parameter specifies a mailbox on the target server. Use the prim Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -502,13 +549,15 @@ 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/exchange/Set-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-MigrationUser.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md index 9a4d3dc9f8..eb848e9dca 100644 --- a/exchange/exchange-ps/exchange/Set-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationuser applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-MigrationUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-migrationuser +schema: 2.0.0 +title: Set-MigrationUser --- # Set-MigrationUser @@ -59,6 +60,9 @@ This example approves all of the skipped items encountered for the user laura@co ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the email address of the user that's being migrated. You can also identify the user by the GUID value in the MigrationUser property from the output of the Get-MigrationUser cmdlet. This identification method is useful if you accidentally submitted the same user in multiple batches. @@ -67,7 +71,6 @@ You can also identify the user by the GUID value in the MigrationUser property f Type: MigrationUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -77,6 +80,9 @@ Accept wildcard characters: False ``` ### -ApproveSkippedItems + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch. @@ -91,7 +97,6 @@ You don't need to specify a value with this switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -101,6 +106,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again. @@ -111,7 +119,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -121,6 +128,9 @@ Accept wildcard characters: False ``` ### -CompleteAfter + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user will start, but won't complete until the date/time you specify with this parameter. @@ -138,7 +148,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -148,6 +157,9 @@ 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`. @@ -157,7 +169,6 @@ 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 @@ -167,6 +178,9 @@ 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. @@ -175,7 +189,6 @@ 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 @@ -185,6 +198,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -200,7 +216,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -210,6 +225,9 @@ 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. @@ -218,7 +236,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -228,6 +245,9 @@ Accept wildcard characters: False ``` ### -StartAfter + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The StartAfter parameter specifies a delay before the data migration for the user is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter. @@ -245,7 +265,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -255,6 +274,9 @@ Accept wildcard characters: False ``` ### -SyncNow + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SyncNow switch specifies whether to trigger an incremental sync for the migrated user. You don't need to specify a value with this switch. An incremental sync copies any recent changes from the source mailbox to the target mailbox. You can perform an incremental sync before you complete the migration batch to reduce the time that's required for the completion. @@ -263,7 +285,6 @@ An incremental sync copies any recent changes from the source mailbox to the tar Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -273,13 +294,15 @@ 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/exchange/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md index 8b2c4058f0..87158f98ac 100644 --- a/exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-mobiledevicemailboxpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MobileDeviceMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-mobiledevicemailboxpolicy +schema: 2.0.0 +title: Set-MobileDeviceMailboxPolicy --- # Set-MobileDeviceMailboxPolicy @@ -118,6 +119,9 @@ This example sets several policy settings for the mobile device mailbox policy D ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mobile device mailbox policy. You can use any value that uniquely identifies the policy. For example: - Name @@ -130,7 +134,6 @@ The name of the built-in mobile device mailbox policy is Default. Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -140,6 +143,9 @@ 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. Valid input for this parameter is $true or $false. The default value is $true. @@ -148,7 +154,6 @@ The AllowApplePushNotifications parameter specifies whether push notifications a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -158,6 +163,9 @@ Accept wildcard characters: False ``` ### -AllowBluetooth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are: - Allow (this is the default value). @@ -172,7 +180,6 @@ The value Disable disables synchronization between Outlook for Android and the O Type: BluetoothType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -182,13 +189,15 @@ Accept wildcard characters: False ``` ### -AllowBrowser + +> Applicable: 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 device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't affect non-Microsoft browsers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -198,13 +207,15 @@ Accept wildcard characters: False ``` ### -AllowCamera + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowCamera parameter specifies whether the mobile device's camera is allowed. Valid input for this parameter is $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 Required: False Position: Named @@ -214,13 +225,15 @@ Accept wildcard characters: False ``` ### -AllowConsumerEmail + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowConsumerEmail parameter specifies whether the user can configure a personal email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access to email accounts using non-Microsoft mobile device email programs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -230,13 +243,15 @@ Accept wildcard characters: False ``` ### -AllowDesktopSync + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowDesktopSync parameter specifies whether the mobile device can synchronize with a desktop computer through a cable. Valid input for this parameter is $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 Required: False Position: Named @@ -246,13 +261,15 @@ Accept wildcard characters: False ``` ### -AllowExternalDeviceManagement + +> Applicable: 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 mobile device. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -262,6 +279,9 @@ Accept wildcard characters: False ``` ### -AllowGooglePushNotifications + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AllowGooglePushNotifications parameter controls whether the user can receive push notifications from Google for Outlook on the web for devices. Valid input for this parameter is $true or $false. The default value is $true. @@ -270,7 +290,6 @@ The AllowGooglePushNotifications parameter controls whether the user can receive Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -280,13 +299,15 @@ Accept wildcard characters: False ``` ### -AllowHTMLEmail + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowHTMLEmail parameter specifies whether HTML-formatted email is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -296,13 +317,15 @@ Accept wildcard characters: False ``` ### -AllowInternetSharing + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowInternetSharing parameter specifies whether the mobile device can be used as a modem to connect a computer to the Internet. This process is also known as tethering. Valid input for this parameter is $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 Required: False Position: Named @@ -312,13 +335,15 @@ Accept wildcard characters: False ``` ### -AllowIrDA + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -328,6 +353,9 @@ Accept wildcard characters: False ``` ### -AllowMicrosoftPushNotifications + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The AllowMicrosoftPushNotifications parameter specifies whether push notifications are enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. @@ -336,7 +364,6 @@ The AllowMicrosoftPushNotifications parameter specifies whether push notificatio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -346,13 +373,15 @@ Accept wildcard characters: False ``` ### -AllowMobileOTAUpdate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowMobileOTAUpdate parameter specifies whether the policy can be sent to the mobile device over a cellular data connection. Valid input for this parameter is $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 Required: False Position: Named @@ -362,6 +391,9 @@ Accept wildcard characters: False ``` ### -AllowNonProvisionableDevices + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowNonProvisionableDevices parameter specifies whether all mobile devices can synchronize with Exchange. Valid input for this parameter is $true or $false. The default value is $true. When set to $true, this parameter enables all mobile devices to synchronize with Exchange, regardless of whether the device can enforce all settings that are defined by the policy. This also includes mobile devices managed by a separate device management system. When set to $false, this parameter blocks mobile devices that aren't provisioned from synchronizing with Exchange. @@ -370,7 +402,6 @@ When set to $true, this parameter enables all mobile devices to synchronize with Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -380,13 +411,15 @@ Accept wildcard characters: False ``` ### -AllowPOPIMAPEmail + +> Applicable: 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 mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access by non-Microsoft email programs. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -396,13 +429,15 @@ Accept wildcard characters: False ``` ### -AllowRemoteDesktop + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowRemoteDesktop parameter specifies whether the mobile device can initiate a remote desktop connection. Valid input for this parameter is $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 Required: False Position: Named @@ -412,13 +447,15 @@ Accept wildcard characters: False ``` ### -AllowSimplePassword + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSimplePassword parameter specifies whether a simple password is allowed on the mobile device. A simple password is a password that has a specific pattern, such as 1111 or 1234. Valid input for this parameter is $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 Required: False Position: Named @@ -428,6 +465,9 @@ Accept wildcard characters: False ``` ### -AllowSMIMEEncryptionAlgorithmNegotiation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the mobile device can negotiate the encryption algorithm if a recipient's certificate doesn't support the specified encryption algorithm. Valid values for this parameter are: - AllowAnyAlgorithmNegotiation @@ -440,7 +480,6 @@ The default value is AllowAnyAlgorithmNegotiation. Type: SMIMEEncryptionAlgorithmNegotiationType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -450,13 +489,15 @@ Accept wildcard characters: False ``` ### -AllowSMIMESoftCerts + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -466,13 +507,15 @@ Accept wildcard characters: False ``` ### -AllowStorageCard + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowStorageCard parameter specifies whether the mobile device can access information stored on a storage card. Valid input for this parameter is $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 Required: False Position: Named @@ -482,13 +525,15 @@ Accept wildcard characters: False ``` ### -AllowTextMessaging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowTextMessaging parameter specifies whether text messaging is allowed from the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -498,13 +543,15 @@ Accept wildcard characters: False ``` ### -AllowUnsignedApplications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -514,13 +561,15 @@ Accept wildcard characters: False ``` ### -AllowUnsignedInstallationPackages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages can be executed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -530,13 +579,15 @@ Accept wildcard characters: False ``` ### -AllowWiFi + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowWiFi parameter specifies whether wireless Internet access is allowed on the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -546,13 +597,15 @@ Accept wildcard characters: False ``` ### -AlphanumericPasswordRequired + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AlphanumericPasswordRequired parameter specifies whether the password for the mobile device must be alphanumeric. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -562,13 +615,15 @@ Accept wildcard characters: False ``` ### -ApprovedApplicationList + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApprovedApplicationList parameter specifies a configured list of approved applications for the device. ```yaml Type: ApprovedApplicationCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -578,6 +633,9 @@ Accept wildcard characters: False ``` ### -AttachmentsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AttachmentsEnabled parameter specifies whether attachments can be downloaded on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. When set to $false, this parameter blocks the user from downloading attachments on the mobile device. @@ -586,7 +644,6 @@ When set to $false, this parameter blocks the user from downloading attachments Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -596,6 +653,9 @@ 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`. @@ -605,7 +665,6 @@ 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 @@ -615,6 +674,9 @@ Accept wildcard characters: False ``` ### -DeviceEncryptionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This setting is supported by Outlook for iOS and Android. The DeviceEncryptionEnabled parameter specifies whether encryption is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. @@ -625,7 +687,6 @@ When this parameter is set to $true, device encryption is enabled on the mobile Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -635,6 +696,9 @@ Accept wildcard characters: False ``` ### -DevicePolicyRefreshInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DevicePolicyRefreshInterval parameter specifies how often the policy is sent to the mobile device. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -645,7 +709,6 @@ The default value is Unlimited. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -655,6 +718,9 @@ 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. @@ -663,7 +729,6 @@ 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 @@ -673,13 +738,15 @@ Accept wildcard characters: False ``` ### -IrmEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mobile device. Valid input for this parameter is $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 Required: False Position: Named @@ -689,6 +756,9 @@ 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. Valid input for this parameter is $true or $false. The default value for the built-in mobile device mailbox policy named Default is $true. The default value for new mobile device mailbox policies that you create is $false. There can be only one default policy. If another policy is currently set as the default, and you set this parameter to $true, this policy becomes the default policy. The value of this parameter on the other policy is automatically changed to $false, and that policy is no longer the default policy. @@ -697,7 +767,6 @@ There can be only one default policy. If another policy is currently set as the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -707,6 +776,9 @@ Accept wildcard characters: False ``` ### -MaxAttachmentSize + +> Applicable: 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 device. Valid input for this parameter is a size value between 0 and 2147482624 bytes (approximately 2 GB), or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4096 or 4KB. @@ -721,7 +793,6 @@ The maximum value is 1024 bytes (one kilobyte) less than two gigabytes (2\*1024^ Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -731,6 +802,9 @@ Accept wildcard characters: False ``` ### -MaxCalendarAgeFilter + +> Applicable: 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 mobile device. Valid values for this parameter are: - All @@ -745,7 +819,6 @@ The default value is All. Type: CalendarAgeFilterType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -755,6 +828,9 @@ Accept wildcard characters: False ``` ### -MaxEmailAgeFilter + +> Applicable: 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 mobile device. Valid values for this parameter are: - All @@ -770,7 +846,6 @@ The default value is All. Type: EmailAgeFilterType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -780,6 +855,9 @@ Accept wildcard characters: False ``` ### -MaxEmailBodyTruncationSize + +> Applicable: 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 mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4KB or 4096. @@ -788,7 +866,6 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -798,6 +875,9 @@ Accept wildcard characters: False ``` ### -MaxEmailHTMLBodyTruncationSize + +> Applicable: 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 truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited. Unqualified values are treated as bytes. You can qualify the value with KB (kilobytes), MB (megabytes) or GB (gigabytes). For example, to set the limit to 4 kilobytes, enter the value 4KB or 4096. @@ -806,7 +886,6 @@ Unqualified values are treated as bytes. You can qualify the value with KB (kilo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -816,6 +895,9 @@ Accept wildcard characters: False ``` ### -MaxInactivityTimeLock + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are: - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour). @@ -825,7 +907,6 @@ The MaxInactivityTimeLock parameter specifies the length of time that the mobile Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -835,6 +916,9 @@ Accept wildcard characters: False ``` ### -MaxPasswordFailedAttempts + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxPasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the mobile device. You can enter any number from 4 through 16 or the value Unlimited. The default value is Unlimited. @@ -843,7 +927,6 @@ You can enter any number from 4 through 16 or the value Unlimited. The default v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -853,6 +936,9 @@ Accept wildcard characters: False ``` ### -MinPasswordComplexCharacters + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are: - Lower case letters. @@ -875,7 +961,6 @@ For Windows Phone 10 devices, the value specifies the following password complex Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -885,6 +970,9 @@ Accept wildcard characters: False ``` ### -MinPasswordLength + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: This setting is supported by Outlook for Android. The MinPasswordLength parameter specifies the minimum number of characters in the mobile device password. @@ -895,7 +983,6 @@ You can enter any number from 1 through 16 or the value $null. The default value Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -905,13 +992,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the friendly name of the mobile device mailbox policy. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -921,6 +1010,9 @@ Accept wildcard characters: False ``` ### -PasswordEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordEnabled parameter specifies whether a password is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. When set to $true, this parameter requires the user to set a password on the mobile device. @@ -929,7 +1021,6 @@ When set to $true, this parameter requires the user to set a password on the mob Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -939,6 +1030,9 @@ Accept wildcard characters: False ``` ### -PasswordExpiration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are: - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years). @@ -948,7 +1042,6 @@ The PasswordExpiration parameter specifies how long a password can be used on a Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -958,6 +1051,9 @@ Accept wildcard characters: False ``` ### -PasswordHistory + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordHistory parameter specifies the number of unique new passwords that need to be created on the mobile device before an old password can be reused. You can enter any number from 0 through 50. The default value is 0. @@ -966,7 +1062,6 @@ You can enter any number from 0 through 50. The default value is 0. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -976,6 +1071,9 @@ Accept wildcard characters: False ``` ### -PasswordRecoveryEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PasswordRecoveryEnabled parameter specifies whether the recovery password for the mobile device is stored in Exchange. Valid input for this parameter is $true or $false. The default value is $false. When set to $true, this parameter enables you to store the recovery password for the mobile device in Exchange. The recovery password can be viewed in Outlook on the web or the Exchange admin center. @@ -984,7 +1082,6 @@ When set to $true, this parameter enables you to store the recovery password for Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -994,13 +1091,15 @@ Accept wildcard characters: False ``` ### -RequireDeviceEncryption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireDeviceEncryption parameter specifies whether encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1010,13 +1109,15 @@ Accept wildcard characters: False ``` ### -RequireEncryptedSMIMEMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireEncryptedSMIMEMessages parameter specifies whether the mobile device must send encrypted S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1026,6 +1127,9 @@ Accept wildcard characters: False ``` ### -RequireEncryptionSMIMEAlgorithm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireEncryptionSMIMEAlgorithm parameter specifies the algorithm that's required to encrypt S/MIME messages on a mobile device. The valid values for this parameter are: - DES @@ -1040,7 +1144,6 @@ The default value is TripleDES. Type: EncryptionSMIMEAlgorithmType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1050,13 +1153,15 @@ Accept wildcard characters: False ``` ### -RequireManualSyncWhenRoaming + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireManualSyncWhenRoaming parameter specifies whether the mobile device must synchronize manually while roaming. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1066,6 +1171,9 @@ Accept wildcard characters: False ``` ### -RequireSignedSMIMEAlgorithm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireSignedSMIMEAlgorithm parameter specifies the algorithm that's used to sign S/MIME messages on the mobile device. Valid values for this parameter are SHA1 or MD5. The default value is SHA1. @@ -1074,7 +1182,6 @@ Valid values for this parameter are SHA1 or MD5. The default value is SHA1. Type: SignedSMIMEAlgorithmType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1084,13 +1191,15 @@ Accept wildcard characters: False ``` ### -RequireSignedSMIMEMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireSignedSMIMEMessages parameter specifies whether the mobile device must send signed S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1100,6 +1209,9 @@ Accept wildcard characters: False ``` ### -RequireStorageCardEncryption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequireStorageCardEncryption parameter specifies whether storage card encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false. Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter to $true. @@ -1108,7 +1220,6 @@ Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1118,13 +1229,15 @@ Accept wildcard characters: False ``` ### -UnapprovedInROMApplicationList + +> Applicable: 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 on the mobile device. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1134,13 +1247,15 @@ Accept wildcard characters: False ``` ### -UNCAccessEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1150,13 +1265,15 @@ 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 @@ -1166,13 +1283,15 @@ Accept wildcard characters: False ``` ### -WSSAccessEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory. ```yaml Type: Boolean 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/exchange/Set-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md index 1d1ecd41fb..e15aaac8ae 100644 --- a/exchange/exchange-ps/exchange/Set-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-moverequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-MoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-moverequest +schema: 2.0.0 +title: Set-MoveRequest --- # Set-MoveRequest @@ -77,6 +78,9 @@ This example changes the move request for Sruthi to approve all skipped items en ## 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 mailbox or mail user. You can use the following values: - GUID @@ -91,7 +95,6 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c Type: MoveRequestIdParameter 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 @@ -101,6 +104,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. In Exchange 2013 or later or Exchange Online, you need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -111,7 +117,6 @@ In Exchange 2010, you need to use this switch if you set the BadItemLimit parame 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 @@ -121,6 +126,9 @@ Accept wildcard characters: False ``` ### -ArchiveTargetDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ArchiveTargetDatabase parameter specifies the target mailbox database for the personal archive. You can use any value that uniquely identifies the database. For example: @@ -135,7 +143,6 @@ You can use this parameter to change the target database only if the move reques Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -145,6 +152,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -157,7 +167,6 @@ In Exchange 2010, if you set this value to 51 or higher, you also need to use th 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 @@ -167,13 +176,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BatchName parameter specifies a different name for a batch. ```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 @@ -183,6 +194,9 @@ Accept wildcard characters: False ``` ### -CompleteAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompleteAfter parameter specifies a delay before the request is completed. The request is started, but not completed until the date/time you specify with this 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". @@ -198,7 +212,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -208,13 +221,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -224,6 +239,9 @@ 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`. @@ -233,7 +251,6 @@ 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 @@ -243,6 +260,9 @@ 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. @@ -251,7 +271,6 @@ 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 @@ -261,13 +280,15 @@ Accept wildcard characters: False ``` ### -IgnoreRuleLimitErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013 + The IgnoreRuleLimitErrors parameter specifies that the command won't move the user's rules to the target server running Microsoft Exchange. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -277,6 +298,9 @@ Accept wildcard characters: False ``` ### -IncrementalSyncInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -287,7 +311,6 @@ Valid values are from 00:00:00 to 120.00:00:00 (120 days). The default value is Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -297,6 +320,9 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. @@ -305,7 +331,6 @@ The InternalFlags parameter specifies the optional steps in the request. This pa Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -315,6 +340,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -332,7 +360,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -342,6 +369,9 @@ Accept wildcard characters: False ``` ### -MoveOptions + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The MoveOptions parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. Don't use this parameter with the SkipMoving parameter. @@ -350,7 +380,6 @@ Don't use this parameter with the SkipMoving parameter. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -360,6 +389,9 @@ Accept wildcard characters: False ``` ### -PreventCompletion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreventCompletion parameter specifies whether to run the move request, but not allow it to complete. Valid values are: - $true: The move request is run, but is not allowed to complete. Instead of this value, we recommend using the CompleteAfter parameter. @@ -369,7 +401,6 @@ The PreventCompletion parameter specifies whether to run the move request, but n Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -379,6 +410,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: @@ -396,7 +430,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -406,6 +439,9 @@ 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. This parameter is reserved for internal Microsoft use. @@ -414,7 +450,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -424,6 +459,9 @@ Accept wildcard characters: False ``` ### -ProxyToMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ProxyToMailbox parameter specifies the move destination by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example: @@ -443,7 +481,6 @@ The ProxyToMailbox parameter specifies the move destination by the location of t Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -453,6 +490,9 @@ Accept wildcard characters: False ``` ### -RemoteCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteCredential parameter specifies the username and password an administrator who has permission to perform the mailbox move. 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). @@ -461,7 +501,6 @@ 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 @@ -471,13 +510,15 @@ Accept wildcard characters: False ``` ### -RemoteGlobalCatalog + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteGlobalCatalog parameter specifies the FQDN of the global catalog server for the remote forest. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -487,13 +528,15 @@ 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. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -503,6 +546,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -516,7 +562,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -526,6 +571,9 @@ Accept wildcard characters: False ``` ### -SkipMoving + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been replaced by the MoveOptions parameter. The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation. @@ -534,7 +582,6 @@ The SkipMoving parameter specifies the stages of the move that you want to skip Type: SkippableMoveComponent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -544,6 +591,9 @@ Accept wildcard characters: False ``` ### -SourceEndpoint + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SourceEndpoint Description }} @@ -552,7 +602,6 @@ This parameter is available only in the cloud-based service. Type: MigrationEndpointIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -562,6 +611,9 @@ Accept wildcard characters: False ``` ### -StartAfter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this 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". @@ -577,7 +629,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -587,6 +638,9 @@ Accept wildcard characters: False ``` ### -SkippedItemApprovalTime + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete. @@ -602,7 +656,6 @@ To specify a date/time value for this parameter, use either of the following opt Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -612,13 +665,15 @@ 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 suspend the move request before it reaches the status of CompletionInProgress. Instead of this parameter, we recommend using CompleteAfter 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 @@ -628,6 +683,9 @@ Accept wildcard characters: False ``` ### -TargetDatabase + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TargetDatabase parameter specifies the target mailbox database for the mailbox. You can use any value that uniquely identifies the database. For example: @@ -642,7 +700,6 @@ You can use this parameter to change the target database only if the move reques Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -652,13 +709,15 @@ 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/exchange/Set-MyAnalyticsFeatureConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MyAnalyticsFeatureConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-MyAnalyticsFeatureConfig.md index 68c9290d33..d4f19a7d95 100644 --- a/exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MyAnalyticsFeatureConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://learn.microsoft.com/powershell/module/exchange/set-myanalyticsfeatureconfig applicable: Exchange Online -title: Set-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/exchange/set-myanalyticsfeatureconfig +schema: 2.0.0 +title: Set-MyAnalyticsFeatureConfig --- # Set-MyAnalyticsFeatureConfig @@ -71,13 +72,15 @@ This example disables the digest email feature for Akshath. ## 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 @@ -87,6 +90,9 @@ Accept wildcard characters: False ``` ### -Feature + +> Applicable: Exchange Online + The Feature parameter specifies the MyAnalytics features to enable or disable for the user. Valid values are: - all (this is the default value) @@ -101,7 +107,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: dashboard, add-in, digest-email, all -Applicable: Exchange Online Required: False Position: Named @@ -111,6 +116,9 @@ Accept wildcard characters: False ``` ### -IsEnabled + +> Applicable: Exchange Online + The IsEnabled parameter specifies whether to enable or disable the feature that's specified by the Feature parameter. Valid values are: - $true: The specified feature is enabled. @@ -120,7 +128,6 @@ The IsEnabled parameter specifies whether to enable or disable the feature that' Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -130,6 +137,9 @@ Accept wildcard characters: False ``` ### -PrivacyMode + +> Applicable: Exchange Online + The PrivacyMode parameter specifies whether to enable or disable MyAnalytics for the specified user. Valid values are: -opt-in: MyAnalytics is enabled for the user. Use the Feature and IsEnabled parameters to enable or disable specific MyAnalytics features. @@ -140,7 +150,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: opt-in, opt-out -Applicable: Exchange Online Required: False Position: Named @@ -150,13 +159,15 @@ 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/exchange/Set-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-Notification.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Notification.md index 4d7ef423b7..6c06dea1f5 100644 --- a/exchange/exchange-ps/exchange/Set-Notification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-notification applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-Notification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-notification +schema: 2.0.0 +title: Set-Notification --- # Set-Notification @@ -69,6 +70,9 @@ This example configures the specified notification event to send notification em ## 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 modify. 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,AlternativeID,StartTime,Status,Type`. Typically, it only makes sense to modify notification recipients for events that haven't completed (if the event has completed, no more notification messages will be sent). @@ -79,7 +83,6 @@ You can't use this parameter with the ProcessType parameter. Type: EwsStoreObjectIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -89,6 +92,9 @@ Accept wildcard characters: False ``` ### -NotificationEmails + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NotificationEmails parameter specifies the recipients for notification emails related to notification events. You can specify multiple recipients separated by commas. You need to use this parameter with either the ProcessType or Identity parameters: @@ -102,7 +108,6 @@ For Migration events, you can also use the NotificationEmails parameter on the N Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -112,6 +117,9 @@ Accept wildcard characters: False ``` ### -ProcessType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ProcessType parameter specifies the notification event type that sends notification emails to users (specified by the required NotificationEmails parameter). The users receive email notification messages for all events of the specified type. The only valid value for this is parameter is CertExpiry. @@ -122,7 +130,6 @@ You can't use this parameter with the Identity parameter. Type: AsyncOperationType Parameter Sets: Settings Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -132,6 +139,9 @@ 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`. @@ -141,7 +151,6 @@ 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 @@ -151,6 +160,9 @@ 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,7 +171,6 @@ 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,13 +180,15 @@ 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/exchange/Set-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-OMEConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md index 5e1079d1bc..bee3418601 100644 --- a/exchange/exchange-ps/exchange/Set-OMEConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-omeconfiguration applicable: Exchange Online, Exchange Online Protection -title: Set-OMEConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-omeconfiguration +schema: 2.0.0 +title: Set-OMEConfiguration --- # Set-OMEConfiguration @@ -53,13 +54,15 @@ This example configures the specified values for the default OME configuration n ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the OME configuration that you want to modify. 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 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -BackgroundColor + +> Applicable: Exchange Online, Exchange Online Protection + The BackgroundColor parameter specifies the background color. Valid values are: - An HTML hexadecimal color code value (#RRGGBB) enclosed in quotation marks. For example, `"#FFFFFF"` is white. @@ -79,7 +85,6 @@ The BackgroundColor parameter specifies the background color. Valid values are: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ Accept wildcard characters: False ``` ### -DisclaimerText + +> Applicable: Exchange Online, Exchange Online Protection + The DisclaimerText parameter specifies the disclaimer text in the email that contains the encrypted message. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks ("). To remove existing text and use the default value, use the value $null for this parameter. @@ -116,7 +126,6 @@ To remove existing text and use the default value, use the value $null for this Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -126,6 +135,9 @@ Accept wildcard characters: False ``` ### -EmailText + +> Applicable: Exchange Online, Exchange Online Protection + The EmailText parameter specifies the default text that accompanies encrypted email messages. The default text appears above the instructions for viewing encrypted messages. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks ("). To remove existing text and use the default value, use the value $null for this parameter. @@ -134,7 +146,6 @@ To remove existing text and use the default value, use the value $null for this Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -144,6 +155,9 @@ Accept wildcard characters: False ``` ### -ExternalMailExpiryInDays + +> Applicable: Exchange Online + This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription. The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0. @@ -156,7 +170,6 @@ In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is Type: String Parameter Sets: Int32 Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -166,6 +179,9 @@ Accept wildcard characters: False ``` ### -Image + +> Applicable: Exchange Online, Exchange Online Protection + The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center. 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`). @@ -180,7 +196,6 @@ To remove an existing image and use the default image, use the value $null for t Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -190,6 +205,9 @@ Accept wildcard characters: False ``` ### -IntroductionText + +> Applicable: Exchange Online, Exchange Online Protection + The IntroductionText parameter specifies the text that appears next to the sender's name and email address. If the value contains spaces, enclose the value in quotation marks ("). To remove existing text and use the default value, use the value $null for this parameter. @@ -198,7 +216,6 @@ To remove existing text and use the default value, use the value $null for this Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -208,6 +225,9 @@ Accept wildcard characters: False ``` ### -OTPEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are: - $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value. @@ -217,7 +237,6 @@ The OTPEnabled parameter specifies whether to allow recipients to use a one-time Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -227,6 +246,9 @@ Accept wildcard characters: False ``` ### -PortalText + +> Applicable: Exchange Online, Exchange Online Protection + The PortalText parameter specifies the text that appears at the top of the encrypted mail viewing portal. The maximum length is 128 characters. If the value contains spaces, enclose the value in quotation marks ("). To remove existing text and use the default value, use the value $null for this parameter. @@ -235,7 +257,6 @@ To remove existing text and use the default value, use the value $null for this Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -245,6 +266,9 @@ Accept wildcard characters: False ``` ### -PrivacyStatementUrl + +> Applicable: Exchange Online, Exchange Online Protection + The PrivacyStatementUrl parameter specifies the Privacy Statement link in the encrypted email notification message. If you don't use this parameter, the Privacy Statement link goes to the default Microsoft privacy statement. @@ -253,7 +277,6 @@ If you don't use this parameter, the Privacy Statement link goes to the default Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -263,6 +286,9 @@ Accept wildcard characters: False ``` ### -ReadButtonText + +> Applicable: Exchange Online, Exchange Online Protection + The ReadButtonText parameter specifies the text that appears on the "Read the message" button. If the value contains spaces, enclose the value in quotation marks ("). To remove existing text and use the default value, use the value $null for this parameter. @@ -271,7 +297,6 @@ To remove existing text and use the default value, use the value $null for this Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -281,6 +306,9 @@ Accept wildcard characters: False ``` ### -SocialIdSignIn + +> Applicable: Exchange Online, Exchange Online Protection + The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, and Microsoft account). Valid values are: - $true: Social network ID sign in is allowed. This is the default value. @@ -290,7 +318,6 @@ The SocialIdSignIn parameter specifies whether a user is allowed to view an encr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -300,13 +327,15 @@ 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/exchange/Set-OMEMessageRevocation.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md similarity index 97% rename from exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md index d08012a2ab..039552654c 100644 --- a/exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-omemessagerevocation applicable: Exchange Online -title: Set-OMEMessageRevocation -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-omemessagerevocation +schema: 2.0.0 +title: Set-OMEMessageRevocation --- # Set-OMEMessageRevocation @@ -44,6 +45,9 @@ This example revokes encryption 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. @@ -52,7 +56,6 @@ 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 @@ -62,6 +65,9 @@ Accept wildcard characters: False ``` ### -Revoke + +> Applicable: Exchange Online + The Revoke parameter specifies whether to revoke encryption for the message. Valid values are: - $true: Encryption for the specified message is revoked. The recipient will get an error when they try to view the encrypted message in the OME portal @@ -71,7 +77,6 @@ The Revoke parameter specifies whether to revoke encryption for the message. Val Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md index 23e45c17c1..528cc598f7 100644 --- a/exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-oabvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-OabVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-oabvirtualdirectory +schema: 2.0.0 +title: Set-OabVirtualDirectory --- # Set-OabVirtualDirectory @@ -53,6 +54,9 @@ This example changes the external URL of the OAB virtual directory OAB (Default ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -65,7 +69,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -75,6 +78,9 @@ 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. @@ -86,7 +92,6 @@ You can use this parameter with the WindowsAuthentication parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -96,6 +101,9 @@ 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,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ 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,6 +140,9 @@ 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. @@ -143,7 +155,6 @@ 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 @@ -153,6 +164,9 @@ 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. @@ -162,7 +176,6 @@ 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 @@ -172,6 +185,9 @@ 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. @@ -184,7 +200,6 @@ 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 @@ -194,13 +209,15 @@ 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 @@ -210,13 +227,15 @@ 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 @@ -226,13 +245,15 @@ Accept wildcard characters: False ``` ### -OAuthAuthentication + +> 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 @@ -242,6 +263,9 @@ Accept wildcard characters: False ``` ### -PollInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange 2010. The PollInterval parameter specifies the time interval in minutes that the distribution service should poll the offline address book generation server for updates. @@ -250,7 +274,6 @@ The PollInterval parameter specifies the time interval in minutes that the distr Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,6 +283,9 @@ Accept wildcard characters: False ``` ### -RequireSSL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are: - $true: SSL encryption is required to connect to the virtual directory. This is the default value. @@ -269,7 +295,6 @@ The RequireSSL parameter specifies whether the client connection to the virtual Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -279,13 +304,15 @@ 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 @@ -295,6 +322,9 @@ 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. @@ -306,7 +336,6 @@ You can use this parameter with the BasicAuthentication parameter. 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/exchange/Set-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md index b6bd614d26..d154f56979 100644 --- a/exchange/exchange-ps/exchange/Set-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-offlineaddressbook applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-OfflineAddressBook -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-offlineaddressbook +schema: 2.0.0 +title: Set-OfflineAddressBook --- # Set-OfflineAddressBook @@ -73,6 +74,9 @@ This example changes the organization mailbox that's responsible for generating ## 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 modify. You can use any value that uniquely identifies the OAB. For example: - Name or \\Name @@ -83,7 +87,6 @@ The Identity parameter specifies the OAB that you want to modify. You can use an Type: OfflineAddressBookIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -93,6 +96,9 @@ 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 or global address lists that are included in the OAB. You can use any value that uniquely identifies the address list. For example: - Name @@ -107,7 +113,6 @@ You can find the identify values of address lists and global address lists by us Type: AddressBookBaseIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -117,6 +122,9 @@ Accept wildcard characters: False ``` ### -ApplyMandatoryProperties + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplyMandatoryProperties switch specifies whether to update the mandatory properties of a legacy OAB. You don't need to specify a value with this switch. This switch was used in coexistence environments when an OAB was migrated from Exchange 2003. @@ -125,7 +133,6 @@ This switch was used in coexistence environments when an OAB was migrated from E 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 @@ -135,6 +142,9 @@ Accept wildcard characters: False ``` ### -ConfiguredAttributes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConfiguredAttributes parameter specifies the recipient MAPI properties that are available in the OAB. This parameter uses the syntax: `"Name1,Type1","Name2,Type2",..."NameN,TypeN"` where Name is the name of the MAPI property (for example, MobileTelephoneNumber), and Type is the value ANR (ambiguous name resolution), Value, or Indicator. To reset this parameter back to the default values, use the UseDefaultAttributes switch. @@ -143,7 +153,6 @@ To reset this parameter back to the default values, use the UseDefaultAttributes 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 @@ -153,6 +162,9 @@ 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`. @@ -162,7 +174,6 @@ 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 @@ -172,13 +183,15 @@ Accept wildcard characters: False ``` ### -DiffRetentionPeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DiffRetentionPeriod parameter specifies the number of days that the OAB difference files are stored on the server. Valid values are integers from 7 to 1825, or the value unlimited. The default value is 30. ```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 @@ -188,6 +201,9 @@ 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. @@ -196,7 +212,6 @@ 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 @@ -206,13 +221,15 @@ Accept wildcard characters: False ``` ### -FullOabDownloadPreventionThreshold + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -222,6 +239,9 @@ Accept wildcard characters: False ``` ### -GeneratingMailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GeneratingMailbox parameter specifies the arbitration mailbox where the OAB is generated. Specifically, the arbitration mailbox must contain the OrganizationCapabilityOABGen value for the PersistedCapability property. An arbitration mailbox with this capability is also known as an organization mailbox. You can use any value that uniquely identifies the mailbox. For example: @@ -245,7 +265,6 @@ A single organization mailbox can generate multiple OABs (you can use the same v Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,6 +274,9 @@ Accept wildcard characters: False ``` ### -GlobalWebDistributionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are: @@ -268,7 +290,6 @@ In Exchange 2013 CU7 or later, we recommend that you use the value $true for thi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -278,6 +299,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsDefault parameter specifies whether the OAB is used by all mailboxes and mailbox databases that don't have an OAB specified. Valid values are: - $true: The OAB is the default OAB. @@ -287,7 +311,6 @@ The IsDefault parameter specifies whether the OAB is used by all mailboxes and m 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 @@ -297,6 +320,9 @@ Accept wildcard characters: False ``` ### -MaxBinaryPropertySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxBinaryPropertySize parameter specifies the maximum size in bytes for binary attributes in the OAB before they're truncated. Valid values are integers from 0 to 999999999. The default value is 65536. @@ -305,7 +331,6 @@ The MaxBinaryPropertySize parameter specifies the maximum size in bytes for bina Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -315,6 +340,9 @@ Accept wildcard characters: False ``` ### -MaxMultivaluedBinaryPropertySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxMultivaluedBinaryPropertySize parameter specifies the maximum size in bytes for multivalued binary attributes in the OAB before they're truncated. Valid values are integers from 0 to 999999999. The default value is 65536 (64 kilobytes). @@ -323,7 +351,6 @@ The MaxMultivaluedBinaryPropertySize parameter specifies the maximum size in byt Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -333,6 +360,9 @@ Accept wildcard characters: False ``` ### -MaxMultivaluedStringPropertySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxMultivaluedStringPropertySize parameter specifies the maximum size for multivalued string attributes in the OAB before they're truncated. Valid values are integers from 0 to 999999999. The default value is 65536 (64 kilobytes). @@ -341,7 +371,6 @@ The MaxMultivaluedStringPropertySize parameter specifies the maximum size for mu Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -351,6 +380,9 @@ Accept wildcard characters: False ``` ### -MaxStringPropertySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxStringPropertySize parameter specifies the maximum size in bytes for string attributes before they're truncated. Valid values are integers from 0 to 999999999. The default value is 3400. @@ -359,7 +391,6 @@ The MaxStringPropertySize parameter specifies the maximum size in bytes for stri Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -369,13 +400,15 @@ Accept wildcard characters: False ``` ### -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 OAB. 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: False Position: Named @@ -385,6 +418,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDistributionEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The PublicFolderDistributionEnabled parameter specifies whether the OAB is to be distributed via public folders. Setting the PublicFolderDistributionEnabled parameter to a value of $true sets the OAB to be distributed via public folders. The default value is $true. @@ -393,7 +429,6 @@ The PublicFolderDistributionEnabled parameter specifies whether the OAB is to be Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -403,6 +438,9 @@ Accept wildcard characters: False ``` ### -Schedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange 2010. In Exchange 2013 or later, this parameter is no longer responsible for the OAB generation schedule. For more information, see [Change the offline address book generation schedule in Exchange](https://learn.microsoft.com/Exchange/plan-and-deploy/post-installation-tasks/change-oab-generation-schedule). @@ -435,7 +473,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -445,6 +482,9 @@ Accept wildcard characters: False ``` ### -ShadowMailboxDistributionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are: @@ -458,7 +498,6 @@ The value of this parameter is only meaningful if you have multiple organization Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -468,13 +507,15 @@ Accept wildcard characters: False ``` ### -UpgradeFromE14 + +> 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 @@ -484,6 +525,9 @@ Accept wildcard characters: False ``` ### -UseDefaultAttributes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseDefaultAttributes switch specifies whether to revert the recipient MAPI properties that are available in the OAB to the default list. You don't need to specify a value with this switch. You can use this switch to undo changes that you've made to the default list by using the ConfiguredAttributes parameter. @@ -492,7 +536,6 @@ You can use this switch to undo changes that you've made to the default list by 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 @@ -502,6 +545,9 @@ Accept wildcard characters: False ``` ### -Versions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Versions parameter specifies the OAB versions that are generated for client download. Valid values are: - Version2 (requires public folder distribution) @@ -512,7 +558,6 @@ The Versions parameter specifies the OAB versions that are generated for client 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 @@ -522,6 +567,9 @@ Accept wildcard characters: False ``` ### -VirtualDirectories + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The VirtualDirectories parameter specifies the OAB virtual directories that accept requests to download the OAB. These locations are advertised in the Autodiscover service. @@ -544,7 +592,6 @@ In Exchange 2013 CU7 or later, we recommend that you set this parameter to $null Type: VirtualDirectoryIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -554,13 +601,15 @@ 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 @@ -570,6 +619,9 @@ Accept wildcard characters: False ``` ### -ZipOabFilesBeforeUploading + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on the OAB files before uploading them to the server. Valid values are: - $true: ZIP the OAB files. @@ -579,7 +631,6 @@ The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md index 98e0bf8f30..4db9c9bead 100644 --- a/exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-onpremisesorganization applicable: Exchange Online, Exchange Online Protection -title: Set-OnPremisesOrganization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-onpremisesorganization +schema: 2.0.0 +title: Set-OnPremisesOrganization --- # Set-OnPremisesOrganization @@ -50,6 +51,9 @@ This example adds a third domain legal.contoso.com to the ExchangeMail OnPremise ## 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 @@ -60,7 +64,6 @@ 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: True Position: 1 @@ -70,13 +73,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -86,6 +91,9 @@ 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`. @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ Accept wildcard characters: False ``` ### -HybridDomains + +> Applicable: Exchange Online + The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com". ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -121,13 +130,15 @@ Accept wildcard characters: False ``` ### -InboundConnector + +> Applicable: Exchange Online + The InboundConnector parameter specifies the name of the inbound connector configured in Microsoft 365 for a hybrid deployment configured with an on-premises Exchange organization. ```yaml Type: InboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -137,13 +148,15 @@ Accept wildcard characters: False ``` ### -OrganizationName + +> Applicable: Exchange Online + The OrganizationName parameter specifies the Active Directory object name of the on-premises Exchange organization. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -153,13 +166,15 @@ Accept wildcard characters: False ``` ### -OrganizationRelationship + +> Applicable: Exchange Online + The OrganizationRelationship parameter specifies the organization relationship configured by the Hybrid Configuration wizard on the Microsoft 365 organization as part of a hybrid deployment with an on-premises Exchange organization. This organization relationship defines the federated sharing features enabled on the Microsoft 365 organization. ```yaml Type: OrganizationRelationshipIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -169,13 +184,15 @@ Accept wildcard characters: False ``` ### -OutboundConnector + +> Applicable: Exchange Online + The OutboundConnector parameter specifies the name of the outbound connector configured on the EOP service for a hybrid deployment configured with an on-premises Exchange organization. ```yaml Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -185,13 +202,15 @@ 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/exchange/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-OrganizationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md index 96e1fdf138..1b229b8837 100644 --- a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-OrganizationConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationconfig +schema: 2.0.0 +title: Set-OrganizationConfig --- # Set-OrganizationConfig @@ -559,6 +560,9 @@ In Exchange Online, this example results in meeting updates being auto-processed ## PARAMETERS ### -ShortenEventScopeDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ShortenEventScopeDefault parameter specifies whether calendar events start late or end early in the organization. Valid values are: @@ -571,7 +575,6 @@ The ShortenEventScopeDefault parameter specifies whether calendar events start l Type: ShortenEventScopeMode Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -581,6 +584,9 @@ Accept wildcard characters: False ``` ### -AcceptedDomainApprovedSendersEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AcceptedDomainApprovedSendersEnabled Description }} @@ -589,7 +595,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -599,6 +604,9 @@ Accept wildcard characters: False ``` ### -ACLableSyncedObjectEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ACLableSyncedObjectEnabled parameter specifies whether remote mailboxes in hybrid environments are stamped as ACLableSyncedMailboxUser. @@ -607,7 +615,6 @@ The ACLableSyncedObjectEnabled parameter specifies whether remote mailboxes in h Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -617,6 +624,9 @@ Accept wildcard characters: False ``` ### -ActionableMessagesExtenalAccessTokenEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ActionableMessagesExtenalAccessTokenEnabled Description }} @@ -625,7 +635,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -635,6 +644,9 @@ Accept wildcard characters: False ``` ### -ActivityBasedAuthenticationTimeoutEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActivityBasedAuthenticationTimeoutEnabled parameter enables or disables the inactivity interval for automatic logoff in Outlook on the web (formerly known as Outlook Web App). Valid values are: - $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This is the default value. @@ -646,7 +658,6 @@ If you're using single sign-on, use the ActivityBasedAuthenticationTimeoutWithSi 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 @@ -656,6 +667,9 @@ Accept wildcard characters: False ``` ### -ActivityBasedAuthenticationTimeoutInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes an automatic logoff in Outlook on the web. You enter this value as a time span: hh:mm:ss where hh = hours, mm = minutes and ss = seconds. @@ -670,7 +684,6 @@ For more information about the activity-based timeout in Outlook on the web, see Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -680,6 +693,9 @@ Accept wildcard characters: False ``` ### -ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter enables or disables the inactivity interval for automatic logoff for single sign-on in Outlook on the Web. Valid values are: - $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This is the default value. @@ -691,7 +707,6 @@ If you aren't using single sign-on, use the ActivityBasedAuthenticationTimeoutEn 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 @@ -701,6 +716,9 @@ Accept wildcard characters: False ``` ### -AdfsAudienceUris + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdfsAudienceUris parameter specifies one or more external URLs that are used for Active Directory Federation Services (AD FS) claims-based authentication. For example, the external Outlook on the web and external Exchange admin center (EAC) URLs. @@ -715,7 +733,6 @@ For more information about configuring AD FS claims based authentication in Exch Type: MultiValuedProperty Parameter Sets: AdfsAuthenticationParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -725,6 +742,9 @@ Accept wildcard characters: False ``` ### -AdfsAuthenticationConfiguration + +> 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. @@ -733,7 +753,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -743,6 +762,9 @@ Accept wildcard characters: False ``` ### -AdfsEncryptCertificateThumbprint + +> 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. @@ -751,7 +773,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AdfsAuthenticationParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -761,6 +782,9 @@ Accept wildcard characters: False ``` ### -AdfsIssuer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdfsIssuer parameter specifies URL of the AD FS server that's used for AD FS claims-based authentication. This is the URL where AD FS relying parties send users for authentication. @@ -771,7 +795,6 @@ To get this value, open Windows PowerShell on the AD FS server and run the comma Type: Uri Parameter Sets: AdfsAuthenticationParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -781,6 +804,9 @@ Accept wildcard characters: False ``` ### -AdfsSignCertificateThumbprints + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AdfsSignCertificateThumbprints parameter specifies one or more X.509 token-signing certificates that are used for AD FS claims-based authentication. This parameter uses certificate thumbprint values (GUIDs) to identify the certificates. @@ -795,7 +821,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: AdfsAuthenticationParameter Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -805,13 +830,15 @@ Accept wildcard characters: False ``` ### -AppsForOfficeEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AppsForOfficeEnabled parameter specifies whether to enable apps for Outlook features. By default, the parameter is set to $true. If the flag is set to $false, no new apps can be activated for any user in the organization. ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -821,6 +848,9 @@ Accept wildcard characters: False ``` ### -AsyncSendEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AsyncSendEnabled parameter specifies whether to enable or disable async send in Outlook on the web. Valid values are: - $true: Async send is enabled. This is the default value. @@ -830,7 +860,6 @@ The AsyncSendEnabled parameter specifies whether to enable or disable async send Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -840,6 +869,9 @@ Accept wildcard characters: False ``` ### -AuditDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AuditDisabled parameter specifies whether to disable or enable mailbox auditing for the organization. Valid values are: @@ -851,7 +883,6 @@ The AuditDisabled parameter specifies whether to disable or enable mailbox audit Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -861,6 +892,9 @@ Accept wildcard characters: False ``` ### -AutodiscoverPartialDirSync + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false. @@ -871,7 +905,6 @@ After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -881,6 +914,9 @@ Accept wildcard characters: False ``` ### -AutoEnableArchiveMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AutoEnableArchiveMailbox specifies whether an archive mailbox is automatically provisioned when the primary mailbox reaches 90% of the size quota (if licenses include archiving). Valid values are: @@ -892,7 +928,6 @@ The AutoEnableArchiveMailbox specifies whether an archive mailbox is automatical Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -902,6 +937,9 @@ Accept wildcard characters: False ``` ### -AutoExpandingArchive + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AutoExpandingArchive switch enables the auto-expanding archiving feature in an Exchange Online organization. You don't need to specify a value with this switch. @@ -912,7 +950,6 @@ After you enable auto-expanding archiving, additional storage space is automatic Type: SwitchParameter Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -922,6 +959,9 @@ Accept wildcard characters: False ``` ### -AutomaticForcedReadReceiptEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AutomaticForcedReadReceiptEnabled Description }} @@ -930,7 +970,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -940,6 +979,9 @@ Accept wildcard characters: False ``` ### -BlockMoveMessagesForGroupFolders + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The BlockMoveMessagesForGroupFolders parameter specifies whether to prevent group owners or group members from moving messages between folders in Microsoft 365 Groups. Valid values are: @@ -960,7 +1002,6 @@ For more information, see [Manage Folders and Rules feature in Microsoft 365 Gro Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -970,6 +1011,9 @@ Accept wildcard characters: False ``` ### -BookingsAddressEntryRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsAddressEntryRestricted parameter specifies whether addresses can be collected from Bookings customers. Valid values are: @@ -981,7 +1025,6 @@ The BookingsAddressEntryRestricted parameter specifies whether addresses can be Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -991,6 +1034,9 @@ Accept wildcard characters: False ``` ### -BookingsAuthEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsAuthEnabled parameter specifies whether to enforce authentication to access all published Bookings pages. Valid values are: @@ -1002,7 +1048,6 @@ The BookingsAuthEnabled parameter specifies whether to enforce authentication to Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1012,6 +1057,9 @@ Accept wildcard characters: False ``` ### -BookingsBlockedWordsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsBlockedWordsEnabled Description }} @@ -1020,7 +1068,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1030,6 +1077,9 @@ Accept wildcard characters: False ``` ### -BookingsCreationOfCustomQuestionsRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsCreationOfCustomQuestionsRestricted parameter specifies whether Bookings admins can add custom questions. Valid values are: @@ -1041,7 +1091,6 @@ The BookingsCreationOfCustomQuestionsRestricted parameter specifies whether Book Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1051,6 +1100,9 @@ Accept wildcard characters: False ``` ### -BookingsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsEnabled parameter specifies whether to enable Microsoft Bookings in an organization. Valid values are: @@ -1064,7 +1116,6 @@ Microsoft Bookings is an online and mobile app for small businesses who provide Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1074,6 +1125,9 @@ Accept wildcard characters: False ``` ### -BookingsExposureOfStaffDetailsRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsExposureOfStaffDetailsRestricted parameter specifies whether the attributes of internal Bookings staff members (for example, email addresses) are visible to external Bookings customers. Valid values are: @@ -1085,7 +1139,6 @@ The BookingsExposureOfStaffDetailsRestricted parameter specifies whether the att Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1095,6 +1148,9 @@ Accept wildcard characters: False ``` ### -BookingsMembershipApprovalRequired + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsMembershipApprovalRequired parameter enables a membership approval requirement when new staff members are added to Bookings calendars. Valid values are: @@ -1106,7 +1162,6 @@ The BookingsMembershipApprovalRequired parameter enables a membership approval r Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1116,6 +1171,9 @@ Accept wildcard characters: False ``` ### -BookingsNamingPolicyEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsNamingPolicyEnabled Description }} @@ -1124,7 +1182,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1134,6 +1191,9 @@ Accept wildcard characters: False ``` ### -BookingsNamingPolicyPrefix + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsNamingPolicyPrefix Description }} @@ -1142,7 +1202,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1152,6 +1211,9 @@ Accept wildcard characters: False ``` ### -BookingsNamingPolicyPrefixEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsNamingPolicyPrefixEnabled Description }} @@ -1160,7 +1222,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1170,6 +1231,9 @@ Accept wildcard characters: False ``` ### -BookingsNamingPolicySuffix + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsNamingPolicySuffix Description }} @@ -1178,7 +1242,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1188,6 +1251,9 @@ Accept wildcard characters: False ``` ### -BookingsNamingPolicySuffixEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsNamingPolicySuffixEnabled Description }} @@ -1196,7 +1262,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1206,6 +1271,9 @@ Accept wildcard characters: False ``` ### -BookingsNotesEntryRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsNotesEntryRestricted parameter specifies whether appointment notes can be collected from Bookings customers. Valid values are: @@ -1217,7 +1285,6 @@ The BookingsNotesEntryRestricted parameter specifies whether appointment notes c Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1227,6 +1294,9 @@ Accept wildcard characters: False ``` ### -BookingsPaymentsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsPaymentsEnabled parameter specifies whether to enable the online payment node inside Bookings. Valid values are: @@ -1238,7 +1308,6 @@ The BookingsPaymentsEnabled parameter specifies whether to enable the online pay Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1248,6 +1317,9 @@ Accept wildcard characters: False ``` ### -BookingsPhoneNumberEntryRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsPhoneNumberEntryRestricted parameter specifies whether phone numbers can be collected from Bookings customers. Valid values are: @@ -1259,7 +1331,6 @@ The BookingsPhoneNumberEntryRestricted parameter specifies whether phone numbers Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1269,6 +1340,9 @@ Accept wildcard characters: False ``` ### -BookingsSearchEngineIndexDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsSearchEngineIndexDisabled Description }} @@ -1277,7 +1351,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1287,6 +1360,9 @@ Accept wildcard characters: False ``` ### -BookingsSmsMicrosoftEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsSmsMicrosoftEnabled Description }} @@ -1295,7 +1371,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1305,6 +1380,9 @@ Accept wildcard characters: False ``` ### -BookingsSocialSharingRestricted + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsSocialSharingRestricted parameter specifies whether users can see the social sharing options inside Bookings. Valid values are: @@ -1316,7 +1394,6 @@ The BookingsSocialSharingRestricted parameter specifies whether users can see th Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1326,6 +1403,9 @@ Accept wildcard characters: False ``` ### -ByteEncoderTypeFor7BitCharsets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encoding method for MIME format for messages sent to this remote domain. The valid values for this parameter are: - 0: Always use default 7-bit transfer encoding for HTML and plain text. @@ -1342,7 +1422,6 @@ If no value is specified, Exchange always uses QP encoding for HTML and plain te 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 @@ -1352,6 +1431,9 @@ Accept wildcard characters: False ``` ### -CalendarVersionStoreEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -1360,7 +1442,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1370,6 +1451,9 @@ Accept wildcard characters: False ``` ### -ComplianceMLBgdCrawlEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ComplianceMLBgdCrawlEnabled Description }} @@ -1378,7 +1462,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1388,6 +1471,9 @@ 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`. @@ -1397,7 +1483,6 @@ 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 @@ -1407,6 +1492,9 @@ Accept wildcard characters: False ``` ### -ConnectorsActionableMessagesEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConnectorsActionableMessagesEnabled parameter specifies whether to enable or disable actionable buttons in messages (connector cards) from connected apps on Outlook on the web. Valid values are: - $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This is the default value. @@ -1418,7 +1506,6 @@ For more information about actionable messages in connected apps, see [Connect a Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1428,6 +1515,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConnectorsEnabled parameter specifies whether to enable or disable all connected apps in organization. Valid values are: - $true: Connectors are enabled. This is the default value. @@ -1439,7 +1529,6 @@ The workloads that are affected by this parameter are Outlook, SharePoint, Teams Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1449,6 +1538,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabledForOutlook + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ConnectorsEnabledForOutlook parameter specifies whether to enable or disable connected apps in Outlook on the web. Valid values are: @@ -1464,7 +1556,6 @@ For more information about connectors for Outlook on the web, see [Connect apps Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1474,6 +1565,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabledForSharepoint + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ConnectorsEnabledForSharepoint parameter specifies whether to enable or disable connected apps on SharePoint. Valid values are: @@ -1485,7 +1579,6 @@ The ConnectorsEnabledForSharepoint parameter specifies whether to enable or disa Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1495,6 +1588,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabledForTeams + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ConnectorsEnabledForTeams parameter specifies whether to enable or disable connected apps on Teams. Valid values are: @@ -1506,7 +1602,6 @@ The ConnectorsEnabledForTeams parameter specifies whether to enable or disable c Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1516,6 +1611,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabledForYammer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Viva Engage. Valid values are: @@ -1527,7 +1625,6 @@ The ConnectorsEnabledForYammer parameter specifies whether to enable or disable Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1537,6 +1634,9 @@ Accept wildcard characters: False ``` ### -CustomerFeedbackEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CustomerFeedbackEnabled parameter specifies whether the Exchange server is enrolled in the Microsoft Customer Experience Improvement Program. @@ -1545,7 +1645,6 @@ The CustomerFeedbackEnabled parameter specifies whether the Exchange server is e Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1555,6 +1654,9 @@ Accept wildcard characters: False ``` ### -CustomerLockboxEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -1563,7 +1665,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1573,6 +1674,9 @@ Accept wildcard characters: False ``` ### -DataClassifications + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1581,7 +1685,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1591,6 +1694,9 @@ Accept wildcard characters: False ``` ### -DefaultAuthenticationPolicy + +> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + The DefaultAuthenticationPolicy parameter specifies the authentication policy that's used for the whole organization. You can use any value that uniquely identifies the policy. For example: - Name @@ -1605,7 +1711,6 @@ You create authentication policies with the New-AuthenticationPolicy cmdlet to b Type: AuthPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1615,6 +1720,9 @@ Accept wildcard characters: False ``` ### -DefaultGroupAccessType + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DefaultGroupAccessType parameter specifies the default access type for Microsoft 365 Groups. Valid values are: @@ -1626,7 +1734,6 @@ The DefaultGroupAccessType parameter specifies the default access type for Micro Type: ModernGroupObjectType Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1636,6 +1743,9 @@ Accept wildcard characters: False ``` ### -DefaultMinutesToReduceLongEventsBy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DefaultMinutesToReduceLongEventsBy parameter specifies the number of minutes to reduce calendar events by if the events are 60 minutes or longer. A valid value is an integer from 0 to 29. The default value is 10. @@ -1648,7 +1758,6 @@ Whether long events start late or end early by the specified number of minutes d Type: Int32 Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named Default value: None @@ -1657,6 +1766,9 @@ Accept wildcard characters: False ``` ### -DefaultMinutesToReduceShortEventsBy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DefaultMinutesToReduceShortEventsBy parameter specifies the number of minutes to reduce calendar events by if the events are less than 60 minutes long. A valid value is an integer from 0 to 29. The default value is 5. @@ -1669,7 +1781,6 @@ Whether short events start late or end early by the specified number of minutes Type: Int32 Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named Default value: None @@ -1678,6 +1789,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderAgeLimit parameter specifies the default age limit for the contents of public folders across the entire organization. Content in a public folder is automatically deleted when this age limit is exceeded. This attribute applies to all public folders in the organization that don't have their own AgeLimit setting. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. Or, enter the value $null. The default value is blank ($null). @@ -1686,7 +1800,6 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hou Type: EnhancedTimeSpan Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1696,13 +1809,15 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderDeletedItemRetention + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderDeletedItemRetention parameter specifies the default value of the length of time to retain deleted items for public folders across the entire organization. This attribute applies to all public folders in the organization that don't have their own RetainDeletedItemsFor attribute set. ```yaml Type: EnhancedTimeSpan Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1712,6 +1827,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderIssueWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderIssueWarningQuota parameter specifies the default value across the entire organization for the public folder size at which a warning message is sent to this folder's owners, warning that the public folder is almost full. This attribute applies to all public folders within the organization that don't have their own warning quota attribute set. The default value of this attribute is unlimited. When you enter a value, qualify the value with one of the following units: @@ -1730,7 +1848,6 @@ The valid input range for this parameter is from 0 through 2199023254529 bytes(2 Type: Unlimited Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1740,6 +1857,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderMaxItemSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderMaxItemSize parameter specifies the default maximum size for posted items within public folders across the entire organization. Items larger than the value of the DefaultPublicFolderMaxItemSize parameter are rejected. This attribute applies to all public folders within the organization that don't have their own MaxItemSize attribute set. The default value of this attribute is unlimited. When you enter a value, qualify the value with one of the following units: @@ -1758,7 +1878,6 @@ The valid input range for this parameter is from 0 through 2199023254529 bytes ( Type: Unlimited Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1768,6 +1887,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderMovedItemRetention + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderMovedItemRetention parameter specifies how long items that have been moved between mailboxes are kept in the source mailbox for recovery purposes before being removed by the Public Folder Assistant. When you move folder contents between mailboxes, a copy of the original data is left on the source mailbox, inaccessible for users but available for recovery by system administrators. If the move process fails and you want to roll it back, use the Set-PublicFolder -OverrideContentMailbox command to recover data. For more information, see [Set-PublicFolder](https://learn.microsoft.com/powershell/module/exchange/set-publicfolder). @@ -1776,7 +1898,6 @@ When you move folder contents between mailboxes, a copy of the original data is Type: EnhancedTimeSpan Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1786,6 +1907,9 @@ Accept wildcard characters: False ``` ### -DefaultPublicFolderProhibitPostQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultPublicFolderProhibitPostQuota parameter specifies the size of a public folder at which users are notified that the public folder is full. Users can't post to a folder whose size is larger than the DefaultPublicFolderProhibitPostQuota parameter value. The default value of this attribute is unlimited. When you enter a value, qualify the value with one of the following units: @@ -1804,7 +1928,6 @@ The valid input range for this parameter is from 0 through 2199023254529 bytes ( Type: Unlimited Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1814,6 +1937,9 @@ Accept wildcard characters: False ``` ### -DelayedDelicensingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The DelayedDelicensingEnabled parameter enables or disables a 30 day grace period for Exchange Online license removals from mailboxes. Valid values are: @@ -1837,7 +1963,6 @@ When you set the value of the DelayedDelicensingEnabled parameter to $false, the Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1847,6 +1972,9 @@ Accept wildcard characters: False ``` ### -DirectReportsGroupAutoCreationEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DirectReportsGroupAutoCreationEnabled parameter specifies whether to enable or disable the automatic creation of direct report Microsoft 365 Groups. Valid values are: @@ -1858,7 +1986,6 @@ The DirectReportsGroupAutoCreationEnabled parameter specifies whether to enable Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1868,6 +1995,9 @@ Accept wildcard characters: False ``` ### -DisablePlusAddressInRecipients + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The DisablePlusAddressInRecipients parameter specifies whether to enable or disable plus addressing (also known as subaddressing) for Exchange Online mailboxes. Valid values are: @@ -1881,7 +2011,6 @@ For more information about plus addressing, see [Plus addressing in Exchange Onl Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1891,13 +2020,15 @@ Accept wildcard characters: False ``` ### -DistributionGroupDefaultOU + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DistributionGroupDefaultOU parameter specifies the container where distribution groups are created by default. ```yaml 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 @@ -1907,13 +2038,15 @@ Accept wildcard characters: False ``` ### -DistributionGroupNameBlockedWordsList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DistributionGroupNameBlockedWordsList parameter specifies words that can't be included in the Display Name values of distribution groups that are created by users. Separate multiple values with 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 @@ -1923,6 +2056,9 @@ Accept wildcard characters: False ``` ### -DistributionGroupNamingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DistributionGroupNamingPolicy parameter specifies the additional text that's applied to the Display Name value of distribution groups created by users. You can require a prefix, a suffix, or both. The prefix and suffix can be text strings, user attribute values from the person who created the group, or a combination of text strings and attributes. The basic syntax for this parameter is `"prefixsuffix"`. The value `` is a literal value that you must always include. @@ -1946,7 +2082,6 @@ For example: `"DL__"`, `"-- 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. @@ -1966,7 +2104,6 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg Type: Fqdn Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1976,6 +2113,9 @@ Accept wildcard characters: False ``` ### -ElcProcessingDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ElcProcessingDisabled parameter specifies whether to enable or disable the processing of mailboxes by the Managed Folder Assistant. Valid values are: @@ -1987,7 +2127,6 @@ The ElcProcessingDisabled parameter specifies whether to enable or disable the p Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1997,6 +2136,9 @@ Accept wildcard characters: False ``` ### -EmptyAddressBookForNonExchangeUsers + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. {{ Fill EmptyAddressBookForNonExchangeUsers Description }} @@ -2005,7 +2147,6 @@ This parameter is available only in on-premises Exchange. Type: SwitchParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2015,6 +2156,9 @@ Accept wildcard characters: False ``` ### -EnableAuthAdminReadSession + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableAuthAdminReadSession switch enables a recipient read session in Exchange 2016 CU17 or later, or in Exchange 2019 CU6 or later. You don't need to specify a value with this switch. @@ -2023,7 +2167,6 @@ The EnableAuthAdminReadSession switch enables a recipient read session in Exchan Type: SwitchParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2033,6 +2176,9 @@ Accept wildcard characters: False ``` ### -EnableDownloadDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The EnableDownloadDomains parameter specifies that Outlook on the web downloads inline images from a different domain than the rest of Outlook on the web. Valid values are: @@ -2046,7 +2192,6 @@ For more information about the security vulnerability that's addressed by this p Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2056,6 +2201,9 @@ Accept wildcard characters: False ``` ### -EnableForwardingAddressSyncForMailboxes + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2064,7 +2212,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2074,6 +2221,9 @@ Accept wildcard characters: False ``` ### -EnableOrgWidePermissionOnScopedRoles + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. {{ Fill EnableOrgWidePermissionOnScopedRoles Description }} @@ -2082,7 +2232,6 @@ This parameter is available only in on-premises Exchange. Type: SwitchParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2092,6 +2241,9 @@ Accept wildcard characters: False ``` ### -EnableOutlookEvents + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EnableOutlookEvents parameter specifies whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to user calendars. Valid values are: @@ -2103,7 +2255,6 @@ The EnableOutlookEvents parameter specifies whether Outlook or Outlook on the we Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2113,6 +2264,9 @@ Accept wildcard characters: False ``` ### -EndUserDLUpgradeFlowsDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The EndUserDLUpgradeFlowsDisabled parameter specifies whether to prevent users from upgrading their own distribution groups to Microsoft 365 Groups in an Exchange Online organization. Valid values are: @@ -2124,7 +2278,6 @@ The EndUserDLUpgradeFlowsDisabled parameter specifies whether to prevent users f Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2134,6 +2287,9 @@ Accept wildcard characters: False ``` ### -EndUserMailNotificationForDelayedDelicensingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EndUserMailNotificationForDelayedDelicensingEnabled parameter enables or disables periodic email warnings to affected users that have pending Exchange Online license removal requests on their mailboxes. Valid values are: @@ -2149,7 +2305,6 @@ Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2159,13 +2314,15 @@ Accept wildcard characters: False ``` ### -EwsAllowEntourage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowEntourage parameter specifies whether to enable or disable Entourage 2008 to access Exchange Web Services (EWS) for the entire organization. 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 @@ -2175,6 +2332,9 @@ Accept wildcard characters: False ``` ### -EwsAllowList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowList parameter specifies the applications that are allowed to access EWS or REST when the EwsApplicationAccessPolicy parameter is set to EwsAllowList. Other applications that aren't specified by this parameter aren't allowed to access EWS or REST. You identify the application by its user agent string value. Wildcard characters (\*) are supported. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -2187,7 +2347,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -2197,13 +2356,15 @@ Accept wildcard characters: False ``` ### -EwsAllowMacOutlook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowMacOutlook parameter enables or disables access to mailboxes by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later). ```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 @@ -2213,13 +2374,15 @@ Accept wildcard characters: False ``` ### -EwsAllowOutlook + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsAllowOutlook parameter enables or disables access to mailboxes by Outlook clients that use Exchange Web Services. Outlook uses Exchange Web Services for free/busy, out-of-office settings, and calendar sharing. ```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 @@ -2229,6 +2392,9 @@ Accept wildcard characters: False ``` ### -EwsApplicationAccessPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsApplicationAccessPolicy parameter specifies the client applications that have access to EWS and REST. Valid values are: - EnforceAllowList: Only applications specified by the EwsAllowList parameter are allowed to access EWS and REST. Access by other applications is blocked. @@ -2240,7 +2406,6 @@ Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parame Type: EwsApplicationAccessPolicy Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2250,6 +2415,9 @@ Accept wildcard characters: False ``` ### -EwsBlockList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsBlockList parameter specifies the applications that aren't allowed to access EWS or REST when the EwsApplicationAccessPolicy parameter is set to EnforceBlockList. All other applications that aren't specified by this parameter are allowed to access EWS or REST. You identify the application by its user agent string value. Wildcard characters (\*) are supported. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -2260,7 +2428,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -2270,6 +2437,9 @@ Accept wildcard characters: False ``` ### -EwsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EwsEnabled parameter specifies whether to globally enable or disable EWS access for the entire organization, regardless of what application is making the request. Valid values are: - $true: All EWS access is enabled. @@ -2282,7 +2452,6 @@ This parameter has no affect on access to REST. 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 @@ -2292,6 +2461,9 @@ Accept wildcard characters: False ``` ### -ExchangeNotificationEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeNotificationEnabled parameter enables or disables Exchange notifications sent to administrators regarding their organizations. Valid input for this parameter is $true or $false. @@ -2300,7 +2472,6 @@ The ExchangeNotificationEnabled parameter enables or disables Exchange notificat Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2310,6 +2481,9 @@ Accept wildcard characters: False ``` ### -ExchangeNotificationRecipients + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeNotificationRecipients parameter specifies the recipients for Exchange notifications sent to administrators regarding their organizations. If the ExchangeNotificationEnabled parameter is set to $false, no notification messages are sent. Be sure to enclose values that contain spaces in quotation marks (") and separate multiple values with commas. If this parameter isn't set, Exchange notifications are sent to all administrators. @@ -2318,7 +2492,6 @@ The ExchangeNotificationRecipients parameter specifies the recipients for Exchan Type: MultiValuedProperty Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2328,6 +2501,9 @@ Accept wildcard characters: False ``` ### -FindTimeAttendeeAuthenticationEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FindTimeAttendeeAuthenticationEnabled parameter controls whether attendees are required to verify their identity in meeting polls using the FindTime Outlook add-in. Valid values are: @@ -2343,7 +2519,6 @@ For more information about FindTime, see [How to create a FindTime poll](https:/ Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2353,6 +2528,9 @@ Accept wildcard characters: False ``` ### -FindTimeAutoScheduleDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FindTimeAutoScheduleDisabled parameter controls automatically scheduling the meeting once a consensus is reached in meeting polls using the FindTime Outlook add-in. Valid values are: @@ -2368,7 +2546,6 @@ For more information about FindTime, see [How to create a FindTime poll](https:/ Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2378,6 +2555,9 @@ Accept wildcard characters: False ``` ### -FindTimeLockPollForAttendeesEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FindTimeLockPollForAttendeesEnabled controls whether the **Lock poll for attendees** setting is managed by the organization. Valid values are: @@ -2393,7 +2573,6 @@ For more information about FindTime, see [How to create a FindTime poll](https:/ Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2403,6 +2582,9 @@ Accept wildcard characters: False ``` ### -FindTimeOnlineMeetingOptionDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FindTimeOnlineMeetingOptionDisabled parameter controls the availability of the **Online meeting** checkbox for Teams or Skype in meeting polls using the FindTime Outlook add-in. Valid values are: @@ -2418,7 +2600,6 @@ For more information about FindTime, see [How to create a FindTime poll](https:/ Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2428,6 +2609,9 @@ Accept wildcard characters: False ``` ### -FocusedInboxOn + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FocusedInboxOn parameter enables or disables Focused Inbox for the organization. Valid values are: @@ -2443,7 +2627,6 @@ Focused Inbox is a replacement for Clutter that separates the Inbox into the Foc Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2453,6 +2636,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. @@ -2463,7 +2649,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2473,6 +2658,9 @@ Accept wildcard characters: False ``` ### -HierarchicalAddressBookRoot + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The HierarchicalAddressBookRoot parameter specifies the user, contact, or group to be used as the root organization for a hierarchical address book in the Exchange organization. You can use any value that uniquely identifies the recipient. For example: - Name @@ -2488,7 +2676,6 @@ The default value is blank. To reset this parameter, use the value $null. Type: UserContactGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2498,6 +2685,9 @@ Accept wildcard characters: False ``` ### -HybridRSVPEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The HybridRSVPEnabled parameter enables or disables Hybrid RSVP for your organization. Hybrid RSVP allows users the option to indicate if they will attend a meeting in-person or virtually when responding to a meeting invitation on Outlook. Valid values are: @@ -2509,7 +2699,6 @@ The HybridRSVPEnabled parameter enables or disables Hybrid RSVP for your organiz Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2519,6 +2708,9 @@ Accept wildcard characters: False ``` ### -Industry + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Industry parameter specifies the industry that best represents your organization. @@ -2527,7 +2719,6 @@ The Industry parameter specifies the industry that best represents your organiza Type: IndustryType Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2537,6 +2728,9 @@ Accept wildcard characters: False ``` ### -IPListBlocked + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter only affects Basic authentication connections. @@ -2559,7 +2753,6 @@ Changes to this parameter might take up to 4 hours to fully propagate across the Type: MultiValuedProperty Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2569,13 +2762,15 @@ Accept wildcard characters: False ``` ### -IsAgendaMailEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2585,6 +2780,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromOffboardMigration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The IsExcludedFromOffboardMigration parameter specifies that no new moves from the cloud to your on-premises organization are permitted. When this flag is set, no offboarding move requests are allowed. @@ -2593,7 +2791,6 @@ The IsExcludedFromOffboardMigration parameter specifies that no new moves from t Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2603,6 +2800,9 @@ Accept wildcard characters: False ``` ### -IsExcludedFromOnboardMigration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The IsExcludedFromOnboardMigration parameter specifies that no new moves from your on-premises organization to the cloud are permitted. When this flag is set, no onboarding move requests are allowed. @@ -2611,7 +2811,6 @@ The IsExcludedFromOnboardMigration parameter specifies that no new moves from yo Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2621,6 +2820,9 @@ Accept wildcard characters: False ``` ### -IsFfoMigrationInProgress + +> 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. @@ -2629,7 +2831,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2639,6 +2840,9 @@ Accept wildcard characters: False ``` ### -IsGroupFoldersAndRulesEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The IsGroupFoldersAndRulesEnabled specifies whether group owners (by default) can create folders and move messages (manually or by using Inbox rules) in Microsoft 365 Groups. Valid values are: @@ -2654,7 +2858,6 @@ For more information, see [Manage Folders and Rules feature in Microsoft 365 Gro Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2664,6 +2867,9 @@ Accept wildcard characters: False ``` ### -IsGroupMemberAllowedToEditContent + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The IsGroupMemberAllowedToEditContent parameter specifies whether group owners can allow group members to manage folders and messages in Microsoft 365 Groups. Valid values are: @@ -2688,7 +2894,6 @@ For more information, see [Manage Folders and Rules feature in Microsoft 365 Gro Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2698,6 +2903,9 @@ Accept wildcard characters: False ``` ### -LeanPopoutEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The LeanPopoutEnabled parameter specifies whether to enable faster loading of pop-out messages in Outlook on the web for Internet Explorer and Microsoft Edge. Valid values are: - $true: Lean pop-outs are enabled. @@ -2712,7 +2920,6 @@ The LeanPopoutEnabled parameter specifies whether to enable faster loading of po Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2722,6 +2929,9 @@ Accept wildcard characters: False ``` ### -LinkPreviewEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is allowed for the organization. Valid values are: - $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This is the default value. @@ -2731,7 +2941,6 @@ The LinkPreviewEnabled parameter specifies whether link preview of URLs in email Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2741,6 +2950,9 @@ Accept wildcard characters: False ``` ### -MailboxDataEncryptionEnabled + +> Applicable: Exchange Server 2019 + This parameter is available only in on-premises Exchange. {{ Fill MailboxDataEncryptionEnabled Description }} @@ -2749,7 +2961,6 @@ This parameter is available only in on-premises Exchange. Type: SwitchParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -2759,13 +2970,15 @@ Accept wildcard characters: False ``` ### -MailTipsAllTipsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipsAllTipsEnabled parameter specifies whether MailTips are enabled. 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 @@ -2775,13 +2988,15 @@ Accept wildcard characters: False ``` ### -MailTipsExternalRecipientsTipsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipsExternalRecipientsTipsEnabled parameter specifies whether MailTips for external recipients are enabled. 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 @@ -2791,13 +3006,15 @@ Accept wildcard characters: False ``` ### -MailTipsGroupMetricsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipsGroupMetricsEnabled parameter specifies whether MailTips that rely on group metrics data are enabled. 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 @@ -2807,13 +3024,15 @@ Accept wildcard characters: False ``` ### -MailTipsLargeAudienceThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipsLargeAudienceThreshold parameter specifies what a large audience is. The default value is 25. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2823,13 +3042,15 @@ Accept wildcard characters: False ``` ### -MailTipsMailboxSourcedTipsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailTipsMailboxSourcedTipsEnabled parameter specifies whether MailTips that rely on mailbox data (out-of-office or full mailbox) are enabled. ```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 @@ -2839,6 +3060,9 @@ Accept wildcard characters: False ``` ### -ManagedFolderHomepage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ManagedFolderHomepage parameter specifies the URL of the web page that's displayed when users click the Managed Folders folder in Outlook. If a URL isn't specified, Outlook doesn't display a managed folders home page. @@ -2847,7 +3071,6 @@ The ManagedFolderHomepage parameter specifies the URL of the web page that's dis Type: String Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2857,6 +3080,9 @@ Accept wildcard characters: False ``` ### -MapiHttpEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MapiHttpEnabled parameter enables or disables access to mailboxes in Outlook by using MAPI over HTTP. Valid values are: @@ -2870,7 +3096,6 @@ You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to overri Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2880,6 +3105,9 @@ Accept wildcard characters: False ``` ### -MaskClientIpInReceivedHeadersEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MaskClientIpInReceivedHeadersEnabled Description }} @@ -2888,7 +3116,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2898,6 +3125,9 @@ Accept wildcard characters: False ``` ### -MatchSenderOrganizerProperties + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MatchSenderOrganizerProperties Description }} @@ -2906,7 +3136,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2916,6 +3145,9 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMigrations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxConcurrentMigrations parameter specifies the maximum number of concurrent migrations that your organization can configure at any specific time. @@ -2924,7 +3156,6 @@ The MaxConcurrentMigrations parameter specifies the maximum number of concurrent Type: Unlimited Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2934,6 +3165,9 @@ Accept wildcard characters: False ``` ### -MessageHighlightsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MessageHighlightsEnabled Description }} @@ -2942,7 +3176,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2952,6 +3185,9 @@ Accept wildcard characters: False ``` ### -MessageRecallAlertRecipientsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MessageRecallAlertRecipientsEnabled Description }} @@ -2960,7 +3196,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2970,6 +3205,9 @@ Accept wildcard characters: False ``` ### -MessageRecallAlertRecipientsReadMessagesOnlyEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MessageRecallAlertRecipientsReadMessagesOnlyEnabled Description }} @@ -2978,7 +3216,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2988,6 +3225,9 @@ Accept wildcard characters: False ``` ### -MessageRecallEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MessageRecallEnabled Description }} @@ -2996,7 +3236,6 @@ This parameter is available only in the cloud-based service. Type: System.Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3006,13 +3245,15 @@ Accept wildcard characters: False ``` ### -MessageRecallMaxRecallableAge + +> Applicable: Exchange Online + {{ Fill MessageRecallMaxRecallableAge Description }} ```yaml Type: Microsoft.Exchange.Data.EnhancedTimeSpan Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3022,6 +3263,9 @@ Accept wildcard characters: False ``` ### -MessageRemindersEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MessageRemindersEnabled parameter enables or disables the message reminders feature in the organization. Valid values are: @@ -3033,7 +3277,6 @@ The MessageRemindersEnabled parameter enables or disables the message reminders Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3043,6 +3286,9 @@ Accept wildcard characters: False ``` ### -MicrosoftExchangeRecipientEmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types may be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter. @@ -3053,7 +3299,6 @@ Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAdd Type: ProxyAddressCollection Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3063,6 +3308,9 @@ Accept wildcard characters: False ``` ### -MicrosoftExchangeRecipientEmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter specifies whether the default email address policy is automatically applied to the Exchange recipient. The default value is $true. If this parameter is set to $true, Exchange automatically adds new email addresses to the Exchange recipient when email address policies are added or modified in the Exchange organization. If this parameter is set to $false, you must manually add new email addresses to the Exchange recipient when email address policies are added or modified. @@ -3073,7 +3321,6 @@ If you change the value of the MicrosoftExchangeRecipientEmailAddressPolicyEnabl Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3083,6 +3330,9 @@ Accept wildcard characters: False ``` ### -MicrosoftExchangeRecipientPrimarySmtpAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MicrosoftExchangeRecipientPrimarySmtpAddress parameter specifies the primary return SMTP email address for the Exchange recipient. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, you can't use the MicrosoftExchangeRecipientPrimarySmtpAddress parameter. @@ -3095,7 +3345,6 @@ The MicrosoftExchangeRecipientPrimarySmtpAddress parameter is meaningful only if Type: SmtpAddress Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3105,6 +3354,9 @@ Accept wildcard characters: False ``` ### -MicrosoftExchangeRecipientReplyRecipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MicrosoftExchangeRecipientReplyRecipient parameter specifies the recipient that should receive messages sent to the Exchange recipient. Typically, you would configure a mailbox to receive the messages sent to the Exchange recipient. You can use any value that uniquely identifies the recipient: For example: @@ -3120,7 +3372,6 @@ The MicrosoftExchangeRecipientReplyRecipient parameter specifies the recipient t Type: RecipientIdParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3130,6 +3381,9 @@ Accept wildcard characters: False ``` ### -MitigationsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MitigationsEnabled parameter specifies whether the Exchange Emergency Mitigation service (EM service) is enabled in the organization. Valid values are: @@ -3143,7 +3397,6 @@ For more information, see [Exchange Emergency Mitigation (EM) service](https://l Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3153,6 +3406,9 @@ Accept wildcard characters: False ``` ### -MobileAppEducationEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MobileAppEducationEnabled specifies whether to show or hide the Outlook for iOS and Android education reminder in Outlook on the web (formerly known as Outlook Web App). Valid values are: @@ -3166,7 +3422,6 @@ This setting will affect Outlook desktop at some point in the future. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3176,6 +3431,9 @@ Accept wildcard characters: False ``` ### -OabShadowDistributionOldestFileAgeLimit + +> Applicable: Exchange Server 2019 + This parameter is available only in on-premises Exchange. {{ Fill OabShadowDistributionOldestFileAgeLimit Description }} @@ -3184,7 +3442,6 @@ This parameter is available only in on-premises Exchange. Type: EnhancedTimeSpan Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -3194,6 +3451,9 @@ Accept wildcard characters: False ``` ### -OAuth2ClientProfileEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OAuth2ClientProfileEnabled parameter enables or disables modern authentication in the Exchange organization. Valid values are: - $true: modern authentication is enabled. @@ -3207,7 +3467,6 @@ When you enable modern authentication in Exchange Online, we recommend that you Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3217,6 +3476,9 @@ Accept wildcard characters: False ``` ### -OnlineMeetingsByDefaultEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Valid values are: @@ -3231,7 +3493,6 @@ If a user has already directly interacted with this setting in Outlook or Outloo Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3241,6 +3502,9 @@ Accept wildcard characters: False ``` ### -OrganizationSummary + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The OrganizationSummary parameter specifies a summarized description that best represents your organization. @@ -3249,7 +3513,6 @@ The OrganizationSummary parameter specifies a summarized description that best r Type: MultiValuedProperty Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3259,6 +3522,9 @@ Accept wildcard characters: False ``` ### -OutlookGifPickerDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookGifPickerDisabled parameter disables the GIF Search (powered by Bing) feature that's built into the Compose page in Outlook on the web. Valid values are: @@ -3270,7 +3536,6 @@ The OutlookGifPickerDisabled parameter disables the GIF Search (powered by Bing) Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3280,6 +3545,9 @@ Accept wildcard characters: False ``` ### -OutlookMobileGCCRestrictionsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookMobileGCCRestrictionsEnabled parameter specifies whether to enable or disable features within Outlook for iOS and Android that are not FedRAMP compliant for Microsoft 365 US Government Community Cloud (GCC) customers. Valid values are: @@ -3300,7 +3568,6 @@ The Outlook for iOS and Android feature and services that are not FedRAMP compli Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3310,6 +3577,9 @@ Accept wildcard characters: False ``` ### -OutlookMobileHelpShiftEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -3318,7 +3588,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3328,6 +3597,9 @@ Accept wildcard characters: False ``` ### -OutlookMobileSingleAccountEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -3336,7 +3608,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3346,6 +3617,9 @@ Accept wildcard characters: False ``` ### -OutlookPayEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookPayEnabled parameter enables or disables Microsoft Pay in the Microsoft 365 organization. Valid values are: @@ -3357,7 +3631,6 @@ The OutlookPayEnabled parameter enables or disables Microsoft Pay in the Microso Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3367,6 +3640,9 @@ Accept wildcard characters: False ``` ### -OutlookTextPredictionDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill OutlookTextPredictionDisabled Description }} @@ -3375,7 +3651,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3385,6 +3660,9 @@ Accept wildcard characters: False ``` ### -PermanentlyDeleteDisabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The PermanentlyDeleteDisabled parameter specifies whether to disable the PermanentlyDelete retention action for messaging records management (MRM). Valid values are: @@ -3398,7 +3676,6 @@ A message that's permanently deleted can't be recovered by using the Recoverable Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -3408,6 +3685,9 @@ Accept wildcard characters: False ``` ### -PerTenantSwitchToESTSEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter has been deprecated and is no longer used. @@ -3416,7 +3696,6 @@ This parameter has been deprecated and is no longer used. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3426,6 +3705,9 @@ Accept wildcard characters: False ``` ### -PostponeRoamingSignaturesUntilLater + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signatures are enabled or disabled in Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are: @@ -3445,7 +3727,6 @@ We have no plans to support roaming signature management in the Microsoft Graph Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3455,13 +3736,15 @@ Accept wildcard characters: False ``` ### -PreferredInternetCodePageForShiftJis + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```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 @@ -3471,13 +3754,15 @@ Accept wildcard characters: False ``` ### -PublicComputersDetectionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web will detect when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web will determine if the user is signing in from a public computer, and all public attachment handling rules will be applied and enforced. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3487,6 +3772,9 @@ Accept wildcard characters: False ``` ### -PublicFolderContentReplicationDisabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The PublicFolderContentReplicationDisabled parameter is used during public folder migration. When you set the PublicFolderContentReplicationDisabled parameter to $true, public folder content is not replicated to Exchange during the initial migration. The default value is $false. @@ -3495,7 +3783,6 @@ The PublicFolderContentReplicationDisabled parameter is used during public folde Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -3505,6 +3792,9 @@ Accept wildcard characters: False ``` ### -PublicFolderMailboxesLockedForNewConnections + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PublicFolderMailboxesLockedForNewConnections parameter specifies whether users are allowed to make new connections to public folder mailboxes. Valid values are: @@ -3516,7 +3806,6 @@ The PublicFolderMailboxesLockedForNewConnections parameter specifies whether use Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3526,6 +3815,9 @@ Accept wildcard characters: False ``` ### -PublicFolderMailboxesMigrationComplete + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration. @@ -3537,7 +3829,6 @@ The PublicFolderMailboxesMigrationComplete parameter is used during public folde Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3547,6 +3838,9 @@ Accept wildcard characters: False ``` ### -PublicFolderMigrationComplete + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PublicFolderMigrationComplete parameter is used during public folder migration. When you set the PublicFolderMigrationComplete parameter to $true, transport starts rerouting the queued messages to a new destination. The default value is $false. @@ -3555,7 +3849,6 @@ The PublicFolderMigrationComplete parameter is used during public folder migrati Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3565,6 +3858,9 @@ Accept wildcard characters: False ``` ### -PublicFoldersEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFoldersEnabled parameter specifies how public folders are deployed in your organization. Valid values are: - Local: The public folders are deployed locally in your organization. @@ -3575,7 +3871,6 @@ The PublicFoldersEnabled parameter specifies how public folders are deployed in Type: PublicFoldersDeployment Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3585,6 +3880,9 @@ Accept wildcard characters: False ``` ### -PublicFolderShowClientControl + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolderShowClientControl parameter enables or disables the control access feature for public folders in Microsoft Outlook. Valid values are: - $true: User access to public folders in Outlook is controlled by the value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet (the default value is $false). @@ -3594,7 +3892,6 @@ The PublicFolderShowClientControl parameter enables or disables the control acce Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3604,6 +3901,9 @@ Accept wildcard characters: False ``` ### -PublicFoldersLockedForMigration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PublicFoldersLockedForMigration parameter specifies whether users are locked out from accessing down level public folder servers. When you set the PublicFoldersLockedForMigration parameter to $true, users are locked out from accessing down level public folder servers. This is used for public folder migration during final stages. The default value is $false, which means that the user is able to access public folder servers. @@ -3612,7 +3912,6 @@ The PublicFoldersLockedForMigration parameter specifies whether users are locked Type: Boolean Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3622,13 +3921,15 @@ Accept wildcard characters: False ``` ### -ReadTrackingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReadTrackingEnabled parameter specifies whether the tracking for read status for messages in an organization is enabled. 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 @@ -3638,6 +3939,9 @@ Accept wildcard characters: False ``` ### -RecallReadMessagesEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RecallReadMessagesEnabled Description }} @@ -3646,7 +3950,6 @@ This parameter is available only in the cloud-based service. Type: System.Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3656,13 +3959,15 @@ Accept wildcard characters: False ``` ### -RefreshSessionEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3672,6 +3977,9 @@ Accept wildcard characters: False ``` ### -RejectDirectSend + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill RejectDirectSend Description }} @@ -3680,7 +3988,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3690,13 +3997,15 @@ Accept wildcard characters: False ``` ### -RemotePublicFolderMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemotePublicFolderMailboxes parameter specifies the identities of the public folder objects (represented as mail user objects locally) corresponding to the public folder mailboxes created in the remote forest. The public folder values set here are used only if the public folder deployment is a remote deployment. ```yaml Type: MultiValuedProperty Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3706,13 +4015,15 @@ Accept wildcard characters: False ``` ### -RequiredCharsetCoverage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```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 @@ -3722,6 +4033,9 @@ Accept wildcard characters: False ``` ### -SCLJunkThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SCLJunkThreshold parameter specifies the spam confidence level (SCL) threshold. Messages with an SCL greater than the value that you specify for the SCLJunkThreshold parameter are moved to the Junk Email folder. Valid values are integers from 0 through 9, inclusive. @@ -3730,7 +4044,6 @@ The SCLJunkThreshold parameter specifies the spam confidence level (SCL) thresho Type: Int32 Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3740,6 +4053,9 @@ Accept wildcard characters: False ``` ### -SendFromAliasEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). Valid values are: @@ -3753,7 +4069,6 @@ For more information about the availability of the feature in Outlook on the web Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3763,6 +4078,9 @@ Accept wildcard characters: False ``` ### -SharedDomainEmailAddressFlowEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill SharedDomainEmailAddressFlowEnabled Description }} @@ -3771,7 +4089,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3781,13 +4098,15 @@ Accept wildcard characters: False ``` ### -SiteMailboxCreationURL + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SiteMailboxCreationURL parameter specifies the URL that's used to create site mailboxes. Site mailboxes improve collaboration and user productivity by allowing access to both SharePoint documents and Exchange email in Outlook 2013 or later. ```yaml Type: Uri Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3797,6 +4116,9 @@ Accept wildcard characters: False ``` ### -SmtpActionableMessagesEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SmtpActionableMessagesEnabled parameter specifies whether to enable or disable action buttons in email messages in Outlook on the web. Valid values are: - $true: Action buttons in email messages are enabled. This is the default value. @@ -3806,7 +4128,6 @@ The SmtpActionableMessagesEnabled parameter specifies whether to enable or disab Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3816,6 +4137,9 @@ Accept wildcard characters: False ``` ### -TenantAdminNotificationForDelayedDelicensingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The TenantAdminNotificationForDelayedDelicensingEnabled parameter enables or disables weekly admin Service Health advisory notifications that are sent to admins. Valid values are: @@ -3833,7 +4157,6 @@ Use the EndUserMailNotificationForDelayedDelicensingEnabled to send affected use Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3843,6 +4166,9 @@ Accept wildcard characters: False ``` ### -TwoClickMailPreviewEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill TwoClickMailPreviewEnabled Description }} @@ -3851,7 +4177,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3861,6 +4186,9 @@ Accept wildcard characters: False ``` ### -UMAvailableLanguages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter has been deprecated and is no longer used. @@ -3869,7 +4197,6 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3879,13 +4206,15 @@ Accept wildcard characters: False ``` ### -UnblockUnsafeSenderPromptEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: ShortenEventScopeParameter, AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3895,6 +4224,9 @@ Accept wildcard characters: False ``` ### -UseIcsSyncStateStreaming + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. {{ Fill UseIcsSyncStateStreaming Description }} @@ -3903,7 +4235,6 @@ This parameter is available only in on-premises Exchange. Type: SwitchParameter Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3913,6 +4244,9 @@ Accept wildcard characters: False ``` ### -VisibleMeetingUpdateProperties + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates will be auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated. @@ -3948,7 +4282,6 @@ In the following scenarios, meeting update messages are not auto-processed, rega Type: String Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3958,6 +4291,9 @@ Accept wildcard characters: False ``` ### -WACDiscoveryEndpoint + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The WacDiscoveryEndpoint parameter specifies the discovery endpoint for Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) for all mailboxes in the organization. For example, `https://oos.internal.contoso.com/hosting/discovery`. @@ -3968,7 +4304,6 @@ Office Online Server enables users to view supported file attachments in Outlook Type: String Parameter Sets: AdfsAuthenticationParameter, AdfsAuthenticationRawConfiguration Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -3978,6 +4313,9 @@ Accept wildcard characters: False ``` ### -WebPushNotificationsDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WebPushNotificationsDisabled parameter specifies whether to enable or disable Web Push Notifications in Outlook on the Web. This feature provides web push notifications which appear on a user's desktop while the user is not using Outlook on the Web. This brings awareness of incoming messages while they are working elsewhere on their computer. Valid values are: @@ -3989,7 +4327,6 @@ The WebPushNotificationsDisabled parameter specifies whether to enable or disabl Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -3999,6 +4336,9 @@ Accept wildcard characters: False ``` ### -WebSuggestedRepliesDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WebSuggestedRepliesDisabled parameter specifies whether to enable or disable Suggested Replies in Outlook on the web. This feature provides suggested replies to emails so users can easily and quickly respond to messages. Valid values are: @@ -4010,7 +4350,6 @@ The WebSuggestedRepliesDisabled parameter specifies whether to enable or disable Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -4020,13 +4359,15 @@ 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 @@ -4036,6 +4377,9 @@ Accept wildcard characters: False ``` ### -WorkspaceTenantEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WorkspaceTenantEnabled parameter enables or disables workspace booking in the organization. Valid values are: @@ -4047,7 +4391,6 @@ The WorkspaceTenantEnabled parameter enables or disables workspace booking in th Type: Boolean Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md similarity index 84% rename from exchange/exchange-ps/exchange/Set-OrganizationRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md index f21e2920e4..1a353d17dc 100644 --- a/exchange/exchange-ps/exchange/Set-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationrelationship applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-OrganizationRelationship -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationrelationship +schema: 2.0.0 +title: Set-OrganizationRelationship --- # Set-OrganizationRelationship @@ -72,6 +73,9 @@ This example disables the organization relationship with Contoso ## 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 relationship that you want to modify. You can use any value that uniquely identifies the organization relationship. For example: - Name @@ -82,7 +86,6 @@ The Identity parameter specifies the organization relationship that you want to 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: True Position: 1 @@ -92,6 +95,9 @@ Accept wildcard characters: False ``` ### -ArchiveAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are: - $true: The external organization provides remote access to mailbox archives. @@ -101,7 +107,6 @@ The ArchiveAccessEnabled parameter specifies whether the organization relationsh 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 @@ -111,6 +116,9 @@ 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`. @@ -120,7 +128,6 @@ 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 @@ -130,6 +137,9 @@ Accept wildcard characters: False ``` ### -DeliveryReportEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are: - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization. @@ -141,7 +151,6 @@ For message tracking to work in a cross-premises Exchange scenario, this paramet 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 @@ -151,6 +160,9 @@ 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. @@ -159,7 +171,6 @@ 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,13 +180,15 @@ Accept wildcard characters: False ``` ### -DomainNames + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The DomainNames parameter specifies the SMTP domains of the external organization. You can specify multiple domains separated by commas (for example, "contoso.com","northamerica.contoso.com"). ```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 @@ -185,6 +198,9 @@ 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 to enable the organization relationship. Valid values are: - $true: The organization relationship is enabled. This is the default value. @@ -194,7 +210,6 @@ The Enabled parameter specifies whether to enable the organization relationship. 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 @@ -204,6 +219,9 @@ 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. @@ -212,7 +230,6 @@ 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 @@ -222,6 +239,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are: - $true: Free/busy information is retrieved from the external organization. @@ -233,7 +253,6 @@ You control the free/busy access level and scope by using the FreeBusyAccessLeve 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 @@ -243,6 +262,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are: - None: No free/busy access. @@ -255,7 +277,6 @@ This parameter is only meaningful when the FreeBusyAccessEnabled parameter value Type: FreeBusyAccessLevel 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 @@ -265,6 +286,9 @@ Accept wildcard characters: False ``` ### -FreeBusyAccessScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example: - Name @@ -278,7 +302,6 @@ This parameter is only meaningful when the FreeBusyAccessEnabled parameter value Type: GroupIdParameter 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,6 +311,9 @@ Accept wildcard characters: False ``` ### -MailboxMoveCapability + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The MailboxMoveCapability parameter is used in cross-tenant mailbox migrations. Valid values are: @@ -303,7 +329,6 @@ For more information, see [Cross-tenant mailbox migration](https://learn.microso Type: MailboxMoveCapability Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -313,6 +338,9 @@ Accept wildcard characters: False ``` ### -MailboxMoveEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are: - $true: Mailbox moves to or from the external organization are allowed. @@ -322,7 +350,6 @@ The MailboxMoveEnabled parameter specifies whether the organization relationship 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 @@ -332,6 +359,9 @@ Accept wildcard characters: False ``` ### -MailboxMovePublishedScopes + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The MailboxMovePublishedScopes parameter is used in cross-tenant mailbox migrations to specify the mail-enabled security groups whose members are allowed to migrate. You can use any value that uniquely identifies the group. For example: @@ -351,7 +381,6 @@ For more information, see [Cross-tenant mailbox migration](https://learn.microso Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -361,6 +390,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are: - $true: MailTips for users in this organization are returned over the organization relationship. @@ -372,7 +404,6 @@ You control the MailTips access level by using the MailTipsAccessLevel parameter 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 @@ -382,6 +413,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessLevel parameter specifies the level of MailTips data externally shared over this organization relationship. This parameter can have the following values: - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned. @@ -394,7 +428,6 @@ This parameter is only meaningful when the MailTipsAccessEnabled parameter value Type: MailTipsAccessLevel 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 @@ -404,6 +437,9 @@ Accept wildcard characters: False ``` ### -MailTipsAccessScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MailTipsAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example: - Name @@ -427,7 +463,6 @@ This restriction only applies to mailboxes, mail users, and mail contacts. It do Type: GroupIdParameter 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 @@ -437,13 +472,15 @@ Accept wildcard characters: False ``` ### -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 organization relationship. The maximum length is 64 characters. ```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 @@ -453,6 +490,9 @@ Accept wildcard characters: False ``` ### -OAuthApplicationId + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The OAuthApplicationId is used in cross-tenant mailbox migrations to specify the application ID of the mailbox migration app that you consented to. For more information, see [Cross-tenant mailbox migration](https://learn.microsoft.com/microsoft-365/enterprise/cross-tenant-mailbox-migration). @@ -461,7 +501,6 @@ The OAuthApplicationId is used in cross-tenant mailbox migrations to specify the Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -471,13 +510,15 @@ Accept wildcard characters: False ``` ### -OrganizationContact + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OrganizationContact parameter specifies the email address that can be used to contact the external organization (for example, administrator@fourthcoffee.com). ```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 @@ -487,6 +528,9 @@ Accept wildcard characters: False ``` ### -PhotosEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are: - $true: Photos for users in this organization are returned over the organization relationship. @@ -496,7 +540,6 @@ The PhotosEnabled parameter specifies whether photos for users in the internal o 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 @@ -506,13 +549,15 @@ Accept wildcard characters: False ``` ### -TargetApplicationUri + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetApplicationUri parameter specifies the target Uniform Resource Identifier (URI) of the external organization. The TargetApplicationUri parameter is specified by Exchange when requesting a delegated token to retrieve free and busy information, for example, mail.contoso.com. ```yaml Type: Uri 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 @@ -522,13 +567,15 @@ Accept wildcard characters: False ``` ### -TargetAutodiscoverEpr + +> Applicable: Exchange Server 2010, 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, for example, `https://contoso.com/autodiscover/autodiscover.svc/wssecurity`. Exchange uses Autodiscover to automatically detect the correct Exchange server endpoint to use for external requests. ```yaml Type: Uri 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 @@ -538,13 +585,15 @@ Accept wildcard characters: False ``` ### -TargetOwaURL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook Web App) URL of the external organization that's defined in the organization relationship. It is used for Outlook on the web redirection in a cross-premise Exchange scenario. Configuring this attribute enables users in the organization to use their current Outlook on the web URL to access Outlook on the web in the external organization. ```yaml Type: Uri 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 @@ -554,6 +603,9 @@ Accept wildcard characters: False ``` ### -TargetSharingEpr + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services for the external organization. If you use this parameter, this URL is always used to reach the external Exchange server. TheURL that's specified by the TargetAutoDiscoverEpr parameter isn't used to locate the external Exchange server. @@ -562,7 +614,6 @@ If you use this parameter, this URL is always used to reach the external Exchang Type: Uri 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 @@ -572,13 +623,15 @@ 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/exchange/Set-OrganizationSegment.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationSegment.md similarity index 97% rename from exchange/exchange-ps/exchange/Set-OrganizationSegment.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OrganizationSegment.md index 49cf493921..97464a039b 100644 --- a/exchange/exchange-ps/exchange/Set-OrganizationSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationSegment.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationsegment applicable: Security & Compliance -title: Set-OrganizationSegment -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-organizationsegment +schema: 2.0.0 +title: Set-OrganizationSegment --- # Set-OrganizationSegment @@ -43,6 +44,9 @@ In this example, for the segment that has the GUID c96e0837-c232-4a8a-841e-ef457 ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the organization segment that you want to modify. You can use any value that uniquely identifies the segment. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the organization segment that you want to modif Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 0 @@ -63,6 +66,9 @@ Accept wildcard characters: False ``` ### -UserGroupFilter + +> Applicable: Security & Compliance + The UserGroupFilter parameter uses OPATH filter syntax to specify the members of the organization segment. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"MemberOf -eq 'Engineering Department'"` or `"ExtensionAttribute1 -eq 'DayTrader'"`). - 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. @@ -76,7 +82,6 @@ Use the same property for all of your segments, and verify that your segments do Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-OutboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md index a73f8dfcd5..6b3cd3576d 100644 --- a/exchange/exchange-ps/exchange/Set-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-outboundconnector applicable: Exchange Online, Exchange Online Protection -title: Set-OutboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-outboundconnector +schema: 2.0.0 +title: Set-OutboundConnector --- # Set-OutboundConnector @@ -63,6 +64,9 @@ This example changes the settings of the existing Outbound connector named Conto ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the connector you want to modify. You can use any value that uniquely identifies the connector. For example: - Name @@ -73,7 +77,6 @@ The Identity parameter specifies the connector you want to modify. You can use a Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -83,6 +86,9 @@ Accept wildcard characters: False ``` ### -AllAcceptedDomains + +> Applicable: Exchange Online, Exchange Online Protection + The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are: - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value. @@ -94,7 +100,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -104,6 +109,9 @@ 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. @@ -117,7 +125,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -127,13 +134,15 @@ 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 @@ -143,6 +152,9 @@ 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`. @@ -152,7 +164,6 @@ 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 @@ -162,6 +173,9 @@ Accept wildcard characters: False ``` ### -ConnectorSource + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorSource parameter specifies how the connector is created. Valid values are: - Default: The connector is manually created. This is the default value for manually created connectors, and we recommend that you don't change this value. @@ -172,7 +186,6 @@ The ConnectorSource parameter specifies how the connector is created. Valid valu Type: TenantConnectorSource Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -182,6 +195,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid values are: - Partner: The connector services domains that are external to your organization. @@ -191,7 +207,6 @@ The ConnectorType parameter specifies a category for the domains that are servic Type: TenantConnectorType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -201,6 +216,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online, Exchange Online Protection + The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are: - $true: The connector is enabled. This is the default value. @@ -210,7 +228,6 @@ The Enabled parameter specifies whether to enable or disable the Outbound connec Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -220,6 +237,9 @@ Accept wildcard characters: False ``` ### -IsTransportRuleScoped + +> Applicable: Exchange Online, Exchange Online Protection + The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are: - $true: The connector is associated with a transport rule. @@ -231,7 +251,6 @@ You scope a transport rule to an Outbound connector by using the RouteMessageOut Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -241,6 +260,9 @@ Accept wildcard characters: False ``` ### -IsValidated + +> Applicable: Exchange Online, Exchange Online Protection + The IsValidated parameter specifies whether the Outbound connector has been validated. Valid values are: - $true: The connector has been validated, @@ -252,7 +274,6 @@ Use the Validate-OutboundConnector cmdlet to validate the connector. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -262,6 +283,9 @@ Accept wildcard characters: False ``` ### -LastValidationTimestamp + +> Applicable: Exchange Online, Exchange Online Protection + The LastValidationTimestamp parameter specifies the date/time that the Outbound connector was validated. To specify a date/time value for this parameter, use either of the following options: @@ -275,7 +299,6 @@ Use the Validate-OutboundConnector cmdlet to validate the connector. Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -285,13 +308,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online, Exchange Online Protection + The Name parameter specifies the unique name for the connector. 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: False Position: Named @@ -301,6 +326,9 @@ Accept wildcard characters: False ``` ### -RecipientDomains + +> Applicable: Exchange Online, Exchange Online Protection + The RecipientDomains parameter specifies the domain that the Outbound connector routes mail to. You can specify multiple domains separated by commas. 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. @@ -309,7 +337,6 @@ You can use a wildcard character to specify all subdomains of a specified domain Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -319,6 +346,9 @@ Accept wildcard characters: False ``` ### -RouteAllMessagesViaOnPremises + +> Applicable: Exchange Online, Exchange Online Protection + The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system. Valid values are: - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. @@ -330,7 +360,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -340,6 +369,9 @@ Accept wildcard characters: False ``` ### -SenderRewritingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are: - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value. @@ -351,7 +383,6 @@ This parameter is effective only for OnPremises connectors. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -361,6 +392,9 @@ Accept wildcard characters: False ``` ### -SmartHosts + +> Applicable: Exchange Online, Exchange Online Protection + The SmartHosts parameter specifies the smart host that the Outbound connector uses to route mail. Valid values are: - FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record: For example, mail.contoso.com. @@ -375,7 +409,6 @@ This parameter is required if you use the value $false for the UseMxRecord param Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -385,6 +418,9 @@ Accept wildcard characters: False ``` ### -TestMode + +> Applicable: Exchange Online, Exchange Online Protection + The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are: - $true: Test mode is enabled. @@ -394,7 +430,6 @@ The TestMode parameter specifies whether you want to enabled or disable test mod Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -404,6 +439,9 @@ Accept wildcard characters: False ``` ### -TlsDomain + +> Applicable: Exchange Online, Exchange Online Protection + The TlsDomain parameter specifies the domain name that the Outbound connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. A valid value for this parameter is an SMTP domain. Wildcards are supported to specify all subdomains of a domain (for example, \*.contoso.com), but you can't embed the wildcard character within the domain (for example, domain.\*.contoso.com). @@ -414,7 +452,6 @@ This parameter meaningful only when the TlsSettings value is DomainValidation. Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -424,6 +461,9 @@ Accept wildcard characters: False ``` ### -TlsSettings + +> Applicable: Exchange Online, Exchange Online Protection + The TlsSettings parameter specifies the TLS authentication level that's used for outbound TLS connections established by this Outbound connector. Valid values are: - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. @@ -435,7 +475,6 @@ The TlsSettings parameter specifies the TLS authentication level that's used for Type: TlsAuthLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -445,6 +484,9 @@ Accept wildcard characters: False ``` ### -UseMXRecord + +> Applicable: Exchange Online, Exchange Online Protection + The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are: - $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value. @@ -454,7 +496,6 @@ The UseMXRecord parameter enables or disables DNS routing for the connector. Val Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -464,13 +505,15 @@ Accept wildcard characters: False ``` ### -ValidationRecipients + +> Applicable: Exchange Online, Exchange Online Protection + The ValidationRecipients parameter specifies the email addresses of the validation recipients for the Outbound connector. You can specify multiple email addresses separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -480,13 +523,15 @@ 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/exchange/Set-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-OutlookAnywhere.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md index bdc199f0c5..a1728d35b0 100644 --- a/exchange/exchange-ps/exchange/Set-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookanywhere applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-OutlookAnywhere -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookanywhere +schema: 2.0.0 +title: Set-OutlookAnywhere --- # Set-OutlookAnywhere @@ -87,6 +88,9 @@ In Exchange 2010 and Exchange 2013, this example sets the available authenticati ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -99,7 +103,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -109,6 +112,9 @@ Accept wildcard characters: False ``` ### -ClientAuthenticationMethod + +> Applicable: Exchange Server 2010 + This parameter is available only in 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: @@ -122,7 +128,6 @@ Although you can use this parameter to set only one authentication method, the c Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -132,6 +137,9 @@ 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,7 +149,6 @@ 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 @@ -151,6 +158,9 @@ Accept wildcard characters: False ``` ### -DefaultAuthenticationMethod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultAuthenticationMethod parameter specifies the default authentication method for Outlook Anywhere. This parameter replaces the existing ExternalClientAuthenticationMethod, InternalClientAuthenticationMethod and IISAuthenticationMethods property values with the value you specify. Valid values are: - Basic @@ -163,7 +173,6 @@ You can't use this parameter with the ExternalClientAuthenticationMethod, Intern Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -173,13 +182,15 @@ 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,6 +200,9 @@ 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. @@ -201,7 +215,6 @@ 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 @@ -211,6 +224,9 @@ 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. @@ -220,7 +236,6 @@ 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 @@ -230,6 +245,9 @@ 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. @@ -242,7 +260,6 @@ 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 @@ -252,6 +269,9 @@ Accept wildcard characters: False ``` ### -ExternalClientAuthenticationMethod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate external Outlook Anywhere clients. Valid values are: - Basic @@ -264,7 +284,6 @@ You can't use this parameter with the DefaultAuthenticationMethods parameter. Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -274,6 +293,9 @@ Accept wildcard characters: False ``` ### -ExternalClientsRequireSsl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are: - $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL. @@ -285,7 +307,6 @@ The value of this parameter is related to the value of the SSLOffloading paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -295,13 +316,15 @@ Accept wildcard characters: False ``` ### -ExternalHostname + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalHostname parameter specifies the external hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com. ```yaml Type: Hostname Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -311,6 +334,9 @@ Accept wildcard characters: False ``` ### -IISAuthenticationMethods + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IISAuthenticationMethods parameter specifies the authentication method that's used on the Outlook Anywhere virtual directory in IIS. Valid values are: - Basic @@ -325,7 +351,6 @@ You can't use this parameter with the DefaultAuthenticationMethods parameter. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -335,6 +360,9 @@ Accept wildcard characters: False ``` ### -InternalClientAuthenticationMethod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are: - Basic @@ -347,7 +375,6 @@ You can't use this parameter with the DefaultAuthenticationMethods parameter. Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,6 +384,9 @@ Accept wildcard characters: False ``` ### -InternalClientsRequireSsl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are: - $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL. @@ -368,7 +398,6 @@ The value of this parameter is related to the value of the SSLOffloading paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -378,13 +407,15 @@ Accept wildcard characters: False ``` ### -InternalHostname + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalHostname parameter specifies the internal hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -394,13 +425,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the Outlook Anywhere virtual directory. The default value is Rpc (Default Web Site). If the value you specify 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 @@ -410,6 +443,9 @@ Accept wildcard characters: False ``` ### -SSLOffloading + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are: - $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value. @@ -425,7 +461,6 @@ The value of this parameter is related to the values of the ExternalClientsRequi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -435,13 +470,15 @@ 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/exchange/Set-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md index 9e222994d5..1dc8022bb0 100644 --- a/exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookprotectionrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-OutlookProtectionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookprotectionrule +schema: 2.0.0 +title: Set-OutlookProtectionRule --- # Set-OutlookProtectionRule @@ -64,13 +65,15 @@ This example sets the priority of the Outlook protection rule OPR-DG-Finance to ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the rule. ```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 @@ -80,13 +83,15 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionTemplate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplyRightsProtectionTemplate parameter specifies an RMS template to be applied to messages matching the conditions. ```yaml Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -96,6 +101,9 @@ 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`. @@ -105,7 +113,6 @@ 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 @@ -115,6 +122,9 @@ 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,7 +133,6 @@ 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,6 +142,9 @@ 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. Use this switch to suppress the confirmation prompt that appears when you modify a rule with no conditions (the rule applies to all messages). @@ -141,7 +153,6 @@ Use this switch to suppress the confirmation prompt that appears when you modify 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 @@ -151,13 +162,15 @@ Accept wildcard characters: False ``` ### -FromDepartment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FromDepartment parameter specifies a department name. The rule is applied to messages where the sender's department attribute matches this value. ```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 @@ -167,13 +180,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a name for the rule. ```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 @@ -183,6 +198,9 @@ 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 Outlook protection rule. Rule priority values can range from 0 through n-1, where n is the total number of existing Outlook protection rules. Any existing rules with priority equal to or higher than the priority being set have their priority incremented by 1. @@ -191,7 +209,6 @@ Any existing rules with priority equal to or higher than the priority being set 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 @@ -201,6 +218,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SentTo parameter specifies one or more recipients. External recipients can be specified using the SMTP address. Internal recipients can be specified using any of the following values: @@ -216,7 +236,6 @@ Internal recipients can be specified using any of the following values: 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 @@ -226,6 +245,9 @@ Accept wildcard characters: False ``` ### -SentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SentToScope parameter specifies the scope of messages to which the rule applies. Valid values include: - All: Applies to all messages. @@ -237,7 +259,6 @@ If not specified, the parameter defaults to All. Type: ToUserScope Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -247,6 +268,9 @@ Accept wildcard characters: False ``` ### -UserCanOverride + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UserCanOverride parameter specifies whether the Outlook user can override the rule behavior, either by using a different RMS template, or by removing rights protection before sending the message. Valid values include: - $true: User can override rule action. @@ -256,7 +280,6 @@ The UserCanOverride parameter specifies whether the Outlook user can override th 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 @@ -266,13 +289,15 @@ 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/exchange/Set-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-OutlookProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md index 3d9413c338..f42e568a0e 100644 --- a/exchange/exchange-ps/exchange/Set-OutlookProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-OutlookProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-outlookprovider +schema: 2.0.0 +title: Set-OutlookProvider --- # Set-OutlookProvider @@ -51,13 +52,15 @@ This example changes the duration that the Autodiscover service settings are val ## 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 for which you want to set global settings. ```yaml Type: OutlookProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -67,6 +70,9 @@ Accept wildcard characters: False ``` ### -CertPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CertPrincipalName parameter specifies the Secure Sockets Layer (SSL) certificate principal name required for connecting to Exchange from an external location. This parameter is only used for Outlook Anywhere clients. @@ -75,7 +81,6 @@ This parameter is only used for Outlook Anywhere clients. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -85,6 +90,9 @@ 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,7 +102,6 @@ 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,13 +111,15 @@ 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 @@ -120,13 +129,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a common name for the Outlook Provider Configuration object. This can be a user-friendly name for identification. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,13 +147,15 @@ Accept wildcard characters: False ``` ### -OutlookProviderFlags + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutlookProviderFlags parameter specifies how Outlook clients should connect to the Exchange server. The value can be set to ServerExclusiveConnect, ExternalClientsRequireSSL, InternalClientsRequireSSL or to None to clear the flags. The recommended value is None, which is also the default setting. ```yaml Type: OutlookProviderFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -152,6 +165,9 @@ Accept wildcard characters: False ``` ### -RequiredClientVersions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequiredClientVersions parameter specifies the minimum version of Microsoft Outlook that's allowed to connect to the Exchange server. This information is in the Autodiscover response to the client connection request. This parameter uses the syntax `"MinimumVersion, ExpirationDate"`. MinimumVersion is the version of Outlook in the format xx.x.xxxx.xxxx. For example, to specify Outlook 2010 Service Pack 2 (SP2), use the value 14.0.7012.1000. @@ -164,7 +180,6 @@ An example of a valid value for this parameter is `"14.0.7012.1000, 2020-01-01T1 Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -174,13 +189,15 @@ 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 use for Outlook Anywhere clients. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -190,6 +207,9 @@ Accept wildcard characters: False ``` ### -TTL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TTL parameter specifies the duration (in hours) that the specified settings are valid. If a value is specified, the settings are rediscovered via the Autodiscover service after the duration specified with this parameter. A value of 0 indicates that no rediscovery is required. The default value is 1 hour. @@ -198,7 +218,6 @@ If a value is specified, the settings are rediscovered via the Autodiscover serv Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -208,13 +227,15 @@ 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/exchange/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md index 6c5b1f1756..e1e688a148 100644 --- a/exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-owamailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-OwaMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-owamailboxpolicy +schema: 2.0.0 +title: Set-OwaMailboxPolicy --- # Set-OwaMailboxPolicy @@ -199,6 +200,9 @@ This example disables Outlook UserVoice for the default mailbox policy in Micros ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the Outlook on the web mailbox policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -209,7 +213,6 @@ The Identity parameter specifies the Outlook on the web mailbox policy that you Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -219,6 +222,9 @@ Accept wildcard characters: False ``` ### -AccountTransferEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -227,7 +233,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -237,6 +242,9 @@ Accept wildcard characters: False ``` ### -ActionForUnknownFileAndMIMETypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: - Allow (This is the default value.) @@ -247,7 +255,6 @@ The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file type Type: AttachmentBlockingActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -257,6 +264,9 @@ Accept wildcard characters: False ``` ### -AdditionalStorageProvidersAvailable + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AdditionalStorageProvidersAvailable parameter specifies whether to allow additional storage providers (for example, Box, Dropbox, Facebook, Google Drive, Egnyte, personal OneDrive) attachments in Outlook on the web. Valid values are: @@ -268,7 +278,6 @@ The AdditionalStorageProvidersAvailable parameter specifies whether to allow add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -278,6 +287,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncIntegrationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: - $true: ActiveSync is available in Outlook on the web. This is the default value. @@ -287,7 +299,6 @@ The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disabl 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 @@ -297,6 +308,9 @@ Accept wildcard characters: False ``` ### -AdditionalAccountsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter has been deprecated and is no longer used. @@ -307,7 +321,6 @@ To enable or disable personal accounts in the new Outlook for Windows, use the P Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -317,6 +330,9 @@ Accept wildcard characters: False ``` ### -AllAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: - $true: All address lists are visible in Outlook on the web. This is the default value. @@ -326,7 +342,6 @@ The AllAddressListsEnabled parameter specifies which address lists are available 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 @@ -336,6 +351,9 @@ Accept wildcard characters: False ``` ### -AllowCopyContactsToDeviceAddressBook + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: - $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. @@ -345,7 +363,6 @@ The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can c Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -355,6 +372,9 @@ Accept wildcard characters: False ``` ### -AllowedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowedFileTypes parameter specifies the attachment file types (file extensions) that can be saved locally or viewed from Outlook on the web. The default values are: .avi, .bmp, .doc, .docm, .docx, .gif, .jpg, .mp3, .one, .pdf, .png, .ppsm, .ppsx, .ppt, .pptm, .pptx, .pub, .rpmsg, .rtf, .tif, .tiff, .txt, .vsd, .wav, .wma, .wmv, .xls, .xlsb, .xlsm, .xlsx, .zip @@ -372,7 +392,6 @@ If the same file types are specified in multiple lists: 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 @@ -382,6 +401,9 @@ Accept wildcard characters: False ``` ### -AllowedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowedMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be saved locally or viewed from Outlook on the web. The default values are: - image/bmp @@ -402,7 +424,6 @@ If the same MIME types are specified in multiple lists: 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 @@ -412,6 +433,9 @@ Accept wildcard characters: False ``` ### -AllowedOrganizationAccountDomains + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The AllowedOrganizationAccountDomains parameter specifies domains where users can add work or school email accounts in the new Outlook for Windows. The default value is blank ($null), which allows work or school accounts from any domain. Setting this parameter to an empty list ([]) prevents any work or school accounts from being added. @@ -420,7 +444,6 @@ The AllowedOrganizationAccountDomains parameter specifies domains where users ca Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -430,6 +453,9 @@ Accept wildcard characters: False ``` ### -AllowOfflineOn + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The AllowOfflineOn parameter specifies when Outlook Web App in offline mode is available for supported web browsers. Valid values are: @@ -444,7 +470,6 @@ When offline mode is available, users can turn offline mode on or off themselves Type: AllowOfflineOnEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -454,6 +479,9 @@ Accept wildcard characters: False ``` ### -BizBarEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BizBarEnabled Description }} @@ -462,7 +490,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -472,6 +499,9 @@ Accept wildcard characters: False ``` ### -BlockedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BlockedFileTypes parameter specifies a list of attachment file types (file extensions) that can't be saved locally or viewed from Outlook on the web. The default values are: .ade, .adp, .apk, .app, .appcontent-ms, .application, .appref-ms, .appx, .asp, .aspx, .asx, .bas, .bat, .bgi, .cab, .cdxml, .cer, .chm, .cmd, .cnt, .com, .cpl, .crt, .csh, .der, .diagcab, .exe, .fxp, .gadget, .grp, .hlp, .hpj, .hta, .htc, .img, .inf, .ins, .iso, .isp, .its, .jar, .jnlp, .js, .jse, .ksh, .library-ms, .lnk, .mad, .maf, .mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mcf, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .mht, .mhtml, .msc, .msh, .msh1, .msh1xml, .msh2, .msh2xml, .mshxml, .msi, .msp, .mst, .msu, .ops, .osd, .pcd, .pif, .pl, .plg, .prf, .prg, .printerexport, .ps1, .ps1xml, .ps2, .ps2xml, .psc1, .psc2, .psd1, .psdm1, .pssc, .pst, .py, .pyc, .pyo, .pyw, .pyz, .pyzw, .reg, .scf, .scr, .sct, .search-ms, .settingcontent-ms, .shb, .shs, .theme, .tmp, .udl, .url, .vb, .vbe, .vbp, .vbs, .vhd, .vhdx, .vsmacros, .vsw, .webpnp, .website, .ws, .wsb, .wsc, .wsf, .wsh, .xbap, .xll, .xnk @@ -489,7 +519,6 @@ If the same file types are specified in multiple lists: 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 @@ -499,6 +528,9 @@ Accept wildcard characters: False ``` ### -BlockedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The BlockedMimeTypes parameter specifies MIME extensions in attachments that prevent the attachments from being saved locally or viewed from Outlook on the web. The default values are: - application/hta @@ -523,7 +555,6 @@ If the same MIME types are specified in multiple lists: 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 @@ -533,6 +564,9 @@ Accept wildcard characters: False ``` ### -BookingsMailboxCreationEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The BookingsMailboxCreationEnabled parameter allows you disable Microsoft Bookings. @@ -541,7 +575,6 @@ The BookingsMailboxCreationEnabled parameter allows you disable Microsoft Bookin Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -551,6 +584,9 @@ Accept wildcard characters: False ``` ### -BookingsMailboxDomain + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill BookingsMailboxDomain Description }} @@ -559,7 +595,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -569,6 +604,9 @@ Accept wildcard characters: False ``` ### -BoxAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -577,7 +615,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -587,6 +624,9 @@ Accept wildcard characters: False ``` ### -CalendarEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook Web App. Valid values are: @@ -598,7 +638,6 @@ The CalendarEnabled parameter specifies whether to enable or disable the calenda 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 @@ -608,6 +647,9 @@ Accept wildcard characters: False ``` ### -ChangePasswordEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: @@ -619,7 +661,6 @@ The ChangePasswordEnabled parameter specifies whether users can change their pas 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 @@ -629,6 +670,9 @@ Accept wildcard characters: False ``` ### -ChangeSettingsAccountEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in the new Outlook for Windows. Valid values are: @@ -642,7 +686,6 @@ The ChangeSettingsAccountEnabled parameter specifies whether users can change th Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -652,6 +695,9 @@ Accept wildcard characters: False ``` ### -ClassicAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: - $true: Users can attach local files to email messages in Outlook on the web. This is the default value. @@ -661,7 +707,6 @@ The ClassicAttachmentsEnabled parameter specifies whether users can attach local Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -671,6 +716,9 @@ Accept wildcard characters: False ``` ### -ConditionalAccessPolicy + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ConditionalAccessPolicy parameter specifies the Outlook on the Web Policy for limited access. For this feature to work properly, you also need to configure a Conditional Access policy in the Microsoft Entra admin center. @@ -687,7 +735,6 @@ Valid values are: Type: PolicyEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -697,6 +744,9 @@ 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`. @@ -706,7 +756,6 @@ 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 @@ -716,6 +765,9 @@ Accept wildcard characters: False ``` ### -ContactsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook Web App. Valid values are: @@ -727,7 +779,6 @@ The ContactsEnabled parameter specifies whether to enable or disable Contacts in 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 @@ -737,13 +788,15 @@ Accept wildcard characters: False ``` ### -DefaultClientLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been deprecated and is no longer 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 @@ -753,6 +806,9 @@ Accept wildcard characters: False ``` ### -DefaultTheme + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. @@ -761,7 +817,6 @@ Note that this parameter is a text string, and the value you specify isn't valid 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 @@ -771,6 +826,9 @@ Accept wildcard characters: False ``` ### -DelegateAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook on the web or Outlook Web App to open folders that they have delegate access to. Valid values are: @@ -782,7 +840,6 @@ The DelegateAccessEnabled parameter specifies whether delegates can use Outlook 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 @@ -792,6 +849,9 @@ Accept wildcard characters: False ``` ### -DirectFileAccessOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: - $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. @@ -803,7 +863,6 @@ By default in Exchange 2013 or later and Exchange Online, all Outlook on the web 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 @@ -813,6 +872,9 @@ Accept wildcard characters: False ``` ### -DirectFileAccessOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DirectFileAccessOnPublicComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: - $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. @@ -824,7 +886,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo 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 @@ -834,6 +895,9 @@ Accept wildcard characters: False ``` ### -DisableFacebook + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. **Note**: Facebook integration is no longer available. For more information, see [Facebook Connect is no longer available](https://support.microsoft.com/office/facebook-connect-is-no-longer-available-f31c8107-7b5a-4e3d-8a22-e506dacb6db6). @@ -849,7 +913,6 @@ The value of this switch is stored in the FacebookEnabled property in the output Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -859,6 +922,9 @@ Accept wildcard characters: False ``` ### -DisplayPhotosEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: - $true: Users see sender photos in Outlook on the web. This is the default value. @@ -868,7 +934,6 @@ The DisplayPhotosEnabled parameter specifies whether users see sender photos in Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -878,6 +943,9 @@ 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. @@ -886,7 +954,6 @@ 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 @@ -896,6 +963,9 @@ Accept wildcard characters: False ``` ### -DropboxAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -904,7 +974,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -914,6 +983,9 @@ Accept wildcard characters: False ``` ### -EmptyStateEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill EmptyStateEnabled Description }} @@ -922,7 +994,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -932,6 +1003,9 @@ Accept wildcard characters: False ``` ### -ExplicitLogonEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: @@ -943,7 +1017,6 @@ The ExplicitLogonEnabled parameter specifies whether to allow a user to open som 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 @@ -953,6 +1026,9 @@ Accept wildcard characters: False ``` ### -ExternalImageProxyEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExternalImageProxyEnabled parameter specifies whether to load all external images through the Outlook external image proxy. Valid values are: @@ -964,7 +1040,6 @@ The ExternalImageProxyEnabled parameter specifies whether to load all external i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -974,6 +1049,9 @@ Accept wildcard characters: False ``` ### -ExternalSPMySiteHostURL + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalSPMySiteHostURL specifies the My Site Host URL for external users (for example, `https://sp01.contoso.com`). This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. @@ -982,7 +1060,6 @@ This parameter is part of rich document collaboration that allows links to docum Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -992,6 +1069,9 @@ Accept wildcard characters: False ``` ### -FeedbackEnabled + +> Applicable: Exchange Online + This cmdlet is available only in the cloud-based service. The FeedbackEnabled parameter specifies whether to enable or disable inline feedback surveys in Outlook on the web. Valid values are: @@ -1005,7 +1085,6 @@ The FeedbackEnabled parameter specifies whether to enable or disable inline feed Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1015,6 +1094,9 @@ Accept wildcard characters: False ``` ### -ForceSaveAttachmentFilteringEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. @@ -1024,7 +1106,6 @@ The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are fi 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 @@ -1034,6 +1115,9 @@ Accept wildcard characters: False ``` ### -ForceSaveFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceSaveFileTypes parameter specifies the attachment file types (file extensions) that can only be saved from Outlook on the web (not opened). The default values are: .ade, .adp, .app, .asp, .aspx, .asx, .bas, .bat, .cer, .chm, .cmd, .com, .cpl, .crt, .csh, .dcr, .dir, .exe, .fxp, .gadget, .hlp, .hta, .htm, .html, .inf, .ins, .isp, .its, .js, .jse, .ksh, .lnk, .mad, .maf, .mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .msc, .msh, .mshxml, .msi, .msp, .mst, .ops, .pcd, .pif, .plg, .prf, .prg, .ps1, .ps1xml, .ps2, .ps2xml, .psc1, .psc2, .pst, .reg, .scf, .scr, .sct, .shb, .shs, .spl, .swf, .tmp, .url, .vb, .vbe, .vbs, .vsmacro, .vss, .vst, .vsw, .ws, .wsc, .wsf, .wsh @@ -1051,7 +1135,6 @@ If the same file types are specified in multiple lists: 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 @@ -1061,6 +1144,9 @@ Accept wildcard characters: False ``` ### -ForceSaveMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceSaveMimeTypes parameter specifies the MIME extensions in attachments that only allow the attachments to be saved locally (not opened). The default values are: - Application/futuresplash @@ -1082,7 +1168,6 @@ If the same MIME types are specified in multiple lists: 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 @@ -1092,6 +1177,9 @@ Accept wildcard characters: False ``` ### -ForceWacViewingFirstOnPrivateComputers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. @@ -1103,7 +1191,6 @@ By default in Exchange 2013 or later and Exchange Online, all Outlook on the web Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1113,6 +1200,9 @@ Accept wildcard characters: False ``` ### -ForceWacViewingFirstOnPublicComputers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. @@ -1124,7 +1214,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1134,6 +1223,9 @@ Accept wildcard characters: False ``` ### -ForceWebReadyDocumentViewingFirstOnPrivateComputers + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: @@ -1147,7 +1239,6 @@ By default in Exchange 2013 or later and Exchange Online, all Outlook on the web Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1157,6 +1248,9 @@ Accept wildcard characters: False ``` ### -ForceWebReadyDocumentViewingFirstOnPublicComputers + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: @@ -1170,7 +1264,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1180,6 +1273,9 @@ Accept wildcard characters: False ``` ### -FreCardsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1188,7 +1284,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1198,6 +1293,9 @@ Accept wildcard characters: False ``` ### -GlobalAddressListEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: - $true: The global address list is visible in Outlook on the web. This is the default value. @@ -1207,7 +1305,6 @@ The GlobalAddressListEnabled parameter specifies whether the global address list 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 @@ -1217,6 +1314,9 @@ Accept wildcard characters: False ``` ### -GoogleDriveAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1225,7 +1325,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1235,6 +1334,9 @@ Accept wildcard characters: False ``` ### -GroupCreationEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The GroupCreationEnabled parameter specifies whether Microsoft 365 Group creation is available in Outlook and Outlook on the web. Valid values are: @@ -1246,7 +1348,6 @@ The GroupCreationEnabled parameter specifies whether Microsoft 365 Group creatio Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1256,6 +1357,9 @@ Accept wildcard characters: False ``` ### -HideClassicOutlookToggleOut + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The HideClassicOutlookToggleOut parameter specifies whether to enable or disable hiding the toggle in new Outlook that allows users to switch back to classic Outlook. Valid values are: @@ -1267,7 +1371,6 @@ The HideClassicOutlookToggleOut parameter specifies whether to enable or disable Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1277,6 +1380,9 @@ Accept wildcard characters: False ``` ### -InstantMessagingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: - $true: Instant messaging is available in Outlook on the web. This is the default value. @@ -1286,7 +1392,6 @@ The InstantMessagingEnabled parameter specifies whether instant messaging is ava 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 @@ -1296,6 +1401,9 @@ Accept wildcard characters: False ``` ### -InstantMessagingType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: - None: This is the default value in on-premises Exchange. @@ -1305,7 +1413,6 @@ The InstantMessagingType parameter specifies the type of instant messaging provi Type: InstantMessagingTypeOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1315,6 +1422,9 @@ Accept wildcard characters: False ``` ### -InterestingCalendarsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The InterestingCalendarsEnabled parameter specifies whether interesting calendars are available in Outlook on the web. Valid values are: @@ -1326,7 +1436,6 @@ The InterestingCalendarsEnabled parameter specifies whether interesting calendar Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1336,6 +1445,9 @@ Accept wildcard characters: False ``` ### -InternalSPMySiteHostURL + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalSPMySiteHostURL specifies the My Site Host URL for internal users (for example, `https://sp01.contoso.com`). This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. @@ -1344,7 +1456,6 @@ This parameter is part of rich document collaboration that allows links to docum Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1354,6 +1465,9 @@ 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) features are available in Outlook on the web. Valid values are: - $true: IRM is available in Outlook on the web. This is the default value. @@ -1363,7 +1477,6 @@ The IRMEnabled parameter specifies whether Information Rights Management (IRM) f 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 @@ -1373,6 +1486,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsDefault switch specifies whether the Outlook on the web policy is the default policy that's used to configure the Outlook on the web settings for new mailboxes. You don't need to specify a value with this switch. If another policy is currently set as the default, this switch replaces the old default policy with this policy. @@ -1383,7 +1499,6 @@ If another policy is currently set as the default, this switch replaces the old Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1393,6 +1508,9 @@ Accept wildcard characters: False ``` ### -ItemsToOtherAccountsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ItemsToOtherAccountsEnabled parameter specifies whether users can move or copy email messages between accounts. Valid values are: @@ -1406,7 +1524,6 @@ The ItemsToOtherAccountsEnabled parameter specifies whether users can move or co Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1416,6 +1533,9 @@ Accept wildcard characters: False ``` ### -JournalEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: - $true: The Journal folder is visible in Outlook on the web. This is the default value. @@ -1425,7 +1545,6 @@ The JournalEnabled parameter specifies whether the Journal folder is available i 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 @@ -1435,6 +1554,9 @@ Accept wildcard characters: False ``` ### -JunkEmailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: @@ -1446,7 +1568,6 @@ The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1456,6 +1577,9 @@ Accept wildcard characters: False ``` ### -LinkedInEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. LinkedIn integration is no longer supported. @@ -1464,7 +1588,6 @@ LinkedIn integration is no longer supported. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1474,6 +1597,9 @@ Accept wildcard characters: False ``` ### -LocalEventsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The LocalEventsEnabled parameter specifies whether local events calendars are available in Outlook on the web. Valid values are: @@ -1485,7 +1611,6 @@ The LocalEventsEnabled parameter specifies whether local events calendars are av Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1495,6 +1620,9 @@ Accept wildcard characters: False ``` ### -LogonAndErrorLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LogonAndErrorLanguage parameter specifies the language that used in Outlook on the web for forms-based authentication and for error messages when a user's current language setting can't be read. A valid value is a supported Microsoft Windows Language Code Identifier (LCID). For example, 1033 is US English. @@ -1505,7 +1633,6 @@ The default value is 0, which means the logon and error language selection is un 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 @@ -1515,6 +1642,9 @@ Accept wildcard characters: False ``` ### -MessagePreviewsDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MessagePreviewsDisabled Description }} @@ -1523,7 +1653,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1533,6 +1662,9 @@ Accept wildcard characters: False ``` ### -MonthlyUpdatesEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MonthlyUpdatesEnabled Description }} @@ -1541,7 +1673,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1551,13 +1682,15 @@ Accept wildcard characters: False ``` ### -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 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: False Position: Named @@ -1567,6 +1700,9 @@ Accept wildcard characters: False ``` ### -NotesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: - $true: The Notes folder is visible in Outlook on the web. This is the default value. @@ -1576,7 +1712,6 @@ The NotesEnabled parameter specifies whether the Notes folder is available in Ou 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 @@ -1586,6 +1721,9 @@ Accept wildcard characters: False ``` ### -NpsSurveysEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The NpsSurveysEnabled parameter specifies whether to enable or disable the Net Promoter Score (NPS) survey in Outlook on the web. The survey allows users to rate Outlook on the web on a scale of 1 to 5, and to provide feedback and suggested improvements in free text. Valid values are: @@ -1597,7 +1735,6 @@ The NpsSurveysEnabled parameter specifies whether to enable or disable the Net P Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1607,6 +1744,9 @@ Accept wildcard characters: False ``` ### -OfflineEnabledWeb + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OfflineEnabledWeb parameter specifies whether offline capabilities are available in Outlook on the web, including saving items to the local device (view items without an internet connection). Valid values are: @@ -1620,7 +1760,6 @@ When offline capabilities are available, users can turn offline capabilities on Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1630,6 +1769,9 @@ Accept wildcard characters: False ``` ### -OfflineEnabledWin + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OfflineEnabledWin parameter specifies whether offline capabilities are available in the new Outlook for Windows, including saving items to the local device (view items without an internet connection). Valid values are: @@ -1643,7 +1785,6 @@ When offline capabilities are available, users can turn offline capabilities on Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1653,6 +1794,9 @@ Accept wildcard characters: False ``` ### -OneDriveAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been deprecated and is no longer used. To enable or disable personal OneDrive in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter. @@ -1661,7 +1805,6 @@ To enable or disable personal OneDrive in Outlook on the web, use the Additional Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1671,6 +1814,9 @@ Accept wildcard characters: False ``` ### -OneWinNativeOutlookEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OneWinNativeOutlookEnabled parameter controls the availability of the new Outlook for Windows App. Valid values are: @@ -1682,7 +1828,6 @@ The OneWinNativeOutlookEnabled parameter controls the availability of the new Ou Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named Default value: None @@ -1691,6 +1836,9 @@ Accept wildcard characters: False ``` ### -OnSendAddinsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The OnSendAddinsEnabled parameter specifies whether a mail item can be edited while an on-send add-in is processing it in Outlook on the web or the new Outlook on Windows. Valid values are: - $true: A user can't edit a mail item while an on-send add-in is processing the item. @@ -1700,7 +1848,6 @@ The OnSendAddinsEnabled parameter specifies whether a mail item can be edited wh Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1710,13 +1857,15 @@ Accept wildcard characters: False ``` ### -OrganizationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + When the OrganizationEnabled parameter is set to $false, the Automatic Reply option doesn't include external and internal options, the address book doesn't show the organization hierarchy, and the Resources tab in Calendar forms is disabled. 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 @@ -1726,6 +1875,9 @@ Accept wildcard characters: False ``` ### -OutboundCharset + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: - AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. @@ -1736,7 +1888,6 @@ The OutboundCharset parameter specifies the character set that's used for outgoi Type: OutboundCharsetOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1746,6 +1897,9 @@ Accept wildcard characters: False ``` ### -OutlookBetaToggleEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookBetaToggleEnabled parameter specifies whether to enable or disable the Outlook on the web Preview toggle. The Preview toggle allows users to try the new Outlook on the web experience. Valid values are: @@ -1757,7 +1911,6 @@ The OutlookBetaToggleEnabled parameter specifies whether to enable or disable th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1767,6 +1920,9 @@ Accept wildcard characters: False ``` ### -OutlookNewslettersAccessLevel + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookNewslettersAccessLevelAccess parameter specifies the access level in Outlook Newsletters. Valid values are: @@ -1780,7 +1936,6 @@ The OutlookNewslettersAccessLevelAccess parameter specifies the access level in Type: OutlookNewslettersAccessLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1790,6 +1945,9 @@ Accept wildcard characters: False ``` ### -OutlookDataFile + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookDataFile parameter specifies what users can do with .pst files in the new Outlook for Windows. Valid values are: @@ -1805,7 +1963,6 @@ The OutlookDataFile parameter specifies what users can do with .pst files in the Type: OutlookDataFileFeatureState Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1815,6 +1972,9 @@ Accept wildcard characters: False ``` ### -OutlookNewslettersReactions + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookNewslettersReactions parameter specifies whether reactions are enabled in Outlook Newsletters. Readers can react to individual sections or the entire newsletter. They can also comment using integrated controls at the end of the newsletter. Valid values are: @@ -1828,7 +1988,6 @@ The OutlookNewslettersReactions parameter specifies whether reactions are enable Type: OutlookNewslettersFeatureState Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1838,6 +1997,9 @@ Accept wildcard characters: False ``` ### -OutlookNewslettersShowMore + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The OutlookNewslettersShowMore parameter specifies whether recommendations to other Outlook Newsletters are included in the footer of published newsletter editions. Valid values are: @@ -1853,7 +2015,6 @@ Authors can disable these recommendations for each individual newsletter edition Type: OutlookNewslettersFeatureState Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1863,6 +2024,9 @@ Accept wildcard characters: False ``` ### -OWALightEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: - $true: The light version of Outlook on the web is available. This is the default value. @@ -1872,7 +2036,6 @@ The OWALightEnabled parameter controls the availability of the light version of 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 @@ -1882,6 +2045,9 @@ Accept wildcard characters: False ``` ### -OWAMiniEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: @@ -1893,7 +2059,6 @@ The OWAMiniEnabled parameter controls the availability of the mini version of Ou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1903,6 +2068,9 @@ Accept wildcard characters: False ``` ### -PersonalAccountCalendarsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PersonalAccountCalendarsEnabled parameter specifies whether to allow users to connect to their personal Outlook.com or Google Calendar in Outlook on the web. Valid values are: @@ -1914,7 +2082,6 @@ The PersonalAccountCalendarsEnabled parameter specifies whether to allow users t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1924,6 +2091,9 @@ Accept wildcard characters: False ``` ### -PersonalAccountsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in the new Outlook for Windows. Valid values are: @@ -1935,7 +2105,6 @@ The PersonalAccountsEnabled parameter specifies whether to allow users to add th Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1945,13 +2114,15 @@ Accept wildcard characters: False ``` ### -PhoneticSupportEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PhoneticSupportEnabled parameter specifies phonetically spelled entries in the address book. This parameter is available for use in Japan. ```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 @@ -1961,6 +2132,9 @@ Accept wildcard characters: False ``` ### -PlacesEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PlacesEnabled parameter specifies whether to enable or disable Places in Outlook on the web. Places lets users search, share, and map location details by using Bing. Valid values are: @@ -1972,7 +2146,6 @@ The PlacesEnabled parameter specifies whether to enable or disable Places in Out Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1982,6 +2155,9 @@ Accept wildcard characters: False ``` ### -PremiumClientEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: - $true: The full version of Outlook Web App is available for supported browsers. This is the default value. @@ -1991,7 +2167,6 @@ The PremiumClientEnabled parameter controls the availability of the full version 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 @@ -2001,6 +2176,9 @@ Accept wildcard characters: False ``` ### -PrintWithoutDownloadEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PrintWithoutDownloadEnabled specifies whether to allow printing of supported files without downloading the attachment in Outlook on the web. Valid values are: @@ -2012,7 +2190,6 @@ The PrintWithoutDownloadEnabled specifies whether to allow printing of supported Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2022,6 +2199,9 @@ Accept wildcard characters: False ``` ### -ProjectMocaEnabled + +> Applicable: Exchange Online + **Note**: The feature that's associated with this parameter is currently in Preview, is not available to all organizations, and is subject to change. This parameter is available only in the cloud-based service. @@ -2035,7 +2215,6 @@ The ProjectMocaEnabled parameter enables or disables access to Project Moca in O Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2045,6 +2224,9 @@ Accept wildcard characters: False ``` ### -PublicFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: @@ -2056,7 +2238,6 @@ The PublicFoldersEnabled parameter specifies whether a user can browse or read i 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 @@ -2066,6 +2247,9 @@ Accept wildcard characters: False ``` ### -RecoverDeletedItemsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: @@ -2077,7 +2261,6 @@ The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outloo 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 @@ -2087,6 +2270,9 @@ Accept wildcard characters: False ``` ### -ReferenceAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: - $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. @@ -2096,7 +2282,6 @@ The ReferenceAttachmentsEnabled parameter specifies whether users can attach fil Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2106,6 +2291,9 @@ Accept wildcard characters: False ``` ### -RemindersAndNotificationsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: - $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. @@ -2117,7 +2305,6 @@ This parameter doesn't apply to the light version of Outlook Web App. 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 @@ -2127,6 +2314,9 @@ Accept wildcard characters: False ``` ### -ReportJunkEmailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: In Exchange Online, this parameter does not affect the ability of users to report messages. Whether a user is able to report messages and where is controlled in the Microsoft Defender portal as described in [User reported message settings](https://learn.microsoft.com/defender-office-365/submissions-user-reported-messages-custom-mailbox). The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: @@ -2140,7 +2330,6 @@ This parameter is meaningful only when the JunkEmailEnabled parameter is set to Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2150,6 +2339,9 @@ Accept wildcard characters: False ``` ### -RulesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: - $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. @@ -2159,7 +2351,6 @@ The RulesEnabled parameter specifies whether a user can view, create, or modify 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 @@ -2169,6 +2360,9 @@ Accept wildcard characters: False ``` ### -SatisfactionEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SatisfactionEnabled parameter specifies whether to enable or disable the satisfaction survey. Valid values are: - $true: The satisfaction survey is enabled. This is the default value. @@ -2178,7 +2372,6 @@ The SatisfactionEnabled parameter specifies whether to enable or disable the sat Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2188,6 +2381,9 @@ Accept wildcard characters: False ``` ### -SaveAttachmentsToCloudEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: - $true: Users can save regular email attachments to the cloud. This is the default value. @@ -2197,7 +2393,6 @@ The SaveAttachmentsToCloudEnabled parameter specifies whether users can save reg Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2207,6 +2402,9 @@ Accept wildcard characters: False ``` ### -SearchFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: - $true: Search Folders are visible in Outlook on the Web. This is the default value. @@ -2216,7 +2414,6 @@ The SearchFoldersEnabled parameter specifies whether Search Folders are availabl 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 @@ -2226,6 +2423,9 @@ Accept wildcard characters: False ``` ### -SetPhotoEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: - $true: Users can manage their photos in Outlook on the web. This is the default value. @@ -2237,7 +2437,6 @@ The SetPhotoEnabled parameter specifies whether users can add, change, and remov Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2247,13 +2446,15 @@ Accept wildcard characters: False ``` ### -SetPhotoURL + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SetPhotoURL parameter controls where users go to select their photo. Note that you can't specify a URL that contains one or more picture files, as there is no mechanism to copy a URL photo to the properties of the users' Exchange Online mailboxes. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2263,6 +2464,9 @@ Accept wildcard characters: False ``` ### -ShowOnlineArchiveEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ShowOnlineArchiveEnabled Description }} @@ -2271,7 +2475,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2281,6 +2484,9 @@ Accept wildcard characters: False ``` ### -SignaturesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: - $true: Signatures are available in Outlook on the web. This is the default value. @@ -2290,7 +2496,6 @@ The SignaturesEnabled parameter specifies whether to enable or disable the use o 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 @@ -2300,6 +2505,9 @@ Accept wildcard characters: False ``` ### -SilverlightEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: @@ -2311,7 +2519,6 @@ The SilverlightEnabled parameter specifies whether a user can use Microsoft Silv 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 @@ -2321,6 +2528,9 @@ Accept wildcard characters: False ``` ### -SkipCreateUnifiedGroupCustomSharepointClassification + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whether to skip a custom SharePoint page during the creation of Microsoft 365 Groups in Outlook on the web. Valid values are: @@ -2332,7 +2542,6 @@ The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2342,6 +2551,9 @@ Accept wildcard characters: False ``` ### -SMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: @@ -2355,7 +2567,6 @@ The SMimeEnabled parameter specifies whether users can download the S/MIME contr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2365,6 +2576,9 @@ Accept wildcard characters: False ``` ### -SMimeSuppressNameChecksEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SMimeSuppressNameChecksEnabled switch specifies whether to suppress name check in S/MIME messages. You don't need to specify a value with this switch. @@ -2373,7 +2587,6 @@ The SMimeSuppressNameChecksEnabled switch specifies whether to suppress name che Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2383,6 +2596,9 @@ Accept wildcard characters: False ``` ### -SpellCheckerEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: @@ -2396,7 +2612,6 @@ This parameter doesn't apply to the light version of Outlook Web App. 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 @@ -2406,6 +2621,9 @@ Accept wildcard characters: False ``` ### -TasksEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The TasksEnabled parameter specifies whether Tasks folder is available in Outlook Web App. Valid values are: @@ -2419,7 +2637,6 @@ This parameter doesn't apply to the light version of Outlook Web App. 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 @@ -2429,6 +2646,9 @@ Accept wildcard characters: False ``` ### -TeamSnapCalendarsEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The TeamSnapCalendarsEnabled parameter specifies whether to allow users to connect to their personal TeamSnap calendars in Outlook on the web. Valid values are: @@ -2440,7 +2660,6 @@ The TeamSnapCalendarsEnabled parameter specifies whether to allow users to conne Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2450,6 +2669,9 @@ Accept wildcard characters: False ``` ### -TextMessagingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: - $true: Text messaging is available in Outlook on the web. This is the default value. @@ -2461,7 +2683,6 @@ This parameter doesn't apply to the light version of Outlook on the web. 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 @@ -2471,6 +2692,9 @@ Accept wildcard characters: False ``` ### -ThemeSelectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: - $true: Users can specify the theme in Outlook on the web. This is the default value. @@ -2480,7 +2704,6 @@ The ThemeSelectionEnabled parameter specifies whether users can change the theme 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 @@ -2490,6 +2713,9 @@ Accept wildcard characters: False ``` ### -ThirdPartyAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -2498,7 +2724,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2508,6 +2733,9 @@ Accept wildcard characters: False ``` ### -UMIntegrationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: - $true: UM integration is enabled in Outlook on the web. This is the default value. @@ -2521,7 +2749,6 @@ This parameter doesn't apply to the light version of Outlook on the web. 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 @@ -2531,6 +2758,9 @@ Accept wildcard characters: False ``` ### -UNCAccessOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter has been deprecated and is no longer used. @@ -2539,7 +2769,6 @@ This parameter has been deprecated and is no longer used. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2549,6 +2778,9 @@ Accept wildcard characters: False ``` ### -UNCAccessOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter has been deprecated and is no longer used. @@ -2557,7 +2789,6 @@ This parameter has been deprecated and is no longer used. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2567,6 +2798,9 @@ Accept wildcard characters: False ``` ### -UseGB18030 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. @@ -2576,7 +2810,6 @@ The UseGB18030 parameter specifies whether to use the GB18030 character set inst 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 @@ -2586,6 +2819,9 @@ Accept wildcard characters: False ``` ### -UseISO885915 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. @@ -2595,7 +2831,6 @@ The UseISO885915 parameter specifies whether to use the character set ISO8859-15 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 @@ -2605,6 +2840,9 @@ Accept wildcard characters: False ``` ### -UserVoiceEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The UserVoiceEnabled parameter specifies whether to enable or disable Outlook UserVoice in Outlook on the web. Outlook UserVoice is a customer feedback area that's available in Microsoft 365. Valid values are: @@ -2616,7 +2854,6 @@ The UserVoiceEnabled parameter specifies whether to enable or disable Outlook Us Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2626,6 +2863,9 @@ Accept wildcard characters: False ``` ### -WacEditingEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: - $true: Users can edit supported documents in Outlook on the web. This is the default value. @@ -2635,7 +2875,6 @@ The WacEditingEnabled parameter specifies whether to enable or disable editing d Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2645,6 +2884,9 @@ Accept wildcard characters: False ``` ### -WacExternalServicesEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WacExternalServicesEnabled parameter specifies whether to enable or disable external services when viewing documents in Outlook on the web (for example, machine translation) by using Office Online Server. Valid values are: - $true: External services are enabled when viewing supported documents in Outlook on the web. This is the default value. @@ -2654,7 +2896,6 @@ The WacExternalServicesEnabled parameter specifies whether to enable or disable Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2664,6 +2905,9 @@ Accept wildcard characters: False ``` ### -WacOMEXEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WacOMEXEnabled parameter specifies whether to enable or disable apps for Outlook in Outlook on the web in Office Online Server. Valid values are: - $true: apps for Outlook are enabled in Outlook on the web. @@ -2673,7 +2917,6 @@ The WacOMEXEnabled parameter specifies whether to enable or disable apps for Out Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2683,6 +2926,9 @@ Accept wildcard characters: False ``` ### -WacViewingOnPrivateComputersEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: - $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. @@ -2694,7 +2940,6 @@ By default in Exchange 2013 or later and Exchange Online, all Outlook on the web Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2704,6 +2949,9 @@ Accept wildcard characters: False ``` ### -WacViewingOnPublicComputersEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: - $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. @@ -2715,7 +2963,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2725,6 +2972,9 @@ Accept wildcard characters: False ``` ### -WeatherEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The WeatherEnabled parameter specifies whether to enable or disable weather information in the calendar in Outlook on the web. Valid values are: @@ -2736,7 +2986,6 @@ The WeatherEnabled parameter specifies whether to enable or disable weather info Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -2746,6 +2995,9 @@ Accept wildcard characters: False ``` ### -WebPartsFrameOptionsType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. @@ -2756,7 +3008,6 @@ The WebPartsFrameOptionsType parameter specifies what sources can access web par Type: WebPartsFrameOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2766,6 +3017,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingForAllSupportedTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: @@ -2777,7 +3031,6 @@ The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2787,6 +3040,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: @@ -2800,7 +3056,6 @@ By default in Exchange 2013, all Outlook on the web sessions are considered to b Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2810,6 +3065,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: @@ -2823,7 +3081,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2833,6 +3090,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingSupportedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. This is a read-only parameter that can't be modified; use the WebReadyFileTypes parameter instead. @@ -2841,7 +3101,6 @@ This is a read-only parameter that can't be modified; use the WebReadyFileTypes Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2851,6 +3110,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingSupportedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. This is a read-only parameter that can't be modified; use the WebReadyMimeTypes parameter instead. @@ -2859,7 +3121,6 @@ This is a read-only parameter that can't be modified; use the WebReadyMimeTypes Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2869,6 +3130,9 @@ Accept wildcard characters: False ``` ### -WebReadyFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyFileTypes parameter specifies the attachment file types (file extensions) that can be viewed by WebReady Document Viewing in Outlook on the web. The default value is all supported file types: @@ -2896,7 +3160,6 @@ This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parame Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2906,6 +3169,9 @@ Accept wildcard characters: False ``` ### -WebReadyMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be viewed by WebReady Document Viewing in Outlook on the web. The default value is all supported MIME types: @@ -2932,7 +3198,6 @@ This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parame Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2942,13 +3207,15 @@ 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 @@ -2958,13 +3225,15 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been deprecated and is no longer used. ```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 @@ -2974,13 +3243,15 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter has been deprecated and is no longer used. ```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/exchange/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md index 14358aa512..aeaf4e63ed 100644 --- a/exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-owavirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-OwaVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-owavirtualdirectory +schema: 2.0.0 +title: Set-OwaVirtualDirectory --- # Set-OwaVirtualDirectory @@ -182,6 +183,9 @@ This example sets the ActionForUnknownFileAndMIMETypes parameter to Block on the ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -194,7 +198,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -204,6 +207,9 @@ Accept wildcard characters: False ``` ### -ActionForUnknownFileAndMIMETypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are: - Allow (This is the default value.) @@ -214,7 +220,6 @@ The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file type Type: AttachmentBlockingActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -224,6 +229,9 @@ Accept wildcard characters: False ``` ### -ActiveSyncIntegrationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are: - $true: ActiveSync is available in Outlook on the web. This is the default value. @@ -233,7 +241,6 @@ The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disabl Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -243,6 +250,9 @@ Accept wildcard characters: False ``` ### -AdfsAuthentication + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdfsAuthentication parameter enables or disables Active Directory Federation Services (ADFS) authentication on the Outlook on the web virtual directory. Valid values are: - $true: ADFS authentication is enabled. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $true before you can use this value. @@ -252,7 +262,6 @@ The AdfsAuthentication parameter enables or disables Active Directory Federation Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -262,6 +271,9 @@ Accept wildcard characters: False ``` ### -AllAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are: - $true: All address lists are visible in Outlook on the web. This is the default value. @@ -271,7 +283,6 @@ The AllAddressListsEnabled parameter specifies which address lists are available Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -281,6 +292,9 @@ Accept wildcard characters: False ``` ### -AllowCopyContactsToDeviceAddressBook + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are: - $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value. @@ -290,7 +304,6 @@ The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can c Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -300,6 +313,9 @@ Accept wildcard characters: False ``` ### -AllowedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowedFileTypes parameter specifies the attachment file types (file extensions) that can be saved locally or viewed from Outlook on the web. The default values are: .avi, .bmp, .doc, .docm, .docx, .gif, .jpg, .mp3, .one, .pdf, .png, .ppsm, .ppsx, .ppt, .pptm, .pptx, .pub, .rpmsg, .rtf, .tif, .tiff, .txt, .vsd, .wav, .wma, .wmv, .xls, .xlsb, .xlsm, .xlsx, .zip @@ -317,7 +333,6 @@ If the same file types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -327,6 +342,9 @@ Accept wildcard characters: False ``` ### -AllowedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowedMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be saved locally or viewed from Outlook on the web. The default values are: - image/bmp @@ -347,7 +365,6 @@ If the same MIME types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,6 +374,9 @@ Accept wildcard characters: False ``` ### -AllowOfflineOn + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowOfflineOn parameter specifies when Outlook on the web in offline mode is available for supported web browsers. Valid values are: - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true). @@ -369,7 +389,6 @@ When offline mode is available, users can turn offline mode on or off themselves Type: AllowOfflineOnEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -379,6 +398,9 @@ Accept wildcard characters: False ``` ### -AnonymousFeaturesEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlook on the web users that are logged on anonymously to access specific features. Valid values are: - $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This is the default value. @@ -388,7 +410,6 @@ The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -398,6 +419,9 @@ 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. @@ -409,7 +433,6 @@ This parameter can be used with the FormsAuthentication parameter or with the Di Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -419,6 +442,9 @@ Accept wildcard characters: False ``` ### -BlockedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedFileTypes parameter specifies a list of attachment file types (file extensions) that can't be saved locally or viewed from Outlook on the web. The default values are: .ade, .adp, .app, .appcontent-ms, .asp, .aspx, .asx, .bas, .bat, .cer, .chm, .cmd, .cnt, .com, .cpl, .crt, .csh, .der, .diagcab, .exe, .fxp, .gadget, .grp, .hlp, .hpj, .hta, .htc, .inf, .ins, .isp, .its, .jar, .jnlp, .js, .jse, .ksh, .lnk, .mad, .maf, .mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mcf, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .mht, .mhtml, .msc, .msh, .msh1, .msh1xml, .msh2, .msh2xml, .mshxml, .msi, .msp, .mst, .msu, .ops, .osd, .pcd, .pif, .pl, .plg, .prf, .prg, .printerexport, .ps1, .ps1xml, .ps2, .ps2xml, .psc1, .psc2, .psd1, .psdm1, .pst, .reg, .scf, .scr, .sct, .settingcontent-ms, .shb, .shs, .theme, .tmp, .url, .vb, .vbe, .vbp, .vbs, .vsmacros, .vsw, .webpnp, .website, .ws, .wsc, .wsf, .wsh, .xbap, .xll, .xnk @@ -436,7 +462,6 @@ If the same file types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -446,6 +471,9 @@ Accept wildcard characters: False ``` ### -BlockedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedMimeTypes parameter specifies MIME extensions in attachments that prevent the attachments from being saved locally or viewed from Outlook on the web. The default values are: - application/hta @@ -470,7 +498,6 @@ If the same MIME types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -480,13 +507,15 @@ Accept wildcard characters: False ``` ### -BoxAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -496,6 +525,9 @@ Accept wildcard characters: False ``` ### -CalendarEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook on the web. Valid values are: - $true: The Calendar is available in Outlook on the web. This is the default value. @@ -505,7 +537,6 @@ The CalendarEnabled parameter specifies whether to enable or disable the calenda Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -515,6 +546,9 @@ Accept wildcard characters: False ``` ### -CalendarPublishingEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CalendarPublishingEnabled parameter specifies whether users can publish their calendar from Outlook Web App. Valid values are: @@ -526,7 +560,6 @@ The CalendarPublishingEnabled parameter specifies whether users can publish thei Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -536,6 +569,9 @@ Accept wildcard characters: False ``` ### -ChangePasswordEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are: - $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange. @@ -545,7 +581,6 @@ The ChangePasswordEnabled parameter specifies whether users can change their pas Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -555,6 +590,9 @@ Accept wildcard characters: False ``` ### -ClassicAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are: - $true: Users can attach local files to email messages in Outlook on the web. This is the default value. @@ -564,7 +602,6 @@ The ClassicAttachmentsEnabled parameter specifies whether users can attach local Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -574,6 +611,9 @@ Accept wildcard characters: False ``` ### -ClientAuthCleanupLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAuthCleanupLevel parameter specifies how much of the cache is cleared when the user logs off from Outlook on the web. Valid values are: - Low @@ -585,7 +625,6 @@ This parameter doesn't apply to the light version of Outlook on the web. Type: ClientAuthCleanupLevels Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -595,6 +634,9 @@ 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`. @@ -604,7 +646,6 @@ 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 @@ -614,6 +655,9 @@ Accept wildcard characters: False ``` ### -ContactsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook on the web. Valid values are: - $true: Contacts are available in Outlook on the web. This is the default value. @@ -623,7 +667,6 @@ The ContactsEnabled parameter specifies whether to enable or disable Contacts in Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -633,6 +676,9 @@ Accept wildcard characters: False ``` ### -CrossSiteRedirectType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CrossSiteRedirectType parameter controls how a Client Access server redirects Outlook Web App to the Client Access server infrastructure in another Active Directory site. Valid values are: @@ -646,7 +692,6 @@ The default value is Manual. Type: LegacyRedirectTypeOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -656,13 +701,15 @@ Accept wildcard characters: False ``` ### -DefaultClientLanguage + +> 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: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -672,13 +719,15 @@ Accept wildcard characters: False ``` ### -DefaultDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultDomain parameter specifies which domain to use when the LogonFormat parameter is set to UserName (for example, contoso.com). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -688,6 +737,9 @@ Accept wildcard characters: False ``` ### -DefaultTheme + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016). Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes. @@ -696,7 +748,6 @@ Note that this parameter is a text string, and the value you specify isn't valid Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -706,6 +757,9 @@ Accept wildcard characters: False ``` ### -DelegateAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The DelegateAccessEnabled parameter specifies whether delegates can use Outlook Web App to open folders that they have delegate access to. Valid values are: @@ -717,7 +771,6 @@ The DelegateAccessEnabled parameter specifies whether delegates can use Outlook Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -727,6 +780,9 @@ 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. @@ -738,7 +794,6 @@ You can use this parameter with the FormsAuthentication parameter. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -748,6 +803,9 @@ Accept wildcard characters: False ``` ### -DirectFileAccessOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are: - $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value. @@ -759,7 +817,6 @@ By default in Exchange 2013 or later, all Outlook on the web sessions are consid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -769,6 +826,9 @@ Accept wildcard characters: False ``` ### -DirectFileAccessOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are: - $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value. @@ -780,7 +840,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -790,6 +849,9 @@ Accept wildcard characters: False ``` ### -DisplayPhotosEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are: - $true: Users see sender photos in Outlook on the web. This is the default value. @@ -799,7 +861,6 @@ The DisplayPhotosEnabled parameter specifies whether users see sender photos in Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -809,13 +870,15 @@ 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 @@ -825,13 +888,15 @@ Accept wildcard characters: False ``` ### -DropboxAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -841,6 +906,9 @@ Accept wildcard characters: False ``` ### -Exchange2003Url + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The Exchange2003Url parameter specifies the Outlook Web App URL for Exchange Server 2003 mailboxes. The URL must include the Outlook Web App virtual directory name, even if you're using a redirect to simplify the URL specified by the Exchange2003Url parameter. @@ -849,7 +917,6 @@ The Exchange2003Url parameter specifies the Outlook Web App URL for Exchange Ser Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -859,13 +926,15 @@ Accept wildcard characters: False ``` ### -ExchwebProxyDestination + +> 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: ExchwebProxyDestinations Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -875,6 +944,9 @@ Accept wildcard characters: False ``` ### -ExplicitLogonEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are: - $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value. @@ -884,7 +956,6 @@ The ExplicitLogonEnabled parameter specifies whether to allow a user to open som Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -894,6 +965,9 @@ 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. @@ -910,7 +984,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -920,6 +993,9 @@ 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 (blank): This is the default value. @@ -933,7 +1009,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -943,6 +1018,9 @@ 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. @@ -955,7 +1033,6 @@ 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 @@ -965,6 +1042,9 @@ 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 @@ -994,7 +1074,6 @@ Although you can specify any of these values, whether or not the authentication Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1004,13 +1083,15 @@ Accept wildcard characters: False ``` ### -ExternalDownloadHostName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ExternalDownloadHostName parameter specifies the download location for files in Outlook on the web for external users (for example, in-line image files). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1020,6 +1101,9 @@ Accept wildcard characters: False ``` ### -ExternalSPMySiteHostURL + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ExternalSPMySiteHostURL specifies the My Site Host URL for external users (for example, `https://sp01.contoso.com`). This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. @@ -1028,7 +1112,6 @@ This parameter is part of rich document collaboration that allows links to docum Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1038,6 +1121,9 @@ 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. @@ -1046,7 +1132,6 @@ This setting is important when Secure Sockets Layer (SSL) is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1056,6 +1141,9 @@ Accept wildcard characters: False ``` ### -FailbackUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FailbackUrl parameter specifies the URL that Outlook on the web uses to connect to the server after failback in a site resilience process and requires a separate DNS entry pointing to the original server's IP address. This parameter value must be different from the ExternalUrl parameter. @@ -1064,7 +1152,6 @@ This parameter value must be different from the ExternalUrl parameter. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1074,6 +1161,9 @@ Accept wildcard characters: False ``` ### -FilterWebBeaconsAndHtmlForms + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are: - UserFilterChoice (This is the default value) @@ -1084,7 +1174,6 @@ The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled Type: WebBeaconFilterLevels Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1094,6 +1183,9 @@ Accept wildcard characters: False ``` ### -ForceSaveAttachmentFilteringEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are: - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web. @@ -1103,7 +1195,6 @@ The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are fi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1113,6 +1204,9 @@ Accept wildcard characters: False ``` ### -ForceSaveFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceSaveFileTypes parameter specifies the attachment file types (file extensions) that can only be saved from Outlook on the web (not opened). The default values are: .ade, .adp, .app, .asp, .aspx, .asx, .bas, .bat, .cer, .chm, .cmd, .com, .cpl, .crt, .csh, .dcr, .dir, .exe, .fxp, .gadget, .hlp, .hta, .htm, .html, .inf, .ins, .isp, .its, .js, .jse, .ksh, .lnk, .mad, .maf, .mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .msc, .msh, .mshxml, .msi, .msp, .mst, .ops, .pcd, .pif, .plg, .prf, .prg, .ps1, .ps1xml, .ps2, .ps2xml, .psc1, .psc2, .pst, .reg, .scf, .scr, .sct, .shb, .shs, .spl, .swf, .tmp, .url, .vb, .vbe, .vbs, .vsmacro, .vss, .vst, .vsw, .ws, .wsc, .wsf, .wsh @@ -1130,7 +1224,6 @@ If the same file types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1140,6 +1233,9 @@ Accept wildcard characters: False ``` ### -ForceSaveMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceSaveMimeTypes parameter specifies the MIME extensions in attachments that only allow the attachments to be saved locally (not opened). The default values are: - Application/futuresplash @@ -1161,7 +1257,6 @@ If the same MIME types are specified in multiple lists: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1171,6 +1266,9 @@ Accept wildcard characters: False ``` ### -ForceWacViewingFirstOnPrivateComputers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are: - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file. @@ -1182,7 +1280,6 @@ By default in Exchange 2013 or later, all Outlook on the web sessions are consid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1192,6 +1289,9 @@ Accept wildcard characters: False ``` ### -ForceWacViewingFirstOnPublicComputers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are: - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file. @@ -1203,7 +1303,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1213,6 +1312,9 @@ Accept wildcard characters: False ``` ### -ForceWebReadyDocumentViewingFirstOnPrivateComputers + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: @@ -1226,7 +1328,6 @@ By default in Exchange 2013 or later, all Outlook on the web sessions are consid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1236,6 +1337,9 @@ Accept wildcard characters: False ``` ### -ForceWebReadyDocumentViewingFirstOnPublicComputers + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 or Exchange Server 2013. The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are: @@ -1249,7 +1353,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -1259,6 +1362,9 @@ Accept wildcard characters: False ``` ### -FormsAuthentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FormsAuthentication parameter enables or disables forms-based authentication on the Outlook on the web virtual directory. Valid values are: - $true: Forms-based authentication is enabled in Outlook on the web. This is the default value. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false. @@ -1268,7 +1374,6 @@ The FormsAuthentication parameter enables or disables forms-based authentication Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1278,13 +1383,15 @@ Accept wildcard characters: False ``` ### -FreCardsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1294,6 +1401,9 @@ Accept wildcard characters: False ``` ### -GlobalAddressListEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are: - $true: The global address list is visible in Outlook on the web. This is the default value. @@ -1303,7 +1413,6 @@ The GlobalAddressListEnabled parameter specifies whether the global address list Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1313,13 +1422,15 @@ Accept wildcard characters: False ``` ### -GoogleDriveAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1329,6 +1440,9 @@ Accept wildcard characters: False ``` ### -GzipLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are: - Off @@ -1340,7 +1454,6 @@ The GzipLevel parameter sets Gzip configuration information for the Outlook on t Type: GzipLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1350,13 +1463,15 @@ Accept wildcard characters: False ``` ### -InstantMessagingCertificateThumbprint + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InstantMessagingCertificateThumbprint parameter specifies the trusted certificate used to communicate between the instant messaging server and the Mailbox server. Use the Get-ExchangeCertificate cmdlet to find the thumbprint of the 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 @@ -1366,6 +1481,9 @@ Accept wildcard characters: False ``` ### -InstantMessagingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are: - $true: Instant messaging is available in Outlook on the web. This is the default value. @@ -1375,7 +1493,6 @@ The InstantMessagingEnabled parameter specifies whether instant messaging is ava Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1385,13 +1502,15 @@ Accept wildcard characters: False ``` ### -InstantMessagingServerName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InstantMessagingServerName parameter specifies the fully qualified domain name (FQDN) of the instant messaging server or set of servers behind a load balancing device. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1401,6 +1520,9 @@ Accept wildcard characters: False ``` ### -InstantMessagingType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are: - None: This is the default value. @@ -1410,7 +1532,6 @@ The InstantMessagingType parameter specifies the type of instant messaging provi Type: InstantMessagingTypeOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1420,6 +1541,9 @@ Accept wildcard characters: False ``` ### -IntegratedFeaturesEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on the web users who are logged on using Integrated Windows authentication to access specific features. Valid values are: - $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This is the default value. @@ -1429,7 +1553,6 @@ The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1439,13 +1562,15 @@ Accept wildcard characters: False ``` ### -InternalDownloadHostName + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The InternalDownloadHostName parameter specifies the download location for files in Outlook on the web for internal users (for example, in-line image files). The default value is blank ($null). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1455,6 +1580,9 @@ Accept wildcard characters: False ``` ### -InternalSPMySiteHostURL + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The InternalSPMySiteHostURL specifies the My Site Host URL for internal users (for example, `https://sp01.contoso.com`). This parameter is part of rich document collaboration that allows links to documents in OneDrive to appear as regular file attachments in messages. @@ -1463,7 +1591,6 @@ This parameter is part of rich document collaboration that allows links to docum Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1473,6 +1600,9 @@ 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. @@ -1481,7 +1611,6 @@ This setting is important when SSL is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1491,6 +1620,9 @@ Accept wildcard characters: False ``` ### -IRMEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are: - $true: IRM is available in Outlook on the web. This is the default value. @@ -1500,7 +1632,6 @@ The IRMEnabled parameter specifies whether Information Rights Management (IRM) f Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1510,6 +1641,9 @@ Accept wildcard characters: False ``` ### -IsPublic + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsPublic parameter specifies whether external users use the virtual directory for Outlook on the web in multiple virtual directory environments (you've configured separate virtual directories on the same server for internal vs. external Outlook on the web connections). Valid values are: - $true: External users use the virtual directory for Outlook on the web. @@ -1519,7 +1653,6 @@ The IsPublic parameter specifies whether external users use the virtual director Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1529,6 +1662,9 @@ Accept wildcard characters: False ``` ### -JournalEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are: - $true: The Journal folder is visible in Outlook on the web. This is the default value. @@ -1538,7 +1674,6 @@ The JournalEnabled parameter specifies whether the Journal folder is available i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1548,6 +1683,9 @@ Accept wildcard characters: False ``` ### -JunkEmailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are: - $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value. @@ -1557,7 +1695,6 @@ The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1567,6 +1704,9 @@ Accept wildcard characters: False ``` ### -LegacyRedirectType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or Front End server when forms-based authentication isn't used on the Exchange 2010 Outlook Web App virtual directory. Valid values are: @@ -1578,7 +1718,6 @@ The LegacyRedirectType parameter specifies the type of redirect that Outlook Web Type: LegacyRedirectTypeOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1588,6 +1727,9 @@ Accept wildcard characters: False ``` ### -LogonAndErrorLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogonAndErrorLanguage parameter specifies the language that used in Outlook on the web for forms-based authentication and for error messages when a user's current language setting can't be read. A valid value is a supported Microsoft Windows Language Code Identifier (LCID). For example, 1033 is US English. @@ -1598,7 +1740,6 @@ The default value is 0, which means the logon and error language selection is un Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1608,6 +1749,9 @@ Accept wildcard characters: False ``` ### -LogonFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogonFormat parameter specifies the type of logon format that's required for forms-based authentication on the Outlook on the web sign-in page. Valid values are: - FullDomain: Requires the format domain\\username. This is the default value. @@ -1618,7 +1762,6 @@ The LogonFormat parameter specifies the type of logon format that's required for Type: LogonFormats Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1628,6 +1771,9 @@ Accept wildcard characters: False ``` ### -LogonPageLightSelectionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogonPageLightSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the option to sign in to the light version of Outlook on the web. Valid values are: - $true: The option to use the light version of Outlook on the web is available on the sign-in page. This is the default value. @@ -1639,7 +1785,6 @@ This parameter is meaningful only for browsers that support the full version of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1649,6 +1794,9 @@ Accept wildcard characters: False ``` ### -LogonPagePublicPrivateSelectionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogonPagePublicPrivateSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the public/private computer session option at sign-in. Valid values are: - $true: The public/private computer session selection is available on the Outlook on the web sign-in page. @@ -1662,7 +1810,6 @@ When you change the value of this parameter, restart IIS (Stop-Service WAS -Forc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1672,6 +1819,9 @@ Accept wildcard characters: False ``` ### -NotesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are: - $true: The Notes folder is visible in Outlook on the web. This is the default value. @@ -1681,7 +1831,6 @@ The NotesEnabled parameter specifies whether the Notes folder is available in Ou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1691,6 +1840,9 @@ Accept wildcard characters: False ``` ### -NotificationInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The NotificationInterval parameter specifies the polling frequency in seconds that the client polls the server for new item notifications, reminder updates, and session time-out information in Outlook Web App. @@ -1703,7 +1855,6 @@ This parameter doesn't apply to the light version of Outlook Web App. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1713,13 +1864,15 @@ Accept wildcard characters: False ``` ### -OAuthAuthentication + +> 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 @@ -1729,13 +1882,15 @@ Accept wildcard characters: False ``` ### -OneDriveAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1745,13 +1900,15 @@ Accept wildcard characters: False ``` ### -OrganizationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + When the OrganizationEnabled parameter is set to $false, the Automatic Reply option doesn't include external and internal options, the address book doesn't show the organization hierarchy, and the Resources tab in Calendar forms is disabled. 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 @@ -1761,6 +1918,9 @@ Accept wildcard characters: False ``` ### -OutboundCharset + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are: - AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value. @@ -1771,7 +1931,6 @@ The OutboundCharset parameter specifies the character set that's used for outgoi Type: OutboundCharsetOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1781,6 +1940,9 @@ Accept wildcard characters: False ``` ### -OWALightEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are: - $true: The light version of Outlook on the web is available. This is the default value. @@ -1790,7 +1952,6 @@ The OWALightEnabled parameter controls the availability of the light version of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1800,6 +1961,9 @@ Accept wildcard characters: False ``` ### -OWAMiniEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are: @@ -1811,7 +1975,6 @@ The OWAMiniEnabled parameter controls the availability of the mini version of Ou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1821,6 +1984,9 @@ Accept wildcard characters: False ``` ### -PremiumClientEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are: - $true: The full version of Outlook Web App is available for supported browsers. This is the default value. @@ -1830,7 +1996,6 @@ The PremiumClientEnabled parameter controls the availability of the full version Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1840,6 +2005,9 @@ Accept wildcard characters: False ``` ### -PublicFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are: @@ -1851,7 +2019,6 @@ The PublicFoldersEnabled parameter specifies whether a user can browse or read i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1861,6 +2028,9 @@ Accept wildcard characters: False ``` ### -RecoverDeletedItemsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are: @@ -1872,7 +2042,6 @@ The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outloo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1882,6 +2051,9 @@ Accept wildcard characters: False ``` ### -RedirectToOptimalOWAServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RedirectToOptimalOWAServer parameter specifies whether to find the optimal server for Outlook on the web. Valid values are: - $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This is the default value. @@ -1891,7 +2063,6 @@ The RedirectToOptimalOWAServer parameter specifies whether to find the optimal s Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1901,6 +2072,9 @@ Accept wildcard characters: False ``` ### -ReferenceAttachmentsEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are: - $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value. @@ -1910,7 +2084,6 @@ The ReferenceAttachmentsEnabled parameter specifies whether users can attach fil Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1920,6 +2093,9 @@ Accept wildcard characters: False ``` ### -RemindersAndNotificationsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are: - $true: Notifications and reminders are enabled in Outlook on the web. This is the default value. @@ -1931,7 +2107,6 @@ This parameter doesn't apply to the light version of Outlook Web App. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1941,6 +2116,9 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsActionForUnknownServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -1949,7 +2127,6 @@ This parameter has been deprecated and is no longer used. Type: RemoteDocumentsActions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1959,6 +2136,9 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsAllowedServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -1967,7 +2147,6 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1977,6 +2156,9 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsBlockedServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -1985,7 +2167,6 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1995,6 +2176,9 @@ Accept wildcard characters: False ``` ### -RemoteDocumentsInternalDomainSuffixList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. This parameter has been deprecated and is no longer used. @@ -2003,7 +2187,6 @@ This parameter has been deprecated and is no longer used. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2013,6 +2196,9 @@ Accept wildcard characters: False ``` ### -ReportJunkEmailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are: - $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft. @@ -2024,7 +2210,6 @@ This parameter is meaningful only when the JunkEmailEnabled parameter is set to Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2034,6 +2219,9 @@ Accept wildcard characters: False ``` ### -RulesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are: - $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value. @@ -2043,7 +2231,6 @@ The RulesEnabled parameter specifies whether a user can view, create, or modify Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2053,6 +2240,9 @@ Accept wildcard characters: False ``` ### -SaveAttachmentsToCloudEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are: - $true: Users can save regular email attachments to the cloud. This is the default value. @@ -2062,7 +2252,6 @@ The SaveAttachmentsToCloudEnabled parameter specifies whether users can save reg Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2072,6 +2261,9 @@ Accept wildcard characters: False ``` ### -SearchFoldersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are: @@ -2083,7 +2275,6 @@ The SearchFoldersEnabled parameter specifies whether Search Folders are availabl Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2093,6 +2284,9 @@ Accept wildcard characters: False ``` ### -SetPhotoEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are: - $true: Users can manage their photos in Outlook on the web. This is the default value. @@ -2102,7 +2296,6 @@ The SetPhotoEnabled parameter specifies whether users can add, change, and remov Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2112,13 +2305,15 @@ Accept wildcard characters: False ``` ### -SetPhotoURL + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SetPhotoURL parameter specifies the location (URL) of user photos. The default value of this parameter is blank ($null). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2128,6 +2323,9 @@ Accept wildcard characters: False ``` ### -SignaturesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are: - $true: Signatures are available in Outlook on the web. This is the default value. @@ -2137,7 +2335,6 @@ The SignaturesEnabled parameter specifies whether to enable or disable the use o Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2147,6 +2344,9 @@ Accept wildcard characters: False ``` ### -SilverlightEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are: @@ -2158,7 +2358,6 @@ The SilverlightEnabled parameter specifies whether a user can use Microsoft Silv Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2168,6 +2367,9 @@ Accept wildcard characters: False ``` ### -SMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are: @@ -2181,7 +2383,6 @@ The SMimeEnabled parameter specifies whether users can download the S/MIME contr Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2191,6 +2392,9 @@ Accept wildcard characters: False ``` ### -SpellCheckerEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are: @@ -2204,7 +2408,6 @@ This parameter doesn't apply to the light version of Outlook Web App. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2214,6 +2417,9 @@ Accept wildcard characters: False ``` ### -TasksEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TasksEnabled parameter specifies whether Tasks folder is available in Outlook on the web. Valid values are: - $true: The Tasks folder is available in Outlook on the web. This is the default value. @@ -2225,7 +2431,6 @@ This parameter doesn't apply to the light version of Outlook on the web. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2235,6 +2440,9 @@ Accept wildcard characters: False ``` ### -TextMessagingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are: - $true: Text messaging is available in Outlook on the web. This is the default value. @@ -2246,7 +2454,6 @@ This parameter doesn't apply to the light version of Outlook on the web. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2256,6 +2463,9 @@ Accept wildcard characters: False ``` ### -ThemeSelectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are: - $true: Users can specify the theme in Outlook on the web. This is the default value. @@ -2265,7 +2475,6 @@ The ThemeSelectionEnabled parameter specifies whether users can change the theme Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2275,6 +2484,9 @@ Accept wildcard characters: False ``` ### -UMIntegrationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are: - $true: UM integration is enabled in Outlook on the web. This is the default value. @@ -2288,7 +2500,6 @@ This parameter doesn't apply to the light version of Outlook on the web. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2298,13 +2509,15 @@ Accept wildcard characters: False ``` ### -UNCAccessOnPrivateComputersEnabled + +> 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: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2314,13 +2527,15 @@ Accept wildcard characters: False ``` ### -UNCAccessOnPublicComputersEnabled + +> 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: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2330,6 +2545,9 @@ Accept wildcard characters: False ``` ### -UseGB18030 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are: - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web. @@ -2339,7 +2557,6 @@ The UseGB18030 parameter specifies whether to use the GB18030 character set inst Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2349,6 +2566,9 @@ Accept wildcard characters: False ``` ### -UseISO885915 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are: - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web. @@ -2358,7 +2578,6 @@ The UseISO885915 parameter specifies whether to use the character set ISO8859-15 Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2368,6 +2587,9 @@ Accept wildcard characters: False ``` ### -UserContextTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UserContextTimeout parameter specifies the time-out setting in minutes for a user context object. This parameter doesn't limit public and private forms-based authentication time-out settings. The default value is 60. @@ -2376,7 +2598,6 @@ The default value is 60. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2386,13 +2607,15 @@ Accept wildcard characters: False ``` ### -VirtualDirectoryType + +> 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: VirtualDirectoryTypes Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2402,6 +2625,9 @@ Accept wildcard characters: False ``` ### -WacEditingEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are: - $true: Users can edit supported documents in Outlook on the web. This is the default value. @@ -2411,7 +2637,6 @@ The WacEditingEnabled parameter specifies whether to enable or disable editing d Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2421,6 +2646,9 @@ Accept wildcard characters: False ``` ### -WacViewingOnPrivateComputersEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are: - $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value. @@ -2432,7 +2660,6 @@ By default in Exchange 2013 or later, all Outlook on the web sessions are consid Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2442,6 +2669,9 @@ Accept wildcard characters: False ``` ### -WacViewingOnPublicComputersEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are: - $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value. @@ -2453,7 +2683,6 @@ In Exchange 2013 or later, users can only specify public computer sessions if yo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2463,6 +2692,9 @@ Accept wildcard characters: False ``` ### -WebPartsFrameOptionsType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are: - None: There are no restrictions on displaying Outlook on the web content in a frame. @@ -2473,7 +2705,6 @@ The WebPartsFrameOptionsType parameter specifies what sources can access web par Type: WebPartsFrameOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2483,6 +2714,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingForAllSupportedTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are: @@ -2494,7 +2728,6 @@ The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2504,6 +2737,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingOnPrivateComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are: @@ -2517,7 +2753,6 @@ By default in Exchange 2013, all Outlook on the web sessions are considered to b Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2527,6 +2762,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingOnPublicComputersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are: @@ -2540,7 +2778,6 @@ In Exchange 2013, users can only specify public computer sessions if you've enab Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2550,6 +2787,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingSupportedFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. This is a read-only parameter that can't be modified; use the WebReadyFileTypes parameter instead. @@ -2558,7 +2798,6 @@ This is a read-only parameter that can't be modified; use the WebReadyFileTypes Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2568,6 +2807,9 @@ Accept wildcard characters: False ``` ### -WebReadyDocumentViewingSupportedMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. This is a read-only parameter that can't be modified; use the WebReadyMimeTypes parameter instead. @@ -2576,7 +2818,6 @@ This is a read-only parameter that can't be modified; use the WebReadyMimeTypes Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2586,6 +2827,9 @@ Accept wildcard characters: False ``` ### -WebReadyFileTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyFileTypes parameter specifies the attachment file types (file extensions) that can be viewed by WebReady Document Viewing in Outlook on the web. The default value is all supported file types: @@ -2613,7 +2857,6 @@ This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parame Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2623,6 +2866,9 @@ Accept wildcard characters: False ``` ### -WebReadyMimeTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013 + This parameter is available only in Exchange Server 2010 and Exchange Server 2013. The WebReadyMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be viewed by WebReady Document Viewing in Outlook on the web. The default value is all supported MIME types: @@ -2649,7 +2895,6 @@ This list is used only if the WebReadyDocumentViewingForAllSupportedTypes parame Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -2659,13 +2904,15 @@ 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 @@ -2675,6 +2922,9 @@ Accept wildcard characters: False ``` ### -WindowsAuthentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WindowsAuthentication parameter enables or disables Integrated Windows authentication on the virtual directory. Valid values are: - $true: Integrated Windows authentication is enabled on the Outlook on the web virtual directory. @@ -2684,7 +2934,6 @@ The WindowsAuthentication parameter enables or disables Integrated Windows authe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2694,13 +2943,15 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPrivateComputersEnabled + +> 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: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2710,13 +2961,15 @@ Accept wildcard characters: False ``` ### -WSSAccessOnPublicComputersEnabled + +> 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: 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/exchange/Set-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-PartnerApplication.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md index 157ce52607..2533b5b171 100644 --- a/exchange/exchange-ps/exchange/Set-PartnerApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-partnerapplication applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-PartnerApplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-partnerapplication +schema: 2.0.0 +title: Set-PartnerApplication --- # Set-PartnerApplication @@ -93,6 +94,9 @@ This example refreshes the auth metadata for the HRApp partner application. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Identity parameter specifies the partner application you want to modify. You can use any value that uniquely identifies the partner application. For example: - Name @@ -104,7 +108,6 @@ The Identity parameter specifies the partner application you want to modify. You Type: PartnerApplicationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -114,13 +117,15 @@ Accept wildcard characters: False ``` ### -AcceptSecurityIdentifierInformation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AcceptSecurityIdentifierInformation parameter specifies whether Exchange should accept security identifiers (SIDs) from another trusted Active Directory forest for the partner application. By default, new partner applications are configured to not accept SIDs from another forest. If you're in deployment with a trusted forest, set the parameter to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -130,6 +135,9 @@ Accept wildcard characters: False ``` ### -AccountType + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are: - OrganizationalAccount: This is the default value @@ -139,7 +147,6 @@ The AccountType parameter specifies the type of Microsoft account that's require Type: SupportedAccountType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -149,13 +156,15 @@ Accept wildcard characters: False ``` ### -ActAsPermissions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ActAsPermissions parameter specifies the delegate permissions that are allowed for the partner application. You can specify multiple values separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -165,13 +174,15 @@ Accept wildcard characters: False ``` ### -ApplicationIdentifier + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ApplicationIdentifier parameter specifies a unique application identifier for the partner application that uses an authorization server. ```yaml Type: String Parameter Sets: ACSTrustApplication Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -181,6 +192,9 @@ Accept wildcard characters: False ``` ### -AppOnlyPermissions + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -189,7 +203,6 @@ This parameter is reserved for internal Microsoft use. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -199,6 +212,9 @@ Accept wildcard characters: False ``` ### -AuthMetadataUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AuthMetadataUrl parameter specifies the URL that Exchange can retrieve the AuthMetadata document from for a partner application that doesn't use an authorization server. @@ -207,7 +223,6 @@ The AuthMetadataUrl parameter specifies the URL that Exchange can retrieve the A Type: String Parameter Sets: AuthMetadataUrl Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -217,6 +232,9 @@ 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`. @@ -226,7 +244,6 @@ 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 @@ -236,6 +253,9 @@ 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. @@ -244,7 +264,6 @@ 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 @@ -254,13 +273,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether the partner application is enabled. By default, new partner applications are enabled. Set the parameter to $false to create the application configuration in a disabled state. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -270,6 +291,9 @@ Accept wildcard characters: False ``` ### -IssuerIdentifier + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter is reserved for internal Microsoft use. @@ -278,7 +302,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -288,13 +311,15 @@ Accept wildcard characters: False ``` ### -LinkedAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LinkedAccount parameter specifies a linked Active Directory user account for the application. Exchange evaluates Role Based Access Control (RBAC) permissions for the linked account when authorizing a token used to perform a task. ```yaml Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -304,13 +329,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies a new name for the partner application. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -320,6 +347,9 @@ Accept wildcard characters: False ``` ### -Realm + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Realm parameter specifies a security realm for the partner application. If the token is from a domain that's not an accepted domain, Exchange checks the realm specified in the token. In such a scenario, only tokens with the same realm specified in the partner application can access Exchange resources. @@ -328,7 +358,6 @@ The Realm parameter specifies a security realm for the partner application. If t Type: String Parameter Sets: ACSTrustApplication Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -338,6 +367,9 @@ Accept wildcard characters: False ``` ### -RefreshAuthMetadata + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RefreshAuthMetadata switch refreshes the auth metadata from the authorization server. You don't need to specify a value with this switch. @@ -346,7 +378,6 @@ The RefreshAuthMetadata switch refreshes the auth metadata from the authorizatio Type: SwitchParameter Parameter Sets: RefreshAuthMetadata Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,6 +387,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch. @@ -366,7 +400,6 @@ We don't recommend using this switch in a production environment. Type: SwitchParameter Parameter Sets: AuthMetadataUrl Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -376,13 +409,15 @@ 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/exchange/Set-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md index a823ef0913..76c559ebd0 100644 --- a/exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-pendingfederateddomain applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PendingFederatedDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-pendingfederateddomain +schema: 2.0.0 +title: Set-PendingFederatedDomain --- # Set-PendingFederatedDomain @@ -49,13 +50,15 @@ This example adds the pending domains contoso.com and sales.contoso.com to the e ## PARAMETERS ### -Identity + +> Applicable: 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ Accept wildcard characters: False ``` ### -PendingAccountNamespace + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PendingAccountNamespace parameter specifies the pending domain that's used as the account namespace for the federation trust. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -116,13 +125,15 @@ Accept wildcard characters: False ``` ### -PendingDomains + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PendingDomains parameter specifies the pending federated domains that are configured for the federation trust. ```yaml Type: SmtpDomain[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,13 +143,15 @@ 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/exchange/Set-PerimeterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PerimeterConfig.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-PerimeterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PerimeterConfig.md index d104c470f0..58bfc8ed09 100644 --- a/exchange/exchange-ps/exchange/Set-PerimeterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PerimeterConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-perimeterconfig applicable: Exchange Online, Exchange Online Protection -title: Set-PerimeterConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-perimeterconfig +schema: 2.0.0 +title: Set-PerimeterConfig --- # Set-PerimeterConfig @@ -43,13 +44,15 @@ This example shows how to add an IP address to cloud-based safelists where the g ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -59,6 +62,9 @@ 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`. @@ -68,7 +74,6 @@ 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,13 +83,15 @@ Accept wildcard characters: False ``` ### -GatewayIPAddresses + +> Applicable: Exchange Online + Use the GatewayIPAddresses parameter to create or modify a list of gateway server IP addresses to add to IP safelists. IP addresses are specified in IPv4 format, for example, 10.1.1.1. If you list more than one IP address, separate each entry with a comma. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -94,13 +101,15 @@ 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/exchange/Set-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md index 2e52b3a0fd..5f43067c19 100644 --- a/exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-phishsimoverridepolicy applicable: Exchange Online -title: Set-PhishSimOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-phishsimoverridepolicy +schema: 2.0.0 +title: Set-PhishSimOverridePolicy --- # Set-PhishSimOverridePolicy @@ -46,6 +47,9 @@ This example disables the phishing simulation override policy. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the phishing simulation override policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -57,7 +61,6 @@ The Identity parameter specifies the phishing simulation override policy that yo Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -67,13 +70,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -83,6 +88,9 @@ 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`. @@ -92,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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 @@ -118,6 +127,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the policy is enabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -127,7 +139,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -137,6 +148,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -145,7 +159,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -155,13 +168,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + The WhatIf switch doesn't work in Security & Compliance PowerShell. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-Place.md b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-Place.md rename to exchange/exchange-ps/ExchangePowerShell/Set-Place.md index aeffd3882a..7cc5608d04 100644 --- a/exchange/exchange-ps/exchange/Set-Place.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-place applicable: Exchange Online -title: Set-Place -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-place +schema: 2.0.0 +title: Set-Place --- # Set-Place @@ -73,6 +74,9 @@ The example adds the specified metadata to the room mailbox named Conference Roo ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the room mailbox that you want to modify. You can use any value that uniquely identifies the room. For example: - Name @@ -86,7 +90,6 @@ The Identity parameter specifies the room mailbox that you want to modify. You c Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -96,6 +99,9 @@ Accept wildcard characters: False ``` ### -AudioDeviceName + +> Applicable: Exchange Online + The AudioDeviceName parameter specifies the name of the audio device in the room. If the value contains spaces, enclose the value in quotation marks ("). The default value is blank ($null). To indicate that this room has no audio device, use the value $null for this parameter. @@ -104,7 +110,6 @@ The default value is blank ($null). To indicate that this room has no audio devi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -114,13 +119,15 @@ Accept wildcard characters: False ``` ### -Building + +> Applicable: Exchange Online + The Building parameter specifies the building name or building number that the room is in. 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 @@ -130,13 +137,15 @@ Accept wildcard characters: False ``` ### -Capacity + +> Applicable: Exchange Online + The Capacity parameter specifies the capacity of the room. A valid value is an integer. ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -146,13 +155,15 @@ Accept wildcard characters: False ``` ### -City + +> Applicable: Exchange Online + The City parameter specifies the room's city. 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 @@ -162,13 +173,15 @@ 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 @@ -178,6 +191,9 @@ Accept wildcard characters: False ``` ### -CountryOrRegion + +> Applicable: Exchange Online + The CountryOrRegion parameter specifies the room's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name). A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). @@ -188,7 +204,6 @@ The friendly name is returned in the CountryOrRegion property value by the Get-P Type: CountryInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -198,6 +213,9 @@ Accept wildcard characters: False ``` ### -DisplayDeviceName + +> Applicable: Exchange Online + The DisplayDeviceName parameter specifies the name of the display device in the room. If the value contains spaces, enclose the value in quotation marks ("). The default value is blank ($null). To indicate that this room has no display device, use the value $null for this parameter. @@ -206,7 +224,6 @@ The default value is blank ($null). To indicate that this room has no display de Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -216,13 +233,15 @@ Accept wildcard characters: False ``` ### -Floor + +> Applicable: Exchange Online + The Floor parameter specifies the floor number that the room is on. ```yaml Type: System.Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -232,13 +251,15 @@ Accept wildcard characters: False ``` ### -FloorLabel + +> Applicable: Exchange Online + The FloorLabel parameter specifies a descriptive label for the floor that the room is on. 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 @@ -248,6 +269,9 @@ Accept wildcard characters: False ``` ### -GeoCoordinates + +> Applicable: Exchange Online + The GeoCoordinates parameter specifies the room's location in latitude, longitude and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats: - Latitude and longitude: For example, "47.644125;-122.122411" @@ -259,7 +283,6 @@ The GeoCoordinates parameter specifies the room's location in latitude, longitud Type: GeoCoordinates Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -269,6 +292,9 @@ Accept wildcard characters: False ``` ### -IsWheelChairAccessible + +> Applicable: Exchange Online + The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are: - $true: The room is wheelchair accessible. @@ -278,7 +304,6 @@ The IsWheelChairAccessible parameter specifies whether the room is wheelchair ac Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -288,13 +313,15 @@ Accept wildcard characters: False ``` ### -Label + +> Applicable: Exchange Online + The Label parameter specifies a descriptive label for the room (for example, a number or name). 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 @@ -304,6 +331,9 @@ Accept wildcard characters: False ``` ### -MTREnabled + +> Applicable: Exchange Online + **Note**: Currently, this parameter is informational only and results in no additional functionality. The MTREnabled parameter identifies the room as configured with a Microsoft Teams room system. You can add Teams room systems as audio sources in Teams meetings that involve the room. Valid values are: @@ -317,7 +347,6 @@ For more information about Microsoft Teams Rooms, see [Microsoft Teams Rooms](ht Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -327,6 +356,9 @@ Accept wildcard characters: False ``` ### -ParentId + +> Applicable: Exchange Online + **Note**: This feature is experimental and is available only for organizations using Microsoft Places. The ParentId parameter specifies the ID of a Place in the parent location hierarchy in Microsoft Places. @@ -337,7 +369,6 @@ Organizations that are onboarding Rooms and Workspaces to Microsoft Places need Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -347,6 +378,9 @@ Accept wildcard characters: False ``` ### -ParentType + +> Applicable: Exchange Online + **Note**: This feature is experimental and is available only for organizations using Microsoft Places. The ParentType parameter specifies the parent type of the ParentId in Microsoft Places. Valid values are: @@ -360,7 +394,6 @@ Organizations that are onboarding Rooms and Workspaces to Microsoft Places need Type: Microsoft.Exchange.Management.RecipientTasks.SetPlaceParentType Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -370,13 +403,15 @@ Accept wildcard characters: False ``` ### -Phone + +> Applicable: Exchange Online + The Phone parameter specifies the room's telephone number. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -386,13 +421,15 @@ Accept wildcard characters: False ``` ### -PostalCode + +> Applicable: Exchange Online + The PostalCode parameter specifies the room's postal code. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -402,13 +439,15 @@ Accept wildcard characters: False ``` ### -State + +> Applicable: Exchange Online + The State parameter specifies the room's state or province. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -418,13 +457,15 @@ Accept wildcard characters: False ``` ### -Street + +> Applicable: Exchange Online + The Street parameter specifies the room's physical address. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -434,6 +475,9 @@ Accept wildcard characters: False ``` ### -Tags + +> Applicable: Exchange Online + The Tags parameter specifies additional features of the room (for example, details like the type of view or furniture type). You can specify multiple labels separated by commas. If the labels contains spaces, enclose the values in quotation marks: `"Label 1","Label 2",..."Label N"`. @@ -442,7 +486,6 @@ You can specify multiple labels separated by commas. If the labels contains spac Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -452,6 +495,9 @@ Accept wildcard characters: False ``` ### -VideoDeviceName + +> Applicable: Exchange Online + The VideoDeviceName parameter specifies the name of the video device in the room. If the value contains spaces, enclose the value in quotation marks ("). The default value is blank ($null). To indicate that this room has no video device, use the value $null for this parameter. @@ -460,7 +506,6 @@ The default value is blank ($null). To indicate that this room has no video devi Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -470,13 +515,15 @@ 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/exchange/Set-PolicyConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-PolicyConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md index 6455c497f6..150586a735 100644 --- a/exchange/exchange-ps/exchange/Set-PolicyConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-policyconfig applicable: Security & Compliance -title: Set-PolicyConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-policyconfig +schema: 2.0.0 +title: Set-PolicyConfig --- # Set-PolicyConfig @@ -70,13 +71,15 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned ## 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 @@ -86,13 +89,15 @@ Accept wildcard characters: False ``` ### -CaseHoldPolicyLimit + +> Applicable: Security & Compliance + {{ Fill CaseHoldPolicyLimit Description }} ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -102,6 +107,9 @@ Accept wildcard characters: False ``` ### -ClassificationScheme + +> Applicable: Security & Compliance + {{ Fill ClassificationScheme Description }} ```yaml @@ -109,7 +117,6 @@ Type: ClassificationScheme Parameter Sets: (All) Aliases: Accepted values: Default, V0_AggregatedOnly, V1_DetailedResults -Applicable: Security & Compliance Required: False Position: Named @@ -119,13 +126,15 @@ Accept wildcard characters: False ``` ### -ComplianceUrl + +> Applicable: Security & Compliance + {{ Fill ComplianceUrl Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -135,6 +144,9 @@ 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. @@ -144,7 +156,6 @@ 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,13 +165,15 @@ Accept wildcard characters: False ``` ### -DlpAppGroups + +> Applicable: Security & Compliance + {{ Fill DlpAppGroups Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -170,13 +183,15 @@ Accept wildcard characters: False ``` ### -DlpAppGroupsPsws + +> Applicable: Security & Compliance + {{ Fill DlpAppGroupsPsws Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -186,13 +201,15 @@ Accept wildcard characters: False ``` ### -DlpExtensionGroups + +> Applicable: Security & Compliance + {{ Fill DlpExtensionGroups Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -202,13 +219,15 @@ Accept wildcard characters: False ``` ### -DlpNetworkShareGroups + +> Applicable: Security & Compliance + {{ Fill DlpNetworkShareGroups Description }} ```yaml Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -218,13 +237,15 @@ Accept wildcard characters: False ``` ### -DlpPrinterGroups + +> Applicable: Security & Compliance + {{ Fill DlpPrinterGroups Description }} ```yaml Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -234,13 +255,15 @@ Accept wildcard characters: False ``` ### -DlpRemovableMediaGroups + +> Applicable: Security & Compliance + {{ Fill DlpRemovableMediaGroups Description }} ```yaml Type: PswsHashtable Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -250,6 +273,9 @@ Accept wildcard characters: False ``` ### -DocumentIsUnsupportedSeverity + +> Applicable: Security & Compliance + {{ Fill DocumentIsUnsupportedSeverity Description }} ```yaml @@ -257,7 +283,6 @@ Type: RuleSeverity Parameter Sets: (All) Aliases: Accepted values: Low, Medium, High, None, Informational, Information -Applicable: Security & Compliance Required: False Position: Named @@ -267,13 +292,15 @@ Accept wildcard characters: False ``` ### -EnableAdvancedRuleBuilder + +> Applicable: Security & Compliance + {{ Fill EnableAdvancedRuleBuilder Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -283,6 +310,9 @@ Accept wildcard characters: False ``` ### -EnableLabelCoauth + +> Applicable: Security & Compliance + The EnableLabelCoauth parameter enables or disables co-authoring support in Office desktop apps for the entire organization. Valid value are: - $true: Co-authoring support in Office desktop apps is enabled. When documents are labeled and encrypted by sensitivity labels, multiple users can edit these documents at the same time. Labeling information for unencrypted files is no longer saved in custom properties. Don't enable co-authoring if you use any apps, services, scripts, or tools that read or write labeling metadata to the old location. @@ -299,7 +329,6 @@ Disabling co-authoring support in Office desktop apps in the organization has th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -309,6 +338,9 @@ Accept wildcard characters: False ``` ### -EnableSpoAipMigration + +> Applicable: Security & Compliance + The EnableSpoAipMigration parameter enables or disables built-in labeling for supported Office files in SharePoint and OneDrive. Valid values are: - $true: Users can apply your sensitivity labels in Office for the web. Users will see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar. @@ -318,7 +350,6 @@ The EnableSpoAipMigration parameter enables or disables built-in labeling for su Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -328,6 +359,9 @@ Accept wildcard characters: False ``` ### -EndpointDlpGlobalSettings + +> Applicable: Security & Compliance + The EndpointDlpGlobalSettings parameter specifies the global endpoints. This parameter uses the following syntax: `@(@{"Setting"=""; "Value"="}",@{"Setting"=""; "Value"=""},...)`. The value of `` is one of the supported values. @@ -350,7 +384,6 @@ Example values: Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -360,13 +393,15 @@ Accept wildcard characters: False ``` ### -EndpointDlpGlobalSettingsPsws + +> Applicable: Security & Compliance + {{ Fill EndpointDlpGlobalSettingsPsws Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -376,6 +411,9 @@ Accept wildcard characters: False ``` ### -ExtendTeamsDlpPoliciesToSharePointOneDrive + +> Applicable: Security & Compliance + The ExtendTeamsDlpPoliciesToSharePointOneDrive parameter enables the Teams DLP Policy to automatically extend protection to the content stored in OneDrive shared in 1:1 chats and content stored in SharePoint associated with Teams teams shared through channel chats. Valid values are: - $true @@ -385,7 +423,6 @@ The ExtendTeamsDlpPoliciesToSharePointOneDrive parameter enables the Teams DLP P Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -395,6 +432,9 @@ Accept wildcard characters: False ``` ### -InformationBarrierMode + +> Applicable: Security & Compliance + The InformationBarrierMode parameter specifies the mode that controls the total number of segments and how many segments a user can be part of. Valid values are: - SingleSegment: Users in the organization can have 5000 segments but can only be assigned to one segment. @@ -405,7 +445,6 @@ Type: InformationBarrierMode Parameter Sets: (All) Aliases: Accepted values: SingleSegment, MultiSegment -Applicable: Security & Compliance Required: False Position: Named @@ -415,6 +454,9 @@ Accept wildcard characters: False ``` ### -InformationBarrierPeopleSearchRestriction + +> Applicable: Security & Compliance + {{ Fill InformationBarrierPeopleSearchRestriction Description }} ```yaml @@ -422,7 +464,6 @@ Type: InformationBarrierPeopleSearchRestriction Parameter Sets: (All) Aliases: Accepted values: Enabled, Disabled -Applicable: Security & Compliance Required: False Position: Named @@ -432,13 +473,15 @@ Accept wildcard characters: False ``` ### -IsDlpSimulationOptedIn + +> Applicable: Security & Compliance + {{ Fill IsDlpSimulationOptedIn Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -448,6 +491,9 @@ Accept wildcard characters: False ``` ### -OnPremisesWorkload + +> Applicable: Security & Compliance + {{ Fill OnPremisesWorkload Description }} ```yaml @@ -455,7 +501,6 @@ Type: Workload Parameter Sets: (All) Aliases: Accepted values: None, Exchange, SharePoint, Intune, OneDriveForBusiness, PublicFolder, SharePointOnPremises, ExchangeOnPremises, AuditAlerting, Skype, ModernGroup, DynamicScope, Teams, UnifiedAuditAzure, EndpointDevices, ThirdPartyApps, OnPremisesScanner -Applicable: Security & Compliance Required: False Position: Named @@ -465,6 +510,9 @@ Accept wildcard characters: False ``` ### -ProcessingLimitExceededSeverity + +> Applicable: Security & Compliance + {{ Fill ProcessingLimitExceededSeverity Description }} ```yaml @@ -472,7 +520,6 @@ Type: RuleSeverity Parameter Sets: (All) Aliases: Accepted values: Low, Medium, High, None, Informational, Information -Applicable: Security & Compliance Required: False Position: Named @@ -482,13 +529,15 @@ Accept wildcard characters: False ``` ### -PurviewLabelConsent + +> Applicable: Security & Compliance + {{ Fill PurviewLabelConsent Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -498,13 +547,15 @@ Accept wildcard characters: False ``` ### -ReservedForFutureUse + +> Applicable: Security & Compliance + {{ Fill ReservedForFutureUse Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -514,13 +565,15 @@ Accept wildcard characters: False ``` ### -RetentionForwardCrawl + +> Applicable: Security & Compliance + {{ Fill RetentionForwardCrawl Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -530,6 +583,9 @@ 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 @@ -540,7 +596,6 @@ Type: PolicyRuleErrorAction Parameter Sets: (All) Aliases: Accepted values: Ignore, RetryThenBlock -Applicable: Security & Compliance Required: False Position: Named @@ -550,6 +605,9 @@ 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. @@ -561,7 +619,6 @@ Type: PolicySenderAddressLocation Parameter Sets: (All) Aliases: Accepted values: Header, Envelope, HeaderOrEnvelope -Applicable: Security & Compliance Required: False Position: Named @@ -571,13 +628,15 @@ Accept wildcard characters: False ``` ### -SiteGroups + +> Applicable: Security & Compliance + {{ Fill SiteGroups Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -587,13 +646,15 @@ Accept wildcard characters: False ``` ### -SiteGroupsPsws + +> Applicable: Security & Compliance + {{ Fill SiteGroupsPsws Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -603,13 +664,15 @@ 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/exchange/Set-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-PolicyTipConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md index 16cd681d3b..9477308f16 100644 --- a/exchange/exchange-ps/exchange/Set-PolicyTipConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-policytipconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-PolicyTipConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-policytipconfig +schema: 2.0.0 +title: Set-PolicyTipConfig --- # Set-PolicyTipConfig @@ -51,6 +52,9 @@ This example replaces the text of all custom Spanish Policy Tips with the value, ## 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 modify. 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. @@ -62,7 +66,6 @@ The Identity parameter specifies the custom Policy Tip you want to modify. You c Type: PolicyTipConfigIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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. @@ -99,7 +107,6 @@ 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,13 +116,15 @@ Accept wildcard characters: False ``` ### -Value + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Value parameter specifies the text that's displayed by the Policy Tip. 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, Exchange Online Required: False Position: Named @@ -125,13 +134,15 @@ 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/exchange/Set-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-PopSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md index a6e5d017f8..e5196cf66a 100644 --- a/exchange/exchange-ps/exchange/Set-PopSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-popsettings applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PopSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-popsettings +schema: 2.0.0 +title: Set-PopSettings --- # Set-PopSettings @@ -100,6 +101,9 @@ This example specifies the certificate that contains mail.contoso.com is used to ## PARAMETERS ### -AuthenticatedConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthenticatedConnectionTimeout parameter specifies the time to wait before closing an idle authenticated connection. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -110,7 +114,6 @@ Valid values are 00:00:30 to 1:00:00. The default value is 00:30:00 (30 minutes) Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,13 +123,15 @@ Accept wildcard characters: False ``` ### -Banner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Banner parameter specifies the text string that's displayed to connecting POP3 clients. The default value is: The Microsoft Exchange POP3 service is ready. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,6 +141,9 @@ Accept wildcard characters: False ``` ### -CalendarItemRetrievalOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are: - 0 or iCalendar. This is the default value. @@ -149,7 +157,6 @@ If you specify 3 or Custom, you need to specify a value for the OwaServerUrl par Type: CalendarItemRetrievalOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,6 +166,9 @@ 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`. @@ -168,7 +178,6 @@ 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 @@ -178,13 +187,15 @@ 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 @@ -194,6 +205,9 @@ Accept wildcard characters: False ``` ### -EnableExactRFC822Size + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients. Valid values are: - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your POP3 clients. @@ -203,7 +217,6 @@ The EnableExactRFC822Size parameter specifies how message sizes are presented to Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -213,6 +226,9 @@ Accept wildcard characters: False ``` ### -EnableGSSAPIAndNTLMAuth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) by using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are: - $true: NTLM for POP3 connections is enabled. This is the default value. @@ -222,7 +238,6 @@ The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Inte Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -232,6 +247,9 @@ Accept wildcard characters: False ``` ### -EnforceCertificateErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnforceCertificateErrors parameter specifies whether to enforce Secure Sockets Layer (SSL) certificate validation failures. Valid values are: - $true: If the certificate isn't valid or doesn't match the target POP3 server's FQDN, the connection attempt fails. @@ -241,7 +259,6 @@ The EnforceCertificateErrors parameter specifies whether to enforce Secure Socke Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -251,6 +268,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used for POP3 connections. Valid values are: - None: Extended Protection for Authentication isn't used. This is the default value. @@ -263,7 +283,6 @@ Extended Protection for Authentication enhances the protection and handling of c Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -273,6 +292,9 @@ Accept wildcard characters: False ``` ### -ExternalConnectionSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by external POP3 clients (POP3 connections from outside your corporate network). This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). @@ -289,7 +311,6 @@ The combination of encryption methods and ports that are specified for this para Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -299,6 +320,9 @@ Accept wildcard characters: False ``` ### -InternalConnectionSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by internal POP3 clients (POP3 connections from inside your corporate network). This setting is also used when a POP3 connection is forwarded to another Exchange server that's running the Microsoft Exchange POP3 service. This parameter uses the syntax `HostName:Port:[]`. The encryption method value is optional (blank indicates unencrypted connections). @@ -315,7 +339,6 @@ The combination of encryption methods and ports that are specified for this para Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -325,6 +348,9 @@ Accept wildcard characters: False ``` ### -LogFileLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogFileLocation parameter specifies the location for the POP3 protocol log files. The default location is%ExchangeInstallPath%Logging\\Pop3. This parameter is only meaningful when the ProtocolLogEnabled parameter value is $true. @@ -333,7 +359,6 @@ This parameter is only meaningful when the ProtocolLogEnabled parameter value is Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -343,6 +368,9 @@ Accept wildcard characters: False ``` ### -LogFileRollOverSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are: - 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016. @@ -356,7 +384,6 @@ This parameter is only meaningful when the LogPerFileSizeQuota parameter value i Type: LogFileRollOver Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -366,6 +393,9 @@ Accept wildcard characters: False ``` ### -LoginType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LoginType parameter specifies the authentication method for POP3 connections. Valid values are: - 1 or PlainTextLogin. @@ -376,7 +406,6 @@ The LoginType parameter specifies the authentication method for POP3 connections Type: LoginOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -386,6 +415,9 @@ Accept wildcard characters: False ``` ### -LogPerFileSizeQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LogPerFileSizeQuota parameter specifies the maximum size of a POP3 protocol log file. When you enter a value, qualify the value with one of the following units: @@ -406,7 +438,6 @@ This parameter is only meaningful when the ProtocolLogEnabled parameter value is Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -416,13 +447,15 @@ Accept wildcard characters: False ``` ### -MaxCommandSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxCommandSize parameter specifies the maximum size in bytes of a single POP3 command. Valid values are from 40 through 1024. The default value is 512. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -432,13 +465,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionFromSingleIP + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionFromSingleIP parameter specifies the maximum number of POP3 connections that are accepted by the Exchange server from a single IP address. Valid values are from 1 through 2147483647. The default value is 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -448,13 +483,15 @@ Accept wildcard characters: False ``` ### -MaxConnections + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnections parameter specifies the maximum number of POP3 connections that are accepted by the Exchange server. Valid values are from 1 through 2147483647. The default value is 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -464,13 +501,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionsPerUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionsPerUser parameter specifies the maximum number of POP3 connections that are allowed for each user. Valid values are from 1 through 2147483647. The default value is 16. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -480,6 +519,9 @@ Accept wildcard characters: False ``` ### -MessageRetrievalMimeFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are: - 0 or TextOnly. @@ -494,7 +536,6 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages Type: MimeTextFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -504,6 +545,9 @@ Accept wildcard characters: False ``` ### -MessageRetrievalSortOrder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are: - 0 or Ascending. This is the default value. @@ -513,7 +557,6 @@ The MessageRetrievalSortOrder parameter specifies how retrieved messages are sor Type: SortOrder Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -523,13 +566,15 @@ Accept wildcard characters: False ``` ### -OwaServerUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaServerUrl parameter specifies the URL that's used to retrieve calendar information for instances of custom Outlook on the web calendar items. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -539,6 +584,9 @@ Accept wildcard characters: False ``` ### -PreAuthenticatedConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PreAuthenticatedConnectionTimeout parameter specifies the time to wait before closing an idle POP3 connection that isn't authenticated. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -549,7 +597,6 @@ Valid values are from00:00:30 to 1:00:00. The default value is 00:01:00 (one min Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -559,6 +606,9 @@ Accept wildcard characters: False ``` ### -ProtocolLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are: - $true: POP3 protocol logging is enabled. @@ -568,7 +618,6 @@ The ProtocolLogEnabled parameter specifies whether to enable protocol logging fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -578,13 +627,15 @@ Accept wildcard characters: False ``` ### -ProxyTargetPort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProxyTargetPort parameter specifies the port on the Microsoft Exchange POP3 Backend service that listens for client connections that are proxied from the Microsoft Exchange POP3 service. The default value is 1995. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -594,6 +645,9 @@ 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 @@ -607,7 +661,6 @@ 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 @@ -617,6 +670,9 @@ Accept wildcard characters: False ``` ### -SSLBindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SSLBindings parameter specifies the IP address and TCP port that's used for an POP3 connection that's always encrypted by SSL/TLS. This parameter uses the syntax `IPv4OrIPv6Address:Port`. The default value is `[::]:995,0.0.0.0:995`. @@ -629,7 +685,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -639,6 +694,9 @@ Accept wildcard characters: False ``` ### -SuppressReadReceipt + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to POP3 clients that have the Send read receipts for messages I send setting configured in their POP3 email program. Valid values are: - $true: The sender receives a read receipt only when the recipient opens the message. @@ -648,7 +706,6 @@ The SuppressReadReceipt parameter specifies whether to stop duplicate read recei Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -658,6 +715,9 @@ Accept wildcard characters: False ``` ### -UnencryptedOrTLSBindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UnencryptedOrTLSBindings parameter specifies the IP address and TCP port that's used for unencrypted POP3 connections, or POP3 connections that are encrypted by using opportunistic TLS (STARTTLS) after the initial unencrypted protocol handshake. This parameter uses the syntax `IPv4OrIPv6Address:Port`. The default value is `[::]:110, 0.0.0.0:110`. @@ -670,7 +730,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -680,13 +739,15 @@ 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 @@ -696,6 +757,9 @@ Accept wildcard characters: False ``` ### -X509CertificateName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X509CertificateName parameter specifies the certificate that's used for encrypting POP3 client connections. A valid value for this parameter is the FQDN from the ExternalConnectionSettings or InternalConnectionSettings parameters (for example, mail.contoso.com or mailbox01.contoso.com). @@ -708,7 +772,6 @@ If you use a wildcard certificate, you don't need to assign the certificate to t 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/exchange/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md index 16c3da7808..b45e775032 100644 --- a/exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-powershellvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PowerShellVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-powershellvirtualdirectory +schema: 2.0.0 +title: Set-PowerShellVirtualDirectory --- # Set-PowerShellVirtualDirectory @@ -54,6 +55,9 @@ This example modifies the external URL of the Contoso Windows PowerShell virtual ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -66,7 +70,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -76,6 +79,9 @@ 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. @@ -85,7 +91,6 @@ 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 @@ -95,13 +100,15 @@ Accept wildcard characters: False ``` ### -CertificateAuthentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CertificateAuthentication parameter specifies whether certificate authentication is enabled on the Windows PowerShell virtual directory. The 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 Required: False Position: Named @@ -111,6 +118,9 @@ 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`. @@ -120,7 +130,6 @@ 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,13 +139,15 @@ 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 @@ -146,6 +157,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionFlags + +> Applicable: 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. @@ -158,7 +172,6 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -168,6 +181,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionSPNList + +> Applicable: 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. @@ -177,7 +193,6 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -187,6 +202,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionTokenChecking + +> Applicable: 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. @@ -199,7 +217,6 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend Type: ExtendedProtectionTokenCheckingMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -209,13 +226,15 @@ 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 @@ -225,13 +244,15 @@ 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 @@ -241,13 +262,15 @@ Accept wildcard characters: False ``` ### -RequireSSL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireSSL parameter specifies whether the Windows PowerShell virtual directory should require that the client connection be made using Secure Sockets Layer (SSL). The valid values are $true and $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 @@ -257,13 +280,15 @@ 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 @@ -273,6 +298,9 @@ 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. @@ -282,7 +310,6 @@ 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 diff --git a/exchange/exchange-ps/exchange/Set-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-ProtectionAlert.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md index 39c461d99d..7a3990e731 100644 --- a/exchange/exchange-ps/exchange/Set-ProtectionAlert.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-protectionalert applicable: Security & Compliance -title: Set-ProtectionAlert -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-protectionalert +schema: 2.0.0 +title: Set-ProtectionAlert --- # Set-ProtectionAlert @@ -74,6 +75,9 @@ This example modifies an alert so that even though it's configured for aggregate ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the alert policy that you want to modify. You can use any value that uniquely identifies the alert policy. For example: - Name @@ -84,7 +88,6 @@ The Identity parameter specifies the alert policy that you want to modify. You c Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -94,6 +97,9 @@ Accept wildcard characters: False ``` ### -AggregationType + +> Applicable: Security & Compliance + The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are: - None: Alerts are triggered for every occurrence of the activity. @@ -104,7 +110,6 @@ The AggregationType parameter specifies the how the alert policy triggers alerts Type: AlertAggregationType Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -114,6 +119,9 @@ Accept wildcard characters: False ``` ### -AlertBy + +> Applicable: Security & Compliance + The AlertBy parameter specifies the scope for aggregated alert policies. Valid values are determined by the ThreatType parameter value: - Activity: Valid values are User or $null (blank, which is the default value). If you don't use the value User, the scope of the alert policy is the entire organization. @@ -127,7 +135,6 @@ You can't use this parameter when the AggregationType parameter value is None (a Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -137,13 +144,15 @@ Accept wildcard characters: False ``` ### -AlertFor + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -153,6 +162,9 @@ Accept wildcard characters: False ``` ### -Category + +> Applicable: Security & Compliance + The Category parameter specifies a category for the alert policy. Valid values are: - AccessGovernance @@ -170,7 +182,6 @@ When an activity occurs that matches the conditions of the alert policy, the ale Type: AlertRuleCategory Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -180,13 +191,15 @@ 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 @@ -196,6 +209,9 @@ 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`. @@ -205,7 +221,6 @@ 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 @@ -215,13 +230,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Security & Compliance + The Description parameter specifies descriptive text for the alert policy. 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 @@ -231,6 +248,9 @@ Accept wildcard characters: False ``` ### -Disabled + +> Applicable: Security & Compliance + The Disabled parameter enables or disables the alert policy. Valid values are: - $true: The alert policy is disabled. @@ -240,7 +260,6 @@ The Disabled parameter enables or disables the alert policy. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -250,6 +269,9 @@ Accept wildcard characters: False ``` ### -Filter + +> Applicable: Security & Compliance + 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. @@ -310,7 +332,6 @@ You can specify multiple criteria by using the -and comparison operator. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -320,6 +341,9 @@ Accept wildcard characters: False ``` ### -NotificationCulture + +> Applicable: Security & Compliance + The NotificationCulture parameter specifies the language or locale that's used for notifications. 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). @@ -328,7 +352,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -338,13 +361,15 @@ Accept wildcard characters: False ``` ### -NotificationEnabled + +> Applicable: Security & Compliance + {{ Fill NotificationEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -354,13 +379,15 @@ Accept wildcard characters: False ``` ### -NotifyUser + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -370,6 +397,9 @@ Accept wildcard characters: False ``` ### -NotifyUserOnFilterMatch + +> Applicable: Security & Compliance + The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are: - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning). @@ -381,7 +411,6 @@ You can't use this parameter when the AggregationType parameter value is None (a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -391,6 +420,9 @@ Accept wildcard characters: False ``` ### -NotifyUserSuppressionExpiryDate + +> Applicable: Security & Compliance + The NotifyUserSuppressionExpiryDate parameter specifies whether to temporarily suspend notifications for the alert policy. Until the specified date-time, no notifications are sent for detected activities. 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". @@ -399,7 +431,6 @@ 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 @@ -409,6 +440,9 @@ Accept wildcard characters: False ``` ### -NotifyUserThrottleThreshold + +> Applicable: Security & Compliance + The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are: - An integer. @@ -418,7 +452,6 @@ The NotifyUserThrottleThreshold parameter specifies the maximum number of notifi Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -428,6 +461,9 @@ Accept wildcard characters: False ``` ### -NotifyUserThrottleWindow + +> Applicable: Security & Compliance + The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are: - An integer. @@ -437,7 +473,6 @@ The NotifyUserThrottleWindow parameter specifies the time interval in minutes th Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -447,6 +482,9 @@ Accept wildcard characters: False ``` ### -Operation + +> Applicable: Security & Compliance + The Operation parameter specifies the activities that are monitored by the alert policy. For the list of available activities, see the Audited activities tab at [Audited activities](https://learn.microsoft.com/purview/audit-log-activities). Although this parameter is technically capable of accepting multiple values separated by commas, multiple values don't work. @@ -457,7 +495,6 @@ You can only use this parameter when the ThreatType parameter has the value Acti Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -467,13 +504,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypes + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -483,13 +522,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypesForCounting + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypesForCounting Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -499,13 +540,15 @@ Accept wildcard characters: False ``` ### -PrivacyManagementScopedSensitiveInformationTypesThreshold + +> Applicable: Security & Compliance + {{ Fill PrivacyManagementScopedSensitiveInformationTypesThreshold Description }} ```yaml Type: System.UInt64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -515,6 +558,9 @@ Accept wildcard characters: False ``` ### -Severity + +> Applicable: Security & Compliance + The Severity parameter specifies the severity of the detection. Valid values are: - Low (This is the default value) @@ -525,7 +571,6 @@ The Severity parameter specifies the severity of the detection. Valid values are Type: RuleSeverity Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -535,6 +580,9 @@ Accept wildcard characters: False ``` ### -Threshold + +> Applicable: Security & Compliance + The Threshold parameter specifies the number of detections that trigger the alert policy (within the time period specified by the TimeWindow parameter). A valid value is an integer that's greater than or equal to 3. You can only use this parameter when the AggregationType parameter value is SimpleAggregation. @@ -543,7 +591,6 @@ You can only use this parameter when the AggregationType parameter value is Simp Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -553,6 +600,9 @@ Accept wildcard characters: False ``` ### -TimeWindow + +> Applicable: Security & Compliance + The TimeWindow parameter specifies the time interval in minutes for number of detections specified by the Threshold parameter. A valid value is an integer that's greater than 60 (one hour). You can only use this parameter when the AggregationType parameter value is SimpleAggregation. @@ -561,7 +611,6 @@ You can only use this parameter when the AggregationType parameter value is Simp Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -571,13 +620,15 @@ Accept wildcard characters: False ``` ### -VolumeThreshold + +> Applicable: Security & Compliance + {{ Fill VolumeThreshold Description }} ```yaml Type: System.UInt64 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -587,13 +638,15 @@ 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/exchange/Set-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-PublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md index 089d38d7be..6f1af2e50d 100644 --- a/exchange/exchange-ps/exchange/Set-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfolder applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-PublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfolder +schema: 2.0.0 +title: Set-PublicFolder --- # Set-PublicFolder @@ -79,13 +80,15 @@ In Exchange 2010, this example sets the folder to replicate only on weekends. ## 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 modify. A valid value uses the format: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`. ```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 @@ -95,6 +98,9 @@ Accept wildcard characters: False ``` ### -AgeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AgeLimit parameter specifies the overall age limit on the folder. Items that reach the age limit are deleted from the public folder. Replicas of this public folder are automatically deleted when the age limit is exceeded. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -103,7 +109,6 @@ 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, Exchange Online Required: False Position: Named @@ -113,6 +118,9 @@ 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,7 +130,6 @@ 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 @@ -132,6 +139,9 @@ 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,7 +150,6 @@ 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,13 +159,15 @@ Accept wildcard characters: False ``` ### -EformsLocaleId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The EformsLocaleId parameter specifies the locale-specific version of the e-forms library. The valid input for the EformsLocaleId parameter is the string names listed in the Culture Name column in the Microsoft .NET Class Library class reference available at [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo). ```yaml Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -166,6 +177,9 @@ 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. @@ -174,7 +188,6 @@ 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 @@ -184,6 +197,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The HiddenFromAddressListsEnabled parameter specifies whether to hide the public folder from address lists. @@ -192,7 +208,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether to hide the public Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -202,6 +217,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IssueWarningQuota parameter specifies the public folder size that triggers a warning to public folder owners stating that the folder is almost full. The default value is unlimited, which is 2 terabytes. @@ -222,7 +240,6 @@ The valid input range for this parameter is from 1 through 2TB. 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 @@ -232,6 +249,9 @@ Accept wildcard characters: False ``` ### -LocalReplicaAgeLimit + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The LocalReplicaAgeLimit parameter specifies the age limit of the replica on the connected server, if there is a replica on it. @@ -240,7 +260,6 @@ The LocalReplicaAgeLimit parameter specifies the age limit of the replica on the Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -250,6 +269,9 @@ Accept wildcard characters: False ``` ### -MailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailEnabled parameter specifies that the public folder is mail-enabled. To do this, you use the value $true. You use this parameter to correct a mail-enabled public folder that lost its mail-enabled status. If you attempt to use this parameter to mail-enable a public folder that was never mail-enabled, the command will fail. @@ -258,7 +280,6 @@ You use this parameter to correct a mail-enabled public folder that lost its mai Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -268,6 +289,9 @@ Accept wildcard characters: False ``` ### -MailRecipientGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MailRecipientGuid parameter specifies the MailRecipientGuid value of the public folder. You use this parameter to correct a mail-enabled public folder that lost its MailRecipientGuid value. The value that you specify for this parameter must match the MailRecipientGuid value of an existing mail-enabled public folder. Otherwise, the command will fail. @@ -276,7 +300,6 @@ The value that you specify for this parameter must match the MailRecipientGuid v Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -286,6 +309,9 @@ Accept wildcard characters: False ``` ### -MaxItemSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxItemSize parameter specifies the maximum size for posted items. Items larger than the value of the MaxItemSize parameter are rejected. The default value is unlimited, which is 2 gigabytes. When you enter a value, qualify the value with one of the following units: When you enter a value, qualify the value with one of the following units: @@ -304,7 +330,6 @@ The valid input range for this parameter is from 1 through 2GB. 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 @@ -314,13 +339,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name for the public folder. ```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 @@ -330,6 +357,9 @@ Accept wildcard characters: False ``` ### -OverrideContentMailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The OverrideContentMailbox parameter specifies the target public folder mailbox whereyou want to move this public folder's content to. You can use any value that uniquely identifies the mailbox. For example: @@ -349,7 +379,6 @@ The OverrideContentMailbox parameter specifies the target public folder mailbox Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -359,13 +388,15 @@ Accept wildcard characters: False ``` ### -Path + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Path parameter specifies the path of the public folder, for example, \\TopLevelPublicFolder\\PublicFolder. ```yaml Type: PublicFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -375,13 +406,15 @@ Accept wildcard characters: False ``` ### -PerUserReadStateEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PerUserReadStateEnabled parameter specifies whether to maintain read and unread data on a per-user basis. ```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 @@ -391,6 +424,9 @@ Accept wildcard characters: False ``` ### -ProhibitPostQuota + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ProhibitPostQuota parameter specifies the size of a public folder at which users are notified that the public folder is full. Users can't post to a folder whose size is larger than the ProhibitPostQuota parameter value. The default value is unlimited, which is 2 terabytes. When you enter a value, qualify the value with one of the following units: @@ -409,7 +445,6 @@ The valid input range for this parameter is from 1 through 2TB. 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 @@ -419,6 +454,9 @@ Accept wildcard characters: False ``` ### -Replicas + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The Replicas parameter specifies a list of public folder databases with which to replicate this public folder. You can use any value that uniquely identifies the database. For example: @@ -433,7 +471,6 @@ You can specify multiple values separated by commas. If the values contain space Type: DatabaseIdParameter[] Parameter Sets: Set2 Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -443,6 +480,9 @@ Accept wildcard characters: False ``` ### -ReplicationSchedule + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The ReplicationSchedule parameter specifies the replication schedule for the folder. @@ -471,7 +511,6 @@ Here are some examples: Type: Schedule Parameter Sets: Set2 Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -481,6 +520,9 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsFor + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetainDeletedItemsFor parameter specifies the retention time for deleted items. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -489,7 +531,6 @@ 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, Exchange Online Required: False Position: Named @@ -499,6 +540,9 @@ 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: @@ -514,7 +558,6 @@ 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 @@ -524,6 +567,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseAgeDefaults + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The UseDatabaseAgeDefaults parameter specifies whether to use the database age limit. @@ -532,7 +578,6 @@ The UseDatabaseAgeDefaults parameter specifies whether to use the database age l Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -542,6 +587,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseQuotaDefaults + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The UseDatabaseQuotaDefaults parameter specifies whether to use the public store quota limits. @@ -550,7 +598,6 @@ The UseDatabaseQuotaDefaults parameter specifies whether to use the public store Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -560,6 +607,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseReplicationSchedule + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The UseDatabaseReplicationSchedule parameter specifies whether to use the public folder replication schedule. @@ -568,7 +618,6 @@ The UseDatabaseReplicationSchedule parameter specifies whether to use the public Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -578,6 +627,9 @@ Accept wildcard characters: False ``` ### -UseDatabaseRetentionDefaults + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The UseDatabaseRetentionDefaults parameter specifies whether to use the database retention defaults. @@ -586,7 +638,6 @@ The UseDatabaseRetentionDefaults parameter specifies whether to use the database Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -596,13 +647,15 @@ 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/exchange/Set-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md index 85ad17feda..e01e0ab87b 100644 --- a/exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfolderdatabase applicable: Exchange Server 2010 -title: Set-PublicFolderDatabase -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfolderdatabase +schema: 2.0.0 +title: Set-PublicFolderDatabase --- # Set-PublicFolderDatabase @@ -76,6 +77,9 @@ This example prevents the deleted items in the public folder database PFDB01 fro ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the public folder database that you want to modify. You can use any value that uniquely identifies the database. For example: - Name @@ -86,7 +90,6 @@ The Identity parameter specifies the public folder database that you want to mod Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -96,13 +99,15 @@ Accept wildcard characters: False ``` ### -AllowFileRestore + +> Applicable: Exchange Server 2010 + The AllowFileRestore parameter specifies that the public folder database can be overwritten if the public folder database is restored. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -112,13 +117,15 @@ Accept wildcard characters: False ``` ### -BackgroundDatabaseMaintenance + +> Applicable: Exchange Server 2010 + The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. The two possible values are $true or $false. If you specify $true, the public folder database reads the object during database mount and initializes the database to perform the background database maintenance. If you specify $false, the public folder database reads the object during database mount and initializes the database without the option to perform the background database maintenance. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -128,13 +135,15 @@ Accept wildcard characters: False ``` ### -CircularLoggingEnabled + +> Applicable: Exchange Server 2010 + The CircularLoggingEnabled parameter specifies whether to enable circular logging. If you specify a value of $true, circular logging is enabled. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -144,6 +153,9 @@ 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`. @@ -153,7 +165,6 @@ 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 @@ -163,6 +174,9 @@ Accept wildcard characters: False ``` ### -CustomReferralServerList + +> Applicable: Exchange Server 2010 + The CustomReferralServerList parameter specifies public folder referral costs to individual servers manually. Costs can be any positive number. Servers not included on the list aren't included for referrals. If this parameter is set with no servers in the list, there are no public folder referrals. The CustomReferralServerList parameter accepts an array in the following format: "serverID:cost". Use a comma to separate multiple servers, for example, "MBXSERVER01:1","MBXSERVER02:5". @@ -171,7 +185,6 @@ The CustomReferralServerList parameter accepts an array in the following format: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -181,13 +194,15 @@ Accept wildcard characters: False ``` ### -DeletedItemRetention + +> Applicable: Exchange Server 2010 + The DeletedItemRetention parameter specifies the time that deleted items are kept in the dumpster before being permanently deleted during store maintenance. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -197,13 +212,15 @@ 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 @@ -213,13 +230,15 @@ Accept wildcard characters: False ``` ### -EventHistoryRetentionPeriod + +> Applicable: Exchange Server 2010 + The EventHistoryRetentionPeriod parameter specifies the length of time that events are retained in the event history table. Events can be retained for up to one week. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -229,13 +248,15 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2010 + The IssueWarningQuota parameter specifies the public folder size at which a warning is issued to public folder owners stating that the folder is almost full. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -245,13 +266,15 @@ Accept wildcard characters: False ``` ### -ItemRetentionPeriod + +> Applicable: Exchange Server 2010 + The ItemRetentionPeriod parameter specifies the length of time that items are retained in a folder before they're deleted during store maintenance. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -261,6 +284,9 @@ Accept wildcard characters: False ``` ### -MaintenanceSchedule + +> Applicable: Exchange Server 2010 + The MaintenanceSchedule parameter specifies the store maintenance schedule. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. @@ -286,7 +312,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -296,13 +321,15 @@ Accept wildcard characters: False ``` ### -MaxItemSize + +> Applicable: Exchange Server 2010 + The MaxItemSize parameter specifies the maximum size of an item that can be posted to or received by a public folder. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -312,13 +339,15 @@ Accept wildcard characters: False ``` ### -MountAtStartup + +> Applicable: Exchange Server 2010 + The MountAtStartup parameter specifies whether the database should be mounted when the store starts. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -328,13 +357,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies the name of the public folder database. Use this parameter to change the name of the public folder database. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -344,13 +375,15 @@ Accept wildcard characters: False ``` ### -ProhibitPostQuota + +> Applicable: Exchange Server 2010 + The ProhibitPostQuota parameter specifies the size of a public folder at which users are notified that the public folder is full. Users can't post to a folder larger than the ProhibitPostQuota parameter value. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -360,6 +393,9 @@ Accept wildcard characters: False ``` ### -QuotaNotificationSchedule + +> Applicable: Exchange Server 2010 + The QuotaNotificationSchedule parameter specifies the interval at which warning messages are sent when public folders exceed their specified size limit. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. @@ -385,7 +421,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -395,6 +430,9 @@ Accept wildcard characters: False ``` ### -ReplicationMessageSize + +> Applicable: Exchange Server 2010 + The ReplicationMessageSize parameter specifies the size of replication messages. Small items may be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size. A valid value is a number up to 2 gigabytes (2147482624 bytes). The default value is 300 kilobytes (307200 bytes). @@ -412,7 +450,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -422,13 +459,15 @@ Accept wildcard characters: False ``` ### -ReplicationPeriod + +> Applicable: Exchange Server 2010 + The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates may occur. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -438,6 +477,9 @@ Accept wildcard characters: False ``` ### -ReplicationSchedule + +> Applicable: Exchange Server 2010 + The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents may occur. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. @@ -464,7 +506,6 @@ Here are some examples: Type: Schedule Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -474,13 +515,15 @@ Accept wildcard characters: False ``` ### -RetainDeletedItemsUntilBackup + +> Applicable: Exchange Server 2010 + The RetainDeletedItemsUntilBackup parameter specifies that deleted items aren't removed until a backup of the public folder database is performed. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -490,6 +533,9 @@ Accept wildcard characters: False ``` ### -UseCustomReferralServerList + +> Applicable: Exchange Server 2010 + The UseCustomReferralServerList parameter specifies whether to use the server costs specified by the PublicFolderReferralServerList parameter. If set to $true, the server uses the PublicFolderReferralServerList parameter costs to make public folder referrals. If set to $false, the server uses Active Directory inter-site costs to make public folder referrals. Setting this parameter to $false also clears the PublicFolderReferralServerList parameter. @@ -498,7 +544,6 @@ Setting this parameter to $false also clears the PublicFolderReferralServerList Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -508,13 +553,15 @@ 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/exchange/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md index 7c4de5b3bf..17ba8371a5 100644 --- a/exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfoldermigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PublicFolderMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfoldermigrationrequest +schema: 2.0.0 +title: Set-PublicFolderMigrationRequest --- # Set-PublicFolderMigrationRequest @@ -69,6 +70,9 @@ This example changes the setting of the PublicFolderMigration migration request ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the migration request that you want to modify. You can use the following values: - Name @@ -78,7 +82,6 @@ The Identity parameter specifies the migration request that you want to modify. Type: PublicFolderMigrationRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -88,6 +91,9 @@ Accept wildcard characters: False ``` ### -RehomeRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RehomeRequest switch tells the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the public folder that's being migrated. You don't need to specify a value with this switch. This switch is used primarily for debugging purposes. @@ -96,7 +102,6 @@ This switch is used primarily for debugging purposes. Type: SwitchParameter Parameter Sets: Rehome Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -106,6 +111,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -114,7 +122,6 @@ You need to use this switch if you set the LargeItemLimit parameter to a value o Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -124,6 +131,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -132,7 +142,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,13 +151,15 @@ Accept wildcard characters: False ``` ### -BatchName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BatchName parameter specifies a descriptive name for the public folder batch migration. You can use the BatchName parameter as a search string when you use the Get-PublicFolderMigrationRequest cmdlet. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -158,13 +169,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -174,6 +187,9 @@ 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`. @@ -183,7 +199,6 @@ 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 @@ -193,13 +208,15 @@ 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 @@ -209,13 +226,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -225,6 +244,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -240,7 +262,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -250,6 +271,9 @@ Accept wildcard characters: False ``` ### -PreventCompletion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PreventCompletion parameter specifies whether to run the migration request, but not allow it to complete. Valid values are: - $true: The migration request is run, but is not allowed to complete. To complete the migration request, set this parameter to $false before you run the Resume-PublicFolderMigrationRequest cmdlet. @@ -259,7 +283,6 @@ The PreventCompletion parameter specifies whether to run the migration request, Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -269,6 +292,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lowest @@ -284,7 +310,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -294,6 +319,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -307,7 +335,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -317,13 +344,15 @@ Accept wildcard characters: False ``` ### -SkipMerging + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SkipMerging parameter specifies whether certain stages of a migration are to be skipped for debugging purposes. Don't use this parameter unless directed to do so by Microsoft Customer Service and Support or specific documentation. ```yaml Type: SkippableMergeComponent[] Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -333,13 +362,15 @@ 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/exchange/Set-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md index f63c7353d0..946a4481df 100644 --- a/exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfoldermoverequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-PublicFolderMoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-publicfoldermoverequest +schema: 2.0.0 +title: Set-PublicFolderMoveRequest --- # Set-PublicFolderMoveRequest @@ -53,13 +54,15 @@ This example changes the public folder move request \\PublicFolderMove to accept ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the public folder move request. The default identity of a public folder move request is \\PublicFolderMove. ```yaml Type: PublicFolderMoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -AcceptLargeDataLoss + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch. You need to use this switch if you set the LargeItemLimit parameter to a value of 51 or higher. Otherwise, the command will fail. @@ -77,7 +83,6 @@ You need to use this switch if you set the LargeItemLimit parameter to a value o Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -87,6 +92,9 @@ Accept wildcard characters: False ``` ### -BadItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete. Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the request again. @@ -95,7 +103,6 @@ Valid input for this parameter is an integer or the value unlimited. The default Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -105,13 +112,15 @@ Accept wildcard characters: False ``` ### -CompletedRequestAgeLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -121,6 +130,9 @@ 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`. @@ -130,7 +142,6 @@ 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 @@ -140,13 +151,15 @@ 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 @@ -156,13 +169,15 @@ Accept wildcard characters: False ``` ### -InternalFlags + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes. ```yaml Type: InternalMrsFlag[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,6 +187,9 @@ Accept wildcard characters: False ``` ### -LargeItemLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. For more information about maximum message size values, see the following topics: @@ -187,7 +205,6 @@ If you set this value to 51 or higher, you also need to use the AcceptLargeDataL Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -197,6 +214,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are: - Lowest @@ -212,7 +232,6 @@ The Priority parameter specifies the order in which the request should be proces Type: RequestPriority Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -222,6 +241,9 @@ Accept wildcard characters: False ``` ### -RequestExpiryInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter: - The completed request is automatically removed based on the CompletedRequestAgeLimit parameter value. @@ -235,7 +257,6 @@ When you use the value Unlimited, the completed request isn't automatically remo Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -245,13 +266,15 @@ Accept wildcard characters: False ``` ### -SuspendWhenReadyToComplete + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendWhenReadyToComplete parameter specifies whether to suspend the request before it reaches the status of CompletionInProgress. After the move is suspended, it has a status of AutoSuspended. You can then manually complete the move by using the Resume-PublicFolderMoveRequest command. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -261,13 +284,15 @@ 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/exchange/Set-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-QuarantinePermissions.md rename to exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md index 124bd14378..87a7ff1dff 100644 --- a/exchange/exchange-ps/exchange/Set-QuarantinePermissions.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-quarantinepermissions applicable: Exchange Online, Exchange Online Protection -title: Set-QuarantinePermissions -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-quarantinepermissions +schema: 2.0.0 +title: Set-QuarantinePermissions --- # Set-QuarantinePermissions @@ -54,13 +55,15 @@ In the same PowerShell session, you can use `$Perms` for the _EndUserQuarantineP ## PARAMETERS ### -QuarantinePermissionsObject + +> Applicable: Exchange Online, Exchange Online Protection + The QuarantinePermissionsObject parameter specifies the existing variable that contains quarantine permissions that you want to modify. For example if you previously ran the command `$Perms = New-QuarantinePermissions `, use the value `$Perms` for this parameter. ```yaml Type: QuarantinePermissions Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 9 @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -PermissionToAllowSender + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are: - $true: Allow sender is available for affected messages in quarantine. @@ -79,7 +85,6 @@ The PermissionToBlockSender parameter specifies whether users are allowed to add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -PermissionToBlockSender + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are: - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine. @@ -98,7 +106,6 @@ The PermissionToBlockSender parameter specifies whether users are allowed to add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 2 @@ -108,6 +115,9 @@ Accept wildcard characters: False ``` ### -PermissionToDelete + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are: - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine. @@ -117,7 +127,6 @@ The PermissionToDelete parameter specifies whether users are allowed to delete m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 3 @@ -127,6 +136,9 @@ Accept wildcard characters: False ``` ### -PermissionToDownload + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are: - $true: The permission is enabled. @@ -138,7 +150,6 @@ Currently, this value has no effect on the available actions in quarantine notif Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 4 @@ -148,6 +159,9 @@ Accept wildcard characters: False ``` ### -PermissionToPreview + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are: - $true: Preview message is available for affected messages in quarantine. @@ -157,7 +171,6 @@ The PermissionToPreview parameter specifies whether users are allowed to preview Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 5 @@ -167,6 +180,9 @@ Accept wildcard characters: False ``` ### -PermissionToRelease + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToRelease parameter specifies whether users are allowed to directly release affected messages from quarantine. Valid values are: - $true: Release is available in quarantine notifications for affected messages, and Release (Release email) is available for affected messages in quarantine. @@ -178,7 +194,6 @@ Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 6 @@ -188,6 +203,9 @@ Accept wildcard characters: False ``` ### -PermissionToRequestRelease + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToRequestRelease parameter specifies whether users are allowed to request messages to be released from quarantine. The request must be approved by an admin. Valid values are: - $true: Request Release is available in quarantine notifications for affected messages, and Request release is available for affected messages in quarantine. @@ -199,7 +217,6 @@ Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 7 @@ -209,6 +226,9 @@ Accept wildcard characters: False ``` ### -PermissionToViewHeader + +> Applicable: Exchange Online, Exchange Online Protection + The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are: - $true: The permission is enabled. @@ -220,7 +240,6 @@ Currently, this value has no effect on available actions in quarantine notificat Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 8 diff --git a/exchange/exchange-ps/exchange/Set-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-QuarantinePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md index 796d65b9a1..baf875814c 100644 --- a/exchange/exchange-ps/exchange/Set-QuarantinePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-quarantinepolicy applicable: Exchange Online, Exchange Online Protection -title: Set-QuarantinePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-quarantinepolicy +schema: 2.0.0 +title: Set-QuarantinePolicy --- # Set-QuarantinePolicy @@ -77,6 +78,9 @@ This example modifies the global settings for quarantine notifications (formerly ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the quarantine policy you want to modify. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -87,7 +91,6 @@ The Identity parameter specifies the quarantine policy you want to modify. You c Type: QuarantineTagIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -97,13 +100,15 @@ Accept wildcard characters: False ``` ### -AdminNotificationFrequencyInDays + +> 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,13 +118,15 @@ Accept wildcard characters: False ``` ### -AdminNotificationLanguage + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: EsnLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Accepted values: Default, English, French, German, Italian, Japanese, Spanish, Korean, Portuguese, Russian, ChineseSimplified, ChineseTraditional, Amharic, Arabic, Bulgarian, BengaliIndia, Catalan, Czech, Cyrillic, Danish, Greek, Estonian, Basque, Persian, Finnish, Filipino, Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Icelandic, Kazakh, Kannada, Lithuanian, Latvian, Malayalam, Marathi, Malay, Dutch, NorwegianNynorsk, Norwegian, Odia, Polish, PortuguesePortugal, Romanian, Slovak, Slovenian, SerbianCyrillic, Serbian, Swedish, Swahili, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese Required: False @@ -130,13 +137,15 @@ Accept wildcard characters: False ``` ### -AdminNotificationsEnabled + +> 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 @@ -146,13 +155,15 @@ Accept wildcard characters: False ``` ### -AdminQuarantinePermissionsList + +> 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 @@ -162,6 +173,9 @@ 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. @@ -171,7 +185,6 @@ 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 @@ -181,13 +194,15 @@ Accept wildcard characters: False ``` ### -CustomDisclaimer + +> 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 @@ -197,13 +212,15 @@ 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 @@ -213,6 +230,9 @@ Accept wildcard characters: False ``` ### -EndUserQuarantinePermissions + +> Applicable: Exchange Online, Exchange Online Protection + **Note**: To set permissions in quarantine policies, we recommend using the EndUserQuarantinePermissionsValue parameter. The EndUserQuarantinePermissions specifies the end-user permissions for the quarantine policy by using a variable from the output of a New-QuarantinePermissions or Set-QuarantinePermissions command. @@ -223,7 +243,6 @@ For example, run the following command to store the required permissions in a va Type: QuarantinePermissions Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -233,6 +252,9 @@ Accept wildcard characters: False ``` ### -EndUserQuarantinePermissionsValue + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserQuarantinePermissionsValue parameter specifies the end-user permissions for the quarantine policy. This parameter uses a decimal value that's converted from a binary value. The binary value corresponds to the list of available permissions in a specific order. For each permission, the value 1 equals True and the value 0 equals False. The required order is described in the following list from highest (1000000 or 128) to lowest (00000001 or 1): @@ -260,7 +282,6 @@ For custom permissions, get the binary value that corresponds to the permissions Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -270,13 +291,15 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationCustomFromAddress + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserSpamNotificationCustomFromAddress specifies the email address of an existing internal sender to use as the sender for quarantine notifications. To set this parameter back to the default email address quarantine@messaging.microsoft.com, use the value $null. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -286,6 +309,9 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationFrequency + +> Applicable: Exchange Online, Exchange Online Protection + The EndUserSpamNotificationFrequency parameter species how often quarantine notifications are sent to users. Valid values are: - 04:00:00 (4 hours) @@ -296,7 +322,6 @@ The EndUserSpamNotificationFrequency parameter species how often quarantine noti Type: TimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -306,13 +331,15 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationFrequencyInDays + +> 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 @@ -322,13 +349,15 @@ Accept wildcard characters: False ``` ### -EndUserSpamNotificationLanguage + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: EsnLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Accepted values: Default, English, French, German, Italian, Japanese, Spanish, Korean, Portuguese, Russian, ChineseSimplified, ChineseTraditional, Amharic, Arabic, Bulgarian, BengaliIndia, Catalan, Czech, Cyrillic, Danish, Greek, Estonian, Basque, Persian, Finnish, Filipino, Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Icelandic, Kazakh, Kannada, Lithuanian, Latvian, Malayalam, Marathi, Malay, Dutch, NorwegianNynorsk, Norwegian, Odia, Polish, PortuguesePortugal, Romanian, Slovak, Slovenian, SerbianCyrillic, Serbian, Swedish, Swahili, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese Required: False @@ -339,6 +368,9 @@ Accept wildcard characters: False ``` ### -EsnCustomSubject + +> Applicable: Exchange Online, Exchange Online Protection + The EsnCustomSubject parameter specifies the text to use in the Subject field of quarantine notifications. You can specify multiple values separated by commas using the syntax: `('value1',''value2',...'valueN')`. For each language that you specify with the MultiLanguageSetting parameter, you need to specify unique Sender text. Be sure to align the corresponding MultiLanguageSetting, MultiLanguageCustomDisclaimer, EsnCustomSubject, and MultiLanguageSenderName parameter values in the same order. @@ -351,7 +383,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: MultiValuedProperty Parameter Sets: (All) Aliases: MultiValuedProperty -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -361,6 +392,9 @@ Accept wildcard characters: False ``` ### -ESNEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are: - $true: Quarantine notifications are enabled. @@ -372,7 +406,6 @@ The ESNEnabled parameter specifies whether to enable quarantine notifications (f Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -382,13 +415,15 @@ Accept wildcard characters: False ``` ### -IgnoreDehydratedFlag + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -398,6 +433,9 @@ Accept wildcard characters: False ``` ### -IncludeMessagesFromBlockedSenderAddress + +> Applicable: Exchange Online, Exchange Online Protection + The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are: - $true: Recipients get quarantine notifications for affected messages from blocked senders. @@ -407,7 +445,6 @@ The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -417,6 +454,9 @@ Accept wildcard characters: False ``` ### -MultiLanguageCustomDisclaimer + +> Applicable: Exchange Online, Exchange Online Protection + The MultiLanguageCustomDisclaimer parameter specifies the custom disclaimer text to use near the bottom of quarantine notifications. The localized text, **A disclaimer from your organization:** is always included first, followed by the text you specify for this parameter. You can specify multiple values separated by commas using the syntax: `('value1',''value2',...'valueN')`. For each language that you specify with the MultiLanguageSetting parameter, you need to specify unique custom disclaimer text. Be sure to align the corresponding MultiLanguageSetting, MultiLanguageCustomDisclaimer, EsnCustomSubject, and MultiLanguageSenderName parameter values in the same order. @@ -429,7 +469,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -439,6 +478,9 @@ Accept wildcard characters: False ``` ### -MultiLanguageSenderName + +> Applicable: Exchange Online, Exchange Online Protection + The MultiLanguageSenderName parameter specifies the email sender's display name to use in quarantine notifications. You can specify multiple values separated by commas using the syntax: `('value1',''value2',...'valueN')`. For each language that you specify with the MultiLanguageSetting parameter, you can specify a unique sender name. Be sure to align the corresponding MultiLanguageSetting, MultiLanguageCustomDisclaimer, and MultiLanguageSenderName parameter values in the same order. @@ -451,7 +493,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -461,6 +502,9 @@ Accept wildcard characters: False ``` ### -MultiLanguageSetting + +> Applicable: Exchange Online, Exchange Online Protection + The MultiLanguageSetting parameter specifies the language of quarantine notifications. Valid values are: Default, Amharic, Arabic, Basque, BengaliIndia, Bulgarian, Catalan, ChineseSimplified, ChineseTraditional, Croatian, Cyrillic, Czech, Danish, Dutch, English, Estonian, Filipino, Finnish, French, Galician, German, Greek, Gujarati, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Italian, Japanese, Kannada, Kazakh, Korean, Latvian, Lithuanian, Malay, Malayalam, Marathi, Norwegian, NorwegianNynorsk, Odia, Persian, Polish, Portuguese, PortuguesePortugal, Romanian, Russian, Serbian, SerbianCyrillic, Slovak, Slovenian, Spanish, Swahili, Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, and Vietnamese. @@ -477,7 +521,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -487,6 +530,9 @@ Accept wildcard characters: False ``` ### -OrganizationBrandingEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The OrganizationBrandingEnabled parameter enables or disables organization branding in the end-user quarantine notification messages. Valid values are: - $true: Organization branding is enabled. The default Microsoft logo that's used in quarantine notifications is replaced by your custom logo. Before you do this, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your custom logo. @@ -498,7 +544,6 @@ This setting is available only in the built-in quarantine policy named DefaultGl Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -508,13 +553,15 @@ Accept wildcard characters: False ``` ### -QuarantineRetentionDays + +> 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 @@ -524,13 +571,15 @@ 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/exchange/Set-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-RMSTemplate.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md index 807ec202d5..08cc4525cd 100644 --- a/exchange/exchange-ps/exchange/Set-RMSTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-rmstemplate applicable: Exchange Online, Exchange Online Protection -title: Set-RMSTemplate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-rmstemplate +schema: 2.0.0 +title: Set-RMSTemplate --- # Set-RMSTemplate @@ -45,6 +46,9 @@ This example changes the RMS template Contoso Confidential from Distributed to A ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the RMS template. You can use any value that uniquely identifies the RMS template, for example: - Name @@ -56,7 +60,6 @@ You can use the Get-RMSTemplate cmdlet to view the RMS templates in your organiz Type: RmsTemplateIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -66,6 +69,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Online, Exchange Online Protection + The Type parameter specifies the type of RMS template. You can specify one of the following values: - Archived @@ -78,7 +84,6 @@ The default type for imported RMS templates is Archived. Type: RmsTemplateType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,13 +114,15 @@ 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/exchange/Set-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-ReceiveConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md index 0243479192..b12c8382c4 100644 --- a/exchange/exchange-ps/exchange/Set-ReceiveConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-receiveconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ReceiveConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-receiveconnector +schema: 2.0.0 +title: Set-ReceiveConnector --- # Set-ReceiveConnector @@ -100,6 +101,9 @@ Configures the Receive connector to time out connections after 15 minutes. ## 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 modify. You can use any value that uniquely identifies the Receive connector. For example: - Name @@ -111,7 +115,6 @@ The Identity parameter specifies the Receive connector that you want to modify. Type: ReceiveConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -121,6 +124,9 @@ Accept wildcard characters: False ``` ### -AdvertiseClientSettings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are: - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients). @@ -130,7 +136,6 @@ The AdvertiseClientSettings parameter specifies whether the SMTP server name, po Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -140,6 +145,9 @@ Accept wildcard characters: False ``` ### -AuthMechanism + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are: - None @@ -162,7 +170,6 @@ You can specify multiple values separated by commas, but some values have depend Type: AuthMechanisms Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,6 +179,9 @@ Accept wildcard characters: False ``` ### -AuthTarpitInterval + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 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. @@ -184,7 +194,6 @@ You can configure the delay for other SMTP failure responses by using the Tarpit Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -194,6 +203,9 @@ Accept wildcard characters: False ``` ### -Banner + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Banner parameter specifies a custom SMTP 220 banner that's displayed to remote messaging servers that connect to the Receive connector. When you specify a value, enclose the value in quotation marks, and start the value with 220 (the default "Service ready" SMTP response code). The default value of this parameter is blank ($null), which uses the following SMTP banner: @@ -204,7 +216,6 @@ The default value of this parameter is blank ($null), which uses the following S Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -214,6 +225,9 @@ Accept wildcard characters: False ``` ### -BareLinefeedRejectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BareLinefeedRejectionEnabled parameter specifies whether this Receive connector rejects messages that contain line feed (LF) characters without immediately preceding carriage return characters (CR) in the SMTP DATA stream. This condition is known as bare line feeds. Valid values are: - $true: Messages that contain bare line feeds are rejected. @@ -225,7 +239,6 @@ Although message that contain bare line feeds might be delivered successfully, t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -235,6 +248,9 @@ Accept wildcard characters: False ``` ### -BinaryMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value. @@ -246,7 +262,6 @@ The binary MIME extension is defined in RFC 3030. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -256,6 +271,9 @@ Accept wildcard characters: False ``` ### -Bindings + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax `"IPv4Address:TCPPort","IPv6Address:TCPPort"`. You can specify an IPv4 address and port, an IPv6 address and port, or both. The IP address values 0.0.0.0 or `[::]` indicate that the Receive connector uses all available local IPv4 or all IPv6 addresses. You need to specify a valid local IP address from the network adapters of the Exchange server. If you specify an invalid local IP address, the Microsoft Exchange Transport service might fail to start when the service is restarted. @@ -269,7 +287,6 @@ The values for this parameter must satisfy one of the following uniqueness requi Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -279,6 +296,9 @@ Accept wildcard characters: False ``` ### -ChunkingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value. @@ -290,7 +310,6 @@ Chunking is defined in RFC 3030. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -300,13 +319,15 @@ 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 @@ -316,6 +337,9 @@ 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`. @@ -325,7 +349,6 @@ 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 @@ -335,6 +358,9 @@ Accept wildcard characters: False ``` ### -ConnectionInactivityTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionInactivityTimeout parameter specifies the maximum amount of idle time before a connection to the Receive connector is closed. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -349,7 +375,6 @@ The value of this parameter must be less than the value of the ConnectionTimeout Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -359,6 +384,9 @@ Accept wildcard characters: False ``` ### -ConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionTimeout parameter specifies the maximum time that the connection to the Receive connector can remain open, even if the connection is actively transmitting data. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -373,7 +401,6 @@ The value of this parameter must be greater than the value of the ConnectionInac Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -383,6 +410,9 @@ Accept wildcard characters: False ``` ### -DefaultDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultDomain parameter specifies the default accepted domain to use for the Exchange organization. You can use any value that uniquely identifies the accepted domain. For example: - Name @@ -399,7 +429,6 @@ Although you can configure any accepted domain as the default domain, you typica Type: AcceptedDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -409,6 +438,9 @@ Accept wildcard characters: False ``` ### -DeliveryStatusNotificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: DSN is enabled and is advertised in the EHLO response. This is the default value. @@ -420,7 +452,6 @@ Delivery status notifications are defined in RFC 3461. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -430,6 +461,9 @@ 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. @@ -438,7 +472,6 @@ 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 @@ -448,6 +481,9 @@ Accept wildcard characters: False ``` ### -DomainSecureEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DomainSecureEnabled parameter specifies whether to enable or disable mutual Transport Layer Security (TLS) authentication (also known as Domain Secure) for the domains that are serviced by the Receive connector. Valid values are: - $true: Mutual TLS authentication is enabled. @@ -465,7 +501,6 @@ Note that setting this parameter to the value $true is only part of the requirem Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -475,6 +510,9 @@ Accept wildcard characters: False ``` ### -EightBitMimeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value. @@ -486,7 +524,6 @@ The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP e Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -496,6 +533,9 @@ Accept wildcard characters: False ``` ### -EnableAuthGSSAPI + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnableAuthGSSAPI parameter enables or disables Kerberos when Integrated Windows authentication is available on the Receive connector (the AuthMechanism parameter contains the value Integrated). Valid values are: - $true: Kerberos is enabled. The Extended SMTP keyword AUTH GSSAPI NTLM is advertised in the EHLO response. Clients can use Kerberos or NTLM for Integrated Windows authentication. @@ -507,7 +547,6 @@ The Generic Security Services application programming interface (GSSAPI) is an I Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -517,6 +556,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are: - $true: The Receive connector is enabled. This is the default value. @@ -526,7 +568,6 @@ The Enabled parameter specifies whether to enable or disable the Receive connect Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -536,6 +577,9 @@ Accept wildcard characters: False ``` ### -EnhancedStatusCodesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value. @@ -547,7 +591,6 @@ Enhanced status codes are defined in RFC 2034. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -557,6 +600,9 @@ Accept wildcard characters: False ``` ### -ExtendedProtectionPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExtendedProtectionPolicy parameter specifies how you want to use Extended Protection for Authentication on the Receive connector.Valid values are: - None: Extended Protection for Authentication won't be used. This is the default value. @@ -569,7 +615,6 @@ Extended Protection for Authentication enhances the protection and handling of c Type: ExtendedProtectionPolicySetting Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -579,6 +624,9 @@ Accept wildcard characters: False ``` ### -Fqdn + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Fqdn parameter specifies the destination FQDN that's shown to connected messaging servers. This value is used in the following locations: - In the default SMTP banner of the Receive connector @@ -594,7 +642,6 @@ Don't modify this value on the default Receive connector named `Default Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are: - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation. @@ -621,7 +671,6 @@ You can only configure this parameter on Receive connectors in the Transport ser Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -631,6 +680,9 @@ Accept wildcard characters: False ``` ### -MaxAcknowledgementDelay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds. @@ -641,7 +693,6 @@ 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 @@ -651,6 +702,9 @@ Accept wildcard characters: False ``` ### -MaxHeaderSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxHeaderSize parameter specifies the maximum size of the SMTP message header before the Receive connector closes the connection. The default value is 256 kilobytes (262144 bytes). When you enter a value, qualify the value with one of the following units: @@ -668,7 +722,6 @@ A valid value is from 1 to 2147483647 bytes. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -678,6 +731,9 @@ Accept wildcard characters: False ``` ### -MaxHopCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxHopCount parameter specifies the maximum number of hops that a message can take before the message is rejected by the Receive connector. The maximum number of hops is determined by the number of Received header fields that exist in a submitted message. A valid value is from 1 to 500. The default value is 30. @@ -686,7 +742,6 @@ A valid value is from 1 to 500. The default value is 30. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -696,6 +751,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnection + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnection parameter specifies the maximum number of inbound connections that this Receive connector serves at the same time. A valid value is from 1 to 2147483647, or the value unlimited. The default value is 5000. @@ -706,7 +764,6 @@ To disable the inbound connection limit on a Receive connector, enter a value of Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -716,6 +773,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnectionPercentagePerSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnectionPercentagePerSource parameter specifies the maximum number of connections that a Receive connector serves at the same time from a single IP address, expressed as the percentage of available remaining connections on a Receive connector. A valid value is from 1 to 100 without the percent sign (%). The default value is 2 percent. @@ -724,7 +784,6 @@ A valid value is from 1 to 100 without the percent sign (%). The default value i Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -734,6 +793,9 @@ Accept wildcard characters: False ``` ### -MaxInboundConnectionPerSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxInboundConnectionPerSource parameter specifies the maximum number of connections that this Receive connector serves at the same time from a single IP address. A valid value is from 1 to 10000, or the value unlimited. The default value is 20. @@ -744,7 +806,6 @@ To disable the inbound connection per source limit on a Receive connector, enter Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -754,6 +815,9 @@ Accept wildcard characters: False ``` ### -MaxLocalHopCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxLocalHopCount parameter specifies the maximum number of local hops that a message can take before the message is rejected by the Receive connector. The maximum number of local hops is determined by the number of Received headers with local server addresses in a submitted message. A valid value is from 0 to 50. The default value is 8. @@ -764,7 +828,6 @@ When you specify the value 0, the message is never rejected based on the number Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -774,6 +837,9 @@ Accept wildcard characters: False ``` ### -MaxLogonFailures + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxLogonFailures parameter specifies the number of logon failures that the Receive connector retries before it closes the connection. A valid value is from 0 to 10. The default value is 3. @@ -784,7 +850,6 @@ When you specify the value 0, the connection is never closed because of logon fa Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -794,6 +859,9 @@ 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 through the Receive connector. The default value is 36 MB, which results in a realistic maximum message size of 25 MB. When you enter a value, qualify the value with one of the following units: @@ -814,7 +882,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -824,6 +891,9 @@ Accept wildcard characters: False ``` ### -MaxProtocolErrors + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxProtocolErrors parameter specifies the maximum number of SMTP protocol errors that the Receive connector accepts before closing the connection. A valid value is from 0 to 2147483647, or the value unlimited. The default value is 5. @@ -834,7 +904,6 @@ When you specify the value unlimited, a connection is never closed because of pr Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -844,6 +913,9 @@ Accept wildcard characters: False ``` ### -MaxRecipientsPerMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxRecipientsPerMessage parameter specifies the maximum number of recipients per message that the Receive connector accepts before closing the connection. A valid value is from 1 to 512000. The default value is 200. @@ -852,7 +924,6 @@ A valid value is from 1 to 512000. The default value is 200. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -862,6 +933,9 @@ Accept wildcard characters: False ``` ### -MessageRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute. A valid value is from 1 to 2147483647, or the value unlimited. @@ -874,7 +948,6 @@ The default value for Receive connectors on Mailbox servers is unlimited. The de Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -884,6 +957,9 @@ Accept wildcard characters: False ``` ### -MessageRateSource + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are: - None: No message submission rate is calculated. @@ -895,7 +971,6 @@ The MessageRateSource parameter specifies how the message submission rate is cal Type: MessageRateSourceFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -905,13 +980,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name for the Receive connector. 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 Required: False Position: Named @@ -921,6 +998,9 @@ Accept wildcard characters: False ``` ### -OrarEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are: - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command. @@ -932,7 +1012,6 @@ If the email address specified in the ORAR information is a long X.400 email add Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -942,6 +1021,9 @@ Accept wildcard characters: False ``` ### -PermissionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PermissionGroups parameter specifies the well-known security principals who are authorized to use the Receive connector and the permissions that are assigned to them. Valid values are: - None @@ -962,7 +1044,6 @@ For more information about the default permissions and security principals for p Type: PermissionGroups Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -972,6 +1053,9 @@ Accept wildcard characters: False ``` ### -PipeliningEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value. @@ -983,7 +1067,6 @@ Pipelining is defined in RFC 2920. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -993,6 +1076,9 @@ Accept wildcard characters: False ``` ### -ProtocolLoggingLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are: - None: Protocol logging is disabled on the Receive connector. This is the default value. @@ -1004,7 +1090,6 @@ For more information about protocol logging, see [Protocol logging](https://lear Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1014,6 +1099,9 @@ Accept wildcard characters: False ``` ### -RejectReservedSecondLevelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are: - $true: RCPT TO commands that contain reserved second-level domains are rejected. @@ -1023,7 +1111,6 @@ The RejectReservedSecondLevelRecipientDomains parameter specifies whether to rej Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1033,6 +1120,9 @@ Accept wildcard characters: False ``` ### -RejectReservedTopLevelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are: - $true: RCPT TO commands that contain reserved TLDs are rejected. @@ -1042,7 +1132,6 @@ The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1052,6 +1141,9 @@ Accept wildcard characters: False ``` ### -RejectSingleLabelRecipientDomains + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are: - $true: RCPT TO commands that contain single-label domains are rejected. @@ -1061,7 +1153,6 @@ The RejectSingleLabelRecipientDomains parameter specifies whether to reject conn Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1071,6 +1162,9 @@ Accept wildcard characters: False ``` ### -RemoteIPRanges + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteIPRanges parameter specifies the remote IP addresses that the Receive connector accepts messages from. Valid values are: - Single IP address: For example, 192.168.1.1 or fe80::39bd:88f7:6969:d223%11. @@ -1091,7 +1185,6 @@ When remote IP address ranges overlap, the Receive connector with the most speci Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1101,6 +1194,9 @@ Accept wildcard characters: False ``` ### -RequireEHLODomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are: - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed. @@ -1110,7 +1206,6 @@ The RequireEHLODomain parameter specifies whether the client must provide a doma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1120,6 +1215,9 @@ Accept wildcard characters: False ``` ### -RequireTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are: - $true: Inbound messages on the Receive connector require TLS transmission. @@ -1129,7 +1227,6 @@ The RequireTLS parameter specifies whether to require TLS transmission for inbou Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1139,13 +1236,15 @@ Accept wildcard characters: False ``` ### -ServiceDiscoveryFqdn + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN). for the Receive connector. ```yaml Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1155,6 +1254,9 @@ Accept wildcard characters: False ``` ### -SizeEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are: - Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value. @@ -1167,7 +1269,6 @@ SIZE is defined in RFC 1870. Type: SizeMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1177,13 +1278,15 @@ Accept wildcard characters: False ``` ### -SmtpUtf8Enabled + +> 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 @@ -1193,6 +1296,9 @@ Accept wildcard characters: False ``` ### -SuppressXAnonymousTls + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are: - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server. @@ -1204,7 +1310,6 @@ The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter conta Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1214,6 +1319,9 @@ Accept wildcard characters: False ``` ### -TarpitInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 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. @@ -1226,7 +1334,6 @@ You can configure the delay for authentication failure responses by using the Au Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1236,13 +1343,15 @@ 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. A valid value for this parameter is `"X.500IssuerX.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint `, run the command `$TLSCertName = "$($TLSCert.Issuer)$($TLSCert.Subject)"` and then use the value $TLSCertName for this parameter. ```yaml Type: SmtpX509Identifier Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1252,6 +1361,9 @@ Accept wildcard characters: False ``` ### -TlsDomainCapabilities + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsDomainCapabilities parameter specifies the capabilities that the Receive connector makes available to specific hosts outside of the organization. Remote hosts are authenticated with TLS with certificate validation before these capabilities are offered. This parameter uses the following syntax: @@ -1273,7 +1385,6 @@ For example, `"contoso.com:AcceptOorgProtocol","fabrikam.com:AcceptCloudServices Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1283,6 +1394,9 @@ Accept wildcard characters: False ``` ### -TransportRole + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created. Valid values are: - FrontendTransport: The Front End Transport service where client or external SMTP connections occur. @@ -1294,7 +1408,6 @@ You can't use this parameter on Edge Transport servers. Type: ServerRole Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1304,13 +1417,15 @@ 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/exchange/Set-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md index d1543894e3..d4143c68a2 100644 --- a/exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-recipientfilterconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-RecipientFilterConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-recipientfilterconfig +schema: 2.0.0 +title: Set-RecipientFilterConfig --- # Set-RecipientFilterConfig @@ -58,13 +59,15 @@ This example makes the following changes to the Recipient Filter agent configura ## PARAMETERS ### -BlockedRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedRecipients parameter specifies one or more SMTP addresses. To enter multiple SMTP addresses, separate the addresses by using a comma. The maximum number of individual SMTP addresses that you can input is 800. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -74,13 +77,15 @@ Accept wildcard characters: False ``` ### -BlockListEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockListEnabled parameter specifies whether the Recipient Filter agent blocks messages sent to recipients listed in the BlockedRecipients parameter. Valid input for the BlockListEnabled parameter is $true or $false. The default setting is $false. When the BlockListEnabled parameter is set to $true, the Recipient Filter agent blocks messages sent to recipients listed in the BlockedRecipients parameter. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -90,6 +95,9 @@ 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,7 +107,6 @@ 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,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the Recipient Filter agent is enabled on the computer on which you're running the command. Valid input for the Enabled parameter is $true or $false. The default setting is $true. When the Enabled parameter is set to $true, the Recipient Filter agent is enabled on the computer on which you're running the command. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -143,13 +154,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether all messages received from unauthenticated connections by servers external to your organization are passed through the Recipient Filter agent for processing. Valid input for the ExternalMailEnabled parameter is $true or $false. The default setting is $true. When the ExternalMailEnabled parameter is set to $true, all messages received from unauthenticated connections by servers external to your organization are passed through the Recipient Filter agent for processing. ```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,13 +172,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether all messages from authenticated sender domains that belong to authoritative domains in the enterprise are passed through the Recipient Filter agent for processing. Valid input for the InternalMailEnabled parameter is $true or $false. The default setting is $false. When the InternalMailEnabled parameter is set to $true, all messages from authenticated sender domains that belong to authoritative domains in the enterprise are passed through the Recipient Filter agent for processing. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -175,13 +190,15 @@ Accept wildcard characters: False ``` ### -RecipientValidationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientValidationEnabled parameter specifies whether the Recipient Filter agent blocks messages addressed to recipients that don't exist in the organization. Valid input for the RecipientValidationEnabled parameter is $true or $false. The default setting is $false. When the RecipientValidationEnabled parameter is set to $true, the Recipient Filter agent blocks messages addressed to recipients that don't exist in the organization. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,13 +208,15 @@ 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/exchange/Set-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md index b3552f8231..a07e6cb8ed 100644 --- a/exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-recordreviewnotificationtemplateconfig applicable: Security & Compliance -title: Set-RecordReviewNotificationTemplateConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-recordreviewnotificationtemplateconfig +schema: 2.0.0 +title: Set-RecordReviewNotificationTemplateConfig --- # Set-RecordReviewNotificationTemplateConfig @@ -42,6 +43,9 @@ This example configures customized review notification text and review reminder ## PARAMETERS ### -IsCustomizedNotificationTemplate + +> Applicable: Security & Compliance + The IsCustomizedNotificationTemplate switch specifies whether to use a customized review notification instead of the system default notification. Valid values are: - $true: Use a customized review notification. You specify the notification text using the CustomizedNotificationDataString parameter. @@ -51,7 +55,6 @@ The IsCustomizedNotificationTemplate switch specifies whether to use a customize Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -61,6 +64,9 @@ Accept wildcard characters: False ``` ### -IsCustomizedReminderTemplate + +> Applicable: Security & Compliance + The IsCustomizedReminderTemplate switch specifies whether to use a customized review reminder instead of the system default reminder: - $true: Use a customized review reminder. You specify the reminder text using the CustomizedReminderDataString parameter. @@ -70,7 +76,6 @@ The IsCustomizedReminderTemplate switch specifies whether to use a customized re Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -80,6 +85,9 @@ Accept wildcard characters: False ``` ### -CustomizedNotificationDataString + +> Applicable: Security & Compliance + The CustomizedNotificationDataString parameter specifies the customized review notification text to use. If the value contains spaces, enclose the value in quotation marks ("). The value of this parameter is meaningful only when the value of the IsCustomizedNotificationTemplate parameter is $true. @@ -88,7 +96,6 @@ The value of this parameter is meaningful only when the value of the IsCustomize Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -98,6 +105,9 @@ Accept wildcard characters: False ``` ### -CustomizedReminderDataString + +> Applicable: Security & Compliance + The CustomizedReminderDataString parameter specifies the customized review reminder text to use. If the value contains spaces, enclose the value in quotation marks ("). The value of this parameter is meaningful only when the value of the IsCustomizedReminderTemplate parameter is $true. @@ -106,7 +116,6 @@ The value of this parameter is meaningful only when the value of the IsCustomize Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md index 8f4caf3d77..509ed99ec7 100644 --- a/exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md @@ -1,9 +1,11 @@ --- +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/exchange/set-regulatorycomplianceui -applicable: Security & Compliance -title: Set-RegulatoryComplianceUI schema: 2.0.0 +title: Set-RegulatoryComplianceUI --- # Set-RegulatoryComplianceUI @@ -38,6 +40,9 @@ This example displays the UI option in retention label settings to mark content ## PARAMETERS ### -Enabled + +> Applicable: Security & Compliance + The Enabled parameter specifies whether to show or hide the UI option in retention label settings to mark content as a regulatory record. Valid values are: $true: The option to mark content as a regulatory record is visible in the UI for retention label settings. @@ -48,7 +53,6 @@ $false: The option to mark content as a regulatory record is not visible in the Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Set-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-RemoteDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md index 8f7c3965a5..bd0e67ac28 100644 --- a/exchange/exchange-ps/exchange/Set-RemoteDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-remotedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-RemoteDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-remotedomain +schema: 2.0.0 +title: Set-RemoteDomain --- # Set-RemoteDomain @@ -81,6 +82,9 @@ This example queries Active Directory for all remote domains for which auto repl ## 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 modify. You can use any value that uniquely identifies the remote domain. For example: - Name @@ -91,7 +95,6 @@ The Identity parameter specifies the remote domain that you want to modify. You Type: RemoteDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -101,6 +104,9 @@ Accept wildcard characters: False ``` ### -AllowedOOFType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AllowedOOFType parameter specifies the type of automatic replies or out-of-office (also known as OOF) notifications than can be sent to recipients in the remote domain. Valid values are: - External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This is the default value. @@ -117,7 +123,6 @@ The value of this parameter is affected by the value of the IsInternal parameter Type: AllowedOOFType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -127,6 +132,9 @@ Accept wildcard characters: False ``` ### -AutoForwardEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoForwardEnabled parameter specifies whether to allow messages that are auto-forwarded by client email programs in your organization. Valid values are: - $true: Auto-forwarded messages are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. @@ -136,7 +144,6 @@ The AutoForwardEnabled parameter specifies whether to allow messages that are au 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 @@ -146,6 +153,9 @@ Accept wildcard characters: False ``` ### -AutoReplyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AutoReplyEnabled parameter specifies whether to allow messages that are automatic replies from client email programs in your organization (for example, automatic reply messages that are generated by rules in Outlook). Valid values are: - $true: Automatic replies are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online. @@ -155,7 +165,6 @@ The AutoReplyEnabled parameter specifies whether to allow messages that are auto 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 @@ -165,6 +174,9 @@ Accept wildcard characters: False ``` ### -ByteEncoderTypeFor7BitCharsets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encoding method for MIME format for messages sent to this remote domain. Valid values are: - Use7Bit: Always use default 7-bit transfer encoding for HTML and plain text. @@ -180,7 +192,6 @@ The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encodi Type: ByteEncoderTypeFor7BitCharsetsEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -190,6 +201,9 @@ Accept wildcard characters: False ``` ### -CharacterSet + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CharacterSet parameter specifies a character set for MIME messages without defined character sets that are sent from your organization to recipients in the remote domain. Valid values 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, or the value $null. @@ -202,7 +216,6 @@ This setting doesn't overwrite character sets that are already specified in outb 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 @@ -212,6 +225,9 @@ 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`. @@ -221,7 +237,6 @@ 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 @@ -231,6 +246,9 @@ Accept wildcard characters: False ``` ### -ContentType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ContentType parameter specifies the outbound message content type and formatting. Valid values are: - MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This is the default value. @@ -241,7 +259,6 @@ The ContentType parameter specifies the outbound message content type and format Type: ContentType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -251,6 +268,9 @@ Accept wildcard characters: False ``` ### -DeliveryReportEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DeliveryReportEnabled parameter specifies whether to allow delivery reports from client software in your organization to recipients in the remote domain. Valid values are: - $true: Delivery reports are delivered to recipients in the remote domain. This is the default value. @@ -260,7 +280,6 @@ The DeliveryReportEnabled parameter specifies whether to allow delivery reports 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 @@ -270,6 +289,9 @@ Accept wildcard characters: False ``` ### -DisplaySenderName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note**: You should only modify this parameter under the direction of Microsoft Customer Service and Support. The DisplaySenderName parameter specifies whether to show the sender's Display Name in the From email address for messages sent to recipients in the remote domain. Valid values are: @@ -281,7 +303,6 @@ The DisplaySenderName parameter specifies whether to show the sender's Display N 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 @@ -291,6 +312,9 @@ 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. @@ -301,7 +325,6 @@ 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 @@ -311,6 +334,9 @@ Accept wildcard characters: False ``` ### -IsCoexistenceDomain + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IsCoexistenceDomain parameter specifies whether this remote domain is used to represent your Exchange Online organization. Valid values are: @@ -322,7 +348,6 @@ The IsCoexistenceDomain parameter specifies whether this remote domain is used t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -332,6 +357,9 @@ Accept wildcard characters: False ``` ### -IsInternal + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsInternal parameter specifies whether the recipients in the remote domain are considered to be internal recipients. Valid values are: - $true: All transport components (for example, transport rules) treat recipients in the remote domain as internal recipients. Typically, you use this value in cross-forest deployments. @@ -346,7 +374,6 @@ The value of this parameter is affected by the value of the AllowedOOFType param 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 @@ -356,13 +383,15 @@ Accept wildcard characters: False ``` ### -LineWrapSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LineWrapSize parameter specifies the line-wrap size for messages to recipients in the remote domain. Valid values are an integer from 0 through 132 or the value to unlimited. 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 @@ -372,6 +401,9 @@ Accept wildcard characters: False ``` ### -MeetingForwardNotificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MeetingForwardNotificationEnabled parameter specifies whether to enable meeting forward notifications for recipients in the remote domain. Valid values are: - $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This is the default value. @@ -381,7 +413,6 @@ The MeetingForwardNotificationEnabled parameter specifies whether to enable meet 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 @@ -391,6 +422,9 @@ Accept wildcard characters: False ``` ### -MessageCountThreshold + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MessageCountThreshold parameter specifies the acceptable message count for the remote domain. If the message count exceeds this value, an event is generated that's visible using the Get-ServerHealth and Get-HealthReport cmdlets. @@ -401,7 +435,6 @@ Valid input for this parameter is an integer. The default value is Int32 (214748 Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -411,13 +444,15 @@ Accept wildcard characters: False ``` ### -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 remote domain 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -427,6 +462,9 @@ Accept wildcard characters: False ``` ### -NDRDiagnosticInfoEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The NDRDiagnosticInfoEnabled parameter specifies whether diagnostic information is included in non-delivery reports (also known NDRs or bounce messages) that are sent to recipients the remote domain. Valid values are: @@ -440,7 +478,6 @@ This parameter is meaningful only when the value of the NDREnabled parameter is 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 @@ -450,6 +487,9 @@ Accept wildcard characters: False ``` ### -NDREnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NDREnabled parameter specifies whether to allow non-delivery reports (also known NDRs or bounce messages) from your organization to recipients in the remote domain. Valid values are: - $true: NDRs from your organization are sent to recipients in the remote domain. This is the default value. @@ -459,7 +499,6 @@ The NDREnabled parameter specifies whether to allow non-delivery reports (also k 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 @@ -469,6 +508,9 @@ Accept wildcard characters: False ``` ### -NonMimeCharacterSet + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NonMimeCharacterSet parameter specifies a character set for plain text messages without defined character sets that are sent from your organization to recipients in the remote domain. Valid values 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, or the value $null. @@ -481,7 +523,6 @@ This setting doesn't overwrite character sets that are already specified in outb 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 @@ -491,6 +532,9 @@ Accept wildcard characters: False ``` ### -PreferredInternetCodePageForShiftJis + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The PreferredInternetCodePageForShiftJis parameter specifies the specific code page to use for Shift JIS character encoding in messages that are sent to recipients in the remote domain. Valid values are: - 50220: Use ISO-2022-JP codepage. @@ -502,7 +546,6 @@ The PreferredInternetCodePageForShiftJis parameter specifies the specific code p Type: PreferredInternetCodePageForShiftJisEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -512,6 +555,9 @@ Accept wildcard characters: False ``` ### -RequiredCharsetCoverage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RequiredCharsetCoverage parameter specifies a percentage threshold for characters in a message that must match to apply your organization's preferred character set before switching to automatic character set detection. For example, if you set this parameter to 60, the preferred character sets will still be used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use. @@ -522,7 +568,6 @@ If recipients in the remote domain use characters that span character sets, you 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 @@ -532,6 +577,9 @@ Accept wildcard characters: False ``` ### -SmtpDaneMandatoryModeEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -540,7 +588,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -550,6 +597,9 @@ Accept wildcard characters: False ``` ### -TargetDeliveryDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetDeliveryDomain parameter specifies whether the remote domain is used in cross-forest deployments to generate target email addresses for new mail users that represent users in the other organization (for example, all mailboxes hosted on Exchange Online are represented as mail users in your on-premises organization). Valid values are: - $true: The remote domain is used for the target email address of mail users that represent the users in the other forest. @@ -559,7 +609,6 @@ The TargetDeliveryDomain parameter specifies whether the remote domain is used i 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 @@ -569,6 +618,9 @@ Accept wildcard characters: False ``` ### -TNEFEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Format (TNEF) message encoding is used on messages sent to the remote domain. Valid values are: - $true: TNEF encoding is used on all messages sent to the remote domain. @@ -579,7 +631,6 @@ The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Form 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 @@ -589,6 +640,9 @@ Accept wildcard characters: False ``` ### -TrustedMailInboundEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TrustedMailInboundEnabled parameter specifies whether messages from senders in the remote domain are treated as trusted messages. Valid values are: - $true: Inbound messages from senders in the remote domain are considered safe and will bypass content filtering and recipient filtering. @@ -598,7 +652,6 @@ The TrustedMailInboundEnabled parameter specifies whether messages from senders 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 @@ -608,6 +661,9 @@ Accept wildcard characters: False ``` ### -TrustedMailOutboundEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TrustedMailOutboundEnabled parameter specifies whether messages sent to recipients in the remote domain are treated as trusted messages. Valid values are: - $true: Outbound messages to recipients in the remote domain are considered safe and will bypass content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments. @@ -617,7 +673,6 @@ The TrustedMailOutboundEnabled parameter specifies whether messages sent to reci 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 @@ -627,6 +682,9 @@ Accept wildcard characters: False ``` ### -UseSimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseSimpleDisplayName parameter specifies whether the sender's simple display name is used for the From email address in messages sent to recipients in the remote domain. Valid values are: - $true: Simple display names are used in messages sent to recipients in the remote domain. If the sender doesn't have a simple display name configured, the From email address is `EmailAddress `. @@ -636,7 +694,6 @@ The UseSimpleDisplayName parameter specifies whether the sender's simple display 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 @@ -646,13 +703,15 @@ 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/exchange/Set-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-RemoteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md index 6850e91830..8f9886cdb7 100644 --- a/exchange/exchange-ps/exchange/Set-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-remotemailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-RemoteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-remotemailbox +schema: 2.0.0 +title: Set-RemoteMailbox --- # Set-RemoteMailbox @@ -113,6 +114,9 @@ This example configures delivery restrictions for the mailbox in the service tha ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the remote mailbox (mail user) that you want to modify. You can use any value that uniquely identifies the mail user. For example: - ADObjectID @@ -128,7 +132,6 @@ The Identity parameter specifies the remote mailbox (mail user) that you want to Type: RemoteMailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -138,6 +141,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -161,7 +167,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,6 +176,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group are allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -194,7 +202,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -204,6 +211,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -229,7 +239,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -239,6 +248,9 @@ 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. - To enable this feature, use this switch without a value. @@ -248,7 +260,6 @@ The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -258,6 +269,9 @@ 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: @@ -282,7 +296,6 @@ 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 @@ -292,13 +305,15 @@ Accept wildcard characters: False ``` ### -ArchiveGuid + +> Applicable: Exchange Server 2010, 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -308,6 +323,9 @@ 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 ("). The following default values are used based on the version of Exchange: @@ -322,7 +340,6 @@ In Outlook, the value of this parameter is ignored. The name of the archive mail Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -332,6 +349,9 @@ Accept wildcard characters: False ``` ### -BypassModerationFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator. To specify senders for this parameter, you can use any value that uniquely identifies the sender. For example: @@ -353,7 +373,6 @@ This parameter is meaningful only when moderation is enabled for the recipient. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -363,6 +382,9 @@ 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`. @@ -372,7 +394,6 @@ 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 @@ -382,13 +403,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -398,13 +421,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -414,13 +439,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -430,13 +457,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -446,13 +475,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -462,13 +493,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -478,13 +511,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -494,13 +529,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -510,13 +547,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -526,13 +565,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -542,13 +583,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -558,13 +601,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -574,13 +619,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -590,13 +637,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -606,13 +655,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -622,13 +673,15 @@ 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 mail user. 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 @@ -638,13 +691,15 @@ 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 @@ -654,6 +709,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -681,7 +739,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -691,6 +748,9 @@ Accept wildcard characters: False ``` ### -EmailAddressPolicyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are: - $true: Email address policies are applied to this recipient. This is the default value. @@ -700,7 +760,6 @@ The EmailAddressPolicyEnabled parameter specifies whether to apply email address Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -710,6 +769,9 @@ Accept wildcard characters: False ``` ### -ExchangeGuid + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExchangeGuid parameter specifies the ExchangeGuid property value of the mail user, which should match the ExchangeGuid value of the corresponding cloud mailbox. The ExchangeGuid property is a unique Exchange mailbox identifier, and corresponds to the msExchMailboxGuid attribute in Active Directory. An example value is d5a0bd9b-4e95-49b5-9736-14fde1eec1e3. Although the syntax is the same, this value is different than the GUID property value, which corresponds to the objectGUID attribute in Active Directory. @@ -718,7 +780,6 @@ The ExchangeGuid property is a unique Exchange mailbox identifier, and correspon Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -728,6 +789,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -740,7 +804,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -750,6 +813,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -762,7 +828,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -772,6 +837,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -784,7 +852,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -794,6 +861,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -806,7 +876,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -816,6 +885,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -828,7 +900,6 @@ Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -838,13 +909,15 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Server 2010, Exchange Server 2013 + The GrantSendOnBehalfTo parameter specifies the DN of recipients that can send messages on behalf of this mail-enabled user. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013 Required: False Position: Named @@ -854,6 +927,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are: - $true: The recipient isn't visible in address lists. @@ -863,7 +939,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether this recipient is Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -873,6 +948,9 @@ 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: @@ -884,7 +962,6 @@ 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 @@ -894,6 +971,9 @@ Accept wildcard characters: False ``` ### -ImmutableId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com. You need to set the ImmutableId parameter if Active Directory Federation Services (AD FS) is deployed to allow single sign-on into an off-premises mailbox and AD FS is configured to use a different attribute than ExchangeGUID for sign-on token requests. Both, Exchange and AD FS must request the same token for the same user to ensure proper functionality for a cross-premises Exchange deployment scenario. @@ -902,7 +982,6 @@ You need to set the ImmutableId parameter if Active Directory Federation Service Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -912,6 +991,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -923,7 +1005,6 @@ When you add a MailTip to a recipient, two things happen: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -933,6 +1014,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -947,7 +1031,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -957,6 +1040,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 @@ -976,7 +1062,6 @@ You need to use this parameter to specify at least one moderator when you set th Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -986,6 +1071,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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. @@ -997,7 +1085,6 @@ 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 Required: False Position: Named @@ -1007,13 +1094,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the mail user. 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 Required: False Position: Named @@ -1023,6 +1112,9 @@ 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. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. If you set the EmailAddressPolicyEnabled parameter to $false, you can specify the primary address using the PrimarySmtpAddress parameter, but the email addresses of the mail user are no longer automatically updated by email address policies. @@ -1033,7 +1125,6 @@ The PrimarySmtpAddress parameter updates the primary email address and WindowsEm Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1043,6 +1134,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder of the mailbox. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes). @@ -1063,7 +1157,6 @@ The RecoverableItemsQuota value must be greater than or equal to the Recoverable Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1073,6 +1166,9 @@ Accept wildcard characters: False ``` ### -RecoverableItemsWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for the mailbox. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes). @@ -1093,7 +1189,6 @@ The RecoverableItemsWarningQuota value must be less than or equal to the Recover Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1103,6 +1198,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders in your organization (mailboxes, mail users, and mail contacts). You can use any value that uniquely identifies the sender. For example: @@ -1126,7 +1224,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1136,6 +1233,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromDLMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are groups in your organization (distribution groups, mail-enabled security groups, and dynamic distribution groups). Specifying a group means all members of the group aren't allowed to send messages to this recipient. You can use any value that uniquely identifies the group. For example: @@ -1159,7 +1259,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1169,6 +1268,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1194,7 +1296,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1204,6 +1305,9 @@ 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's associated with this mail user. You shouldn't have to change the remote routing address if the address was automatically configured by Exchange when the mail user and its associated mailbox in the service were created. @@ -1212,7 +1316,6 @@ You shouldn't have to change the remote routing address if the address was autom Type: ProxyAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1222,6 +1325,9 @@ Accept wildcard characters: False ``` ### -RemovePicture + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemovePicture switch removes the picture from the mail user. You don't need to specify a value with this switch. You can add a picture to a mail user by using the Import-RecipientDataProperty cmdlet. @@ -1230,7 +1336,6 @@ You can add a picture to a mail user by using the Import-RecipientDataProperty c Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1240,6 +1345,9 @@ Accept wildcard characters: False ``` ### -RemoveSpokenName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoveSpokenName switch removes the spoken name from the mail user. You don't need to specify a value with this switch. You can add a picture to a mail user by using the Import-RecipientDataProperty cmdlet. @@ -1248,7 +1356,6 @@ You can add a picture to a mail user by using the Import-RecipientDataProperty c Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1258,6 +1365,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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. @@ -1269,7 +1379,6 @@ The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1279,6 +1388,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. @@ -1288,7 +1400,6 @@ The ResetPasswordOnNextLogon parameter specifies whether the user must change th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1298,13 +1409,15 @@ Accept wildcard characters: False ``` ### -SamAccountName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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). The maximum length is 20 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1314,6 +1427,9 @@ Accept wildcard characters: False ``` ### -SendModerationNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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. @@ -1328,7 +1444,6 @@ The default value is Never. Type: TransportModerationNotificationFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1338,6 +1453,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Type parameter specifies the type for the mailbox in the service. Valid values are: - Regular @@ -1355,7 +1473,6 @@ Notes on the value Shared: Type: ConvertibleRemoteMailboxSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1365,13 +1482,15 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1381,13 +1500,15 @@ 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 @@ -1397,6 +1518,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -1408,7 +1532,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director Type: SmtpAddress 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/exchange/Set-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md index 5aaeb7f9dd..bbf459dc8b 100644 --- a/exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-reportsubmissionpolicy applicable: Exchange Online -title: Set-ReportSubmissionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-reportsubmissionpolicy +schema: 2.0.0 +title: Set-ReportSubmissionPolicy --- # Set-ReportSubmissionPolicy @@ -166,13 +167,15 @@ If the report submission rule doesn't already exist (the Get-ReportSubmissionRul ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the report submission policy that you want to modify. The only available policy is named DefaultReportSubmissionPolicy. ```yaml Type: ReportSubmissionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -182,6 +185,9 @@ 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. @@ -191,7 +197,6 @@ 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 @@ -201,6 +206,9 @@ Accept wildcard characters: False ``` ### -DisableQuarantineReportingOption + +> Applicable: Exchange Online + The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are: - $true: Users can't report quarantined messages from quarantine. @@ -212,7 +220,6 @@ This parameter is meaningful only reporting in Outlook is enabled as described i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -222,13 +229,15 @@ Accept wildcard characters: False ``` ### -DisableUserSubmissionOptions + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -238,13 +247,15 @@ Accept wildcard characters: False ``` ### -EnableCustomizedMsg + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -254,6 +265,9 @@ Accept wildcard characters: False ``` ### -EnableCustomNotificationSender + +> Applicable: Exchange Online + The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use a custom Microsoft 365 sender email address. @@ -265,7 +279,6 @@ You specify the sender email address using the NotificationSenderAddress paramet Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -275,6 +288,9 @@ Accept wildcard characters: False ``` ### -EnableOrganizationBranding + +> Applicable: Exchange Online + The EnableOrganizationBranding parameter specifies whether to show the company logo in the footer of result messages that users receive after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Use the company logo in the footer text instead of the Microsoft logo. @@ -286,7 +302,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -296,6 +311,9 @@ Accept wildcard characters: False ``` ### -EnableReportToMicrosoft + +> Applicable: Exchange Online + The EnableReportToMicrosoft parameter specifies whether Microsoft integrated reporting experience is enabled or disabled. Valid values are $true or $false. The value $true for this parameter enables reporting in Outlook. The following configurations are possible: @@ -313,7 +331,6 @@ The value $false for this parameter disables reporting in Outlook. The following Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -323,6 +340,9 @@ Accept wildcard characters: False ``` ### -EnableThirdPartyAddress + +> Applicable: Exchange Online + The EnableThirdPartyAddress parameter specifies whether you're using non-Microsoft reporting tools in Outlook instead of Microsoft tools to send messages to the reporting mailbox in Exchange Online. Valid values are $true or $false. The value $true enables Microsoft to capture information about email sent to the non-Microsoft reporting mailbox. The following configurations are possible: @@ -336,7 +356,6 @@ The value $false means non-Microsoft reporting tools in Outlook aren't used. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -346,6 +365,9 @@ Accept wildcard characters: False ``` ### -EnableUserEmailNotification + +> Applicable: Exchange Online + The EnableUserEmailNotification parameter species whether users receive result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are: - $true: Customized admin review result messages are sent. This value is required when user reported messages go only to the reporting mailbox (the value of the EnableReportToMicrosoft parameter is $false). @@ -361,7 +383,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -371,6 +392,9 @@ Accept wildcard characters: False ``` ### -JunkReviewResultMessage + +> Applicable: Exchange Online + The JunkReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as junk. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -383,7 +407,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -393,6 +416,9 @@ Accept wildcard characters: False ``` ### -NotJunkReviewResultMessage + +> Applicable: Exchange Online + The NotJunkReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as not junk. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -405,7 +431,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -415,6 +440,9 @@ Accept wildcard characters: False ``` ### -NotificationFooterMessage + +> Applicable: Exchange Online + The NotificationFooterMessage parameter specifies the custom footer text to use in email notifications after an admin reviews and marks the reported messages as junk, not junk, or phishing. If the value contains spaces, enclose the value in quotation marks. You can use the EnableOrganizationBranding parameter to include your company logo in the message footer. @@ -425,7 +453,6 @@ This parameter is meaningful only when the value of the EnableUserEmailNotificat Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -435,6 +462,9 @@ Accept wildcard characters: False ``` ### -NotificationSenderAddress + +> Applicable: Exchange Online + The NotificationSenderAddress parameter specifies the sender email address to use in result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. The email address must be in Exchange Online. This parameter is meaningful only when reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -443,7 +473,6 @@ This parameter is meaningful only when reporting in Outlook is enabled for Micro Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -453,13 +482,15 @@ Accept wildcard characters: False ``` ### -NotificationsForCleanSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -469,13 +500,15 @@ Accept wildcard characters: False ``` ### -NotificationsForPhishMalwareSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -485,13 +518,15 @@ Accept wildcard characters: False ``` ### -NotificationsForSpamSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -501,13 +536,15 @@ Accept wildcard characters: False ``` ### -NotificationsForSubmissionAirInvestigationsEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -517,13 +554,15 @@ Accept wildcard characters: False ``` ### -OnlyShowPhishingDisclaimer + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -533,6 +572,9 @@ Accept wildcard characters: False ``` ### -PhishingReviewResultMessage + +> Applicable: Exchange Online + The PhishingReviewResultMessage parameter specifies the custom text to use in result messages after an admin reviews and marks the reported messages as phishing. If the value contains spaces, enclose the value in quotation marks ("). This parameter is meaningful only when the value of the EnableUserEmailNotification parameter is $true and reporting in Outlook is enabled for Microsoft reporting tools in Outlook as described in the EnableReportToMicrosoft parameter. @@ -545,7 +587,6 @@ Use the NotificationSenderAddress parameter to customize the sender email addres Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -555,6 +596,9 @@ Accept wildcard characters: False ``` ### -PostSubmitMessage + +> Applicable: Exchange Online + The PostSubmitMessage parameter specifies the custom pop-up message text to use in Outlook notifications after users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message title using the PostSubmitMessageTitle parameter. @@ -565,7 +609,6 @@ This parameter is meaningful only when the value of the PostSubmitMessageEnabled Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -575,6 +618,9 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageEnabled + +> Applicable: Exchange Online + The PostSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see after they report messages using Microsoft reporting tools. Valid values are: - $true: Users receive pop-up notifications in Outlook after they report messages. This is the default value. @@ -584,7 +630,6 @@ The PostSubmitMessageEnabled parameter enables or disables the pop-up Outlook no Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -594,13 +639,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -610,13 +657,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -626,13 +675,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -642,6 +693,9 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitle + +> Applicable: Exchange Online + The PostSubmitMessage parameter parameter specifies the custom pop-up message title to use in Outlook notifications after users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message text using the PostSubmitMessage parameter. @@ -652,7 +706,6 @@ This parameter is meaningful only when the value of the PostSubmitMessageEnabled Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -662,13 +715,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -678,13 +733,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -694,13 +751,15 @@ Accept wildcard characters: False ``` ### -PostSubmitMessageTitleForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PostSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -710,6 +769,9 @@ Accept wildcard characters: False ``` ### -PreSubmitMessage + +> Applicable: Exchange Online + The PreSubmitMessage parameter specifies the custom pop-up message text to use in Outlook notifications before users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the custom pop-up message title using the PreSubmitMessageTitle parameter. @@ -720,7 +782,6 @@ This parameter is meaningful only when the value of the PreSubmitMessageEnabled Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -730,6 +791,9 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageEnabled + +> Applicable: Exchange Online + The PreSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see before they report messages using Microsoft reporting tools. Valid values are: - $true: Users receive pop-up notifications in Outlook before they report messages. This is the default value. @@ -739,7 +803,6 @@ The PreSubmitMessageEnabled parameter enables or disables the pop-up Outlook not Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -749,13 +812,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -765,13 +830,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -781,13 +848,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessage parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -797,6 +866,9 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitle + +> Applicable: Exchange Online + The PreSubmitMessage parameter parameter specifies the custom pop-up message title to use in Outlook notifications before users report messages. If the value contains spaces, enclose the value in quotation marks ("). You specify the pop-up message text using the PreSubmitMessage parameter. @@ -807,7 +879,6 @@ This parameter is meaningful only when the value of the PreSubmitMessageEnabled Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -817,13 +888,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -833,13 +906,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForNotJunk + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -849,13 +924,15 @@ Accept wildcard characters: False ``` ### -PreSubmitMessageTitleForPhishing + +> Applicable: Exchange Online + Don't use this parameter. Use the PreSubmitMessageTitle parameter instead. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -865,13 +942,15 @@ Accept wildcard characters: False ``` ### -ReportChatMessageEnabled + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -881,13 +960,15 @@ Accept wildcard characters: False ``` ### -ReportChatMessageToCustomizedAddressEnabled + +> Applicable: Exchange Online + {{ Fill ReportChatMessageToCustomizedAddressEnabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -897,6 +978,9 @@ Accept wildcard characters: False ``` ### -ReportJunkAddresses + +> Applicable: Exchange Online + **Note**: You aren't absolutely required to use this parameter. You specify the email address of the reporting mailbox using the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. To reduce confusion, set this parameter to the same value. The ReportJunkAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. @@ -909,7 +993,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -919,6 +1002,9 @@ Accept wildcard characters: False ``` ### -ReportJunkToCustomizedAddress + +> Applicable: Exchange Online + The ReportJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -930,7 +1016,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -940,6 +1025,9 @@ Accept wildcard characters: False ``` ### -ReportNotJunkAddresses + +> Applicable: Exchange Online + **Note**: You aren't absolutely required to use this parameter. You specify the email address of the reporting mailbox using the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. To reduce confusion, set this parameter to the same value. The ReportNotJunkAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. @@ -952,7 +1040,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -962,6 +1049,9 @@ Accept wildcard characters: False ``` ### -ReportNotJunkToCustomizedAddress + +> Applicable: Exchange Online + The ReportNotJunkToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -973,7 +1063,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -983,6 +1072,9 @@ Accept wildcard characters: False ``` ### -ReportPhishAddresses + +> Applicable: Exchange Online + **Note**: You aren't absolutely required to use this parameter. You specify the email address of the reporting mailbox using the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. To reduce confusion, set this parameter to the same value. The ReportPhishAddresses parameter specifies the email address of the reporting mailbox in Exchange Online to receive user reported messages in reporting in Outlook using Microsoft or non-Microsoft reporting tools in Outlook. @@ -995,7 +1087,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1005,6 +1096,9 @@ Accept wildcard characters: False ``` ### -ReportPhishToCustomizedAddress + +> Applicable: Exchange Online + The ReportPhishToCustomizedAddress parameter specifies whether to send user reported messages from Outlook (using Microsoft or non-Microsoft reporting tools) to the reporting mailbox as part of reporting in Outlook. Valid values are: - $true: User reported messages are sent to the reporting mailbox. @@ -1016,7 +1110,6 @@ You can't use this parameter by itself. You need to specify the same value for t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1026,6 +1119,9 @@ Accept wildcard characters: False ``` ### -ThirdPartyReportAddresses + +> Applicable: Exchange Online + **Note**: You aren't absolutely required to use this parameter. You specify the email address of the reporting mailbox using the SentTo parameter on the New-ReportSubmissionRule or Set-ReportSubmissionRule cmdlet. To reduce confusion, set this parameter to the same value. Use the ThirdPartyReportAddresses parameter to specify the email address of the reporting mailbox when you're using a non-Microsoft product for user submissions instead of reporting in Outlook. @@ -1038,7 +1134,6 @@ For more information about using non-Microsoft reporting tools with or without r Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1048,13 +1143,15 @@ Accept wildcard characters: False ``` ### -UserSubmissionOptions + +> Applicable: Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1064,13 +1161,15 @@ Accept wildcard characters: False ``` ### -UserSubmissionOptionsMessage + +> 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 @@ -1080,13 +1179,15 @@ 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/exchange/Set-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md index c4e6300e20..e1d862e8b1 100644 --- a/exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-reportsubmissionrule applicable: Exchange Online -title: Set-ReportSubmissionRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-reportsubmissionrule +schema: 2.0.0 +title: Set-ReportSubmissionRule --- # Set-ReportSubmissionRule @@ -55,13 +56,15 @@ This example changes the reporting mailbox to userreportedmessages@contoso.onmic ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the report submission rule that you want to modify. The default rule is named DefaultReportSubmissionRule. ```yaml Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -71,13 +74,15 @@ 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 @@ -87,6 +92,9 @@ 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`. @@ -96,7 +104,6 @@ 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,13 +113,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the name of the report submission rule. When the rule is automatically created, the name of the rule is DefaultReportSubmissionRule. We recommend using this value to avoid confusion. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -122,13 +131,15 @@ Accept wildcard characters: False ``` ### -ReportSubmissionPolicy + +> Applicable: Exchange Online + The ReportSubmissionPolicy parameter specifies the report submission policy that's associated with this rule. The only available policy is named DefaultReportSubmissionPolicy. ```yaml Type: ReportSubmissionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -138,6 +149,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Online + The SentTo parameter specifies the email address of the reporting mailbox in Exchange Online where user reported messages are sent. The value of this parameter is meaningful only if reporting in Outlook is enabled, and user reported messages are sent to a reporting mailbox as configured in the \*-ReportSubmissionPolicy cmdlets (either of the following scenarios): @@ -156,7 +170,6 @@ When you use this cmdlet to set the email address of the reporting mailbox, the Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -166,13 +179,15 @@ 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/exchange/Set-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ResourceConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md index 19453e4a45..544e6e7280 100644 --- a/exchange/exchange-ps/exchange/Set-ResourceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-resourceconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-ResourceConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-resourceconfig +schema: 2.0.0 +title: Set-ResourceConfig --- # Set-ResourceConfig @@ -52,6 +53,9 @@ This example adds the custom resource property Room/TV and removes Equipment/Lap ## PARAMETERS ### -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`. @@ -61,7 +65,6 @@ 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 @@ -71,6 +74,9 @@ 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. @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -ResourcePropertySchema + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ResourcePropertySchema parameter specifies the custom resource property that you want to make available to room or equipment mailboxes. This parameter uses the syntax `Room/` or `Equipment/` where the `` value doesn't contain spaces. For example, `Room/Whiteboard` or `Equipment/Van`. You can specify multiple values separated by commas. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -99,7 +107,6 @@ To add or remove one or more values without affecting any existing entries, use 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 @@ -109,13 +116,15 @@ 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/exchange/Set-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-ResubmitRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md index 222f007a7c..21508a1f46 100644 --- a/exchange/exchange-ps/exchange/Set-ResubmitRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-resubmitrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ResubmitRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-resubmitrequest +schema: 2.0.0 +title: Set-ResubmitRequest --- # Set-ResubmitRequest @@ -43,13 +44,15 @@ This example disables the resubmit request with the identity 8. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the resubmit request you want to modify. 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: True Position: 1 @@ -59,13 +62,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter enables or disables an active resubmit request. Valid input for this parameter is $true or $false. Setting the value to $false disables the resubmit request. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -75,6 +80,9 @@ 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`. @@ -84,7 +92,6 @@ 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 @@ -94,6 +101,9 @@ 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 @@ -107,7 +117,6 @@ 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 @@ -117,13 +126,15 @@ 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/exchange/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md index b953c9c959..72c8f0baa0 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-retentioncompliancepolicy applicable: Security & Compliance -title: Set-RetentionCompliancePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-retentioncompliancepolicy +schema: 2.0.0 +title: Set-RetentionCompliancePolicy --- # Set-RetentionCompliancePolicy @@ -224,6 +225,9 @@ Policy exclusions must remain within the supported limits for retention policies ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -234,7 +238,6 @@ The Identity parameter specifies the retention policy that you want to modify. Y Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -244,6 +247,9 @@ Accept wildcard characters: False ``` ### -RetryDistribution + +> Applicable: Security & Compliance + The RetryDistribution switch specifies whether to redistribute the policy to all Exchange Online and SharePoint locations. You don't need to specify a value with this switch. Locations whose initial distributions succeeded aren't included in the retry. Policy distribution errors are reported when you use this switch. @@ -252,7 +258,6 @@ Locations whose initial distributions succeeded aren't included in the retry. Po Type: SwitchParameter Parameter Sets: RetryDistribution Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -262,6 +267,9 @@ Accept wildcard characters: False ``` ### -AddAdaptiveScopeLocation + +> Applicable: Security & Compliance + The AddAdaptiveScopeLocation parameter specifies the adaptive scope location to add to 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 @@ -274,7 +282,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -284,6 +291,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocation + +> Applicable: Security & Compliance + The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -302,7 +312,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -312,6 +321,9 @@ Accept wildcard characters: False ``` ### -AddExchangeLocationException + +> Applicable: Security & Compliance + This parameter specifies the mailboxes to add to the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. Valid values are: - A mailbox @@ -330,7 +342,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -340,6 +351,9 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocation + +> Applicable: Security & Compliance + The AddModernGroupLocation parameter specifies the Microsoft 365 Groups to add to the list of included Microsoft 365 Groups when you aren't using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -355,7 +369,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -365,6 +378,9 @@ Accept wildcard characters: False ``` ### -AddModernGroupLocationException + +> Applicable: Security & Compliance + The AddModernGroupLocationException parameter specifies the Microsoft 365 Groups to add to the list of excluded Microsoft 365 Groups when you're using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -380,7 +396,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -390,6 +405,9 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocation + +> Applicable: Security & Compliance + The AddOneDriveLocation parameter specifies the OneDrive sites to add to the list of included sites when you aren't using 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"`. @@ -398,7 +416,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -408,6 +425,9 @@ Accept wildcard characters: False ``` ### -AddOneDriveLocationException + +> Applicable: Security & Compliance + This parameter specifies the OneDrive sites to add to the list of excluded sites 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"`. @@ -416,7 +436,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -426,13 +445,15 @@ Accept wildcard characters: False ``` ### -AddPublicFolderLocation + +> Applicable: Security & Compliance + The AddPublicFolderLocation parameter specifies that you want to add all public folders to the retention policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -442,6 +463,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocation + +> Applicable: Security & Compliance + The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites when you aren't using 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"`. @@ -452,7 +476,6 @@ SharePoint sites can't be added to the policy until they have been indexed. Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -462,6 +485,9 @@ Accept wildcard characters: False ``` ### -AddSharePointLocationException + +> Applicable: Security & Compliance + This parameter specifies the SharePoint sites to add to the list of excluded sites 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"`. @@ -470,7 +496,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -480,6 +505,9 @@ Accept wildcard characters: False ``` ### -AddSkypeLocation + +> Applicable: Security & Compliance + The AddSkypeLocation parameter specifies the Skype for Business Online users to add from the list of included Skype for Business Online users. You can use any value that uniquely identifies the user. For example: @@ -495,7 +523,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -505,13 +532,15 @@ Accept wildcard characters: False ``` ### -AddSkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -521,6 +550,9 @@ Accept wildcard characters: False ``` ### -AddTeamsChannelLocation + +> Applicable: Security & Compliance + The AddTeamsChannelLocation parameter specifies the Teams to add to the policy. You can use any value that uniquely identifies the team. For example: @@ -535,7 +567,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -545,6 +576,9 @@ Accept wildcard characters: False ``` ### -AddTeamsChannelLocationException + +> Applicable: Security & Compliance + The AddTeamsChannelLocationException parameter specifies the Teams to add to the exclusion list when you use the value All for the TeamsChannelLocation parameter. You can use any value that uniquely identifies the team. For example: - Name @@ -557,7 +591,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -567,6 +600,9 @@ Accept wildcard characters: False ``` ### -AddTeamsChatLocation + +> Applicable: Security & Compliance + The AddTeamsChatLocation parameter specifies the Teams users to add to the policy. You can use any value that uniquely identifies the user. For example: @@ -582,7 +618,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -592,6 +627,9 @@ Accept wildcard characters: False ``` ### -AddTeamsChatLocationException + +> Applicable: Security & Compliance + The AddTeamsChatLocationException parameter specifies the Teams users to add to the exclusion list when you use the value All for the TeamsChatLocation parameter. You can use any value that uniquely identifies the user. For example: - Name @@ -604,7 +642,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -614,6 +651,9 @@ Accept wildcard characters: False ``` ### -Applications + +> Applicable: Security & Compliance + The Applications parameter specifies the target when Microsoft 365 Groups are included in the policy (the ModernGroups parameter is set). Valid values are: - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group. @@ -625,7 +665,6 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -635,13 +674,15 @@ 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: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -651,6 +692,9 @@ 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`. @@ -660,7 +704,6 @@ 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 @@ -670,6 +713,9 @@ Accept wildcard characters: False ``` ### -DeletedResources + +> Applicable: Security & Compliance + The DeletedResources parameter specifies the deleted Microsoft 365 Group, mailbox, or mail user to be removed or added as an exclusion to the respective location list. Use this parameter with the AddModernGroupLocationException and RemoveModernGroupLocation parameters for deleted Microsoft 365 Groups, or with the AddTeamsChatLocationException parameter for deleted mailboxes or mail users. A valid value is a JSON string. Refer to the Examples section for syntax and usage examples of this parameter. @@ -686,7 +732,6 @@ For more information about the inactive mailbox scenario, see [Learn about inact Type: String Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -696,6 +741,9 @@ 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. @@ -705,7 +753,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -715,6 +762,9 @@ Accept wildcard characters: False ``` ### -EnforceSimulationPolicy + +> Applicable: Security & Compliance + The EnforceSimulationPolicy parameter specifies whether to enforce a simulation policy as an active policy. Valid values are: - $true: Enforce the simulation policy as an active policy. @@ -726,7 +776,6 @@ For more information about simulation mode, see [Learn about simulation mode](ht Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -736,6 +785,9 @@ 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. @@ -744,7 +796,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity, TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -754,6 +805,9 @@ 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. @@ -764,7 +818,6 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -774,13 +827,15 @@ Accept wildcard characters: False ``` ### -PolicyTemplateInfo + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: PswsHashtable Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -790,6 +845,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to update a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -798,7 +856,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -808,6 +865,9 @@ Accept wildcard characters: False ``` ### -RemoveAdaptiveScopeLocation + +> Applicable: Security & Compliance + The RemoveAdaptiveScopeLocation parameter specifies the adaptive scope location to remove from 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 @@ -820,7 +880,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: AdaptiveScopeLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -830,6 +889,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocation + +> Applicable: Security & Compliance + The RemoveExchangeLocation parameter specifies the mailboxes to remove from the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. You can use any value that uniquely identifies the mailbox. For example: @@ -845,7 +907,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -855,6 +916,9 @@ Accept wildcard characters: False ``` ### -RemoveExchangeLocationException + +> Applicable: Security & Compliance + The RemoveExchangeLocationException parameter specifies the mailboxes to remove from the list of excluded mailboxes when you use the value All for the ExchangeLocation parameter. You can use any value that uniquely identifies the mailbox. For example: @@ -870,7 +934,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -880,6 +943,9 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocation + +> Applicable: Security & Compliance + The RemoveModernGroupLocation parameter specifies the Microsoft 365 Groups to remove from the list of included groups when you aren't using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -895,7 +961,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -905,6 +970,9 @@ Accept wildcard characters: False ``` ### -RemoveModernGroupLocationException + +> Applicable: Security & Compliance + The RemoveModernGroupLocationException parameter specifies the Microsoft 365 Groups to remove from the list of excluded groups when you're using the value All for the ModernGroupLocation parameter. You can use any value that uniquely identifies the Microsoft 365 Group. For example: @@ -920,7 +988,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -930,6 +997,9 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocation + +> Applicable: Security & Compliance + The RemoveOneDriveLocation parameter specifies the OneDrive sites to remove from the list of included sites when you aren't using 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"`. @@ -938,7 +1008,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -948,6 +1017,9 @@ Accept wildcard characters: False ``` ### -RemoveOneDriveLocationException + +> Applicable: Security & Compliance + This parameter specifies the OneDrive sites to remove from the list of excluded sites 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"`. @@ -956,7 +1028,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -966,13 +1037,15 @@ Accept wildcard characters: False ``` ### -RemovePublicFolderLocation + +> Applicable: Security & Compliance + The RemovePublicFolderLocation parameter specifies that you want to remove all public folders from the retention policy. You use the value All for this parameter. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -982,6 +1055,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocation + +> Applicable: Security & Compliance + The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites when you aren't using 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"`. @@ -990,7 +1066,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1000,6 +1075,9 @@ Accept wildcard characters: False ``` ### -RemoveSharePointLocationException + +> Applicable: Security & Compliance + This parameter specifies the SharePoint sites to remove from the list of excluded sites 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"`. @@ -1008,7 +1086,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1018,6 +1095,9 @@ Accept wildcard characters: False ``` ### -RemoveSkypeLocation + +> Applicable: Security & Compliance + The RemoveSkypeLocation parameter specifies the Skype for Business Online users to remove from the list of included Skype for Business Online users. You can use any value that uniquely identifies the user. For example: @@ -1033,7 +1113,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1043,13 +1122,15 @@ Accept wildcard characters: False ``` ### -RemoveSkypeLocationException + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1059,6 +1140,9 @@ Accept wildcard characters: False ``` ### -RestrictiveRetention + +> Applicable: Security & Compliance + The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for a retention policy or retention label 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. @@ -1072,7 +1156,6 @@ Therefore, before you lock a policy for retention, it's critical that you unders Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1082,6 +1165,9 @@ Accept wildcard characters: False ``` ### -RemoveTeamsChannelLocation + +> Applicable: Security & Compliance + The RemoveTeamsChannelLocation parameter specifies the Teams to remove from the policy. You can use any value that uniquely identifies the team. For example: @@ -1096,7 +1182,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1106,6 +1191,9 @@ Accept wildcard characters: False ``` ### -RemoveTeamsChannelLocationException + +> Applicable: Security & Compliance + The RemoveTeamsChannelLocationException parameter specifies the Teams to remove from the exclusion list when you use the value All for the TeamsChannelLocation parameter. You can use any value that uniquely identifies the team. For example: - Name @@ -1118,7 +1206,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1128,6 +1215,9 @@ Accept wildcard characters: False ``` ### -RemoveTeamsChatLocation + +> Applicable: Security & Compliance + The RemoveTeamsChatLocation parameter specifies the Teams users to remove from the policy. You can use any value that uniquely identifies the user. For example: @@ -1143,7 +1233,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1153,6 +1242,9 @@ Accept wildcard characters: False ``` ### -RemoveTeamsChatLocationException + +> Applicable: Security & Compliance + The RemoveTeamsChatLocationException parameter specifies the Teams users to remove from the exclusion list when you use the value All for the TeamsChatLocation parameter. You can use any value that uniquely identifies the user. For example: - Name @@ -1165,7 +1257,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: MultiValuedProperty Parameter Sets: TeamLocation Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1175,6 +1266,9 @@ Accept wildcard characters: False ``` ### -StartSimulation + +> Applicable: Security & Compliance + The StartSimulation parameter specifies whether to start the simulation for a policy that was created in simulation mode. Valid values are: - $true: Start the simulation. @@ -1186,7 +1280,6 @@ For more information about simulation mode, see [Learn about simulation mode](ht Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -1196,13 +1289,15 @@ 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/exchange/Set-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md index b34336842e..af0377a20c 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-retentioncompliancerule applicable: Security & Compliance -title: Set-RetentionComplianceRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-retentioncompliancerule +schema: 2.0.0 +title: Set-RetentionComplianceRule --- # Set-RetentionComplianceRule @@ -55,6 +56,9 @@ This example changes the hold duration for the existing retention rule named "In ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the retention rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the retention rule that you want to modify. You Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -75,6 +78,9 @@ Accept wildcard characters: False ``` ### -ApplyComplianceTag + +> Applicable: Security & Compliance + The ApplyComplianceTag parameter specifies the label that's applied to email messages or documents by the rule (which affects how long the content is retained). A valid value for this parameter is the name of an existing label. If the value contains spaces, enclose the value in quotation marks. You view and create labels by using the Get-ComplianceTag and New-ComplianceTag cmdlets. @@ -87,7 +93,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -97,13 +102,15 @@ 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,6 +120,9 @@ 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`. @@ -122,7 +132,6 @@ 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 @@ -132,6 +141,9 @@ 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"})`. @@ -144,7 +156,6 @@ You can't use this parameter for Teams retention rules. Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -154,6 +165,9 @@ 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". @@ -162,7 +176,6 @@ 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 @@ -172,6 +185,9 @@ 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". @@ -180,7 +196,6 @@ 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 @@ -190,6 +205,9 @@ 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). @@ -200,7 +218,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -210,6 +227,9 @@ 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 @@ -231,7 +251,6 @@ You can't use this parameter for Teams retention rules. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -241,6 +260,9 @@ 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 @@ -252,7 +274,6 @@ You can't use this parameter for Teams retention rules. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -262,13 +283,15 @@ Accept wildcard characters: False ``` ### -IRMRiskyUserProfiles + +> Applicable: Security & Compliance + {{ Fill IRMRiskyUserProfiles Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -278,6 +301,9 @@ Accept wildcard characters: False ``` ### -PriorityCleanup + +> Applicable: Security & Compliance + The PriorityCleanup switch specifies whether to update the rule associated with a Priority cleanup policy. You don't need to specify a value with this switch. Priority cleanup policies expedite the deletion of sensitive content by overriding any existing retention settings or eDiscovery holds. For more information, see [Priority Cleanup](https://learn.microsoft.com/purview/priority-cleanup). @@ -286,7 +312,6 @@ Priority cleanup policies expedite the deletion of sensitive content by overridi Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -296,6 +321,9 @@ Accept wildcard characters: False ``` ### -RetentionComplianceAction + +> Applicable: Security & Compliance + The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: - Delete @@ -306,7 +334,6 @@ The RetentionComplianceAction parameter specifies the retention action for the r Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -316,6 +343,9 @@ 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. @@ -325,7 +355,6 @@ The RetentionDuration parameter specifies the hold duration for the retention ru Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -335,6 +364,9 @@ 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 @@ -349,7 +381,6 @@ You can't use this parameter for Teams retention rules. Type: HoldDurationHint Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -359,13 +390,15 @@ 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/exchange/Set-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-RetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md index 14102c1ff4..dc5bbe96e0 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-retentionpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-RetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-retentionpolicy +schema: 2.0.0 +title: Set-RetentionPolicy --- # Set-RetentionPolicy @@ -51,13 +52,15 @@ The Identity parameter is a positional parameter. Positional parameters can be u ## 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, distinguished name (DN), or GUID of the retention policy. ```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: True Position: 1 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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. Use this switch to hide the confirmation prompt when you use the RetentionId parameter. @@ -112,7 +122,6 @@ Use this switch to hide the confirmation prompt when you use the RetentionId par 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 @@ -122,6 +131,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch. @@ -141,7 +153,6 @@ Changes to the default retention policy that affect existing mailboxes can poten Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -151,6 +162,9 @@ Accept wildcard characters: False ``` ### -IsDefaultArbitrationMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The IsDefaultArbitrationMailbox switch configures this policy as the default retention policy for arbitration mailboxes in your Exchange Online organization. You don't need to specify a value with this switch. @@ -161,7 +175,6 @@ This parameter isn't available in on-premises deployments. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -171,13 +184,15 @@ Accept wildcard characters: False ``` ### -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 retention policy. ```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 @@ -187,6 +202,9 @@ Accept wildcard characters: False ``` ### -RetentionId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionId parameter specifies the identity of the retention policy to make sure mailboxes moved between two Exchange organizations continue to have the same retention policy applied to them. For example, in a cross-forest deployment or in a cross-premises deployment, when a mailbox is moved from an on-premises Exchange server to the cloud, or a cloud-based mailbox is moved to an on-premises Exchange server, this parameter is used to make sure the same retention policy is applied to the mailbox. It's not normally required to specify or modify the RetentionId parameter for a retention tag. The parameter is populated automatically when importing retention tags using the Import-RetentionTags.ps1 script. @@ -195,7 +213,6 @@ It's not normally required to specify or modify the RetentionId parameter for a Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -205,13 +222,15 @@ Accept wildcard characters: False ``` ### -RetentionPolicyTagLinks + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionPolicyTagLinks parameter specifies the identity of retention policy tags to associate with the retention policy. Mailboxes that get a retention policy applied have retention tags linked with that retention policy. ```yaml Type: RetentionPolicyTagIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -221,13 +240,15 @@ 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/exchange/Set-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md index f4d7334536..2a50b9e5ce 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-retentionpolicytag applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-RetentionPolicyTag -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-retentionpolicytag +schema: 2.0.0 +title: Set-RetentionPolicyTag --- # Set-RetentionPolicyTag @@ -91,13 +92,15 @@ This example makes optional retention tags available to user Terry Adams using t ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the name, distinguished name (DN), or GUID of the retention policy tag to be modified. ```yaml Type: RetentionPolicyTagIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -107,6 +110,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailbox parameter specifies a mailbox for assigning opt-in tags. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -126,7 +132,6 @@ You must use this parameter with the OptionalInMailbox parameter. Type: MailboxIdParameter Parameter Sets: MailboxTask Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -136,6 +141,9 @@ Accept wildcard characters: False ``` ### -AddressForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -144,7 +152,6 @@ This parameter is reserved for internal Microsoft use. Type: RecipientIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -154,13 +161,15 @@ Accept wildcard characters: False ``` ### -AgeLimitForRetention + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date the item was delivered, or the date an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned. ```yaml Type: EnhancedTimeSpan Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -170,13 +179,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Comment parameter specifies a comment for the retention policy tag. ```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 @@ -186,6 +197,9 @@ 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,7 +209,6 @@ 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 @@ -205,6 +218,9 @@ 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. @@ -213,7 +229,6 @@ 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 @@ -223,6 +238,9 @@ 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. Use this switch to hide the confirmation prompt when you use the RetentionId parameter. @@ -231,7 +249,6 @@ Use this switch to hide the confirmation prompt when you use the RetentionId par 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 @@ -241,6 +258,9 @@ Accept wildcard characters: False ``` ### -JournalingEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -249,7 +269,6 @@ This parameter is reserved for internal Microsoft use. Type: Boolean Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -259,6 +278,9 @@ Accept wildcard characters: False ``` ### -LabelForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -267,7 +289,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -277,13 +298,15 @@ Accept wildcard characters: False ``` ### -LegacyManagedFolder + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LegacyManagedFolder parameter specifies the name of a managed folder. The retention tag is created by using retention settings from the managed folder and its managed content settings. You can use this parameter to create retention tags based on existing managed folders to migrate users from managed folder mailbox policies to retention policies. ```yaml Type: ELCFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -293,13 +316,15 @@ Accept wildcard characters: False ``` ### -LocalizedComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LocalizedComment parameter specifies the localized comment and language for the retention policy tag. This comment is displayed in Microsoft Outlook based on the user's locale. ```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 @@ -309,13 +334,15 @@ Accept wildcard characters: False ``` ### -LocalizedRetentionPolicyTagName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The LocalizedRetentionPolicyTagName parameter specifies a localized name for the retention policy tag. This name is displayed in Outlook based on the user's locale. ```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 @@ -325,6 +352,9 @@ Accept wildcard characters: False ``` ### -MessageClass + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MessageClass parameter specifies the message type to which the tag applies. If not specified, the default value is set to \*. With the exception of a default policy tag (DPT) for voicemail, Exchange doesn't support retention tags for different message types. Only tags with a MessageClass of \* are supported and they apply to all message types. @@ -337,7 +367,6 @@ A DPT for voice mail messages applies only to Microsoft Exchange Unified Messagi 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 @@ -347,6 +376,9 @@ Accept wildcard characters: False ``` ### -MessageFormatForJournaling + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. This parameter is reserved for internal Microsoft use. @@ -355,7 +387,6 @@ This parameter is reserved for internal Microsoft use. Type: JournalingFormat Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -365,13 +396,15 @@ Accept wildcard characters: False ``` ### -MustDisplayCommentEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MustDisplayCommentEnabled parameter specifies whether the comment can be hidden. 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 @@ -381,13 +414,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the retention policy tag. ```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 @@ -397,13 +432,15 @@ 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 assign personal tags to the mailbox. You can use this parameter to make available to a user a personal tag that isn't assigned to the retention policy applied to the specified mailbox. You can specify multiple personal tags separated by commas. ```yaml Type: RetentionPolicyTagIdParameter[] Parameter Sets: MailboxTask Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -413,6 +450,9 @@ Accept wildcard characters: False ``` ### -RetentionAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionAction parameter specifies the action for the retention policy. Valid values are: - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder. @@ -428,7 +468,6 @@ If this parameter isn't present and the RetentionEnabled parameter is set to $tr Type: RetentionAction Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -438,6 +477,9 @@ Accept wildcard characters: False ``` ### -RetentionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionEnabled parameter specifies whether the tag is enabled. When set to $false, the tag is disabled and no retention action is taken on messages that have the tag applied. Messages with a disabled tag are still considered tagged, so any default policy tags in the user's retention policy aren't applied to such messages. @@ -448,7 +490,6 @@ When you set the RetentionEnabled parameter to $false, the retention period for 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 @@ -458,6 +499,9 @@ Accept wildcard characters: False ``` ### -RetentionId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RetentionId parameter specifies an alternate tag ID to ensure the retention tag found on mailbox items tagged in one Exchange organization matches the tag when the mailbox is moved to another Exchange organization (for example, in a cross-forest deployment or in a cross-premises deployment, when a mailbox is moved from an on-premises Exchange server to the cloud, or a cloud-based mailbox is moved to an on-premises Exchange server). Typically, you don't need to specify or modify the RetentionId parameter for a retention tag. This parameter is populated automatically when importing retention tags in a cross-forest or cross-premises deployment. @@ -466,7 +510,6 @@ Typically, you don't need to specify or modify the RetentionId parameter for a r Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -476,13 +519,15 @@ Accept wildcard characters: False ``` ### -SystemTag + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SystemTag parameter specifies whether the retention policy tag is created for internal Exchange functionality. ```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 @@ -492,13 +537,15 @@ 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/exchange/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md index eca66e5008..eb43ebf270 100644 --- a/exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-roleassignmentpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-RoleAssignmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-roleassignmentpolicy +schema: 2.0.0 +title: Set-RoleAssignmentPolicy --- # Set-RoleAssignmentPolicy @@ -50,13 +51,15 @@ This example changes the default assignment policy. New mailboxes or mailboxes m ## 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 assignment policy to modify. 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 Required: True Position: 1 @@ -66,6 +69,9 @@ 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`. @@ -75,7 +81,6 @@ 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,13 +90,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Description parameter specifies the description that's displayed when the role assignment policy is viewed using the Get-RoleAssignmentPolicy cmdlet. Enclose the description 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: False Position: Named @@ -101,6 +108,9 @@ 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. @@ -111,7 +121,6 @@ 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 @@ -121,6 +130,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The IsDefault switch makes the assignment policy the default assignment policy. You don't need to specify a value with this switch. New mailboxes or mailboxes moved from previous versions of Exchange are assigned the default assignment policy when an explicit assignment policy isn't provided. @@ -129,7 +141,6 @@ New mailboxes or mailboxes moved from previous versions of Exchange are assigned 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 @@ -139,13 +150,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the new name of the assignment policy. If the assignment policy name contains spaces, enclose the name in quotation marks ("). The maximum length of the name is 64 characters. ```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 @@ -155,13 +168,15 @@ 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/exchange/Set-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-RoleGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md index b0c9fd04a3..75734b96cc 100644 --- a/exchange/exchange-ps/exchange/Set-RoleGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-rolegroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: Set-RoleGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-rolegroup +schema: 2.0.0 +title: Set-RoleGroup --- # Set-RoleGroup @@ -89,13 +90,15 @@ The first command retrieves the credentials using the Get-Credential cmdlet and ## 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 name of the role group to modify. If the 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 @@ -105,6 +108,9 @@ 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 fully qualified domain name (FQDN) or IP address of the domain controller in the forest where the foreign USG resides. The domain controller you specify is used to get security information for the foreign USG specified by the LinkedForeignGroup parameter. @@ -115,7 +121,6 @@ You can only use the LinkedDomainController parameter with a linked role group. Type: String Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -125,6 +130,9 @@ Accept wildcard characters: False ``` ### -LinkedForeignGroup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The LinkedForeignGroup parameter specifies the name of the foreign USG you want to link this role group to. If the foreign USG name contains spaces, enclose the name in quotation marks ("). @@ -137,7 +145,6 @@ If you use the LinkedForeignGroup parameter, you must specify a domain controlle Type: UniversalSecurityGroupIdParameter Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -147,6 +154,9 @@ 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: @@ -158,7 +168,6 @@ 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 @@ -168,6 +177,9 @@ 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`. @@ -177,7 +189,6 @@ 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 @@ -187,13 +198,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Description parameter specifies the description displayed when the role group is viewed using the Get-RoleGroup cmdlet. Enclose the description 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, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -203,13 +216,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter has a maximum length of 256 characters. ```yaml 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 @@ -219,6 +234,9 @@ 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. @@ -227,7 +245,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -237,6 +254,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Security & Compliance, 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. @@ -247,7 +267,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -257,6 +276,9 @@ 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 username and password that's used to access the domain controller specified by the LinkedDomainController parameter. @@ -269,7 +291,6 @@ You can only use the LinkedCredential parameter with a linked role group. Type: PSCredential Parameter Sets: CrossForest Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Position: Named Default value: None Accept pipeline input: False @@ -277,6 +298,9 @@ 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 the users or USG who can modify the configuration of a role group or add or remove members to or from a role group. The list you specify with this parameter overwrites the existing ManagedBy list. To add or remove individual role group managers, and for more information about modifying multivalued properties, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help). You can use the name, distinguished name (DN), or primary SMTP address of the user or USG you want to add. If the name of the user or USG contains spaces, enclose the name in quotation marks ("). @@ -287,7 +311,6 @@ If you want to add more than one user or USG, separate them using commas. 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 @@ -297,13 +320,15 @@ 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 role group. The name can contain up to 64 characters. If the name contains spaces, enclose the name 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, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -313,6 +338,9 @@ Accept wildcard characters: False ``` ### -WellKnownObject + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill WellKnownObject Description }} @@ -321,7 +349,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -331,6 +358,9 @@ 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. @@ -339,7 +369,6 @@ 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/exchange/Set-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md index d17b041270..092b16811e 100644 --- a/exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-routinggroupconnector applicable: Exchange Server 2010 -title: Set-RoutingGroupConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-routinggroupconnector +schema: 2.0.0 +title: Set-RoutingGroupConnector --- # Set-RoutingGroupConnector @@ -57,13 +58,15 @@ This example makes the following configuration changes to the routing group conn ## 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. ```yaml Type: RoutingGroupConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ Accept wildcard characters: False ``` ### -Cost + +> Applicable: Exchange Server 2010 + The Cost parameter specifies a cost to the connector. Transport servers use the connector cost to determine the least cost routing path from a source server to the destination server for message delivery. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -108,13 +115,15 @@ 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 @@ -124,6 +133,9 @@ Accept wildcard characters: False ``` ### -MaxMessageSize + +> Applicable: Exchange Server 2010 + The MaxMessageSize parameter specifies the maximum size of a message that can pass through a routing group connector. The default value is unlimited. When you enter a value, qualify the value with one of the following units: - B (bytes) @@ -137,7 +149,6 @@ Unqualified values are treated as bytes. The valid input range for this paramete Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -147,13 +158,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010 + The Name parameter specifies the name of the routing group connector. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -163,13 +176,15 @@ Accept wildcard characters: False ``` ### -PublicFolderReferralsEnabled + +> Applicable: Exchange Server 2010 + The PublicFolderReferralsEnabled parameter specifies whether users can use this routing group connector to access a public folder replica located in the routing group of the target servers when an instance of that public folder isn't available in the same routing group as the user's mailbox. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -179,13 +194,15 @@ Accept wildcard characters: False ``` ### -SourceTransportServers + +> Applicable: Exchange Server 2010 + The SourceTransportServers parameter specifies the host name or FQDN of the transport servers that are used to send messages to the target transport servers. You can specify more than one server by separating each entry with a comma. For more information about how to add or remove values from multivalued properties, see [Modifying Multivalued Properties](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb684908(v=exchg.141)). ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -195,13 +212,15 @@ Accept wildcard characters: False ``` ### -TargetTransportServers + +> Applicable: Exchange Server 2010 + The TargetTransportServers parameter specifies the host name or FQDN of the transport servers that receive messages from the source transport servers. You can specify more than one server by separating each entry with a comma. For more information about how to add or remove values from multivalued properties, see [Modifying Multivalued Properties](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb684908(v=exchg.141)). ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -211,13 +230,15 @@ 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/exchange/Set-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-RpcClientAccess.md rename to exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md index 970b171e11..95e3e25b08 100644 --- a/exchange/exchange-ps/exchange/Set-RpcClientAccess.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-rpcclientaccess applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-RpcClientAccess -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-rpcclientaccess +schema: 2.0.0 +title: Set-RpcClientAccess --- # Set-RpcClientAccess @@ -60,6 +61,9 @@ This example prevents Outlook Anywhere connections by Outlook 2013 clients that ## PARAMETERS ### -Server + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 @@ -71,7 +75,6 @@ The Server parameter specifies the Client Access server where you want to run th Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -81,6 +84,9 @@ Accept wildcard characters: False ``` ### -BlockedClientVersions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedClientVersions parameter specifies the RPC client versions that aren't allowed to connect to the specified Exchange server. For example, the Microsoft Exchange RPC Client Access service rejects an Outlook Anywhere connection if the version of Outlook is the specified value, or is in the specified range. Valid version values are in the format X.Y.Z. RPC client versions are typically reported in format X.0.Y.Z format, but for this parameter, you need to specify the value as X.Y.Z. @@ -99,7 +105,6 @@ Be careful when you restrict client access, because Exchange server components m Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -109,6 +114,9 @@ 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`. @@ -118,7 +126,6 @@ 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 @@ -128,13 +135,15 @@ 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 @@ -144,6 +153,9 @@ Accept wildcard characters: False ``` ### -EncryptionRequired + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EncryptionRequired parameter specifies whether encryption is required for RPC client connections. Valid values are: - $true: Unencrypted RPC client connections are rejected. This is the default value. @@ -153,7 +165,6 @@ The EncryptionRequired parameter specifies whether encryption is required for RP Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -163,6 +174,9 @@ Accept wildcard characters: False ``` ### -MaximumConnections + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaximumConnections parameter specifies the maximum number of concurrent client connections that are allowed by the Microsoft Exchange RPC Client Access service. The default value is 65536. **Note**: Although you can configure a non-default value for this parameter, changes to this setting aren't enforced. @@ -171,7 +185,6 @@ The MaximumConnections parameter specifies the maximum number of concurrent clie Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,13 +194,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the configuration object in Active Directory. By default, this parameter is set to RpcClientAccess. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -197,13 +212,15 @@ 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/exchange/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md index fbaa17c621..c985e58209 100644 --- a/exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-safeattachmentpolicy applicable: Exchange Online -title: Set-SafeAttachmentPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-safeattachmentpolicy +schema: 2.0.0 +title: Set-SafeAttachmentPolicy --- # Set-SafeAttachmentPolicy @@ -52,6 +53,9 @@ This example modifies the existing safe attachment policy named Engineering Bloc ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the safe attachment policy that you want to modify. You can use any value that uniquely identifies the policy. For example: @@ -64,7 +68,6 @@ You can use any value that uniquely identifies the policy. For example: Type: SafeAttachmentPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -74,6 +77,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Online + The Action parameter specifies the action for the safe attachment policy. Valid values are: - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal. @@ -90,7 +96,6 @@ The results of all actions are available in message trace. Type: SafeAttachmentAction Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -100,13 +105,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -116,6 +123,9 @@ 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,7 +135,6 @@ 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 @@ -135,6 +144,9 @@ Accept wildcard characters: False ``` ### -Enable + +> Applicable: Exchange Online + The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are: - $true: The Action parameter specifies the action for the safe attachment policy. @@ -146,7 +158,6 @@ To enable or disable an existing Safe Attachments policy, use the Enable-SafeAtt Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -156,6 +167,9 @@ Accept wildcard characters: False ``` ### -QuarantineTag + +> Applicable: Exchange Online + The QuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as malware by Safe Attachments. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -172,7 +186,6 @@ 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 @@ -182,6 +195,9 @@ Accept wildcard characters: False ``` ### -Redirect + +> Applicable: Exchange Online + The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are: - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow. @@ -191,7 +207,6 @@ The Redirect parameter specifies whether to deliver messages to an alternate ema Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -201,6 +216,9 @@ Accept wildcard characters: False ``` ### -RedirectAddress + +> Applicable: Exchange Online + The RedirectAddress parameter specifies the destination email address to deliver messages if malware is detected in an attachment. The value of this parameter is meaningful only when value of the Redirect parameter is $true and the value of the Action parameter is Allow. @@ -209,7 +227,6 @@ The value of this parameter is meaningful only when value of the Redirect parame Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -219,13 +236,15 @@ 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/exchange/Set-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md index 985e31a012..1f74e7e4c6 100644 --- a/exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-safeattachmentrule applicable: Exchange Online -title: Set-SafeAttachmentRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-safeattachmentrule +schema: 2.0.0 +title: Set-SafeAttachmentRule --- # Set-SafeAttachmentRule @@ -59,6 +60,9 @@ This example modifies the existing safe attachment rule named Engineering Depart ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the safe attachment rule that you want to modify. You can use any value that uniquely identifies the rule. For example: @@ -71,7 +75,6 @@ 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 @@ -81,13 +84,15 @@ 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 @@ -97,6 +102,9 @@ 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`. @@ -106,7 +114,6 @@ 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 @@ -116,13 +123,15 @@ 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 @@ -132,6 +141,9 @@ 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 @@ -147,7 +159,6 @@ 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 @@ -157,6 +168,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + 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 @@ -174,7 +188,6 @@ 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 @@ -184,13 +197,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the safe attachment rule. 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 @@ -200,6 +215,9 @@ 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. Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: @@ -214,7 +232,6 @@ 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 Required: False Position: Named @@ -224,13 +241,15 @@ 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 @@ -240,6 +259,9 @@ Accept wildcard characters: False ``` ### -SafeAttachmentPolicy + +> Applicable: Exchange Online + The SafeAttachmentPolicy parameter specifies the safe attachment policy that's associated with this safe attachment rule. The rule defines the conditions, and the policy defines the actions. You can use any value that uniquely identifies the policy. For example: @@ -254,7 +276,6 @@ You can't specify a safe attachment policy that's already associated with anothe Type: SafeAttachmentPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -264,6 +285,9 @@ 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 @@ -279,7 +303,6 @@ 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 @@ -289,6 +312,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Online + 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 @@ -306,7 +332,6 @@ 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 @@ -316,13 +341,15 @@ 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/exchange/Set-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md index 4587cee20b..23887ead7e 100644 --- a/exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-safelinkspolicy applicable: Exchange Online -title: Set-SafeLinksPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-safelinkspolicy +schema: 2.0.0 +title: Set-SafeLinksPolicy --- # Set-SafeLinksPolicy @@ -58,6 +59,9 @@ This example modifies the existing Safe Links policy named Engineering Block URL ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Safe Links policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -68,7 +72,6 @@ The Identity parameter specifies the Safe Links policy that you want to modify. Type: SafeLinksPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -78,13 +81,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -94,6 +99,9 @@ Accept wildcard characters: False ``` ### -AllowClickThrough + +> Applicable: Exchange Online + The AllowClickThrough parameter specifies whether to allow users to click through to the original URL on warning pages. Valid values are: $true: The user is allowed to click through to the original URL. @@ -105,7 +113,6 @@ In PowerShell, the default value is $false. In new Safe Links policies created i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -115,6 +122,9 @@ 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`. @@ -124,7 +134,6 @@ 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,13 +143,15 @@ Accept wildcard characters: False ``` ### -CustomNotificationText + +> Applicable: Exchange Online + The custom notification text specifies the customized notification text to show to users. 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 @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -DeliverMessageAfterScan + +> Applicable: Exchange Online + The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are: - $true: Wait until Safe Links scanning is complete before delivering the message. This is the default value. Messages that contain malicious links are not delivered. @@ -159,7 +173,6 @@ The DeliverMessageAfterScan parameter specifies whether to deliver email message Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -169,6 +182,9 @@ Accept wildcard characters: False ``` ### -DisableUrlRewrite + +> Applicable: Exchange Online + The DisableUrlRewrite parameter specifies whether to rewrite (wrap) URLs in email messages. Valid values are: - $true: URLs in messages are not rewritten, but messages are still scanned by Safe Links prior to delivery. Time of click checks on links are done using the Safe Links API in supported Outlook clients (currently, Outlook for Windows and Outlook for Mac). @@ -180,7 +196,6 @@ In PowerShell, the default value is $false. In new Safe Links policies created i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -190,6 +205,9 @@ Accept wildcard characters: False ``` ### -DoNotRewriteUrls + +> Applicable: Exchange Online + The DoNotRewriteUrls parameter specifies the URLs that are not rewritten by Safe Links scanning. The list of entries allows users who are included in the policy to access the specified URLs that would otherwise be blocked by Safe Links. 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"`. @@ -200,7 +218,6 @@ For details about the entry syntax, see [Entry syntax for the "Do not rewrite th Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -210,6 +227,9 @@ Accept wildcard characters: False ``` ### -EnableForInternalSenders + +> Applicable: Exchange Online + The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are: - $true: The policy is applied to internal and external senders. This is the default value. @@ -219,7 +239,6 @@ The EnableForInternalSenders parameter specifies whether the Safe Links policy i Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -229,6 +248,9 @@ Accept wildcard characters: False ``` ### -EnableOrganizationBranding + +> Applicable: Exchange Online + The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are: - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo. @@ -238,7 +260,6 @@ The EnableOrganizationBranding parameter specifies whether your organization's l Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -248,6 +269,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForEmail + +> Applicable: Exchange Online + The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are: - $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link will be checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -257,7 +281,6 @@ The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links pro Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -267,6 +290,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForOffice + +> Applicable: Exchange Online + The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are: - $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -278,7 +304,6 @@ Note that this protection applies to links in Office documents, not links in ema Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -288,6 +313,9 @@ Accept wildcard characters: False ``` ### -EnableSafeLinksForTeams + +> Applicable: Exchange Online + The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are: - $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser. @@ -297,7 +325,6 @@ The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -307,6 +334,9 @@ Accept wildcard characters: False ``` ### -ScanUrls + +> Applicable: Exchange Online + The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are: - $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value. @@ -316,7 +346,6 @@ The ScanUrls parameter specifies whether to enable or disable real-time scanning Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -326,6 +355,9 @@ Accept wildcard characters: False ``` ### -TrackClicks + +> Applicable: Exchange Online + The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are: - $true: User clicks are tracked. This is the default value. @@ -335,7 +367,6 @@ The TrackClicks parameter specifies whether to track user clicks related to Safe Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -345,6 +376,9 @@ Accept wildcard characters: False ``` ### -UseTranslatedNotificationText + +> Applicable: Exchange Online + The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are: - $true: Translate custom notification text to the user's language. @@ -354,7 +388,6 @@ The UseTranslatedNotificationText specifies whether to use Microsoft Translator Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -364,13 +397,15 @@ 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/exchange/Set-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-SafeLinksRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md index 6db4b01eeb..1d6ad7df8d 100644 --- a/exchange/exchange-ps/exchange/Set-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-safelinksrule applicable: Exchange Online -title: Set-SafeLinksRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-safelinksrule +schema: 2.0.0 +title: Set-SafeLinksRule --- # Set-SafeLinksRule @@ -75,6 +76,9 @@ This example is similar to Example 2, but in this example, the Safe Links rule i ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Safe Links rule that you want to modify. You can use any value that uniquely identifies the rule. For example: @@ -87,7 +91,6 @@ 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 @@ -97,13 +100,15 @@ 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,6 +118,9 @@ 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`. @@ -122,7 +130,6 @@ 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 @@ -132,13 +139,15 @@ 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 @@ -148,6 +157,9 @@ 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 @@ -163,7 +175,6 @@ 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 @@ -173,6 +184,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + 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 @@ -190,7 +204,6 @@ 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 @@ -200,13 +213,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a unique name for the Safe Links rule. 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 @@ -216,6 +231,9 @@ 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. Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: @@ -230,7 +248,6 @@ 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 Required: False Position: Named @@ -240,13 +257,15 @@ 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 @@ -256,6 +275,9 @@ Accept wildcard characters: False ``` ### -SafeLinksPolicy + +> Applicable: Exchange Online + The SafeLinksPolicy parameter specifies the Safe Links policy that's associated with this Safe Links rule. The rule defines the conditions and the policy defines the actions. You can use any value that uniquely identifies the policy. For example: @@ -270,7 +292,6 @@ You can't specify a Safe Attachments policy that's already associated with anoth Type: SafeLinksPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -280,6 +301,9 @@ 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 @@ -295,7 +319,6 @@ 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 @@ -305,6 +328,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Online + 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 @@ -322,7 +348,6 @@ 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 @@ -332,13 +357,15 @@ 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/exchange/Set-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md index 4288a07794..216d734a24 100644 --- a/exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-searchdocumentformat applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SearchDocumentFormat -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-searchdocumentformat +schema: 2.0.0 +title: Set-SearchDocumentFormat --- # Set-SearchDocumentFormat @@ -47,13 +48,15 @@ This command disables the Zip file format for indexing by Exchange Search. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the file format. ```yaml Type: SearchDocumentFormatId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -63,13 +66,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the file format is enabled. Set the parameter to $false to disable the format for content indexing. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -79,6 +84,9 @@ 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`. @@ -88,7 +96,6 @@ 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 @@ -98,6 +105,9 @@ 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 @@ -111,7 +121,6 @@ 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 @@ -121,13 +130,15 @@ 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/exchange/Set-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md index d1f54d8ff0..b471f4c783 100644 --- a/exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-secopsoverridepolicy applicable: Exchange Online -title: Set-SecOpsOverridePolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-secopsoverridepolicy +schema: 2.0.0 +title: Set-SecOpsOverridePolicy --- # Set-SecOpsOverridePolicy @@ -48,6 +49,9 @@ This example modifies the SecOPs mailbox override policy with the specified sett ## 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 @@ -59,7 +63,6 @@ The Identity parameter specifies the SecOps override policy that you want to mod Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 0 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -AddSentTo + +> Applicable: Exchange Online + The AddSentTo parameter specifies an entry to add to the existing list of SecOps mailbox email addresses. Groups are not allowed. You can specify multiple values separated by commas. @@ -77,7 +83,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -87,13 +92,15 @@ 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: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -103,6 +110,9 @@ 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`. @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ 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 @@ -138,6 +149,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether the policy is enabled. Valid values are: - $true: The policy is enabled. This is the default value. @@ -147,7 +161,6 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -157,6 +170,9 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: 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. @@ -165,7 +181,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -175,6 +190,9 @@ Accept wildcard characters: False ``` ### -RemoveSentTo + +> Applicable: Exchange Online + The RemoveSentTo parameter specifies an entry to remove from the existing list of SecOps mailbox email addresses. Groups are not allowed. You can specify multiple values separated by commas. @@ -183,7 +201,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -193,6 +210,9 @@ 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. The WhatIf switch doesn't work in Security & Compliance PowerShell. @@ -201,7 +221,6 @@ The WhatIf switch doesn't work in Security & Compliance PowerShell. Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-SendConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md index 481f2bf0c3..c2a12042bf 100644 --- a/exchange/exchange-ps/exchange/Set-SendConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-sendconnector applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SendConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-sendconnector +schema: 2.0.0 +title: Set-SendConnector --- # Set-SendConnector @@ -79,13 +80,15 @@ This example makes the following configuration changes to the Send connector nam ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GUID or connector name that represents the Send connector you want to modify. ```yaml Type: SendConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -95,6 +98,9 @@ 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 Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. - AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed. @@ -121,7 +127,6 @@ Although you can configure non-SMTP address spaces on a Send connector in the Tr Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,6 +136,9 @@ Accept wildcard characters: False ``` ### -AuthenticationCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AuthenticationCredential parameter specifies the username and password that's required to use the connector. 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). @@ -139,7 +147,6 @@ 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,6 +156,9 @@ Accept wildcard characters: False ``` ### -CloudServicesMailEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **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. @@ -162,7 +172,6 @@ Valid values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,13 +181,15 @@ Accept wildcard characters: False ``` ### -Comment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + TheComment parameter specifies an optional comment. You must enclose the Comment parameter 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 @@ -188,6 +199,9 @@ 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`. @@ -197,7 +211,6 @@ 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 @@ -207,6 +220,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are: - Default: The connector isn't used to send messages to Microsoft 365. This is the default value. @@ -216,7 +232,6 @@ The ConnectorType parameter specifies whether the connector is used in hybrid de Type: TenantConnectorType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -226,6 +241,9 @@ Accept wildcard characters: False ``` ### -ConnectionInactivityTimeOut + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionInactivityTimeOut parameter specifies the maximum time an idle connection can remain open. The default value is ten 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. @@ -236,7 +254,6 @@ For example, to specify fifteen minutes, set it to 00:15:00. The valid input ran Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -246,13 +263,15 @@ Accept wildcard characters: False ``` ### -DNSRoutingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DNSRoutingEnabled parameter specifies whether the Send connector uses Domain Name System (DNS) to route mail. Valid values for this parameter are $true or $false. The default value is $true. If you specify a SmartHosts parameter, the DNSRoutingEnabled parameter must be $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 @@ -262,6 +281,9 @@ 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. @@ -270,7 +292,6 @@ 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 @@ -280,6 +301,9 @@ Accept wildcard characters: False ``` ### -DomainSecureEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DomainSecureEnabled parameter is part of the process to enable mutual Transport Layer Security (TLS) authentication for the domains serviced by this Send connector. Mutual TLS authentication functions correctly only when the following conditions are met: - The value of the DomainSecureEnabled parameter must be $true. @@ -299,7 +323,6 @@ The default value for the DomainSecureEnabled parameter is $true for default Sen Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -309,13 +332,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether to enable the Send connector to process email messages. Valid values are $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 @@ -325,6 +350,9 @@ Accept wildcard characters: False ``` ### -ErrorPolicies + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ErrorPolicies parameter specifies how communication errors are treated. Possible values are the following: - Default: A non-delivery report (NDR) is generated for communication errors. @@ -340,7 +368,6 @@ Specify a value other than Default for this parameter only if this Send connecto Type: ErrorPolicies Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -350,6 +377,9 @@ 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. @@ -358,7 +388,6 @@ 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 @@ -368,13 +397,15 @@ Accept wildcard characters: False ``` ### -ForceHELO + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceHELO parameter specifies whether HELO is sent instead of the default EHLO. Valid values are $true or $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 Required: False Position: Named @@ -384,6 +415,9 @@ Accept wildcard characters: False ``` ### -Fqdn + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Fqdn parameter specifies the FQDN used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this parameter is displayed to connected messaging servers whenever a source server name is required, as in the following examples: - In the EHLO/HELO command when the Send connector communicates with the next hop messaging server @@ -396,7 +430,6 @@ The default value of the Fqdn parameter is $null. This means the default FQDN va Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -406,13 +439,15 @@ Accept wildcard characters: False ``` ### -FrontendProxyEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -422,13 +457,15 @@ Accept wildcard characters: False ``` ### -IgnoreSTARTTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IgnoreSTARTTLS parameter specifies whether to ignore the StartTLS option offered by a remote sending server. This parameter is used with remote domains. This parameter must be set to $false if the RequireTLS parameter is set to $true. Valid values for this parameter are $true or $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 @@ -438,6 +475,9 @@ Accept wildcard characters: False ``` ### -IsCoexistenceConnector + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IsCoexistenceConnector parameter specifies whether this Send connector is used for secure mail flow between your on-premises deployment and your Microsoft 365 organization. The default value is $false. @@ -446,7 +486,6 @@ The IsCoexistenceConnector parameter specifies whether this Send connector is us Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -456,13 +495,15 @@ 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 with the Transport service. 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 only be used by Transport service on 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 @@ -472,6 +513,9 @@ Accept wildcard characters: False ``` ### -LinkedReceiveConnector + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The LinkedReceiveConnector parameter forces all messages received by the specified Receive connector out through this Send connector. The value of the LinkedReceiveConnector parameter can use any of the following identifiers to specify the Receive connector: @@ -492,7 +536,6 @@ When you use the LinkedReceiveConnector parameter with this command, you must al Type: ReceiveConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -502,6 +545,9 @@ 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 can pass through a connector. The default value is 25 MB. When you enter a value, qualify the value with one of the following units: @@ -520,7 +566,6 @@ The valid input range for this parameter is 0 to 2147483647 bytes. To remove the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -530,13 +575,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the administrator-supplied name of the connector. You must enclose the Name parameter in quotation marks (") if the name contains spaces. For example, "New Send Connector". ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -546,13 +593,15 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Port parameter specifies the port number for smart host forwarding, if you specify a value in the SmartHosts parameter. The valid input range is an integer from 0 through 65535. The default value is 25. In most organizations, the port number is set to 25. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -562,13 +611,15 @@ Accept wildcard characters: False ``` ### -ProtocolLoggingLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProtocolLoggingLevel parameter specifies whether to enable protocol logging. Verbose enables protocol logging. None disables protocol logging. The location of the Send connector protocol logs for all Send connectors configured in the Transport service on a Mailbox server or on an Edge server is specified with the SendProtocolLogPath parameter of the Set-TransportService cmdlet. ```yaml Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -578,13 +629,15 @@ Accept wildcard characters: False ``` ### -RequireOorg + +> 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 @@ -594,13 +647,15 @@ Accept wildcard characters: False ``` ### -RequireTLS + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequireTLS parameter specifies whether all messages sent through this connector must be transmitted using TLS. 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 @@ -610,13 +665,15 @@ Accept wildcard characters: False ``` ### -SmartHostAuthMechanism + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmartHostAuthMechanism parameter specifies the smart host authentication mechanism to use for authentication with a remote server. Use this parameter only when a smart host is configured and the DNSRoutingEnabled parameter is set to $false. Valid values are None, BasicAuth, BasicAuthRequireTLS, ExchangeServer, and ExternalAuthoritative. All values are mutually exclusive. If you select BasicAuth or BasicAuthRequireTLS, you must use the AuthenticationCredential parameter to specify the authentication credential. ```yaml Type: AuthMechanisms Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -626,6 +683,9 @@ Accept wildcard characters: False ``` ### -SmartHosts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmartHosts parameter specifies the smart hosts the Send connector uses to route mail. This parameter is required if you set the DNSRoutingEnabled parameter to $false and it must be specified on the same command line. The SmartHosts parameter takes one or more FQDNs, such as server.contoso.com, or one or more IP addresses, or a combination of both FQDNs and IP addresses. If you enter an IP address, you must enter the IP address as a literal. For example, 10.10.1.1. The smart host identity can be the FQDN of a smart-host server, a mail exchanger (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart-host server. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -636,7 +696,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -646,13 +705,15 @@ Accept wildcard characters: False ``` ### -SmtpMaxMessagesPerConnection + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SmtpMaxMessagesPerConnection parameter specifies the maximum number of messages the server can send per connection. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -662,13 +723,15 @@ Accept wildcard characters: False ``` ### -SourceIPAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SourceIPAddress parameter specifies the local IP address to use as the endpoint for an SMTP connection to a remote messaging server. The default IP address is 0.0.0.0. This value means that the server can use any available local IP address. This parameter is valid only for Send connectors configured on an Edge server. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -678,6 +741,9 @@ 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 can use this Send connector. This parameter isn't valid for Send connectors configured on an Edge server. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -688,7 +754,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -698,6 +763,9 @@ Accept wildcard characters: False ``` ### -TlsAuthLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsAuthLevel parameter specifies the TLS authentication level that is used for outbound TLS connections established by this Send connector. Valid values are: - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed. @@ -710,7 +778,6 @@ You can't specify a value for this parameter if the IgnoreSTARTTLS parameter is Type: TlsAuthLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -720,13 +787,15 @@ 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. A valid value for this parameter is `"X.500IssuerX.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint `, run the command `$TLSCertName = "$($TLSCert.Issuer)$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter. ```yaml Type: SmtpX509Identifier Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -736,6 +805,9 @@ Accept wildcard characters: False ``` ### -TlsDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TlsDomain parameter specifies the domain name that the Send connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection. This parameter is used only if the TlsAuthLevel parameter is set to DomainValidation. @@ -749,7 +821,6 @@ A value for this parameter is required if: Type: SmtpDomainWithSubdomains Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -759,13 +830,15 @@ Accept wildcard characters: False ``` ### -UseExternalDNSServersEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseExternalDNSServersEnabled parameter specifies whether this Send connector uses the external DNS list specified by the ExternalDNSServers parameter of the Set-TransportService cmdlet. 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 @@ -775,13 +848,15 @@ 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/exchange/Set-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-SenderFilterConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md index 1b634750be..11ae642e6b 100644 --- a/exchange/exchange-ps/exchange/Set-SenderFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-senderfilterconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SenderFilterConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-senderfilterconfig +schema: 2.0.0 +title: Set-SenderFilterConfig --- # Set-SenderFilterConfig @@ -57,13 +58,15 @@ It adds user1@contoso.com and user2@contoso.com to the blocked senders list with ## PARAMETERS ### -Action + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Action parameter specifies the action that the Sender Filter agent takes on messages from blocked senders or domains. Valid input for this parameter is StampStatus or Reject. The default value is Reject. ```yaml Type: BlockedSenderAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -73,13 +76,15 @@ Accept wildcard characters: False ``` ### -BlankSenderBlockingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlankSenderBlockingEnabled parameter blocks or allows messages that don't contain a sender value in the SMTP command MAIL FROM. Valid input for this parameter is $true or $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 Required: False Position: Named @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -BlockedDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedDomains parameter specifies the domain names to block. When the Sender Filter agent encounters a message from a domain on this list, the Sender Filter agent takes the action specified by the Action parameter. Valid input for this parameter is one or more domains or subdomains. Wildcard characters aren't permitted. For example, if you specify the values contoso.com and marketing.contoso.com, only messages from those domains are blocked by the Sender Filter agent. Messages from sales.contoso.com aren't blocked by the Sender Filter agent. @@ -103,7 +111,6 @@ The maximum number of entries for this parameter is 800. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -113,6 +120,9 @@ Accept wildcard characters: False ``` ### -BlockedDomainsAndSubdomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedDomainsAndSubdomains parameter specifies the domain names to block. When the Sender Filter agent encounters a message from a domain on this list, or from any of the domain's subdomains, the Sender Filter agent takes the action specified by the Action parameter. Valid input for this parameter is one or more domains. Wildcard characters aren't permitted. For example, if you specify the value contoso.com, messages from contoso.com, sales.contoso.com, and all other subdomains of contoso.com are blocked by the Sender Filter agent. @@ -127,7 +137,6 @@ The maximum number of entries for this parameter is 800. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -137,6 +146,9 @@ Accept wildcard characters: False ``` ### -BlockedSenders + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BlockedSenders parameter specifies one or more SMTP email addresses to block. When the Sender Filter agent encounters a message from a sender on this list, the Sender Filter agent takes the action specified by the Action parameter. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -149,7 +161,6 @@ The maximum number of entries for this parameter is 800. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,6 +170,9 @@ 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`. @@ -168,7 +182,6 @@ 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 @@ -178,6 +191,9 @@ 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. @@ -186,7 +202,6 @@ 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 @@ -196,13 +211,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter enables or disables sender filtering on your Exchange server. 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 @@ -212,13 +229,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter enables or disables sender filtering on unauthenticated connections from external messaging servers. 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 @@ -228,13 +247,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter enables or disables sender filtering on authenticated connections from authoritative domains in your organization. Valid input for this parameter is $true or $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 Required: False Position: Named @@ -244,6 +265,9 @@ Accept wildcard characters: False ``` ### -RecipientBlockedSenderAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientBlockedSenderAction parameter specifies the action that the Sender Filter agent takes on messages received from blocked senders that are defined by SafeList aggregation. SafeList aggregation adds blocked senders that are defined by your users in Microsoft Outlook or Outlook on the web to the Blocked Senders list that's used by the Sender Filter agent. Valid input for this parameter is Delete or Reject. The default value is Reject. @@ -252,7 +276,6 @@ Valid input for this parameter is Delete or Reject. The default value is Reject. Type: RecipientBlockedSenderAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -262,13 +285,15 @@ 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/exchange/Set-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-SenderIdConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md index eaeddca576..6c2a1b9e47 100644 --- a/exchange/exchange-ps/exchange/Set-SenderIdConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-senderidconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SenderIdConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-senderidconfig +schema: 2.0.0 +title: Set-SenderIdConfig --- # Set-SenderIdConfig @@ -53,13 +54,15 @@ This example makes the following modifications to the Sender ID configuration: ## PARAMETERS ### -BypassedRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedRecipients parameter specifies one or more SMTP email addresses. Messages bound for the email addresses listed in this parameter are excluded from processing by the Sender ID agent. You can specify multiple values separated by commas. You can enter a maximum of 100 email addresses. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -69,13 +72,15 @@ Accept wildcard characters: False ``` ### -BypassedSenderDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BypassedSenderDomains parameter specifies one or more domain names. Messages that originate from the domains listed in this parameter are excluded from processing by the Sender ID agent. You can specify multiple values separated by commas. You can enter a maximum of 100 domain names. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -85,6 +90,9 @@ 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,7 +102,6 @@ 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,6 +111,9 @@ 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. @@ -112,7 +122,6 @@ 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 @@ -122,13 +131,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter specifies whether the Sender ID agent is enabled on the computer on which you're running the command. Valid input for the Enabled parameter is $true or $false. The default setting is $true. When the Enabled parameter is set to $true, the Sender ID agent is enabled on the computer on which you're running the command. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -138,13 +149,15 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections external to your organization are passed through the Sender ID agent for processing. Valid input for the ExternalMailEnabled parameter is $true or $false. The default setting is $true. When the ExternalMailEnabled parameter is set to $true, all messages from unauthenticated connections external to your organization are passed through the Sender ID agent for processing. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -154,13 +167,15 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter specifies whether all messages from authenticated sender domains that belong to authoritative domains in your enterprise are passed through the Sender ID agent for processing. Valid input for the InternalMailEnabled parameter is $true or $false. The default setting is $false. When the InternalMailEnabled parameter is set to $true, all messages from authenticated sender domains that belong to authoritative domains in your enterprise are passed through the Sender ID agent for processing. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -170,13 +185,15 @@ Accept wildcard characters: False ``` ### -SpoofedDomainAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SpoofedDomainAction parameter specifies the action that the Sender ID agent takes on the message when the sender domain shows evidence of being spoofed. The SpoofedDomainAction parameter takes the following values: StampStatus, Reject or Delete. The default value is StampStatus. ```yaml Type: SenderIdAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -186,13 +203,15 @@ Accept wildcard characters: False ``` ### -TempErrorAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TempErrorAction parameter specifies the action that the Sender ID agent takes on the message when a Sender ID status of TempError is returned. The TempErrorAction parameter takes the following values: StampStatus, Reject or Delete. The default value is StampStatus. ```yaml Type: SenderIdAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -202,13 +221,15 @@ 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/exchange/Set-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-SenderReputationConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md index 610a9441ff..3a4d94f348 100644 --- a/exchange/exchange-ps/exchange/Set-SenderReputationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-senderreputationconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SenderReputationConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-senderreputationconfig +schema: 2.0.0 +title: Set-SenderReputationConfig --- # Set-SenderReputationConfig @@ -56,6 +57,9 @@ It sets the number of hours that senders are put on the blocked senders list to ## 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`. @@ -65,7 +69,6 @@ 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 @@ -75,6 +78,9 @@ 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. @@ -83,7 +89,6 @@ 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 @@ -93,6 +98,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Enabled parameter enables or disables sender reputation on the Exchange server. Valid values are: - $true: Sender reputation is enabled. This is the default value. @@ -102,7 +110,6 @@ The Enabled parameter enables or disables sender reputation on the Exchange serv Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -112,6 +119,9 @@ Accept wildcard characters: False ``` ### -ExternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalMailEnabled parameter allows or prevents sender reputation from processing messages from unauthenticated connections that are external to your Exchange organization. Valid values are: - $true: Sender reputation is enabled on mail from external sources. This is the default value. @@ -121,7 +131,6 @@ The ExternalMailEnabled parameter allows or prevents sender reputation from proc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -131,6 +140,9 @@ Accept wildcard characters: False ``` ### -InternalMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalMailEnabled parameter allows or prevents sender reputation from processing messages from authenticated sender domains that are authoritative domains in your Exchange organization. Valid values are: - $true: Sender reputation is enabled on mail from internal sources. @@ -140,7 +152,6 @@ The InternalMailEnabled parameter allows or prevents sender reputation from proc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,6 +161,9 @@ Accept wildcard characters: False ``` ### -OpenProxyDetectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OpenProxyDetectionEnabled parameter allows or prevents sender reputation from attempting to connect to the message's source IP address to send a test message back to the Exchange server. This test determines if the sender is an open proxy server. Valid values are: - $true: Open proxy server detection is enabled. This is the default value. @@ -165,7 +179,6 @@ The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -175,6 +188,9 @@ Accept wildcard characters: False ``` ### -ProxyServerName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProxyServerName parameter specifies the name or IP address of your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection. The default value is blank ($null). To clear this value, use the value $null. @@ -183,7 +199,6 @@ The default value is blank ($null). To clear this value, use the value $null. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -193,6 +208,9 @@ Accept wildcard characters: False ``` ### -ProxyServerPort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProxyServerPort parameter specifies the port number that's used by your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection. The default value is 0. @@ -201,7 +219,6 @@ The default value is 0. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -211,6 +228,9 @@ Accept wildcard characters: False ``` ### -ProxyServerType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProxyServerType parameter specifies the type of your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection. Valid values are: - None: This is the default value. @@ -226,7 +246,6 @@ The ProxyServerType parameter specifies the type of your organization's proxy se Type: ProxyType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,6 +255,9 @@ Accept wildcard characters: False ``` ### -SenderBlockingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SenderBlockingEnabled parameter allows or prevents sender reputation from blocking senders when their sender reputation level (SRL) meets or exceeds the value of the SrlBlockThreshold parameter. Valid values are: - $true: Sender blocking is enabled. This is the default value. @@ -249,7 +271,6 @@ The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -259,13 +280,15 @@ Accept wildcard characters: False ``` ### -SenderBlockingPeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SenderBlockingPeriod parameter specifies the number of hours that a sender remains on the blocked senders list when their SRL meets or exceeds the value of the SrlBlockThreshold parameter. Valid input for this parameter is an integer from 0 through 48. The default value is 24. ```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,6 +298,9 @@ Accept wildcard characters: False ``` ### -SrlBlockThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SrlBlockThreshold specifies the SRL rating that must be met or exceeded for sender reputation to block a sender. Valid input for this parameter is an integer from 0 through 9. The default value is 7. Messages are blocked only when the SenderBlockingEnabled parameter is set to $true. @@ -283,7 +309,6 @@ Messages are blocked only when the SenderBlockingEnabled parameter is set to $tr Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -293,13 +318,15 @@ 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/exchange/Set-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ServerComponentState.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md index 11c76cf3c6..2e52de78d2 100644 --- a/exchange/exchange-ps/exchange/Set-ServerComponentState.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-servercomponentstate applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ServerComponentState -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-servercomponentstate +schema: 2.0.0 +title: Set-ServerComponentState --- # Set-ServerComponentState @@ -61,6 +62,9 @@ The second command changes the state to Active after the maintenance is over (re ## 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 @@ -72,7 +76,6 @@ 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 @@ -82,13 +85,15 @@ 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 set the state. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -98,6 +103,9 @@ Accept wildcard characters: False ``` ### -Requester + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Requester parameter specifies the system requesting this state change. Valid values are: - HealthAPI @@ -110,7 +118,6 @@ The Requester parameter specifies the system requesting this state change. Valid Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -120,6 +127,9 @@ Accept wildcard characters: False ``` ### -State + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The State parameter specifies the state that you want for the component. Valid values are: - Active @@ -130,7 +140,6 @@ The State parameter specifies the state that you want for the component. Valid v Type: ServiceState Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -140,6 +149,9 @@ 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`. @@ -149,7 +161,6 @@ 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 @@ -159,6 +170,9 @@ 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. @@ -167,7 +181,6 @@ 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 @@ -177,13 +190,15 @@ Accept wildcard characters: False ``` ### -LocalOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LocalOnly switch specifies that the changes are written to the registry of the Exchange server only and not to Active Directory. 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 @@ -193,13 +208,15 @@ Accept wildcard characters: False ``` ### -RemoteOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoteOnly switch specifies that the changes are written to Active Directory only and not to the registry of the Exchange server. 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 @@ -209,13 +226,15 @@ Accept wildcard characters: False ``` ### -TimeoutInSeconds + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -225,13 +244,15 @@ 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/exchange/Set-ServerMonitor.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-ServerMonitor.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md index 42b0c4a810..abd66790db 100644 --- a/exchange/exchange-ps/exchange/Set-ServerMonitor.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-servermonitor applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ServerMonitor -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-servermonitor +schema: 2.0.0 +title: Set-ServerMonitor --- # Set-ServerMonitor @@ -43,6 +44,9 @@ This example sets the maintenance monitor on 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 @@ -54,7 +58,6 @@ The Server parameter specifies the Exchange server where you want to run this co Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -64,13 +67,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the monitor identity. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -80,6 +85,9 @@ Accept wildcard characters: False ``` ### -Repairing + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Repairing parameter specifies whether to set or clear the repairing property on a monitor. The default value is $true. @@ -88,7 +96,6 @@ The default value is $true. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -98,6 +105,9 @@ 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`. @@ -107,7 +117,6 @@ 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 @@ -117,13 +126,15 @@ Accept wildcard characters: False ``` ### -TargetResource + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetResource parameter specifies the target resource that you want to set the monitor on. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -133,13 +144,15 @@ 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/exchange/Set-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-ServicePrincipal.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md index 78b5a30bc0..6c3e27ac68 100644 --- a/exchange/exchange-ps/exchange/Set-ServicePrincipal.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md @@ -1,12 +1,14 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-serviceprincipal applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Set-ServicePrincipal -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda ms.reviewer: bili1 +online version: https://learn.microsoft.com/powershell/module/exchange/set-serviceprincipal +schema: 2.0.0 +title: Set-ServicePrincipal --- # Set-ServicePrincipal @@ -45,6 +47,9 @@ This example sets the service principal in Exchange Online with the specified di ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Identity parameter specifies the service principal that you want to modify. You can use any value that uniquely identifies the service principal. For example: - Name @@ -57,7 +62,6 @@ The Identity parameter specifies the service principal that you want to modify. Type: ServicePrincipalIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -67,6 +71,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -76,7 +83,6 @@ 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 @@ -86,13 +92,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The DisplayName parameter specifies the friendly name of the service principal. If the name contains spaces, enclose the name in quotation marks ("). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -102,13 +110,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-SettingOverride.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md index f038384c37..a9eaae1a17 100644 --- a/exchange/exchange-ps/exchange/Set-SettingOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-settingoverride applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SettingOverride -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-settingoverride +schema: 2.0.0 +title: Set-SettingOverride --- # Set-SettingOverride @@ -53,6 +54,9 @@ This example modifies the setting override named Change OAB Generation on the se ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the setting override that you want to modify. You can use any value that uniquely identifies the override. For example: - Name @@ -63,7 +67,6 @@ The Identity parameter specifies the setting override that you want to modify. Y Type: SettingOverrideIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -73,6 +76,9 @@ 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`. @@ -82,7 +88,6 @@ 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 @@ -92,13 +97,15 @@ 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 @@ -108,6 +115,9 @@ 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. @@ -116,7 +126,6 @@ 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 @@ -126,6 +135,9 @@ Accept wildcard characters: False ``` ### -MaxVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxVersion parameter specifies the latest version of Exchange 2016 that this override applies to (up to and including the specified value). Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42. @@ -136,7 +148,6 @@ To remove a configured version value so the override applies to all versions of Type: Version Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,6 +157,9 @@ Accept wildcard characters: False ``` ### -MinVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MinVersion parameter specifies the earliest version of Exchange 2016 that this override applies to (up to and including the specified value). Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42. @@ -156,7 +170,6 @@ To remove a configured version value so the override applies to all versions of Type: Version Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -166,6 +179,9 @@ Accept wildcard characters: False ``` ### -Parameters + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Parameters parameter specifies one or more parameters for the override that are available for the combination of the Component and Section parameter values. This parameter uses the syntax: `@("Parameter1=Value1","Parameter2=Value2"...)`. For example: - `@("Enabled=true")` @@ -175,7 +191,6 @@ The Parameters parameter specifies one or more parameters for the override that Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -185,13 +200,15 @@ Accept wildcard characters: False ``` ### -Reason + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Reason parameter is used to provide a description of why the override was created. 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: False Position: Named @@ -201,6 +218,9 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter specifies the name of the Exchange 2016 server where you want the override applied. You can specify a single Exchange 2016 server name, or an array of Exchange 2016 server name wildcards. For example, if you have three Exchange 2016 servers named Exchange01, Exchange02 and Exchange03, specify the value Exchange\* to apply the override to all of them. To remove the specified server so the override applies to all Exchange 2016 servers in the Active Directory forest, use the value $null. @@ -209,7 +229,6 @@ To remove the specified server so the override applies to all Exchange 2016 serv Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -219,13 +238,15 @@ 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/exchange/Set-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-SharingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md index 5f5182f760..4f1aee7043 100644 --- a/exchange/exchange-ps/exchange/Set-SharingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-sharingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-SharingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-sharingpolicy +schema: 2.0.0 +title: Set-SharingPolicy --- # Set-SharingPolicy @@ -63,6 +64,9 @@ This example disables the sharing policy SharingPolicy01. ## 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 sharing policy that you want to modify. You can use one of the following values: - ADObjectID @@ -74,7 +78,6 @@ The Identity parameter specifies the identity of the sharing policy that you wan Type: SharingPolicyIdParameter 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 @@ -84,6 +87,9 @@ 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`. @@ -93,7 +99,6 @@ 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 @@ -103,6 +108,9 @@ Accept wildcard characters: False ``` ### -Default + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Default switch specifies that the sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch. If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you disable the default policy. @@ -111,7 +119,6 @@ If no sharing policy has been applied to a mailbox, the default policy is automa 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 @@ -121,6 +128,9 @@ 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,7 +139,6 @@ 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,6 +148,9 @@ Accept wildcard characters: False ``` ### -Domains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Domains parameter specifies the domains and the associated sharing options for those domains in the sharing policy. Values for this parameter use the basic syntax: `'Domain: SharingPolicyAction'`. You can use the following values for `Domain`: @@ -160,7 +172,6 @@ You can specify multiple `'Domain: SharingPolicyAction'` values separated by com 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 @@ -170,6 +181,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Enabled parameter specifies whether to enable the sharing policy. Valid values for this parameter are $true or $false. The default is $true. When the sharing policy is disabled, users who are provisioned to use this policy continue to share information until the sharing policy assistant runs. @@ -178,7 +192,6 @@ When the sharing policy is disabled, users who are provisioned to use this polic 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 @@ -188,13 +201,15 @@ Accept wildcard characters: False ``` ### -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 sharing 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: False Position: Named @@ -204,13 +219,15 @@ 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/exchange/Set-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-SiteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md index c9c67e224a..973a3b30bb 100644 --- a/exchange/exchange-ps/exchange/Set-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-sitemailbox applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SiteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-sitemailbox +schema: 2.0.0 +title: Set-SiteMailbox --- # Set-SiteMailbox @@ -61,6 +62,9 @@ This example disables the duplication of email messages in the site mailbox SMO\ ## 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 site mailbox. For example: - Name @@ -74,7 +78,6 @@ 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: True Position: 1 @@ -84,13 +87,15 @@ Accept wildcard characters: False ``` ### -Active + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Active parameter specifies whether to change the site mailbox's lifecycle status. This parameter accepts $true or $false. This parameter is intended for use only by the user interface. We recommend that you don't use this parameter in the Exchange Management Shell. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -100,6 +105,9 @@ 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`. @@ -109,7 +117,6 @@ 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 @@ -119,13 +126,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DisplayName parameter specifies the display name of the site mailbox. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -135,13 +144,15 @@ 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 @@ -151,6 +162,9 @@ 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. @@ -159,7 +173,6 @@ 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 @@ -169,6 +182,9 @@ Accept wildcard characters: False ``` ### -Members + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is intended for use only by the user interface. We recommend that you don't use this parameter. The Members parameter specifies the members of the site mailbox. You can add or remove members using this parameter. @@ -188,7 +204,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -198,6 +213,9 @@ Accept wildcard characters: False ``` ### -Owners + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is intended for use only by the user interface. We recommend that you don't use this parameter. The Owners parameter specifies the owners of the site mailbox. You can add or remove owners using this parameter. @@ -217,7 +235,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -227,13 +244,15 @@ Accept wildcard characters: False ``` ### -RemoveDuplicateMessages + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RemoveDuplicateMessages parameter specifies that when users post messages to a site mailbox, duplicate messages will be deleted. This parameter accepts the values of $true or $false. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -243,13 +262,15 @@ Accept wildcard characters: False ``` ### -SharePointUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SharePointUrl parameter specifies the URL of the SharePoint site, for example, "https://myserver/teams/edu". ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -259,6 +280,9 @@ Accept wildcard characters: False ``` ### -ShowInMyClient + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is intended for use only by the user interface. We recommend that you don't use this parameter. The ShowInMyClient parameter specifies that the site mailbox folder will show in your email client. @@ -267,7 +291,6 @@ The ShowInMyClient parameter specifies that the site mailbox folder will show in Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,6 +300,9 @@ Accept wildcard characters: False ``` ### -SyncEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The SyncEnabled parameter specifies whether to enable or disable synchronization for the site mailbox. Valid values are: - $true: Synchronization is enabled. @@ -286,7 +312,6 @@ The SyncEnabled parameter specifies whether to enable or disable synchronization Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -296,13 +321,15 @@ 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/exchange/Set-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md index 460a831c41..5739f8f674 100644 --- a/exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-sitemailboxprovisioningpolicy applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SiteMailboxProvisioningPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-sitemailboxprovisioningpolicy +schema: 2.0.0 +title: Set-SiteMailboxProvisioningPolicy --- # Set-SiteMailboxProvisioningPolicy @@ -68,6 +69,9 @@ This example changes the default provisioning policy named SM\_DefaultPolicy and ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the site mailbox provisioning policy that you want to edit. You can use any value that uniquely identifies the policy. For example: - Name @@ -78,7 +82,6 @@ The Identity parameter specifies the identity of the site mailbox provisioning p Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -88,6 +91,9 @@ Accept wildcard characters: False ``` ### -AliasPrefix + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are: - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified. @@ -97,7 +103,6 @@ The AliasPrefix parameter specifies the custom text prefix to add to the aliases Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -107,6 +112,9 @@ 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`. @@ -116,7 +124,6 @@ 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 @@ -126,6 +133,9 @@ Accept wildcard characters: False ``` ### -DefaultAliasPrefixEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are: - $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`). @@ -137,7 +147,6 @@ The value of this parameter is related to the value of the AliasPrefix parameter Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,13 +156,15 @@ 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 @@ -163,6 +174,9 @@ Accept wildcard characters: False ``` ### -IsDefault + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsDefault switch specifies that the site mailbox provisioning policy is the default policy. You don't need to specify a value with this switch. You can have multiple policies, but only the default policy is followed when users create site mailboxes. @@ -171,7 +185,6 @@ You can have multiple policies, but only the default policy is followed when use Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,6 +194,9 @@ Accept wildcard characters: False ``` ### -IssueWarningQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -201,7 +217,6 @@ The default value is 49 GB. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -211,6 +226,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the site mailbox. Messages larger than the maximum size are rejected. When you enter a value, qualify the value with one of the following units: @@ -228,7 +246,6 @@ A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the val Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,13 +255,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name of the site mailbox provisioning 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -254,6 +273,9 @@ Accept wildcard characters: False ``` ### -ProhibitSendReceiveQuota + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox. A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. When you enter a number, you can qualify it with one of the following units: @@ -274,7 +296,6 @@ The default value is 50 GB. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -284,13 +305,15 @@ 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/exchange/Set-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-SmimeConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md index de3c3c22fa..28d2f0b7da 100644 --- a/exchange/exchange-ps/exchange/Set-SmimeConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-smimeconfig applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-SmimeConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-smimeconfig +schema: 2.0.0 +title: Set-SmimeConfig --- # Set-SmimeConfig @@ -70,13 +71,15 @@ This example sets the S/MIME configuration to allow users the choice of signing ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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 Required: False Position: 1 @@ -86,13 +89,15 @@ Accept wildcard characters: False ``` ### -Confirm + +> 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: (All) Aliases: cf -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -102,6 +107,9 @@ Accept wildcard characters: False ``` ### -OWAAllowUserChoiceOfSigningCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAAllowUserChoiceOfSigningCertificate parameter specifies whether to allow users to select the certificate to use when they digitally sign email messages in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -110,7 +118,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -120,6 +127,9 @@ Accept wildcard characters: False ``` ### -OWAAlwaysEncrypt + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAAlwaysEncrypt parameter specifies whether all outgoing messages are automatically encrypted in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -128,7 +138,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -138,6 +147,9 @@ Accept wildcard characters: False ``` ### -OWAAlwaysSign + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAAlwaysSign parameter specifies whether all outgoing messages are automatically signed in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -146,7 +158,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -156,6 +167,9 @@ Accept wildcard characters: False ``` ### -OWABCCEncryptedEmailForking + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWABCCEncryptedEmailForking parameter specifies how Bcc messages are encrypted in Outlook on the web. Valid values are: - 0: One encrypted message per Bcc recipient. This is the default value. @@ -168,7 +182,6 @@ This setting affects the security and privacy of Outlook on the web. Consult you Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -178,6 +191,9 @@ Accept wildcard characters: False ``` ### -OWACheckCRLOnSend + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWACheckCRLOnSend parameter specifies how the certificate revocation list (CRL) check is enforced when an email message is sent in Outlook on the web. Valid values are: - $true: When the CRL distribution point is inaccessible, Outlook on the web displays a warning dialog box and prevents signed or encrypted messages from being sent. @@ -187,7 +203,6 @@ The OWACheckCRLOnSend parameter specifies how the certificate revocation list (C Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -197,6 +212,9 @@ Accept wildcard characters: False ``` ### -OWAClearSign + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAClearSign parameter specifies how email messages are signed in Outlook on the web. Valid values are: - $true: Digitally signed messages are clear-signed. This is the default value. @@ -208,7 +226,6 @@ Clear-signed messages are larger than opaque-signed messages, but clear-signed m Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -218,13 +235,15 @@ Accept wildcard characters: False ``` ### -OWACopyRecipientHeaders + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + 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, Exchange Online Required: False Position: Named @@ -234,6 +253,9 @@ Accept wildcard characters: False ``` ### -OWACRLConnectionTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWACRLConnectionTimeout parameter specifies the time in milliseconds that Outlook on the web waits while connecting to retrieve a single CRL as part of a certificate validation operation. A valid value is an integer between 0 and 4294967295 (UInt32). The default value is 60000 (60 seconds). @@ -244,7 +266,6 @@ When multiple CRLs in a certificate chain must be retrieved, the time limit that Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -254,6 +275,9 @@ Accept wildcard characters: False ``` ### -OWACRLRetrievalTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWACRLRetrievalTimeout parameter specifies the time in milliseconds that Outlook on the web waits to retrieve all CRLs when validating a certificate. VA valid value is an integer between 0 and 4294967295 (UInt32). The default value is 10000 (10 seconds). @@ -264,7 +288,6 @@ If all the required CRLs are not retrieved before the time limit expires, the op Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -274,6 +297,9 @@ Accept wildcard characters: False ``` ### -OWADisableCRLCheck + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWADisableCRLCheck parameter enables or disables CRL checking in Outlook on the web. Valid values are: - $true: CRL checks are disabled when validating certificates. @@ -285,7 +311,6 @@ Disabling CRL checking can decrease the time that's required to validate the sig Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -295,6 +320,9 @@ Accept wildcard characters: False ``` ### -OWADLExpansionTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWADLExpansionTimeout parameter specifies the time in milliseconds that Outlook on the web waits when sending encrypted messages to members of a distribution group that requires expansion. A valid value is an integer between 0 and 4294967295 (UInt32). The default value is 60000 (60 seconds). If the operation doesn't complete in the time specified by this parameter, the operation fails and the message is not sent. @@ -307,7 +335,6 @@ The timeout value that's specified by this parameter is applied to the expansion Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -317,6 +344,9 @@ Accept wildcard characters: False ``` ### -OWAEncryptionAlgorithms + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAEncryptionAlgorithms parameter specifies a list of symmetric encryption algorithms that are used by Outlook on the web to encrypt messages. Valid values are: - 6601: DES (56-bit) @@ -336,7 +366,6 @@ If the parameter is not specified or is not formatted correctly, Outlook on the Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -346,6 +375,9 @@ Accept wildcard characters: False ``` ### -OWAEncryptTemporaryBuffers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAEncryptTemporaryBuffers parameter specifies whether the Outlook on the web client-side temporary message storage buffers are encrypted. Valid values are: - $true: All client-side temporary buffers that store message data are encrypted using an ephemeral key and the 3DES algorithm. This is the default value. @@ -357,7 +389,6 @@ Disabling encryption of the buffers can increase performance of the Outlook on t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -367,6 +398,9 @@ Accept wildcard characters: False ``` ### -OWAForceSMIMEClientUpgrade + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAForceSMIMEClientUpgrade parameter specifies whether or not users are forced to upgrade an S/MIME control that's older than their current version in Outlook on the web. - $true: Users need to download and install the new control before they can use S/MIME. This is the default value. @@ -376,7 +410,6 @@ The OWAForceSMIMEClientUpgrade parameter specifies whether or not users are forc Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -386,6 +419,9 @@ Accept wildcard characters: False ``` ### -OWAIncludeCertificateChainAndRootCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAIncludeCertificateChainAndRootCertificate parameter specifies whether the certificate chains and root certificates of the signing or encryption certificates are included in the message in Outlook on the web. Valid input for this parameter is $true or $false. The default value is $false. @@ -394,7 +430,6 @@ Valid input for this parameter is $true or $false. The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -404,6 +439,9 @@ Accept wildcard characters: False ``` ### -OWAIncludeCertificateChainWithoutRootCertificate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAIncludeCertificateChainWithoutRootCertificate parameter specifies whether the certificate chains of the signing or encryption certificates are included in messages in Outlook on the web. Valid values are: - $true: Signed or encrypted messages include the full certificate chain, but not the root certificate. @@ -413,7 +451,6 @@ The OWAIncludeCertificateChainWithoutRootCertificate parameter specifies whether Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -423,6 +460,9 @@ Accept wildcard characters: False ``` ### -OWAIncludeSMIMECapabilitiesInMessage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAIncludeSMIMECapabilitiesInMessage parameter specifies whether signed and encrypted messages in Outlook on the web include attributes that describe the supported encryption and signing algorithms. Valid input for this parameter is $true or $false. The default is $false. @@ -433,7 +473,6 @@ Enabling this option increases the size of messages, but may make it easier for Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -443,6 +482,9 @@ Accept wildcard characters: False ``` ### -OWAOnlyUseSmartCard + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAOnlyUseSmartCard parameter specifies whether smartcard-based certificates are required for Outlook on the web message signing and decryption. Valid values are: $true: Smartcard-based certificates for signing and decryption are required when you use Outlook on the web and the S/MIME control. @@ -453,7 +495,6 @@ $false: Smartcard-based certificates for signing and decryption aren't required Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -463,6 +504,9 @@ Accept wildcard characters: False ``` ### -OWASenderCertificateAttributesToDisplay + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWASenderCertificateAttributesToDisplay parameter controls which certificate attributes are displayed when signature verification proceeds despite a mismatch between the sender's email address and the email address in sender's certificate. The parameter accepts a comma-separated list of object identifiers (OIDs). This setting is blank ($null) by default. @@ -471,7 +515,6 @@ The parameter accepts a comma-separated list of object identifiers (OIDs). This Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -481,6 +524,9 @@ Accept wildcard characters: False ``` ### -OWASignedEmailCertificateInclusion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWASignedEmailCertificateInclusion parameter specifies whether the sender's encryption certificate is excluded from a signed email message in Outlook on the web. Valid values are: - $true: Outlook on the web and the S/MIME control include both signing and encrypting certificates with signed email messages. This is the default value. @@ -492,7 +538,6 @@ When you don't include the certificates with signed email messages, the size of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -502,6 +547,9 @@ Accept wildcard characters: False ``` ### -OWASigningAlgorithms + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWASigningAlgorithms parameter specifies the list of symmetric encryption signing algorithms that are used by Outlook on the web to sign messages with the S/MIME control. Valid values are: - 8003: CALG\_MD5 or 128-bit MD5 @@ -522,7 +570,6 @@ If this parameter is not specified or is not formatted correctly, Outlook on the Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -532,6 +579,9 @@ Accept wildcard characters: False ``` ### -OWATripleWrapSignedEncryptedMail + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWATripleWrapSignedEncryptedMail parameter specifies whether signed and encrypted email messages in Outlook on the web are triple-wrapped. Valid values are: - $true: A signed message is encrypted, and then the encrypted message is signed (signed-encrypted-signed). @@ -543,7 +593,6 @@ Triple-wrapped messages offer the highest level of security for messages under t Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -553,6 +602,9 @@ Accept wildcard characters: False ``` ### -OWAUseKeyIdentifier + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAUseKeyIdentifier parameter specifies whether a certificate's key identifier is used to encode the asymmetrically encrypted token in Outlook on the web. Valid input for this parameter is $true or $false. The default is $false. @@ -565,7 +617,6 @@ This parameter causes the use of a certificate's key identifier when encoding th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -575,6 +626,9 @@ Accept wildcard characters: False ``` ### -OWAUseSecondaryProxiesWhenFindingCertificates + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OWAUseSecondaryProxiesWhenFindingCertificates parameter specifies whether alternative proxies are used during the certificate search in Outlook on the web. Valid input for this parameter is $true or $false. The default is $true. @@ -585,7 +639,6 @@ Outlook on the web attempts to find the correct certificate for a recipient when Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -595,6 +648,9 @@ Accept wildcard characters: False ``` ### -NoSignOnReply + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter applies only to new Outlook for Windows. It doesn't apply to Outlook on the web. @@ -608,7 +664,6 @@ The NoSignOnReply parameter specifies whether S/MIME signatures are inherited in Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -618,6 +673,9 @@ Accept wildcard characters: False ``` ### -SMIMECertificateIssuingCA + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SMIMECertificateIssuingCA parameter specifies the serialized certificate store (SST) that contains the Certificate Authority (CA) signing and intermediate certificate 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`). @@ -628,7 +686,6 @@ Each certificate is checked, and if any certificates are expired, the operation Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -638,13 +695,15 @@ 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/exchange/Set-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md index ac5377657b..b12e6d0082 100644 --- a/exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-supervisoryreviewpolicyv2 applicable: Security & Compliance -title: Set-SupervisoryReviewPolicyV2 -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-supervisoryreviewpolicyv2 +schema: 2.0.0 +title: Set-SupervisoryReviewPolicyV2 --- # Set-SupervisoryReviewPolicyV2 @@ -53,6 +54,9 @@ This example adds reviewers and updates the comment for the supervisory review p ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the supervisory review policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -63,7 +67,6 @@ The Identity parameter specifies the supervisory review policy that you want to Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -73,13 +76,15 @@ Accept wildcard characters: False ``` ### -AddReviewers + +> Applicable: Security & Compliance + The AddReviewers parameter specifies the SMTP addresses of reviewers to add to the supervisory review policy. You can specify multiple email addresses separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -89,13 +94,15 @@ 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 @@ -105,6 +112,9 @@ 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,7 +124,6 @@ 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 @@ -124,13 +133,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Security & Compliance + {{ Fill Enabled Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -140,6 +151,9 @@ 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. @@ -148,7 +162,6 @@ 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 @@ -158,13 +171,15 @@ Accept wildcard characters: False ``` ### -PolicyRBACScopes + +> Applicable: Security & Compliance + {{ Fill PolicyRBACScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All)) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -174,13 +189,15 @@ Accept wildcard characters: False ``` ### -PolicyTemplate + +> Applicable: Security & Compliance + {{ Fill PolicyTemplate Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -190,13 +207,15 @@ Accept wildcard characters: False ``` ### -PreservationPeriodInDays + +> Applicable: Security & Compliance + {{ Fill PreservationPeriodInDays Description }} ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -206,13 +225,15 @@ Accept wildcard characters: False ``` ### -RemoveReviewers + +> Applicable: Security & Compliance + The RemoveReviewers parameter specifies the SMTP addresses of reviewers to remove from the supervisory review policy. You can specify multiple email addresses separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -222,13 +243,15 @@ Accept wildcard characters: False ``` ### -RetentionPeriodInDays + +> Applicable: Security & Compliance + The RetentionPeriodInDays parameter specifies the number of days that the messages will be retained for review. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -238,6 +261,9 @@ Accept wildcard characters: False ``` ### -Reviewers + +> Applicable: Security & Compliance + The Reviewers parameter specifies the SMTP addresses of the reviewers for the supervisory review policy. You can specify multiple email addresses separated by commas. The reviewers that you specify with this parameter replace the existing reviewers. To selectively add or remove reviewers, use the AddReviewers and RemoveReviewers parameters. @@ -246,7 +272,6 @@ The reviewers that you specify with this parameter replace the existing reviewer Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -256,13 +281,15 @@ Accept wildcard characters: False ``` ### -UserReportingWorkloads + +> Applicable: Security & Compliance + {{ Fill UserReportingWorkloads Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -272,13 +299,15 @@ 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/exchange/Set-SupervisoryReviewRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewRule.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewRule.md index 3b3c0210d9..71a2cb1c47 100644 --- a/exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-supervisoryreviewrule applicable: Security & Compliance -title: Set-SupervisoryReviewRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-supervisoryreviewrule +schema: 2.0.0 +title: Set-SupervisoryReviewRule --- # Set-SupervisoryReviewRule @@ -65,6 +66,9 @@ This example modifies the existing rule named EU Brokers Rule with the following ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the supervisory review rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -75,7 +79,6 @@ The Identity parameter specifies the supervisory review rule that you want to mo Type: ComplianceRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -85,13 +88,15 @@ Accept wildcard characters: False ``` ### -AdvancedRule + +> Applicable: Security & Compliance + {{ Fill AdvancedRule Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -101,13 +106,15 @@ Accept wildcard characters: False ``` ### -CcsiDataModelOperator + +> Applicable: Security & Compliance + {{ Fill CcsiDataModelOperator Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -117,6 +124,9 @@ Accept wildcard characters: False ``` ### -Condition + +> Applicable: Security & Compliance + The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax: - User or group communications to supervise: `"((Reviewee:) -OR (Reviewee:)...)"`. Exceptions use the syntax `"(NOT((Reviewee:) -OR (Reviewee:)...))"`. @@ -133,7 +143,6 @@ The Condition parameter specifies the conditions and exceptions for the rule. Th Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -143,6 +152,9 @@ 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`. @@ -152,7 +164,6 @@ 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 @@ -162,13 +173,15 @@ Accept wildcard characters: False ``` ### -ContentContainsSensitiveInformation + +> Applicable: Security & Compliance + {{ Fill ContentContainsSensitiveInformation Description }} ```yaml Type: PswsHashtable[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -178,13 +191,15 @@ Accept wildcard characters: False ``` ### -ContentMatchesDataModel + +> Applicable: Security & Compliance + {{ Fill ContentMatchesDataModel Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -194,13 +209,15 @@ Accept wildcard characters: False ``` ### -ContentSources + +> Applicable: Security & Compliance + {{ Fill ContentSources Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -210,13 +227,15 @@ Accept wildcard characters: False ``` ### -DayXInsights + +> Applicable: Security & Compliance + {{ Fill DayXInsights Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -226,13 +245,15 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom + +> Applicable: Security & Compliance + {{ Fill ExceptIfFrom Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -242,13 +263,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfRecipientDomainIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -258,13 +281,15 @@ Accept wildcard characters: False ``` ### -ExceptIfRevieweeIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfRevieweeIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -274,13 +299,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs + +> Applicable: Security & Compliance + {{ Fill ExceptIfSenderDomainIs Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -290,13 +317,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Security & Compliance + {{ Fill ExceptIfSentTo Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -306,13 +335,15 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords + +> Applicable: Security & Compliance + {{ Fill ExceptIfSubjectOrBodyContainsWords Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -322,13 +353,15 @@ Accept wildcard characters: False ``` ### -From + +> Applicable: Security & Compliance + {{ Fill From Description }} ```yaml Type: MultiValuedProperty Parameter Sets: Default Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -338,13 +371,15 @@ Accept wildcard characters: False ``` ### -IncludeAdaptiveScopes + +> Applicable: Security & Compliance + {{ Fill IncludeAdaptiveScopes Description }} ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -354,13 +389,15 @@ Accept wildcard characters: False ``` ### -InPurviewFilter + +> Applicable: Security & Compliance + {{ Fill InPurviewFilter Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -370,13 +407,15 @@ Accept wildcard characters: False ``` ### -Ocr + +> Applicable: Security & Compliance + {{ Fill Ocr Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -386,13 +425,15 @@ Accept wildcard characters: False ``` ### -PolicyRBACScopes + +> Applicable: Security & Compliance + {{ Fill PolicyRBACScopes Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -402,13 +443,15 @@ Accept wildcard characters: False ``` ### -SamplingRate + +> Applicable: Security & Compliance + The SamplingRate parameter specifies the percentage of communications for review. If you want reviewers to review all detected items, use the value 100. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -418,13 +461,15 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Security & Compliance + {{ Fill SentTo Description }} ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -434,13 +479,15 @@ 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/exchange/Set-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-SweepRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md index 184a02c1af..32df7589fb 100644 --- a/exchange/exchange-ps/exchange/Set-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-sweeprule applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-SweepRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-sweeprule +schema: 2.0.0 +title: Set-SweepRule --- # Set-SweepRule @@ -55,6 +56,9 @@ This example modifies the existing rule that has the rule ID value x2hlsdpGmUifj ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the Sweep rule that you want to modify. You can use any value that uniquely identifies the rule. For example: - RuleId property (for example, x2hlsdpGmUifjFgxxGIOJw==). @@ -67,7 +71,6 @@ You can get these identity values by using the Get-SweepRule cmdlet. Type: SweepRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -77,6 +80,9 @@ 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,7 +92,6 @@ 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 @@ -96,6 +101,9 @@ Accept wildcard characters: False ``` ### -DestinationFolder + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The DestinationFolder parameter specifies an action for the Sweep rule that moves messages to the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: @@ -117,7 +125,6 @@ Example values for this parameter are `john@contoso.com:\Unimportant` or `John:\ Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -127,6 +134,9 @@ 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. @@ -135,7 +145,6 @@ 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 @@ -145,13 +154,15 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -161,6 +172,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFlagged + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExceptIfFlagged parameter specifies an exception for the Sweep rule that looks messages with a message flag applied. Valid values are: @@ -186,7 +200,6 @@ The typical message flag values are: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -196,6 +209,9 @@ Accept wildcard characters: False ``` ### -ExceptIfPinned + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PinMessage parameter specifies an exception for the Sweep rule that looks for pinned messages. Valid values are: @@ -207,7 +223,6 @@ The PinMessage parameter specifies an exception for the Sweep rule that looks fo Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -217,6 +232,9 @@ Accept wildcard characters: False ``` ### -KeepForDays + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The KeepForDays parameter specifies an action for the Sweep rule that specifies the number of days to keep messages that match the conditions of the rule. After the number of days have passed, the messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder). You can't use this parameter with the KeepLatest parameter, and the Sweep rule must contain a KeepForDays or KeepLatest parameter value. @@ -225,7 +243,6 @@ You can't use this parameter with the KeepLatest parameter, and the Sweep rule m Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -235,6 +252,9 @@ Accept wildcard characters: False ``` ### -KeepLatest + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The KeepLatest parameter specifies an action for the Sweep rule that specifies the number of messages to keep that match the conditions of the rule. After the number of messages is exceeded, the oldest messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder). You can't use this parameter with the KeepForDays parameter, and the Sweep rule must contain a KeepForDays or KeepLatest parameter value. @@ -243,7 +263,6 @@ You can't use this parameter with the KeepForDays parameter, and the Sweep rule Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -253,6 +272,9 @@ 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 modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -270,7 +292,6 @@ The Mailbox parameter specifies the mailbox that contains the rule you want to m Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -280,13 +301,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Name parameter specifies the name of the Sweep rule. 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 @@ -296,6 +319,9 @@ Accept wildcard characters: False ``` ### -Provider + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Provider parameter specifies the provider for the Sweep rule. If the value contains spaces, enclose the value in quotation marks. For Sweep rules that you create in Outlook on the web, the default value is Exchange16. @@ -304,7 +330,6 @@ For Sweep rules that you create in Outlook on the web, the default value is Exch Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -314,6 +339,9 @@ Accept wildcard characters: False ``` ### -Sender + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Sender parameter specifies a condition for the Sweep rule that looks for the specified sender in messages. For internal senders, you can use any value that uniquely identifies the sender. For example: - Name @@ -329,7 +357,6 @@ For external senders, use their email address. Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -339,6 +366,9 @@ Accept wildcard characters: False ``` ### -SourceFolder + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SourceFolder parameter specifies a condition for the Sweep rule that looks for messages in the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`. For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example: @@ -360,7 +390,6 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In Type: MailboxFolderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -370,6 +399,9 @@ Accept wildcard characters: False ``` ### -SystemCategory + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SystemCategory parameter specifies a condition for the sweep rule that looks for messages with the specified system category. System categories are available to all mailboxes in the organization. Valid values are: - NotDefined @@ -401,7 +433,6 @@ The SystemCategory parameter specifies a condition for the sweep rule that looks Type: SystemCategoryType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -411,13 +442,15 @@ 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/exchange/Set-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-SystemMessage.md rename to exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md index 0cb1bfebec..607f1c6cfe 100644 --- a/exchange/exchange-ps/exchange/Set-SystemMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-systemmessage applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-SystemMessage -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-systemmessage +schema: 2.0.0 +title: Set-SystemMessage --- # Set-SystemMessage @@ -53,6 +54,9 @@ This example modifies the text of the custom English WarningMailbox quota messag ## 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 modify. You can use any value that uniquely identifies the system message. For example: - Identity @@ -108,7 +112,6 @@ Maximum number of levels (depth) in a mailbox folder: Type: SystemMessageIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -118,6 +121,9 @@ 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`. @@ -127,7 +133,6 @@ 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 @@ -137,6 +142,9 @@ 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. @@ -145,7 +153,6 @@ 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 @@ -155,13 +162,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies a descriptive name for the system message. 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 Required: False Position: Named @@ -171,6 +180,9 @@ Accept wildcard characters: False ``` ### -Original + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Original switch specifies whether to stop using the custom system message and start using the default system message. You don't need to specify a value with this switch. This switch is useful when you want to preserve the custom system message without using it. @@ -181,7 +193,6 @@ This switch only works on custom system messages for default (not new) enhanced Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,6 +202,9 @@ Accept wildcard characters: False ``` ### -Text + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Text parameter specifies the text in the custom system message. The text should explain why the system message was sent and any actions that the user should take. This parameter can contain text and HTML tags. The maximum length is 512 characters (which includes all text and HTML tags). @@ -218,7 +232,6 @@ Here's an example value for this parameter that uses HTML tags and special chara Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -228,13 +241,15 @@ 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/exchange/Set-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md index 65370a81b9..9818faa14f 100644 --- a/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-teamsprotectionpolicy applicable: Exchange Online -title: Set-TeamsProtectionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-teamsprotectionpolicy +schema: 2.0.0 +title: Set-TeamsProtectionPolicy --- # Set-TeamsProtectionPolicy @@ -46,13 +47,15 @@ This example changes the quarantine policy that's used for high confidence phish ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Teams protection policy that you want to modify. 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: True Position: 1 @@ -62,13 +65,15 @@ Accept wildcard characters: False ``` ### -AdminDisplayName + +> Applicable: Exchange Online + 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 Required: False Position: Named @@ -78,6 +83,9 @@ 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`. @@ -87,7 +95,6 @@ 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 @@ -97,6 +104,9 @@ Accept wildcard characters: False ``` ### -HighConfidencePhishQuarantineTag + +> Applicable: Exchange Online + The HighConfidencePhishQuarantineTag parameter specifies the quarantine policy that's used for messages that are quarantined as high confidence phishing by ZAP for Teams. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -111,7 +121,6 @@ If you don't use this parameter, the default quarantine policy that's used is na Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -121,6 +130,9 @@ Accept wildcard characters: False ``` ### -MalwareQuarantineTag + +> Applicable: Exchange Online + The MalwareQuarantineTag parameter specifies the quarantine policy that's used for messages that are quarantined as malware by ZAP for Teams. You can use any value that uniquely identifies the quarantine policy. For example: - Name @@ -135,7 +147,6 @@ If you don't use this parameter, the default quarantine policy that's used is na Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -145,14 +156,18 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online + + +> 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 -Applicable: Exchange Online Required: False Position: Named @@ -162,6 +177,9 @@ Accept wildcard characters: False ``` ### -ZapEnabled + +> Applicable: Exchange Online + The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are: - $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value. @@ -171,7 +189,6 @@ The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md similarity index 97% rename from exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md index 859d7e7ee7..10be482392 100644 --- a/exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-teamsprotectionpolicyrule applicable: Exchange Online -title: Set-TeamsProtectionPolicyRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-teamsprotectionpolicyrule +schema: 2.0.0 +title: Set-TeamsProtectionPolicyRule --- # Set-TeamsProtectionPolicyRule @@ -49,13 +50,15 @@ This example modifies the existing Teams protection policy rule by excluding rec ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the Teams protection policy rule that you want to modify. 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: True Position: 1 @@ -65,13 +68,15 @@ 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 @@ -81,6 +86,9 @@ 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`. @@ -90,7 +98,6 @@ 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 @@ -100,6 +107,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Online + The ExceptIfRecipientDomainIs parameter specifies an exception to ZAP for Teams protection that looks for recipients of Teams messages with email addresses in the specified domains. To replace all existing domains with the values you specify, use the following syntax: `Domain1,Domain2,...DomainN`. @@ -136,7 +146,6 @@ To empty the list, use the value $null for this parameter. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -146,6 +155,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Online + The ExceptIfSentTo parameter specifies an exception to ZAP for Teams protection that looks for recipients of Teams messages. You can use any value that uniquely identifies the recipient. For example: - Name @@ -189,7 +201,6 @@ To empty the list, use the value $null for this parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -199,6 +210,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Online + The ExceptIfSentToMemberOf parameter specifies an exception to ZAP for Teams protection that looks for Teams messages sent to members of distribution groups or mail-enabled security groups. You can use any value that uniquely identifies the group. For example: - Name @@ -242,7 +256,6 @@ To empty the list, use the value $null for this parameter. Type: RecipientIdParameter[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -252,13 +265,15 @@ 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/exchange/Set-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md index 797710eedf..8000263224 100644 --- a/exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-tenantallowblocklistitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Set-TenantAllowBlockListItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-tenantallowblocklistitems +schema: 2.0.0 +title: Set-TenantAllowBlockListItems --- # Set-TenantAllowBlockListItems @@ -72,6 +73,9 @@ This example changes the expiration date of the URL allow entry for the specifie ## PARAMETERS ### -Entries + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Entries parameter specifies the entries that you want to modify based on the ListType parameter value. Valid values are: - FileHash: The exact SHA256 file hash value. @@ -88,7 +92,6 @@ You can't use this parameter with the Ids parameter. ```yaml Type: String[] Parameter Sets: Entries -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -98,6 +101,9 @@ Accept wildcard characters: False ``` ### -Ids + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Ids parameter specifies the entries that you want to modify. This value is shown in the Identity property in the output of the Get-TenantAllowBlockListItems cmdlet. An example value for this parameter is `RgAAAAAI8gSyI_NmQqzeh-HXJBywBwCqfQNJY8hBTbdlKFkv6BcUAAAl_QCZAACqfQNJY8hBTbdlKFkv6BcUAAAl_oSPAAAA0`. @@ -108,7 +114,6 @@ You can't use this parameter with the Entries parameter. Type: String[] Parameter Sets: Ids Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -118,6 +123,9 @@ Accept wildcard characters: False ``` ### -ListType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListType parameter specifies the type of entry that you want to modify. Valid values are: - FileHash @@ -131,7 +139,6 @@ Use the Entries or Ids parameter with this parameter to identify the entry itsel Type: ListType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -141,6 +148,9 @@ Accept wildcard characters: False ``` ### -NoExpiration + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The NoExpiration switch specifies that the entry should never expire. You don't need to specify a value with this switch. This switch is available to use with the following types of entries: @@ -155,7 +165,6 @@ You can't use this switch with the ExpirationDate parameter. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -165,13 +174,15 @@ Accept wildcard characters: False ``` ### -Allow + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Allow switch specifies that you're modifying an allow entry. 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 @@ -181,13 +192,15 @@ Accept wildcard characters: False ``` ### -Block + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Block switch specifies that you're modifying a block entry. 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 @@ -197,6 +210,9 @@ 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: @@ -210,7 +226,6 @@ You can't use this parameter with the NoExpiration or RemoveAfter parameters. Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -220,6 +235,9 @@ Accept wildcard characters: False ``` ### -ListSubType + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The ListSubType parameter further specifies the entry that you want to modify. Valid values are: - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). @@ -229,7 +247,6 @@ The ListSubType parameter further specifies the entry that you want to modify. V Type: ListSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -239,13 +256,15 @@ Accept wildcard characters: False ``` ### -Notes + +> Applicable: Exchange Online, Security & Compliance, 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 Online, Security & Compliance, Exchange Online Protection Required: False Position: Named @@ -255,6 +274,9 @@ 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. @@ -263,7 +285,6 @@ 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 @@ -273,6 +294,9 @@ Accept wildcard characters: False ``` ### -RemoveAfter + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The RemoveAfter parameter enables the **Remove on** \> **45 days after last used date** feature for an allow entry. The LastUsedDate property is populated when the bad entity in the allow entry is encountered by the filtering system during mail flow or time of click. The allow entry is kept for 45 days after the filtering system determines that the entity is clean. The only valid value for this parameter is 45. @@ -285,7 +309,6 @@ To change the allow entry to a static expiration date/time value that doesn't de Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md index e410aa39ca..38fa5dfa9f 100644 --- a/exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-tenantallowblocklistspoofitems applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Set-TenantAllowBlockListSpoofItems -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-tenantallowblocklistspoofitems +schema: 2.0.0 +title: Set-TenantAllowBlockListSpoofItems --- # Set-TenantAllowBlockListSpoofItems @@ -53,13 +54,15 @@ This example removes all external spoof pairs from the Tenant Allow/Block List. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Identity parameter uses the value Default. ```yaml Type: HostedConnectionFilterPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: 0 @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -Action + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Action parameter specifies whether this entry is an allow or block spoofed sender entry. Valid values are: - Allow @@ -78,7 +84,6 @@ The Action parameter specifies whether this entry is an allow or block spoofed s Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -88,13 +93,15 @@ Accept wildcard characters: False ``` ### -Ids + +> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection + The Ids parameter specifies the spoof pair that you want to modify. A valid value is the Identity property value from the output of the Get-TenantAllowBlockListSpoofItems cmdlet. You can specify multiple values separated by commas. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection Required: True Position: Named @@ -104,6 +111,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: 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`. @@ -113,7 +123,6 @@ 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 @@ -123,13 +132,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Online, Security & Compliance, 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, Security & Compliance, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-TextMessagingAccount.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md index 57563a2af1..bd688891db 100644 --- a/exchange/exchange-ps/exchange/Set-TextMessagingAccount.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-textmessagingaccount applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-TextMessagingAccount -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-textmessagingaccount +schema: 2.0.0 +title: Set-TextMessagingAccount --- # Set-TextMessagingAccount @@ -58,6 +59,9 @@ This example sets the region, mobile operator and notification phone number for ## 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 use any value that uniquely identifies the mailbox. For example: - Name @@ -75,7 +79,6 @@ The Identity parameter specifies the target mailbox. You can use any value that 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,6 +88,9 @@ 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`. @@ -94,7 +100,6 @@ 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 @@ -104,6 +109,9 @@ Accept wildcard characters: False ``` ### -CountryRegionId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The CountryRegionId parameter specifies the country/region that your mobile phone is registered in. Although this parameter accepts any valid ISO 3166-1 two-letter country code value (for example, AU for Australia), the following values correspond to the country/region selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App): - US @@ -116,7 +124,6 @@ A reference for two-letter country codes is available at [Country Codes List](ht Type: RegionInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -126,6 +133,9 @@ 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,7 +144,6 @@ 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 @@ -144,6 +153,9 @@ 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: @@ -155,7 +167,6 @@ 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 @@ -165,6 +176,9 @@ Accept wildcard characters: False ``` ### -MobileOperatorId + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MobileOperatorId parameter specifies the mobile operator (carrier) for your phone. Although this parameter accepts any random number, the following values correspond to the country/region and mobile operator selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App): United States: @@ -187,7 +201,6 @@ Romania: 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 @@ -197,13 +210,15 @@ Accept wildcard characters: False ``` ### -NotificationPhoneNumber + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The NotificationPhoneNumber parameter specifies the telephone number to use for your text messaging notifications. This parameter uses the E.164 format: `+` (for example, `+15551234567`). ```yaml Type: E164Number Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -213,13 +228,15 @@ 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/exchange/Set-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md index aec6333325..1a8ac6e193 100644 --- a/exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-throttlingpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ThrottlingPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-throttlingpolicy +schema: 2.0.0 +title: Set-ThrottlingPolicy --- # Set-ThrottlingPolicy @@ -207,13 +208,15 @@ This example modifies a throttling policy so that it restricts a user to be able ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter uniquely identifies the throttling policy that you want to modify values for. The name you use is the name of the throttling policy object in Active Directory. ```yaml Type: ThrottlingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -223,13 +226,15 @@ Accept wildcard characters: False ``` ### -AnonymousCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousCutoffBalance parameter specifies the resource consumption limits for an anonymous user before the user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -239,13 +244,15 @@ Accept wildcard characters: False ``` ### -AnonymousMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousMaxBurst parameter specifies the amount of time that an anonymous user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,13 +262,15 @@ Accept wildcard characters: False ``` ### -AnonymousMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousMaxConcurrency parameter specifies how many anonymous connections can be made to a user's calendar data at the same time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If anonymous users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The AnonymousMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 1. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -271,6 +280,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInAD parameter specifies the percentage of a minute that anonymous users can spend executing LDAP requests (PercentTimeInAD) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -279,7 +291,6 @@ The AnonymousPercentTimeInAD parameter specifies the percentage of a minute that Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -289,6 +300,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInCAS parameter specifies the percentage of a minute that anonymous users can spend executing CAS code (PercentTimeInCAS) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -297,7 +311,6 @@ The AnonymousPercentTimeInCAS parameter specifies the percentage of a minute tha Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -307,6 +320,9 @@ Accept wildcard characters: False ``` ### -AnonymousPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The AnonymousPercentTimeInMailboxRPC parameter specifies the percentage of a minute that anonymous users can spend executing mailbox RPC requests (PercentTimeInMailboxRPC) to a user's calendar data. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -315,7 +331,6 @@ The AnonymousPercentTimeInMailboxRPC parameter specifies the percentage of a min Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -325,13 +340,15 @@ Accept wildcard characters: False ``` ### -AnonymousRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AnonymousRechargeRate parameter specifies the rate at which an anonymous user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -341,13 +358,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -357,13 +376,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -373,13 +394,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -389,13 +412,15 @@ Accept wildcard characters: False ``` ### -BookingSelfServiceRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -405,13 +430,15 @@ Accept wildcard characters: False ``` ### -ComplianceMaxExpansionDGRecipients + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ComplianceMaxExpansionDGRecipients parameter specifies the maximum number of recipients to expand in distribution groups when a discovery search is looking for a specified recipient. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -421,13 +448,15 @@ Accept wildcard characters: False ``` ### -ComplianceMaxExpansionNestedDGs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ComplianceMaxExpansionNestedDGs parameter specifies the maximum number of nested distribution groups to expand when a discovery search is looking for a specified recipient. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -437,6 +466,9 @@ 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`. @@ -446,7 +478,6 @@ 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 @@ -456,13 +487,15 @@ Accept wildcard characters: False ``` ### -ConsensusCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -472,13 +505,15 @@ Accept wildcard characters: False ``` ### -ConsensusMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -488,13 +523,15 @@ Accept wildcard characters: False ``` ### -ConsensusMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -504,13 +541,15 @@ Accept wildcard characters: False ``` ### -ConsensusRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -520,13 +559,15 @@ Accept wildcard characters: False ``` ### -CpaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaCutoffBalance parameter specifies the resource consumption limits for a cross-premises user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -536,13 +577,15 @@ Accept wildcard characters: False ``` ### -CpaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaMaxBurst parameter specifies the amount of time that a cross-premises user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -552,13 +595,15 @@ Accept wildcard characters: False ``` ### -CPAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaMaxConcurrency parameter specifies how many concurrent connections a cross-premises user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The CpaMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -568,13 +613,15 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + The CPAPercentTimeInCAS parameter specifies the percentage of a minute that a cross-premises user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -584,6 +631,9 @@ Accept wildcard characters: False ``` ### -CPAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CPAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that a cross-premises user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -592,7 +642,6 @@ The CPAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -602,13 +651,15 @@ Accept wildcard characters: False ``` ### -CpaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CpaRechargeRate parameter specifies the rate at which a cross premises user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -618,6 +669,9 @@ Accept wildcard characters: False ``` ### -CPUStartPercent + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The CPUStartPercent parameter specifies the per-process CPU percentage at which users governed by this policy begin to be backed off. Valid values are from 0 through 100. Use $null to turn off CPU percentage-based throttling for this policy. @@ -626,7 +680,6 @@ The CPUStartPercent parameter specifies the per-process CPU percentage at which Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -636,13 +689,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. To modify the discovery throttling parameters, create a new policy and name it "DiscoveryThrottlingPolicy". ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -652,13 +707,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxKeywords parameter specifies the maximum number of keywords that a user can include in a discovery search. For more information, see [Search-Mailbox](https://learn.microsoft.com/powershell/module/exchange/search-mailbox). ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -668,13 +725,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxKeywordsPerPage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxKeywordsPerPage parameter specifies the number of keywords for which to show statistics on a single page in the EAC. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -684,13 +743,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxMailboxes parameter specifies the maximum number of source mailboxes that a user can include in a discovery search. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -700,13 +761,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxPreviewSearchMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxPreviewSearchMailboxes parameter specifies the maximum number of mailboxes that a user can include in eDiscovery Search Preview. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -716,13 +779,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxRefinerResults + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't used and will be removed. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -732,13 +797,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxSearchQueueDepth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxSearchQueueDepth parameter specifies the maximum number of concurrent discovery search threads that can be active at the same time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -748,13 +815,15 @@ Accept wildcard characters: False ``` ### -DiscoveryMaxStatsSearchMailboxes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryMaxStatsSearchMailboxes parameter specifies the maximum number of mailboxes that a user can search in an In-Place eDiscovery search without being able to view the statistics. When the number of mailboxes configured with the DiscoveryMaxStatsSearchMailboxes parameter is exceeded, the user must copy the search results to a discovery mailbox to view the statistics for the discovery search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery). ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -764,13 +833,15 @@ Accept wildcard characters: False ``` ### -DiscoveryPreviewSearchResultsPageSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoveryPreviewSearchResultsPageSize parameter specifies the number of messages displayed on a single page in eDiscovery Search Preview. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -780,13 +851,15 @@ Accept wildcard characters: False ``` ### -DiscoverySearchTimeoutPeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -796,6 +869,9 @@ 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. @@ -804,7 +880,6 @@ 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 @@ -814,13 +889,15 @@ Accept wildcard characters: False ``` ### -EasCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasCutoffBalance parameter specifies the resource consumption limits for an Exchange ActiveSync user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -830,13 +907,15 @@ Accept wildcard characters: False ``` ### -EasMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxBurst parameter specifies the amount of time that an Exchange ActiveSync user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -846,13 +925,15 @@ Accept wildcard characters: False ``` ### -EASMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxConcurrency parameter specifies how many concurrent connections an Exchange ActiveSync user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EasMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -862,13 +943,15 @@ Accept wildcard characters: False ``` ### -EASMaxDeviceDeletesPerMonth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxDeviceDeletesPerMonth parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can delete per month. By default, each user can delete a maximum of 20 partnerships per calendar month. When the limit is reached, the partnership deletion attempt fails and an error message is displayed to the user. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -878,13 +961,15 @@ Accept wildcard characters: False ``` ### -EASMaxDevices + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxDevices parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can have at one time. By default, each user can create 100 Exchange ActiveSync partnerships with their Exchange account. After users exceed the limit, they must delete one of their existing partnerships before they can create any more new partnerships. An email error message describing the limitation is sent to the user when the limit is exceeded. Additionally, an event is logged in the Application log when a user exceeds the limit. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -894,13 +979,15 @@ Accept wildcard characters: False ``` ### -EasMaxInactivityForDeviceCleanup + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -910,6 +997,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInAD parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -918,7 +1008,6 @@ The EASPercentTimeInAD parameter specifies the percentage of a minute that an Ex Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -928,6 +1017,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInCAS parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -936,7 +1028,6 @@ The EASPercentTimeInCAS parameter specifies the percentage of a minute that an E Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -946,6 +1037,9 @@ Accept wildcard characters: False ``` ### -EASPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EASPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Exchange ActiveSync user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -954,7 +1048,6 @@ The EASPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -964,13 +1057,15 @@ Accept wildcard characters: False ``` ### -EasRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EasRechargeRate parameter specifies the rate at which an Exchange ActiveSync user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -980,13 +1075,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -996,13 +1093,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1012,13 +1111,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1028,13 +1129,15 @@ Accept wildcard characters: False ``` ### -EncryptionRecipientRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1044,13 +1147,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1060,13 +1165,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1076,13 +1183,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1092,13 +1201,15 @@ Accept wildcard characters: False ``` ### -EncryptionSenderRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1108,13 +1219,15 @@ Accept wildcard characters: False ``` ### -EwsCostThreshold + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The EwsCostThreshold parameter specifies the cost threshold for Exchange Web Services users. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1124,13 +1237,15 @@ Accept wildcard characters: False ``` ### -EwsCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsCutoffBalance parameter specifies the resource consumption limits for an Exchange Web Services user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1140,13 +1255,15 @@ Accept wildcard characters: False ``` ### -EwsMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxBurst parameter specifies the amount of time that an Exchange Web Services user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1156,6 +1273,9 @@ Accept wildcard characters: False ``` ### -EWSFastSearchTimeoutInSeconds + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSFastSearchTimeoutInSeconds parameter specifies the amount of time that searches made using Exchange Web Services continue before they time out. If the search takes more than the time indicated by the policy value, the search stops and an error is returned. The default value of this setting is 60 seconds. @@ -1164,7 +1284,6 @@ The EWSFastSearchTimeoutInSeconds parameter specifies the amount of time that se Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1174,6 +1293,9 @@ Accept wildcard characters: False ``` ### -EWSFindCountLimit + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSFindCountLimit parameter specifies the maximum result size of FindItem or FindFolder calls that can exist in memory on the Client Access server at the same time for this user in this current process. If an attempt is made to find more items or folders than your policy limit allows, an error is returned. However, the limit isn't strictly enforced if the call is made within the context of an indexed page view. Specifically, in this scenario, the search results are truncated to include the number of items and folders that fit within the policy limit. You can then continue paging into your results set via further FindItem or FindFolder calls. @@ -1182,7 +1304,6 @@ The EWSFindCountLimit parameter specifies the maximum result size of FindItem or Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1192,13 +1313,15 @@ Accept wildcard characters: False ``` ### -EWSMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxConcurrency parameter specifies how many concurrent connections an Exchange Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EwsMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1208,13 +1331,15 @@ Accept wildcard characters: False ``` ### -EWSMaxSubscriptions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsMaxSubscriptions parameter specifies the maximum number of active push and pull subscriptions that an Exchange Web Services user can have on a specified Exchange server at the same time. If a user tries to create more subscriptions than the configured maximum, the subscription fails, and an event is logged in Event Viewer. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1224,6 +1349,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInAD parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1232,7 +1360,6 @@ The EWSPercentTimeInAD parameter specifies the percentage of a minute that an Ex Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1242,6 +1369,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInCAS parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1250,7 +1380,6 @@ The EWSPercentTimeInCAS parameter specifies the percentage of a minute that an E Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1260,6 +1389,9 @@ Accept wildcard characters: False ``` ### -EWSPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The EWSPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Exchange Web Services user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1268,7 +1400,6 @@ The EWSPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1278,13 +1409,15 @@ Accept wildcard characters: False ``` ### -EwsRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EwsRechargeRate parameter specifies the rate at which an Exchange Web Services user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1294,6 +1427,9 @@ Accept wildcard characters: False ``` ### -ExchangeMaxCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExchangeMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is slowed down. The value specified by this parameter should be less than the value specified by the PowerShellMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. We recommend that you set values for both parameters at the same time. @@ -1302,7 +1438,6 @@ The time period used for this limit is specified by the PowerShellMaxCmdletsTime Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1312,6 +1447,9 @@ 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. @@ -1320,7 +1458,6 @@ 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 @@ -1330,13 +1467,15 @@ Accept wildcard characters: False ``` ### -ForwardeeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForwardeeLimit parameter specifies the limits for the number of recipients that can be configured in Inbox Rules when using the forward or redirect action. This parameter doesn't limit the number of messages that can be forwarded or redirected to the recipients that are configured. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1346,13 +1485,15 @@ Accept wildcard characters: False ``` ### -ImapCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapCutoffBalance parameter specifies the resource consumption limits for an IMAP user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1362,13 +1503,15 @@ Accept wildcard characters: False ``` ### -ImapMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapMaxBurst parameter specifies the amount of time that an IMAP user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1378,13 +1521,15 @@ Accept wildcard characters: False ``` ### -IMAPMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapMaxConcurrency parameter specifies how many concurrent connections an IMAP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The ImapMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1394,6 +1539,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInAD parameter specifies the percentage of a minute that an IMAP user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1402,7 +1550,6 @@ The IMAPPercentTimeInAD parameter specifies the percentage of a minute that an I Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1412,6 +1559,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInCAS parameter specifies the percentage of a minute that an IMAP user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1420,7 +1570,6 @@ The IMAPPercentTimeInCAS parameter specifies the percentage of a minute that an Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1430,6 +1579,9 @@ Accept wildcard characters: False ``` ### -IMAPPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The IMAPPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an IMAP user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1438,7 +1590,6 @@ The IMAPPercentTimeInMailboxRPC parameter specifies the percentage of a minute t Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1448,13 +1599,15 @@ Accept wildcard characters: False ``` ### -ImapRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ImapRechargeRate parameter specifies the rate at which the IMAP user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1464,6 +1617,9 @@ Accept wildcard characters: False ``` ### -IsServiceAccount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IsServiceAccount switch specifies that the user accounts associated with this policy are moderated by per-user thresholds and the health of system resources (for example, overall CPU usage). You don't need to specify a value with this switch. You might want to use this switch if you intend to associate this policy with user accounts that require higher throttling limits (for example, service accounts that perform IMAP mailbox migrations or nightly Windows PowerShell tasks). @@ -1474,7 +1630,6 @@ By using this switch, work done by these accounts is moderated by the higher use Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1484,13 +1639,15 @@ Accept wildcard characters: False ``` ### -MessageRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRateLimit parameter specifies the number of messages per minute that can be submitted to transport by POP3 or IMAP4 clients that use SMTP. Clients receive a transient error if they submit messages at a rate that exceeds the value of this parameter. Exchange attempts to connect and send the messages at a later time. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1500,13 +1657,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy`. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1516,13 +1675,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1532,13 +1693,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1548,13 +1711,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1564,13 +1729,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSocketConnectionsPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1580,13 +1747,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSocketConnectionsPerUser + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1596,13 +1765,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceMaxSubscriptions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1612,13 +1783,15 @@ Accept wildcard characters: False ``` ### -OutlookServiceRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1628,13 +1801,15 @@ Accept wildcard characters: False ``` ### -OwaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1644,13 +1819,15 @@ Accept wildcard characters: False ``` ### -OwaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaMaxBurst parameter specifies the amount of time that an Outlook on the web user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1660,6 +1837,9 @@ Accept wildcard characters: False ``` ### -OWAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. A valid value for this parameter is an integer from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), use the value $null. @@ -1670,7 +1850,6 @@ A valid value for this parameter is an integer from 0 through 2147483647 inclusi Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1680,6 +1859,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInAD parameter specifies the percentage of a minute that an Outlook Web App user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1688,7 +1870,6 @@ The OWAPercentTimeInAD parameter specifies the percentage of a minute that an Ou Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1698,6 +1879,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInCAS parameter specifies the percentage of a minute that an Outlook Web App user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1706,7 +1890,6 @@ The OWAPercentTimeInCAS parameter specifies the percentage of a minute that an O Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1716,6 +1899,9 @@ Accept wildcard characters: False ``` ### -OWAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The OWAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an Outlook Web App user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1724,7 +1910,6 @@ The OWAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1734,13 +1919,15 @@ Accept wildcard characters: False ``` ### -OwaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaRechargeRate parameter specifies the rate at which an Outlook on the web user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1750,13 +1937,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web voice user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1766,13 +1955,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceMaxBurst parameter specifies the amount of time that an Outlook on the web voice user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1782,13 +1973,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web voice user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The OwaVoiceMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1798,13 +1991,15 @@ Accept wildcard characters: False ``` ### -OwaVoiceRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OwaVoiceRechargeRate parameter specifies the rate at which an Outlook on the web voice user's budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1814,13 +2009,15 @@ Accept wildcard characters: False ``` ### -PopCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1830,13 +2027,15 @@ Accept wildcard characters: False ``` ### -PopMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1846,13 +2045,15 @@ Accept wildcard characters: False ``` ### -POPMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopMaxConcurrency parameter specifies how many concurrent connections a POP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PopMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 20. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1862,6 +2063,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInAD parameter specifies the percentage of a minute a POP user can spend executing LDAP requests (PercentTimeInAD). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1870,7 +2074,6 @@ The POPPercentTimeInAD parameter specifies the percentage of a minute a POP user Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1880,6 +2083,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInCAS parameter specifies the percentage of a minute a POP user can spend executing CAS code (PercentTimeInCAS). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1888,7 +2094,6 @@ The POPPercentTimeInCAS parameter specifies the percentage of a minute a POP use Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1898,6 +2103,9 @@ Accept wildcard characters: False ``` ### -POPPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The POPPercentTimeInMailboxRPC parameter specifies the percentage of a minute a POP user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -1906,7 +2114,6 @@ The POPPercentTimeInMailboxRPC parameter specifies the percentage of a minute a Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -1916,13 +2123,15 @@ Accept wildcard characters: False ``` ### -PopRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PopRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1932,13 +2141,15 @@ Accept wildcard characters: False ``` ### -PowerShellCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1948,13 +2159,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1964,13 +2177,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdletQueueDepth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1980,13 +2195,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is stopped. The value specified by this parameter should be more than the value specified by the ExchangeMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. Both values should be set at the same time. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1996,13 +2213,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxCmdletsTimePeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine whether the number of cmdlets being executed exceeds the limits specified by the PowerShellMaxCmdlets and ExchangeMaxCmdlets parameters. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2012,6 +2231,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxConcurrency parameter specifies different information depending on context: - In the context of remote PowerShell, the PowerShellMaxConcurrency parameter specifies the maximum number of remote PowerShell sessions that a remote PowerShell user can have open at the same time. @@ -2023,7 +2245,6 @@ This parameter value doesn't necessarily correlate to the number of browsers ope Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2033,6 +2254,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxDestructiveCmdlets + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive: - Disable-Mailbox @@ -2051,7 +2275,6 @@ The time period used for this limit is specified by the PowerShellMaxDestructive Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2061,13 +2284,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxDestructiveCmdletsTimePeriod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxDestructiveCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many destructive cmdlets can be run. You set a value for this parameter when you set the PowerShellMaxDestructiveCmdlets parameter. Both values should be set at the same time. For more information, see the description for the PowerShellMaxDestructiveCmdlets parameter. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2077,13 +2302,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxOperations + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2093,13 +2320,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxRunspaces + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a user is allowed to have. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2109,13 +2338,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxRunspacesTimePeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxRunspacesTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many Windows PowerShell sessions can be run. You set this value when you set the PowerShellMaxRunspaces parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2125,6 +2356,9 @@ Accept wildcard characters: False ``` ### -PowerShellMaxTenantConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxTenantConcurrency parameter limits the number of concurrent Windows PowerShell connections per tenant organization. By default, the limit for concurrent Windows PowerShell connections per tenant organization is set to 9. If users in a tenant organization try to make more concurrent requests than the limit set by the PowerShellMaxTenantConcurrency parameter, the new connection attempt fails. However, the existing connections remain valid. This limit is enforced even if a single user hasn't exceeded the per-user limit set by the PowerShellMaxConcurrency parameter. The PowerShellMaxTenantConcurrency parameter has a valid range from 0 through 100 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. This property can only be set for the default throttling policy. @@ -2133,7 +2367,6 @@ This property can only be set for the default throttling policy. Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2143,13 +2376,15 @@ Accept wildcard characters: False ``` ### -PowerShellMaxTenantRunspaces + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellMaxTenantRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a tenant is allowed to have. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2159,13 +2394,15 @@ Accept wildcard characters: False ``` ### -PowerShellRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PowerShellRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2175,6 +2412,9 @@ Accept wildcard characters: False ``` ### -PswsMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxConcurrency parameter specifies how many concurrent connections a Windows PowerShell Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PswsMaxConcurrency parameter has a default value of 18. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null. @@ -2183,7 +2423,6 @@ The PswsMaxConcurrency parameter has a default value of 18. To indicate that the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2193,13 +2432,15 @@ Accept wildcard characters: False ``` ### -PswsMaxRequest + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxRequest parameter specifies how many requests a Windows PowerShell Web Services user can have against an Exchange server at one time. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2209,13 +2450,15 @@ Accept wildcard characters: False ``` ### -PswsMaxRequestTimePeriod + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PswsMaxRequestTimePeriod parameter specifies the period of time, in seconds, that the throttling policy uses to determine how many requests can be run. The default setting is Unlimited. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2225,13 +2468,15 @@ Accept wildcard characters: False ``` ### -PushNotificationCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2241,13 +2486,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2257,13 +2504,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxBurstPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2273,13 +2522,15 @@ Accept wildcard characters: False ``` ### -PushNotificationMaxConcurrency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2289,13 +2540,15 @@ Accept wildcard characters: False ``` ### -PushNotificationRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2305,13 +2558,15 @@ Accept wildcard characters: False ``` ### -PushNotificationRechargeRatePerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2321,13 +2576,15 @@ Accept wildcard characters: False ``` ### -PushNotificationSamplingPeriodPerDevice + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2337,13 +2594,15 @@ Accept wildcard characters: False ``` ### -RcaCutoffBalance + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2353,13 +2612,15 @@ Accept wildcard characters: False ``` ### -RcaMaxBurst + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2369,6 +2630,9 @@ Accept wildcard characters: False ``` ### -RCAMaxConcurrency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaMaxConcurrency parameter specifies how many concurrent connections an RPC Client Access user can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if the user goes offline). If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. A valid value is an integer from 0 through 4294967295, or the value unlimited. The default value is 40. @@ -2379,7 +2643,6 @@ To indicate that the number of concurrent connections should be unthrottled (no Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2389,6 +2652,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInAD + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInAD parameter specifies the percentage of a minute that an Outlook user can spend executing directory requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2397,7 +2663,6 @@ The RCAPercentTimeInAD parameter specifies the percentage of a minute that an Ou Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2407,6 +2672,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInCAS + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInCAS parameter specifies the percentage of a minute that an Outlook user can spend executing CAS mailbox requests. A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2415,7 +2683,6 @@ The RCAPercentTimeInCAS parameter specifies the percentage of a minute that an O Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2425,6 +2692,9 @@ Accept wildcard characters: False ``` ### -RCAPercentTimeInMailboxRPC + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RCAPercentTimeInMailboxRPC parameter specifies the percentage of a minute that an RPC Client Access user can spend executing mailbox RPC requests (PercentTimeInMailboxRPC). A value of 100 indicates that for every one-minute window, the user can spend 60 seconds of that time consuming the resource in question. @@ -2433,7 +2703,6 @@ The RCAPercentTimeInMailboxRPC parameter specifies the percentage of a minute th Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -2443,13 +2712,15 @@ Accept wildcard characters: False ``` ### -RcaRechargeRate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RcaRechargeRate parameter specifies the rate at which the budget for the user is charged (how much the budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2459,13 +2730,15 @@ Accept wildcard characters: False ``` ### -RcaSharedCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedCutoffBalance parameter specifies the resource consumption limits for all users before they're completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2475,13 +2748,15 @@ Accept wildcard characters: False ``` ### -RcaSharedMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaShardMaxBurst parameter specifies the amount of time that all users can consume elevated amounts of resources before being throttled. This is measured in milliseconds. This value is set separately for each component. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2491,6 +2766,9 @@ Accept wildcard characters: False ``` ### -RcaSharedMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedMaxConcurrency parameter specifies how many concurrent connections all RPC Client Access users can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if users go offline). If there are more concurrent requests than the policy allows, new connection attempts fail. However, the existing connections remain valid. The default value is unlimited, which means the limit is controlled individually for each user by the RcaMaxConcurrency parameter. @@ -2499,7 +2777,6 @@ The default value is unlimited, which means the limit is controlled individually Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2509,13 +2786,15 @@ Accept wildcard characters: False ``` ### -RcaSharedRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The RcaSharedRechargeRate parameter specifies the rate at which the budget for all users is charged (how much the budget grows by) during the budget time. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2525,13 +2804,15 @@ Accept wildcard characters: False ``` ### -RecipientRateLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientRateLimit parameter specifies the limits on the number of recipients that a user can address in a 24-hour period. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2541,13 +2822,15 @@ Accept wildcard characters: False ``` ### -SchedulesCutoffBalance + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2557,13 +2840,15 @@ Accept wildcard characters: False ``` ### -SchedulesMaxBurst + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2573,13 +2858,15 @@ Accept wildcard characters: False ``` ### -SchedulesMaxConcurrency + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2589,13 +2876,15 @@ Accept wildcard characters: False ``` ### -SchedulesRechargeRate + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2605,6 +2894,9 @@ 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: - Regular: This scope specifies a custom policy that applies to specific users. @@ -2617,7 +2909,6 @@ For more information about throttling policy scopes, see [User workload manageme Type: ThrottlingPolicyScopeType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2627,13 +2918,15 @@ 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/exchange/Set-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md similarity index 92% rename from exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md rename to exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md index 7179fe0d72..20f9e47794 100644 --- a/exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-throttlingpolicyassociation applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-ThrottlingPolicyAssociation -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-throttlingpolicyassociation +schema: 2.0.0 +title: Set-ThrottlingPolicyAssociation --- # Set-ThrottlingPolicyAssociation @@ -61,13 +62,15 @@ You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the object to which you want to associate a throttling policy. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account. ```yaml Type: ThrottlingPolicyAssociationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -77,6 +80,9 @@ 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,7 +92,6 @@ 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 @@ -96,6 +101,9 @@ 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. @@ -104,7 +112,6 @@ 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 @@ -114,13 +121,15 @@ Accept wildcard characters: False ``` ### -ThrottlingPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ThrottlingPolicy parameter specifies the throttling policy that you want the object specified by the Identity parameter to be associated with. ```yaml Type: ThrottlingPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,13 +139,15 @@ 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/exchange/Set-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md index 65fa73a458..5505f73921 100644 --- a/exchange/exchange-ps/exchange/Set-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-transportagent applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-TransportAgent -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-transportagent +schema: 2.0.0 +title: Set-TransportAgent --- # Set-TransportAgent @@ -45,13 +46,15 @@ This example modifies the priority of a fictitious agent named Test App in the F ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name (Identity property value) of the transport agent that you want to modify. If the name contains spaces, enclose the name in quotation marks ("). ```yaml Type: TransportAgentObjectId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -61,6 +64,9 @@ 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`. @@ -70,7 +76,6 @@ 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 @@ -80,6 +85,9 @@ 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. @@ -88,7 +96,6 @@ 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 @@ -98,13 +105,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Priority parameter specifies the priority of the transport agent. The priority of the transport agent controls the order in which the transport agents process email messages. The priority must be a value between 0 and the maximum number of transport agents. The default behavior is to append a new transport agent to the end of the priority list. Transport agents with a priority closest to 0 process email messages first. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -114,6 +123,9 @@ 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. @@ -126,7 +138,6 @@ 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 @@ -136,13 +147,15 @@ 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/exchange/Set-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-TransportConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md index 57473281ff..9d86b64a34 100644 --- a/exchange/exchange-ps/exchange/Set-TransportConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-transportconfig applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Set-TransportConfig -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-transportconfig +schema: 2.0.0 +title: Set-TransportConfig --- # Set-TransportConfig @@ -114,6 +115,9 @@ To avoid journaling issues, we recommend that you set JournalingReportNdrTo to a ## 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. @@ -122,7 +126,6 @@ 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 @@ -132,6 +135,9 @@ Accept wildcard characters: False ``` ### -AddressBookPolicyRoutingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AddressBookPolicyRoutingEnabled parameter controls how recipients are resolved in an organization that uses address book policies to create separate virtual organizations within the same Exchange organization. Specifically, the global address list (GAL) that's specified in the user's address book policy controls how recipients are resolved. When the value of this parameter is $true, users that are assigned different GALs appear as external recipients. When the value of this parameter is $false, users that are assigned different GALs appear as internal recipients. The default value is $false. Note that this parameter has no effect if your organization doesn't use address book policies, or if the address book policy routing agent isn't installed and enabled. Also note that changing the value of this parameter may take up to 30 minutes to take effect. For more information about address book policies, see [Address book policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies). @@ -140,7 +146,6 @@ The default value is $false. Note that this parameter has no effect if your orga Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -150,6 +155,9 @@ Accept wildcard characters: False ``` ### -AgentGeneratedMessageLoopDetectionInSubmissionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AgentGeneratedMessageLoopDetectionInSubmissionEnabled parameter controls the behavior of messages loop detection in for loops caused by transport agents in the Mailbox Transport Submission service. An agent-generated loop occurs when an agent creates a new copy of a message or adds recipients to a message, and the agent continues to process these resulting messages by creating copies or adding recipients. @@ -162,7 +170,6 @@ When Exchange detects an agent-generated message loop, the loop is stopped. When Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,6 +179,9 @@ Accept wildcard characters: False ``` ### -AgentGeneratedMessageLoopDetectionInSmtpEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AgentGeneratedMessageLoopDetectionInSmtpEnabled parameter controls the behavior of messages loop detection in for loops caused by transport agents in the Transport service. An agent-generated loop occurs when an agent creates a new copy of a message or adds recipients to a message, and the agent continues to process these resulting messages by creating copies or adding recipients. @@ -184,7 +194,6 @@ When Exchange detects an agent-generated message loop, the loop is stopped. When Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -194,6 +203,9 @@ Accept wildcard characters: False ``` ### -AllowLegacyTLSClients + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AllowLegacyTLSClients Description }} @@ -202,7 +214,6 @@ This parameter is available only in the cloud-based service. Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -212,13 +223,15 @@ Accept wildcard characters: False ``` ### -ClearCategories + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ClearCategories parameter keeps or removes Microsoft Outlook message categories during content conversion. Valid input for this parameter is $true or $false. The default value is $true. This means that by default, Outlook message categories are removed during content conversion. ```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 @@ -228,6 +241,9 @@ 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`. @@ -237,7 +253,6 @@ 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 @@ -247,6 +262,9 @@ Accept wildcard characters: False ``` ### -ConvertDisclaimerWrapperToEml + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ConvertDisclaimerWrapperToEml parameter specifies whether the original message will be added as a TNEF attachment or a regular EML attachment to a disclaimer when all of the following are true: - Message is sent to an external user. @@ -261,7 +279,6 @@ Valid input for this parameter is $true or $false. The default value is $false. 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 @@ -271,6 +288,9 @@ Accept wildcard characters: False ``` ### -DiagnosticsAggregationServicePort + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The DiagnosticsAggregationServicePort parameter specifies the TCP port that's used to collect message queue diagnostic information. The default value is 9710. @@ -279,7 +299,6 @@ The DiagnosticsAggregationServicePort parameter specifies the TCP port that's us Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -289,6 +308,9 @@ 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. @@ -299,7 +321,6 @@ 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 @@ -309,6 +330,9 @@ Accept wildcard characters: False ``` ### -DSNConversionMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The DSNConversionMode parameter controls how Exchange handles delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) that are generated by earlier versions of Exchange or other email systems. Valid values are: - DoNotConvert: DSNs aren't modified. The DSN is delivered as a standard message. @@ -321,7 +345,6 @@ The default value in Exchange 2010 and Exchange 2013 is UseExchangeDSNs. Otherwi Type: DSNConversionOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -331,13 +354,15 @@ Accept wildcard characters: False ``` ### -ExternalDelayDsnEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalDelayDsnEnabled parameter specifies whether a delay delivery status notification (DSN) message should be created for external messages that couldn't be immediately delivered. 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, Exchange Online Required: False Position: Named @@ -347,13 +372,15 @@ Accept wildcard characters: False ``` ### -ExternalDsnDefaultLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalDsnDefaultLanguage parameter specifies which Exchange server language should be used by default when you create external DSN messages. The default value is the default Windows server language. ```yaml Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -363,13 +390,15 @@ Accept wildcard characters: False ``` ### -ExternalDsnLanguageDetectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalDsnLanguageDetectionEnabled parameter specifies whether the server should try to send an external DSN message in the same language as the original message that generated the notification. 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, Exchange Online Required: False Position: Named @@ -379,6 +408,9 @@ Accept wildcard characters: False ``` ### -ExternalDsnMaxMessageAttachSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ExternalDsnMaxMessageAttachSize parameter specifies the maximum size of the original message attached to an external DSN message. If the original message exceeds this size, only the headers of the original message are included in the DSN message. The default value is 10 megabytes (MB). @@ -399,7 +431,6 @@ The valid input range for this parameter is from 0 through 2147483647 bytes. If Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -409,13 +440,15 @@ Accept wildcard characters: False ``` ### -ExternalDsnReportingAuthority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalDsnReportingAuthority parameter specifies the domain in the machine-readable part of external DSN messages. The default value is blank ($null), which means the value is the authoritative domain that you specified during the creation of the organization. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -425,6 +458,9 @@ Accept wildcard characters: False ``` ### -ExternalDsnSendHtml + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalDsnSendHtml parameter specifies whether external DSN messages should be HTML or plain text. Valid values are: - $true: External DSNs are HTML. This is the default value. @@ -434,7 +470,6 @@ The ExternalDsnSendHtml parameter specifies whether external DSN messages should 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 @@ -444,6 +479,9 @@ Accept wildcard characters: False ``` ### -ExternalPostmasterAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExternalPostmasterAddress parameter specifies the email address in the From header field of an external DSN message. The default value is blank ($null). The default value means the external postmaster address is `postmaster@` in the following locations: @@ -460,7 +498,6 @@ To override the default behavior, you can specify an email address for the Exter 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 @@ -470,6 +507,9 @@ 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. @@ -478,7 +518,6 @@ 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 @@ -488,6 +527,9 @@ Accept wildcard characters: False ``` ### -GenerateCopyOfDSNFor + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The GenerateCopyOfDSNFor parameter controls the non-delivery reports (NDRs) that are copied to a mailbox by specifying the DSN codes that you want to monitor. You must configure the list of monitored DSNs on one Mailbox server and locally on each Edge Transport server in your Exchange organization. @@ -515,7 +557,6 @@ To assign a mailbox to the Exchange recipient, use the Set-OrganizationConfig cm Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -525,6 +566,9 @@ Accept wildcard characters: False ``` ### -HeaderPromotionModeSetting + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The HeaderPromotionModeSetting parameter specifies whether named properties are created for custom X-headers on messages received. Valid values are: - MustCreate: Exchange creates a named property for each new custom X-header. @@ -535,7 +579,6 @@ The HeaderPromotionModeSetting parameter specifies whether named properties are Type: HeaderPromotionMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -545,13 +588,15 @@ Accept wildcard characters: False ``` ### -InternalDelayDsnEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalDelayDsnEnabled parameter specifies whether a delay DSN message should be created for messages sent to or from recipients or senders in the same Exchange organization that couldn't be immediately delivered. 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, Exchange Online Required: False Position: Named @@ -561,13 +606,15 @@ Accept wildcard characters: False ``` ### -InternalDsnDefaultLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalDsnDefaultLanguage parameter specifies which Exchange server language should be used by default when you create internal DSN messages. The default value is the default Windows server language. ```yaml Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -577,13 +624,15 @@ Accept wildcard characters: False ``` ### -InternalDsnLanguageDetectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalDsnLanguageDetectionEnabled parameter specifies whether the server should try to send an internal DSN message in the same language as the original message that generated the notification. 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, Exchange Online Required: False Position: Named @@ -593,6 +642,9 @@ Accept wildcard characters: False ``` ### -InternalDsnMaxMessageAttachSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalDsnMaxMessageAttachSize parameter specifies the maximum size of the original message that generated an internal DSN message. If the original message exceeds this size, only the headers of the original message are included in the DSN message. The default value is 10 MB. @@ -612,7 +664,6 @@ The valid input range for this parameter is from 0 through 2147483647 bytes. If Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -622,13 +673,15 @@ Accept wildcard characters: False ``` ### -InternalDsnReportingAuthority + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalDsnReportingAuthority parameter specifies the domain in the machine-readable part of internal DSN messages. The default value is blank ($null), which means the value is the authoritative domain that you specified during the creation of the organization. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -638,6 +691,9 @@ Accept wildcard characters: False ``` ### -InternalDsnSendHtml + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InternalDsnSendHtml parameter specifies whether internal DSN messages should be HTML or plain text. Valid values are: - $true: Internal DSNs are HTML. This is the default value. @@ -647,7 +703,6 @@ The InternalDsnSendHtml parameter specifies whether internal DSN messages should 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 @@ -657,6 +712,9 @@ Accept wildcard characters: False ``` ### -InternalSMTPServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The InternalSMTPServers parameter specifies a list of internal SMTP server IP addresses or IP address ranges that should be ignored by Sender ID and connection filtering. @@ -669,7 +727,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -679,6 +736,9 @@ Accept wildcard characters: False ``` ### -JournalMessageExpirationDays + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The JournalMessageExpirationDays parameter extends the number of days that undeliverable journal reports are queued before they expire. A valid value is an integer from 0 to 7. The default value is 0, which means undeliverable journal reports are treated like regular undeliverable messages. @@ -687,7 +747,6 @@ The JournalMessageExpirationDays parameter extends the number of days that undel Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -697,13 +756,15 @@ Accept wildcard characters: False ``` ### -JournalingReportNdrTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The JournalingReportNdrTo parameter specifies the email address to which journal reports are sent if the journaling mailbox is unavailable. By default, if this parameter is left empty, Exchange continues to try to deliver the journal report to the journaling mailbox. We recommended that you use a dedicated (non-user) mailbox as the value for this parameter. Like the journaling mailbox, the alternate journaling mailbox can't be an Exchange Online mailbox. ```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 @@ -713,6 +774,9 @@ Accept wildcard characters: False ``` ### -LegacyJournalingMigrationEnabled + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The LegacyJournalingMigrationEnabled parameter specifies whether journal messages generated in Microsoft Exchange Server 2003 will be reformatted by Exchange 2010. @@ -723,7 +787,6 @@ The default value is $false. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -733,6 +796,9 @@ Accept wildcard characters: False ``` ### -MaxAllowedAgentGeneratedMessageDepth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxAllowedAgentGeneratedMessageDepth parameter specifies how many times all agents can process any resulting copies of the same message. The default value is 3. Valid input for this parameter is an integer. @@ -741,7 +807,6 @@ The MaxAllowedAgentGeneratedMessageDepth parameter specifies how many times all Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -751,6 +816,9 @@ Accept wildcard characters: False ``` ### -MaxAllowedAgentGeneratedMessageDepthPerAgent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxAllowedAgentGeneratedMessageDepthPerAgent parameter specifies how many times a single agent can process any resulting copies of the same message. The default value is 2. @@ -761,7 +829,6 @@ The value of the MaxAllowedAgentGeneratedMessageDepth parameter should be larger Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -771,6 +838,9 @@ Accept wildcard characters: False ``` ### -MaxDumpsterSizePerDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. @@ -795,7 +865,6 @@ There's no replacement for this parameter in later versions of Exchange. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -805,6 +874,9 @@ Accept wildcard characters: False ``` ### -MaxDumpsterTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. @@ -823,7 +895,6 @@ This parameter is replaced by the SafetyNetHoldTime parameter. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -833,6 +904,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxReceiveSize parameter specifies the maximum message size that can be received by recipients in the organization. The default value is 10 MB. @@ -856,7 +930,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -866,6 +939,9 @@ Accept wildcard characters: False ``` ### -MaxRecipientEnvelopeLimit + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The MaxRecipientEnvelopeLimit parameter specifies the maximum number of recipients in a message. Exchange treats an unexpanded distribution group as one recipient. In on-premises Exchange, the default value is 500. The valid input range for this parameter is from 0 through 2147483647. If you enter a value of Unlimited, no limit is imposed on the number of recipients in a message. @@ -876,7 +952,6 @@ In Exchange Online, the default value is Unlimited, which means the organization 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 @@ -886,6 +961,9 @@ Accept wildcard characters: False ``` ### -MaxRetriesForLocalSiteShadow + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxRetriesForLocalSiteShadow parameter specifies the maximum number of attempts to make a shadow copy of the message in the local Active Directory site. Valid input for this parameter is an integer between 0 and 255. The default value is 2. The total number of attempts to create a shadow copy of the message is controlled by the ShadowMessagePreferenceSetting parameter: @@ -900,7 +978,6 @@ If a shadow copy of the message isn't created after the specified number of atte Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -910,6 +987,9 @@ Accept wildcard characters: False ``` ### -MaxRetriesForRemoteSiteShadow + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxRetriesForRemoteSiteShadow parameter specifies the maximum number of attempts to make a shadow copy of the message in a different Active Directory site. Valid input for this parameter is an integer between 0 and 255. The default value is 4. The total number of attempts to create a shadow copy of the message is controlled by the ShadowMessagePreferenceSetting parameter: @@ -924,7 +1004,6 @@ If a shadow copy of the message isn't created after the specified number of atte Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -934,6 +1013,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MaxSendSize parameter specifies the maximum message size that can be sent by senders in the organization. The default value is 10 MB. @@ -957,7 +1039,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -967,6 +1048,9 @@ Accept wildcard characters: False ``` ### -MessageExpiration + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MessageExpiration parameter specifies the message expiration timeout interval for the organization. @@ -983,7 +1067,6 @@ Queued messages typically expire after 24 hours, resulting in an NDR for failed Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -993,6 +1076,9 @@ Accept wildcard characters: False ``` ### -PreventDuplicateJournalingEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The PreventDuplicateJournalingEnabled parameter prevents duplicate journaling reports that can occur when messages are processed by both on-premises and cloud journaling agents. Valid values are: @@ -1004,7 +1090,6 @@ The PreventDuplicateJournalingEnabled parameter prevents duplicate journaling re Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1014,6 +1099,9 @@ Accept wildcard characters: False ``` ### -QueueDiagnosticsAggregationInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The QueueDiagnosticsAggregationInterval parameter specifies the polling interval that's used to retrieve message queue diagnostic information. The default value is 00:01:00 or one minute. @@ -1024,7 +1112,6 @@ 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 @@ -1034,6 +1121,9 @@ Accept wildcard characters: False ``` ### -RejectMessageOnShadowFailure + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The RejectMessageOnShadowFailure parameter specifies whether to accept or reject messages when shadow copies of the messages can't be created. Valid values are: @@ -1047,7 +1137,6 @@ The number of attempts to make a shadow copy of the message and where to make th Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1057,6 +1146,9 @@ Accept wildcard characters: False ``` ### -ReplyAllStormBlockDurationHours + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ReplyAllStormBlockDurationHours Description }} @@ -1065,7 +1157,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1075,6 +1166,9 @@ Accept wildcard characters: False ``` ### -ReplyAllStormDetectionMinimumRecipients + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ReplyAllStormDetectionMinimumRecipients Description }} @@ -1083,7 +1177,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1093,6 +1186,9 @@ Accept wildcard characters: False ``` ### -ReplyAllStormDetectionMinimumReplies + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ReplyAllStormDetectionMinimumReplies Description }} @@ -1101,7 +1197,6 @@ This parameter is available only in the cloud-based service. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1111,6 +1206,9 @@ Accept wildcard characters: False ``` ### -ReplyAllStormProtectionEnabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill ReplyAllStormProtectionEnabled Description }} @@ -1119,7 +1217,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1129,13 +1226,15 @@ Accept wildcard characters: False ``` ### -Rfc2231EncodingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Rfc2231EncodingEnabled parameter specifies whether the RFC 2231 encoding of MIME parameters for outbound messages is enabled in your organization. Valid input for this parameter is $true or $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 @@ -1145,6 +1244,9 @@ Accept wildcard characters: False ``` ### -SafetyNetHoldTime + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SafetyNetHoldTime parameter specifies how long a copy of a successfully processed message is retained in Safety Net. Unacknowledged shadow copies of messages auto-expire from Safety Net based on adding the values of the SafetyNetHoldTime parameter and the MessageExpirationTimeout parameter on the Set-TransportService cmdlet. @@ -1157,7 +1259,6 @@ The default value is 2.00:00:00 or 2 days. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1167,6 +1268,9 @@ Accept wildcard characters: False ``` ### -ShadowHeartbeatFrequency + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowHeartbeatFrequency parameter specifies the amount of time a server waits before establishing a connection to a primary server to query the discard status of shadow messages. @@ -1179,7 +1283,6 @@ Valid input for this parameter is 00:00:01 to 1.00:00:00. The default value is 0 Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1189,6 +1292,9 @@ Accept wildcard characters: False ``` ### -ShadowHeartbeatRetryCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. @@ -1201,7 +1307,6 @@ This parameter is replaced by the ShadowResubmitTimeSpan parameter. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1211,6 +1316,9 @@ Accept wildcard characters: False ``` ### -ShadowHeartbeatTimeoutInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments. @@ -1227,7 +1335,6 @@ This parameter is replaced by the ShadowHeartbeatFrequency parameter. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1237,6 +1344,9 @@ Accept wildcard characters: False ``` ### -ShadowMessageAutoDiscardInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowMessageAutoDiscardInterval parameter specifies how long a server retains discard events for shadow messages. A primary server queues discard events until queried by the shadow server. However, if the shadow server doesn't query the primary server for the duration specified in this parameter, the primary server deletes the queued discard events. @@ -1249,7 +1359,6 @@ Valid input for this parameter is 00:00:05 to 90.00:00:00. The default value is Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1259,6 +1368,9 @@ Accept wildcard characters: False ``` ### -ShadowMessagePreferenceSetting + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowMessagePreferenceSetting parameter specifies the preferred location for making a shadow copy of a message. Valid values are: @@ -1273,7 +1385,6 @@ The default value is PreferRemote. Type: ShadowMessagePreference Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1283,6 +1394,9 @@ Accept wildcard characters: False ``` ### -ShadowRedundancyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowRedundancyEnabled parameter specifies whether shadow redundancy is enabled in the organization. Valid input for this parameter is $true or $false. The default value is $true. @@ -1291,7 +1405,6 @@ The ShadowRedundancyEnabled parameter specifies whether shadow redundancy is ena Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1301,6 +1414,9 @@ Accept wildcard characters: False ``` ### -ShadowResubmitTimeSpan + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ShadowResubmitTimeSpan parameter specifies amount of time a server waits before deciding that a primary server has failed and assumes ownership of shadow messages in the shadow queue for the primary server that's unreachable. @@ -1315,7 +1431,6 @@ This parameter replaces the ShadowHeartbeatRetryCount parameter. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1325,6 +1440,9 @@ Accept wildcard characters: False ``` ### -SmtpClientAuthenticationDisabled + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SmtpClientAuthenticationDisabled parameter specifies whether to disable authenticated SMTP (SMTP AUTH) for the whole organization. Examples of clients and services that require authenticated SMTP to send email messages include: @@ -1347,7 +1465,6 @@ To selectively enable authenticated SMTP for specific mailboxes only: disable au Type: Boolean Parameter Sets: Exchange Online Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -1357,6 +1474,9 @@ Accept wildcard characters: False ``` ### -SupervisionTags + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The SupervisionTags parameter specifies the various tags that are used for transport supervision in the organization. @@ -1367,7 +1487,6 @@ When you install Exchange, two tags, Allow and Reject, are created by default. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1377,6 +1496,9 @@ Accept wildcard characters: False ``` ### -TLSReceiveDomainSecureList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TLSReceiveDomainSecureList parameter specifies the domains from which you want to receive domain secured email by using mutual Transport Layer Security (TLS) authentication. To fully support mutual TLS authentication, you must also perform the following steps: @@ -1395,7 +1517,6 @@ The wildcard character (\*) isn't supported in the domains listed in the TLSRece Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1405,6 +1526,9 @@ Accept wildcard characters: False ``` ### -TLSSendDomainSecureList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TLSSendDomainSecureList parameter specifies the domains from which you want to send domain secured email by using mutual TLS authentication. To fully support mutual TLS authentication, you must also perform the following steps: @@ -1423,7 +1547,6 @@ Multiple domains may be separated by commas. The wildcard character (\*) isn't s Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1433,6 +1556,9 @@ Accept wildcard characters: False ``` ### -TransportRuleAttachmentTextScanLimit + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TransportRuleAttachmentTextScanLimit parameter specifies the maximum size of text to extract from attachments for scanning by attachment scanning predicates in transport rules and data loss prevention (DLP) policies. @@ -1454,7 +1580,6 @@ If the amount of text in the attachment is larger than the value of this paramet Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1464,6 +1589,9 @@ Accept wildcard characters: False ``` ### -VerifySecureSubmitEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The VerifySecureSubmitEnabled parameter verifies that email clients submitting messages from mailboxes on Mailbox servers are using encrypted MAPI submission. The valid values for this parameter are $true or $false. The default value is $false @@ -1476,7 +1604,6 @@ If the VerifySecureSubmitEnabled parameter is set to $false, all MAPI message su Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1486,6 +1613,9 @@ Accept wildcard characters: False ``` ### -VoicemailJournalingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in on-premises Exchange. The VoicemailJournalingEnabled parameter specifies whether Unified Messaging voice mail messages are journaled by the Journaling agent. Valid input for this parameter is $true or $false. The default value is $true. @@ -1494,7 +1624,6 @@ The VoicemailJournalingEnabled parameter specifies whether Unified Messaging voi 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 @@ -1504,13 +1633,15 @@ 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 @@ -1520,6 +1651,9 @@ Accept wildcard characters: False ``` ### -Xexch50Enabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Xexch50Enabled parameter specifies whether Xexch50 authentication should be enabled for backward compatibility with computers running Exchange 2003. Valid input for this parameter is $true or $false. The default value is $true. @@ -1528,7 +1662,6 @@ The Xexch50Enabled parameter specifies whether Xexch50 authentication should be 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/exchange/Set-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Set-TransportRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md index a3b87868a6..a51ec19f6f 100644 --- a/exchange/exchange-ps/exchange/Set-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-transportrule applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-TransportRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-transportrule +schema: 2.0.0 +title: Set-TransportRule --- # Set-TransportRule @@ -225,6 +226,9 @@ This example modifies the existing rule named Sales Team Disclaimer transport ru ## 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 modify. You can use any value that uniquely identifies the rule. For example: - Name @@ -235,7 +239,6 @@ The Identity parameter specifies the rule that you want to modify. 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 @@ -245,6 +248,9 @@ Accept wildcard characters: False ``` ### -ActivationDate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/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". @@ -253,7 +259,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -263,6 +268,9 @@ Accept wildcard characters: False ``` ### -ADComparisonAttribute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -305,7 +313,6 @@ If you don't use the ADComparisonOperator parameter, the default comparison oper Type: ADAttribute 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 @@ -315,6 +322,9 @@ Accept wildcard characters: False ``` ### -ADComparisonOperator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -328,7 +338,6 @@ The ADComparisonOperator parameter specifies the comparison operator for the ADC Type: Evaluation 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 @@ -338,6 +347,9 @@ Accept wildcard characters: False ``` ### -AddManagerAsRecipientType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -355,7 +367,6 @@ This action only works if the sender's Manager attribute is defined. Type: AddedRecipientType 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,6 +376,9 @@ Accept wildcard characters: False ``` ### -AddToRecipients + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -384,7 +398,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -394,6 +407,9 @@ Accept wildcard characters: False ``` ### -AnyOfCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -417,7 +433,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -427,6 +442,9 @@ Accept wildcard characters: False ``` ### -AnyOfCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -450,7 +468,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -460,6 +477,9 @@ Accept wildcard characters: False ``` ### -AnyOfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -474,7 +494,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: Word[] 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 @@ -484,6 +503,9 @@ Accept wildcard characters: False ``` ### -AnyOfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -498,7 +520,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: Pattern[] 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 @@ -508,6 +529,9 @@ Accept wildcard characters: False ``` ### -AnyOfToCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -531,7 +555,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -541,6 +564,9 @@ Accept wildcard characters: False ``` ### -AnyOfToCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -564,7 +590,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -574,6 +599,9 @@ Accept wildcard characters: False ``` ### -AnyOfToHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -597,7 +625,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -607,6 +634,9 @@ Accept wildcard characters: False ``` ### -AnyOfToHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -630,7 +660,6 @@ A match for this condition applies the rule action to all recipients of the mess Type: RecipientIdParameter[] 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 @@ -640,6 +669,9 @@ Accept wildcard characters: False ``` ### -ApplyClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -652,7 +684,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -662,6 +693,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerFallbackAction + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -685,7 +719,6 @@ If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the Type: DisclaimerFallbackAction 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 @@ -695,6 +728,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -710,7 +746,6 @@ If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the Type: DisclaimerLocation 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 @@ -720,6 +755,9 @@ Accept wildcard characters: False ``` ### -ApplyHtmlDisclaimerText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -760,7 +798,6 @@ You use the ApplyHtmlDisclaimerLocation parameter to specify where to insert the Type: DisclaimerText 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 @@ -770,6 +807,9 @@ Accept wildcard characters: False ``` ### -ApplyOME + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -783,7 +823,6 @@ The ApplyOME parameter specifies an action that encrypts messages and their atta Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -793,6 +832,9 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionCustomizationTemplate + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -803,7 +845,6 @@ The ApplyRightsProtectionCustomizationTemplate parameter specifies an action tha Type: OMEConfigurationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -813,6 +854,9 @@ Accept wildcard characters: False ``` ### -ApplyRightsProtectionTemplate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -829,7 +873,6 @@ For more information, see [Transport protection rules](https://learn.microsoft.c 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: Named @@ -839,6 +882,9 @@ Accept wildcard characters: False ``` ### -AttachmentContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -851,7 +897,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] 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,6 +906,9 @@ Accept wildcard characters: False ``` ### -AttachmentExtensionMatchesWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -873,7 +921,6 @@ The AttachmentExtensionMatchesWords parameter specifies a condition that looks f Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -883,6 +930,9 @@ Accept wildcard characters: False ``` ### -AttachmentHasExecutableContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -898,7 +948,6 @@ The system inspects the file properties rather than relying on the file extensio 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 @@ -908,6 +957,9 @@ Accept wildcard characters: False ``` ### -AttachmentIsPasswordProtected + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -921,7 +973,6 @@ The AttachmentIsPasswordProtected parameter specifies a condition that looks for 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 @@ -931,6 +982,9 @@ Accept wildcard characters: False ``` ### -AttachmentIsUnsupported + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -950,7 +1004,6 @@ In Exchange 2010, to extend the list of supported file types, see [Register Filt 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 @@ -960,6 +1013,9 @@ Accept wildcard characters: False ``` ### -AttachmentMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -974,7 +1030,6 @@ Only the first 150 kilobytes (KB) of the attachment is scanned when trying to ma Type: Pattern[] 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 @@ -984,6 +1039,9 @@ Accept wildcard characters: False ``` ### -AttachmentNameMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -994,7 +1052,6 @@ The AttachmentNameMatchesPatterns parameter specifies a condition that looks for Type: Pattern[] 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 @@ -1004,6 +1061,9 @@ Accept wildcard characters: False ``` ### -AttachmentProcessingLimitExceeded + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1019,7 +1079,6 @@ You use this condition to create rules that work together with other attachment 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 @@ -1029,6 +1088,9 @@ Accept wildcard characters: False ``` ### -AttachmentPropertyContainsWords + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1058,7 +1120,6 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1068,6 +1129,9 @@ Accept wildcard characters: False ``` ### -AttachmentSizeOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -1090,7 +1154,6 @@ The embedded images are treated as attachments (for example, messages with a pic Type: ByteQuantifiedSize 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 @@ -1100,6 +1163,9 @@ Accept wildcard characters: False ``` ### -BetweenMemberOf1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1119,7 +1185,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1129,6 +1194,9 @@ Accept wildcard characters: False ``` ### -BetweenMemberOf2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1148,7 +1216,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1158,6 +1225,9 @@ Accept wildcard characters: False ``` ### -BlindCopyTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1177,7 +1247,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1187,13 +1256,15 @@ Accept wildcard characters: False ``` ### -Comments + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Comments parameter specifies optional descriptive text for the rule (for example, what the rule is used for, or how it has changed over time). The length of the comment can't exceed 1024 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, Exchange Online Protection Required: False Position: Named @@ -1203,6 +1274,9 @@ 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`. @@ -1212,7 +1286,6 @@ 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 @@ -1222,6 +1295,9 @@ Accept wildcard characters: False ``` ### -ContentCharacterSetContainsWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -1234,7 +1310,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1244,6 +1319,9 @@ Accept wildcard characters: False ``` ### -CopyTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1263,7 +1341,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1273,6 +1350,9 @@ Accept wildcard characters: False ``` ### -DeleteMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -1286,7 +1366,6 @@ The DeleteMessage parameter specifies an action that silently drops messages wit 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 @@ -1296,6 +1375,9 @@ Accept wildcard characters: False ``` ### -Disconnect + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -1309,7 +1391,6 @@ The Disconnect parameter specifies an action that ends the SMTP connection betwe 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 @@ -1319,6 +1400,9 @@ 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 specifies the data loss prevention (DLP) policy that's associated with the rule. Each DLP policy is enforced using a set of mail flow rules (transport rules). To learn more about DLP, see [Data loss prevention in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/data-loss-prevention/data-loss-prevention). @@ -1327,7 +1411,6 @@ The DlpPolicy parameter specifies the data loss prevention (DLP) policy that's a Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -1337,6 +1420,9 @@ 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. @@ -1347,7 +1433,6 @@ 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 @@ -1357,6 +1442,9 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonAttribute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1399,7 +1487,6 @@ If you don't use the ExceptIfADComparisonOperator parameter, the default compari Type: ADAttribute 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 @@ -1409,6 +1496,9 @@ Accept wildcard characters: False ``` ### -ExceptIfADComparisonOperator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1422,7 +1512,6 @@ The ExceptIfADComparisonOperator parameter specifies the comparison operator for Type: Evaluation 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 @@ -1432,6 +1521,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1455,7 +1547,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1465,6 +1556,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1488,7 +1582,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1498,6 +1591,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1512,7 +1608,6 @@ A match for this exception prevents the rule action from being applied to all re Type: Word[] 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 @@ -1522,6 +1617,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1536,7 +1634,6 @@ A match for this exception prevents the rule action from being applied to all re Type: Pattern[] 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 @@ -1546,6 +1643,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1569,7 +1669,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1579,6 +1678,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToCcHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1602,7 +1704,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1612,6 +1713,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1635,7 +1739,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1645,6 +1748,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAnyOfToHeaderMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1668,7 +1774,6 @@ A match for this exception prevents the rule action from being applied to all re Type: RecipientIdParameter[] 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 @@ -1678,6 +1783,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1690,7 +1798,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] 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 @@ -1700,6 +1807,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentExtensionMatchesWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1712,7 +1822,6 @@ The ExceptIfAttachmentExtensionMatchesWords parameter specifies an exception tha Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1722,6 +1831,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentHasExecutableContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1737,7 +1849,6 @@ The system inspects the file properties rather than relying on the file extensio 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 @@ -1747,6 +1858,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsPasswordProtected + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1760,7 +1874,6 @@ The ExceptIfAttachmentIsPasswordProtected parameter specifies an exception that 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 @@ -1770,6 +1883,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentIsUnsupported + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1789,7 +1905,6 @@ In Exchange 2010, to extend the list of supported file types, see [Register Filt 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 @@ -1799,6 +1914,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1813,7 +1931,6 @@ Only the first 150 KB of the attachment is scanned when trying to match a text p Type: Pattern[] 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 @@ -1823,6 +1940,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentNameMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1833,7 +1953,6 @@ The ExceptIfAttachmentNameMatchesPatterns parameter specifies an exception that Type: Pattern[] 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 @@ -1843,6 +1962,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentProcessingLimitExceeded + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1858,7 +1980,6 @@ You use this exception to create rules that work together with other attachment 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 @@ -1868,6 +1989,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentPropertyContainsWords + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1897,7 +2021,6 @@ When you specify multiple properties, or multiple values for the same property, Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1907,6 +2030,9 @@ Accept wildcard characters: False ``` ### -ExceptIfAttachmentSizeOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -1927,7 +2053,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize 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 @@ -1937,6 +2062,9 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf1 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1956,7 +2084,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1966,6 +2093,9 @@ Accept wildcard characters: False ``` ### -ExceptIfBetweenMemberOf2 + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -1985,7 +2115,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -1995,6 +2124,9 @@ Accept wildcard characters: False ``` ### -ExceptIfContentCharacterSetContainsWords + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2007,7 +2139,6 @@ To specify multiple words or phrases, this parameter uses the syntax: Word1,"Phr Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2017,6 +2148,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFrom + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2038,7 +2172,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -2048,6 +2181,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2060,7 +2196,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] 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 @@ -2070,6 +2205,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2084,7 +2222,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Pattern[] 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 @@ -2094,6 +2231,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2115,7 +2255,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -2125,6 +2264,9 @@ Accept wildcard characters: False ``` ### -ExceptIfFromScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2138,7 +2280,6 @@ The ExceptIfFromScope parameter specifies an exception that looks for the locati Type: FromUserScope 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 @@ -2148,6 +2289,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2164,7 +2308,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -2174,6 +2317,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasNoClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2187,7 +2333,6 @@ The ExceptIfHasNoClassification parameter specifies an exception that looks for 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 @@ -2197,6 +2342,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHasSenderOverride + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. @@ -2212,7 +2360,6 @@ The ExceptIfHasSenderOverride parameter specifies an exception that looks for me 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 @@ -2222,6 +2369,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2232,7 +2382,6 @@ The ExceptIfHeaderContainsMessageHeader parameter specifies the name of header f Type: HeaderName 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 @@ -2242,6 +2391,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2256,7 +2408,6 @@ You specify the header field to search by using the ExceptIfHeaderContainsMessag Type: Word[] 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 @@ -2266,6 +2417,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2276,7 +2430,6 @@ The ExceptIfHeaderMatchesMessageHeader parameter specifies the name of header fi Type: HeaderName 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 @@ -2286,6 +2439,9 @@ Accept wildcard characters: False ``` ### -ExceptIfHeaderMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2298,7 +2454,6 @@ You specify the header field to search by using the ExceptIfHeaderMatchesMessage Type: Pattern[] 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 @@ -2308,6 +2463,9 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2329,7 +2487,6 @@ You specify if you want to look for these users as managers of senders or recipi Type: RecipientIdParameter[] 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 @@ -2339,6 +2496,9 @@ Accept wildcard characters: False ``` ### -ExceptIfManagerForEvaluatedUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2354,7 +2514,6 @@ You specify the users to look for by using the ExceptIfManagerAddresses paramete Type: EvaluatedUser 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 @@ -2364,6 +2523,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageContainsDataClassifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. @@ -2380,7 +2542,6 @@ For a list of sensitive information types available, see [Sensitive information Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -2390,6 +2551,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageSizeOver + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2410,7 +2574,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2420,6 +2583,9 @@ Accept wildcard characters: False ``` ### -ExceptIfMessageTypeMatches + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2440,7 +2606,6 @@ The ExceptIfMessageTypeMatches parameter specifies an exception that looks for m Type: MessageType 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 @@ -2450,6 +2615,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2496,7 +2664,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -2506,6 +2673,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2550,7 +2720,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -2560,6 +2729,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2570,7 +2742,6 @@ The ExceptIfRecipientAddressContainsWords parameter specifies an exception that Type: Word[] 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 @@ -2580,6 +2751,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2592,7 +2766,6 @@ This parameter works when the recipient is an individual user. This parameter do Type: Pattern[] 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 @@ -2602,6 +2775,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2614,7 +2790,6 @@ This exception matches domains and subdomains. For example, "contoso.com" matche Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2624,6 +2799,9 @@ Accept wildcard characters: False ``` ### -ExceptIfRecipientInSenderList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2632,7 +2810,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2642,6 +2819,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSCLOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2657,7 +2837,6 @@ The rule looks for messages with an SCL value that's greater than or equal to th Type: SclValue 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 @@ -2667,6 +2846,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2713,7 +2895,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -2723,6 +2904,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2767,7 +2951,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -2777,6 +2960,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2791,7 +2977,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2801,6 +2986,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderInRecipientList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -2809,7 +2997,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2819,6 +3006,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderIpRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2837,7 +3027,6 @@ In Exchange Online, the IP address that's used during evaluation of this excepti 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 @@ -2847,6 +3036,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSenderManagementRelationship + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2860,7 +3052,6 @@ The ExceptIfSenderManagementRelationship parameter specifies an exception that l Type: ManagementRelationship 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 @@ -2870,6 +3061,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2889,7 +3083,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -2899,6 +3092,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. 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: @@ -2916,7 +3112,6 @@ If you remove the group after you create the rule, no exception is made for mess Type: RecipientIdParameter[] 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 @@ -2926,6 +3121,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -2941,7 +3139,6 @@ The ExceptIfSentToScope parameter specifies an exception that looks for the loca Type: ToUserScope 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 @@ -2951,6 +3148,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2965,7 +3165,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -2975,6 +3174,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -2985,7 +3187,6 @@ The ExceptIfSubjectMatchesPatterns parameter specifies an exception that looks f Type: Pattern[] 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 @@ -2995,6 +3196,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -3009,7 +3213,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -3019,6 +3222,9 @@ Accept wildcard characters: False ``` ### -ExceptIfSubjectOrBodyMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available on Mailbox servers and Edge Transport servers. @@ -3029,7 +3235,6 @@ The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception that l Type: Pattern[] 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 @@ -3039,6 +3244,9 @@ Accept wildcard characters: False ``` ### -ExceptIfWithImportance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. In on-premises Exchange, this exception is available only on Mailbox servers. @@ -3053,7 +3261,6 @@ The ExceptIfWithImportance parameter specifies an exception that looks for messa Type: Importance 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 @@ -3063,6 +3270,9 @@ Accept wildcard characters: False ``` ### -ExpiryDate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix. The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time. @@ -3073,7 +3283,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -3083,6 +3292,9 @@ Accept wildcard characters: False ``` ### -From + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3104,7 +3316,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -3114,6 +3325,9 @@ Accept wildcard characters: False ``` ### -FromAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3126,7 +3340,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] 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 @@ -3136,6 +3349,9 @@ Accept wildcard characters: False ``` ### -FromAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3150,7 +3366,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Pattern[] 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 @@ -3160,6 +3375,9 @@ Accept wildcard characters: False ``` ### -FromMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3181,7 +3399,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: RecipientIdParameter[] 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 @@ -3191,6 +3408,9 @@ Accept wildcard characters: False ``` ### -FromScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3204,7 +3424,6 @@ The FromScope parameter specifies a condition that looks for the location of mes Type: FromUserScope 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 @@ -3214,6 +3433,9 @@ Accept wildcard characters: False ``` ### -GenerateIncidentReport + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3233,7 +3455,6 @@ The GenerateIncidentReport parameter specifies where to send the incident report Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3243,6 +3464,9 @@ Accept wildcard characters: False ``` ### -GenerateNotification + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3264,7 +3488,6 @@ The maximum number of characters is 5120. Type: DisclaimerText Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3274,6 +3497,9 @@ Accept wildcard characters: False ``` ### -HasClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3290,7 +3516,6 @@ The message classification referred to in this parameter is the custom message c 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 @@ -3300,6 +3525,9 @@ Accept wildcard characters: False ``` ### -HasNoClassification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3313,7 +3541,6 @@ The HasNoClassification parameter specifies a condition that looks for messages 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 @@ -3323,6 +3550,9 @@ Accept wildcard characters: False ``` ### -HasSenderOverride + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. @@ -3338,7 +3568,6 @@ The HasSenderOverride parameter specifies a condition that looks for messages wh 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 @@ -3348,6 +3577,9 @@ Accept wildcard characters: False ``` ### -HeaderContainsMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3358,7 +3590,6 @@ The HeaderContainsMessageHeader parameter specifies the name of header field in Type: HeaderName 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 @@ -3368,6 +3599,9 @@ Accept wildcard characters: False ``` ### -HeaderContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3382,7 +3616,6 @@ You specify the header field to search by using the HeaderContainsMessageHeader Type: Word[] 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 @@ -3392,6 +3625,9 @@ Accept wildcard characters: False ``` ### -HeaderMatchesMessageHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3402,7 +3638,6 @@ The HeaderMatchesMessageHeader parameter specifies the name of header field in t Type: HeaderName 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 @@ -3412,6 +3647,9 @@ Accept wildcard characters: False ``` ### -HeaderMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3424,7 +3662,6 @@ You specify the header field to search by using the HeaderMatchesMessageHeader p Type: Pattern[] 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 @@ -3434,6 +3671,9 @@ Accept wildcard characters: False ``` ### -IncidentReportContent + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3461,7 +3701,6 @@ You use this parameter with the GenerateIncidentReport parameter. Type: IncidentReportContent[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3471,6 +3710,9 @@ Accept wildcard characters: False ``` ### -IncidentReportOriginalMail + +> Applicable: Exchange Server 2013 + This parameter is available only in Exchange Server 2013. This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail. @@ -3488,7 +3730,6 @@ The IncidentReportOriginalMail parameter specifies whether to include the origin Type: IncidentReportOriginalMail Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013 Required: False Position: Named @@ -3498,6 +3739,9 @@ Accept wildcard characters: False ``` ### -LogEventText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -3516,7 +3760,6 @@ The entry contains the following information: Type: EventLogText 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 @@ -3526,6 +3769,9 @@ Accept wildcard characters: False ``` ### -ManagerAddresses + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3547,7 +3793,6 @@ You specify if you want to look for these users as managers of senders or recipi Type: RecipientIdParameter[] 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 @@ -3557,6 +3802,9 @@ Accept wildcard characters: False ``` ### -ManagerForEvaluatedUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3572,7 +3820,6 @@ You specify the users to look for by using the ManagerAddresses parameter. Type: EvaluatedUser 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 @@ -3582,6 +3829,9 @@ Accept wildcard characters: False ``` ### -MessageContainsDataClassifications + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. @@ -3600,7 +3850,6 @@ You can specify the notification options by using the NotifySender parameter. Type: Hashtable[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3610,6 +3859,9 @@ Accept wildcard characters: False ``` ### -MessageSizeOver + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -3630,7 +3882,6 @@ Unqualified values are typically treated as bytes, but small values may be round Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3640,6 +3891,9 @@ Accept wildcard characters: False ``` ### -MessageTypeMatches + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3660,7 +3914,6 @@ The MessageTypeMatches parameter specifies a condition that looks for messages o Type: MessageType 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 @@ -3670,6 +3923,9 @@ 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. Valid values are: - Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs. @@ -3680,7 +3936,6 @@ The Mode parameter specifies how the rule operates. Valid values are: 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 @@ -3690,6 +3945,9 @@ Accept wildcard characters: False ``` ### -ModerateMessageByManager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3705,7 +3963,6 @@ This action only works if the sender's Manager attribute is defined. 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 @@ -3715,6 +3972,9 @@ Accept wildcard characters: False ``` ### -ModerateMessageByUser + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -3736,7 +3996,6 @@ You can't use a distribution group as a moderator. Type: RecipientIdParameter[] 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 @@ -3746,13 +4005,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Name parameter specifies the display name of the transport rule to be created. The length of the name canThe Name parameter specifies the unique name of the rule. 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, Exchange Online Protection Required: False Position: Named @@ -3762,6 +4023,9 @@ Accept wildcard characters: False ``` ### -NotifySender + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + **Note:** This parameter is functional only in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -3786,7 +4050,6 @@ This action is applicable to messages sent by internal users only. External send Type: NotifySenderType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -3796,6 +4059,9 @@ Accept wildcard characters: False ``` ### -PrependSubject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -3808,7 +4074,6 @@ Consider ending the value for this parameter with a colon (:) and a space, or at Type: SubjectPrefix 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 @@ -3818,6 +4083,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2010, 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: @@ -3832,7 +4100,6 @@ 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 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3842,6 +4109,9 @@ Accept wildcard characters: False ``` ### -Quarantine + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Edge Transport servers. @@ -3857,7 +4127,6 @@ If this action is in a rule that's not the last rule in the list, rule evaluatio 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 @@ -3867,6 +4136,9 @@ Accept wildcard characters: False ``` ### -RecipientADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3913,7 +4185,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -3923,6 +4194,9 @@ Accept wildcard characters: False ``` ### -RecipientADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3967,7 +4241,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -3977,6 +4250,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -3987,7 +4263,6 @@ The RecipientAddressContainsWords parameter specifies a condition that looks for Type: Word[] 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 @@ -3997,6 +4272,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4009,7 +4287,6 @@ This parameter works when the recipient is an individual user. This parameter do Type: Pattern[] 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 @@ -4019,6 +4296,9 @@ Accept wildcard characters: False ``` ### -RecipientAddressType + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are: @@ -4030,7 +4310,6 @@ The RecipientAddressType parameter specifies how conditions and exceptions check Type: RecipientAddressType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4040,6 +4319,9 @@ Accept wildcard characters: False ``` ### -RecipientDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4052,7 +4334,6 @@ This condition matches domains and subdomains. For example, "contoso.com" matche Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4062,6 +4343,9 @@ Accept wildcard characters: False ``` ### -RecipientInSenderList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -4070,7 +4354,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4080,6 +4363,9 @@ Accept wildcard characters: False ``` ### -RedirectMessageTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4099,7 +4385,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -4109,6 +4394,9 @@ Accept wildcard characters: False ``` ### -RejectMessageEnhancedStatusCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4125,7 +4413,6 @@ To further customize the NDR (for example, multiple languages), you need to crea Type: RejectEnhancedStatus 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 @@ -4135,6 +4422,9 @@ Accept wildcard characters: False ``` ### -RejectMessageReasonText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4155,7 +4445,6 @@ To further customize the NDR (for example, multiple languages), you need to crea Type: RejectText 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 @@ -4165,6 +4454,9 @@ Accept wildcard characters: False ``` ### -RemoveHeader + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4175,7 +4467,6 @@ The RemoveHeader parameter specifies an action that removes a header field from Type: HeaderName 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 @@ -4185,6 +4476,9 @@ Accept wildcard characters: False ``` ### -RemoveOME + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4198,7 +4492,6 @@ The RemoveOME parameter specifies an action that removes the previous version of Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4208,6 +4501,9 @@ Accept wildcard characters: False ``` ### -RemoveOMEv2 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4221,7 +4517,6 @@ The RemoveOMEv2 parameter specifies an action that removes Office 365 Message En Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4231,6 +4526,9 @@ Accept wildcard characters: False ``` ### -RemoveRMSAttachmentEncryption + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4246,7 +4544,6 @@ The RemoveRMSAttachmentEncryption parameter specifies an action that removes Mic Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4256,6 +4553,9 @@ Accept wildcard characters: False ``` ### -RouteMessageOutboundConnector + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter specifies an action or part of an action for the rule. @@ -4270,7 +4570,6 @@ The RouteMessageOutboundConnector parameter specifies an action that routes mess Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4280,6 +4579,9 @@ Accept wildcard characters: False ``` ### -RouteMessageOutboundRequireTls + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4293,7 +4595,6 @@ The RouteMessageOutboundRequireTls parameter specifies an action that uses Trans 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 @@ -4303,6 +4604,9 @@ Accept wildcard characters: False ``` ### -RuleErrorAction + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are: - Ignore: The message is sent anyway. This is the default value. @@ -4312,7 +4616,6 @@ The RuleErrorAction parameter specifies what to do if rule processing can't be c Type: RuleErrorAction Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4322,6 +4625,9 @@ Accept wildcard characters: False ``` ### -RuleSubType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RuleSubType parameter specifies the rule type. Valid values are: - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange. @@ -4331,7 +4637,6 @@ The RuleSubType parameter specifies the rule type. Valid values are: Type: RuleSubType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4341,6 +4646,9 @@ Accept wildcard characters: False ``` ### -SCLOver + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4356,7 +4664,6 @@ The rule looks for messages with an SCL value that's greater than or equal to th Type: SclValue 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 @@ -4366,6 +4673,9 @@ Accept wildcard characters: False ``` ### -SenderADAttributeContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4412,7 +4722,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Word[] 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 @@ -4422,6 +4731,9 @@ Accept wildcard characters: False ``` ### -SenderADAttributeMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4466,7 +4778,6 @@ When you specify multiple attributes, or multiple values for the same attribute, Type: Pattern[] 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 @@ -4476,6 +4787,9 @@ Accept wildcard characters: False ``` ### -SenderAddressLocation + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + 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, in on-premises Exchange the the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1). @@ -4494,7 +4808,6 @@ Message envelope searching is available only for the following conditions and ex Type: SenderAddressLocation Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4504,6 +4817,9 @@ Accept wildcard characters: False ``` ### -SenderDomainIs + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4518,7 +4834,6 @@ You can use SenderAddressLocation parameter to specify where to look for the sen Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4528,6 +4843,9 @@ Accept wildcard characters: False ``` ### -SenderInRecipientList + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -4536,7 +4854,6 @@ This parameter is reserved for internal Microsoft use. Type: Word[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -4546,6 +4863,9 @@ Accept wildcard characters: False ``` ### -SenderIpRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4564,7 +4884,6 @@ In Exchange Online, the IP address that's used during evaluation of this conditi 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 @@ -4574,6 +4893,9 @@ Accept wildcard characters: False ``` ### -SenderManagementRelationship + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4587,7 +4909,6 @@ The SenderManagementRelationship parameter specifies a condition that looks for Type: ManagementRelationship 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 @@ -4597,6 +4918,9 @@ Accept wildcard characters: False ``` ### -SentTo + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4616,7 +4940,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: RecipientIdParameter[] 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 @@ -4626,6 +4949,9 @@ Accept wildcard characters: False ``` ### -SentToMemberOf + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4647,7 +4973,6 @@ If you remove the group after you create the rule, no action is taken on message Type: RecipientIdParameter[] 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 @@ -4657,6 +4982,9 @@ Accept wildcard characters: False ``` ### -SentToScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4672,7 +5000,6 @@ The SentToScope parameter specifies a condition that looks for the location of r Type: ToUserScope 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 @@ -4682,6 +5009,9 @@ Accept wildcard characters: False ``` ### -SetAuditSeverity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available only on Mailbox servers. @@ -4697,7 +5027,6 @@ The SetAuditSeverity parameter specifies an action that sets the severity level 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 @@ -4707,6 +5036,9 @@ Accept wildcard characters: False ``` ### -SetHeaderName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4717,7 +5049,6 @@ The SetHeaderName parameter specifies an action that adds or modifies a header f Type: HeaderName 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 @@ -4727,6 +5058,9 @@ Accept wildcard characters: False ``` ### -SetHeaderValue + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4737,7 +5071,6 @@ The SetHeaderValue parameter specifies an action that adds or modifies a header Type: HeaderValue 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 @@ -4747,6 +5080,9 @@ Accept wildcard characters: False ``` ### -SetSCL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4760,7 +5096,6 @@ The SetSCL parameter specifies an action that adds or modifies the SCL value of Type: SclValue 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 @@ -4770,6 +5105,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectStatusCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -4782,7 +5120,6 @@ You can use this parameter with the SmtpRejectMessageRejectText parameter. If yo Type: RejectStatusCode 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 @@ -4792,6 +5129,9 @@ Accept wildcard characters: False ``` ### -SmtpRejectMessageRejectText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter is functional only on Edge Transport servers in on-premises Exchange. This parameter specifies an action or part of an action for the rule. @@ -4804,7 +5144,6 @@ You can use this parameter with the SmtpRejectMessageRejectStatusCode parameter. Type: RejectText 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 @@ -4814,6 +5153,9 @@ Accept wildcard characters: False ``` ### -StopRuleProcessing + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies an action or part of an action for the rule. In on-premises Exchange, this action is available on Mailbox servers and Edge Transport servers. @@ -4827,7 +5169,6 @@ The StopRuleProcessing parameter specifies an action that stops processing more 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 @@ -4837,6 +5178,9 @@ Accept wildcard characters: False ``` ### -SubjectContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4851,7 +5195,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -4861,6 +5204,9 @@ Accept wildcard characters: False ``` ### -SubjectMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4871,7 +5217,6 @@ The SubjectMatchesPatterns parameter specifies a condition that looks for text p Type: Pattern[] 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 @@ -4881,6 +5226,9 @@ Accept wildcard characters: False ``` ### -SubjectOrBodyContainsWords + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4895,7 +5243,6 @@ The maximum length of this parameter is 128 characters. Type: Word[] 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 @@ -4905,6 +5252,9 @@ Accept wildcard characters: False ``` ### -SubjectOrBodyMatchesPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available on Mailbox servers and Edge Transport servers. @@ -4915,7 +5265,6 @@ The SubjectOrBodyMatchesPatterns parameter specifies a condition that looks for Type: Pattern[] 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 @@ -4925,13 +5274,15 @@ 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 @@ -4941,6 +5292,9 @@ Accept wildcard characters: False ``` ### -WithImportance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf. In on-premises Exchange, this condition is available only on Mailbox servers. @@ -4955,7 +5309,6 @@ The WithImportance parameter specifies a condition that looks for messages with Type: Importance 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/exchange/Set-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-TransportServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md index ed3050e054..8571c2bd3b 100644 --- a/exchange/exchange-ps/exchange/Set-TransportServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-transportserver applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-TransportServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-transportserver +schema: 2.0.0 +title: Set-TransportServer --- # Set-TransportServer @@ -150,6 +151,9 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs ## 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 modify. You can use any value that uniquely identifies the server. For example: - Name @@ -161,7 +165,6 @@ The Identity parameter specifies the Transport server that you want to modify. Y Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -171,6 +174,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxAge parameter specifies the maximum duration that the per user activity statistics log files are kept. Log files older than the specified value are deleted. 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. @@ -181,7 +187,6 @@ For example, to specify 10 days for this parameter, use 10.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,6 +196,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the per user activity statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 megabyte (MB). The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -209,7 +217,6 @@ The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -219,6 +226,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size for the per user activity statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -237,7 +247,6 @@ The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -247,6 +256,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogPath parameter specifies the location of per user activity statistics log storage. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\ActiveUsersStats. @@ -258,7 +270,6 @@ Setting the value of this parameter to $null disables server statistics logging. Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -268,13 +279,15 @@ Accept wildcard characters: False ``` ### -AgentLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -284,6 +297,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -294,7 +310,6 @@ Setting the value of the AgentLogMaxAge parameter to 00:00:00 prevents the autom Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -304,6 +319,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -322,7 +340,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -332,6 +349,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -350,7 +370,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -360,13 +379,15 @@ Accept wildcard characters: False ``` ### -AgentLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -376,6 +397,9 @@ Accept wildcard characters: False ``` ### -AntispamAgentsEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Transport service on Mailbox servers and $true on Edge servers. You set this parameter by using a script. You shouldn't modify this parameter manually. @@ -384,7 +408,6 @@ You set this parameter by using a script. You shouldn't modify this parameter ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -394,6 +417,9 @@ 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`. @@ -403,7 +429,6 @@ 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 @@ -413,13 +438,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. 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 @@ -429,6 +456,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. 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. @@ -439,7 +469,6 @@ For example, to specify 25 days for this parameter, use 25.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -449,6 +478,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: @@ -467,7 +499,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -477,6 +508,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -495,7 +529,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -505,6 +538,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Connectivity @@ -516,7 +552,6 @@ Setting the value of this parameter to $null disables connectivity logging. Howe Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -526,6 +561,9 @@ Accept wildcard characters: False ``` ### -ContentConversionTracingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service on a Mailbox server or on the Edge server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows: - Administrators: Full Control @@ -536,7 +574,6 @@ The ContentConversionTracingEnabled parameter specifies whether content conversi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -546,6 +583,9 @@ Accept wildcard characters: False ``` ### -DelayNotificationTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DelayNotificationTimeout parameter specifies how long the server waits before it generates a delayed delivery status notification (DSN) message. The default value is 4 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. @@ -556,7 +596,6 @@ For example, to specify 3.5 hours for this parameter, use 03:30:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -566,13 +605,15 @@ Accept wildcard characters: False ``` ### -DnsLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -582,6 +623,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -592,7 +636,6 @@ Setting the value of the DnsLogMaxAge parameter to 00:00:00 prevents the automat Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -602,6 +645,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB. When you enter a value, qualify the value with one of the following units: @@ -620,7 +666,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -630,6 +675,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -648,7 +696,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -658,13 +705,15 @@ Accept wildcard characters: False ``` ### -DnsLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks ("). ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -674,6 +723,9 @@ 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. @@ -682,7 +734,6 @@ 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 @@ -692,13 +743,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter 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 @@ -708,6 +761,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterGuid + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used. @@ -716,7 +772,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -726,13 +781,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSProtocolOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any. ```yaml Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -742,6 +799,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. DNS servers are specified by IP address. The default value is an empty list ({}). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -754,7 +814,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the Ext Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -764,13 +823,15 @@ Accept wildcard characters: False ``` ### -ExternalIPAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Edge server or the Transport service on a Mailbox server. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -780,13 +841,15 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter 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 @@ -796,6 +859,9 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterGuid + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used. @@ -804,7 +870,6 @@ If the value of the InternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -814,6 +879,9 @@ Accept wildcard characters: False ``` ### -InternalDNSProtocolOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly. The default value is Any. @@ -822,7 +890,6 @@ The default value is Any. Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -832,6 +899,9 @@ Accept wildcard characters: False ``` ### -InternalDNSServers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address. The default value is any empty list ({}). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -844,7 +914,6 @@ If the InternalDNSAdapterGuid parameter is set, and the value of the InternalDNS Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -854,6 +923,9 @@ Accept wildcard characters: False ``` ### -IntraOrgConnectorProtocolLoggingLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connectors that are used to transmit messages between Exchange servers in the Exchange organization. Valid values for this parameter are None or Verbose. The value Verbose enables protocol logging for the connector. The value None disables protocol logging for the connector. The default value is None. When the IntraOrgConnectorProtocolLoggingLevel parameter is set to Verbose, the information is written to the Send connector protocol log specified by the SendProtocolLog parameters. @@ -862,7 +934,6 @@ Valid values for this parameter are None or Verbose. The value Verbose enables p Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -872,13 +943,15 @@ Accept wildcard characters: False ``` ### -IntraOrgConnectorSmtpMaxMessagesPerConnection + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntraOrgConnectorSmtpMaxMessagesPerConnection parameter specifies the maximum number of messages per connection limit on the implicit and invisible intra-organization Send connectors that are used to transmit messages between Exchange servers in the Exchange organization. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -888,6 +961,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: - $true: Enable IRM logging @@ -897,7 +973,6 @@ The IrmLogEnabled parameter enables logging of Information Rights Management (IR Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -907,6 +982,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. 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. @@ -917,7 +995,6 @@ The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -927,6 +1004,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -945,7 +1025,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -955,6 +1034,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -973,7 +1055,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -983,13 +1064,15 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled to $false. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -999,13 +1082,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxDeliveries + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1015,13 +1100,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxSubmissions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1031,13 +1118,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionRatePerMinute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1047,13 +1136,15 @@ Accept wildcard characters: False ``` ### -MaxOutboundConnections + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxOutboundConnections parameter specifies the maximum number of outbound connections that can be open at a time. The default value is 1000. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections. The value of the MaxOutboundConnections parameter must be greater than or equal to the value of the MaxPerDomainOutboundConnections parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1063,13 +1154,15 @@ Accept wildcard characters: False ``` ### -MaxPerDomainOutboundConnections + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 40. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections per domain. The value of the MaxPerDomainOutboundConnections parameter must be less than or equal to the value of the MaxOutboundConnections parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1079,6 +1172,9 @@ Accept wildcard characters: False ``` ### -MessageExpirationTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageExpirationTimeout parameter specifies the maximum time that a particular message can remain in a queue. If a message remains in the queue for longer than this period of time, the message is returned to the sender as a permanent failure. The default value is 2 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. @@ -1089,7 +1185,6 @@ For example, to specify 3 days for this parameter, use 3.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1099,6 +1194,9 @@ Accept wildcard characters: False ``` ### -MessageRetryInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. 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. @@ -1109,7 +1207,6 @@ For example, to specify 20 minutes for this parameter, use 00:20:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1119,13 +1216,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogEnabled parameter specifies whether message tracking is enabled. 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 @@ -1135,6 +1234,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxAge parameter specifies the message tracking log maximum file age. Log files older than the specified value are deleted. 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. @@ -1145,7 +1247,6 @@ For example, to specify 20 days for this parameter, use 20.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1155,6 +1256,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxDirectorySize parameter specifies the maximum size of the message tracking log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The maximum size of the message tracking log directory is calculated as the total size of all log files that have the same name prefix. Other files that don't follow the name prefix convention aren't counted in the total directory size calculation. Renaming old log files or copying other files into the message tracking log directory could cause the directory to exceed its specified maximum size. @@ -1179,7 +1283,6 @@ The value of the MessageTrackingLogMaxFileSize parameter must be less than or eq Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1189,6 +1292,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the message tracking log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1206,7 +1312,6 @@ The value of the MessageTrackingLogMaxFileSize parameter must be less than or eq Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1216,13 +1321,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogPath parameter specifies the location of the message tracking logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\MessageTracking. Setting the value of this parameter to $null disables message tracking. However, setting this parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true generates event log errors. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1232,13 +1339,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogSubjectLoggingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogSubjectLoggingEnabled parameter specifies whether the message subject should be included in the message tracking log. 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 @@ -1248,6 +1357,9 @@ Accept wildcard characters: False ``` ### -OutboundConnectionFailureRetryInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutboundConnectionFailureRetryInterval parameter specifies the retry interval for subsequent connection attempts to a remote server where previous connection attempts have failed. The previously failed connection attempts are controlled by the TransientFailureRetryCount and TransientFailureRetryInterval parameters. For the Transport service on a Mailbox server, the default value of the OutboundConnectionFailureRetryInterval parameter is 10 minutes. On an Edge server, 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. @@ -1258,7 +1370,6 @@ For example, to specify 15 minutes for this parameter, use 00:15:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1268,6 +1379,9 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxHeaderSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header size that can be submitted to the Pickup directory. The default value is 64 KB. When you enter a value, qualify the value with one of the following units: @@ -1285,7 +1399,6 @@ The valid input range for this parameter is from 32768 through 2147483647 bytes. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1295,13 +1408,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxMessagesPerMinute + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxMessagesPerMinute parameter specifies the maximum number of messages processed per minute by the Pickup directory and by the Replay directory. Each directory can independently process message files at the rate specified by the PickupDirectoryMaxMessagesPerMinute parameter. The default value is 100. The valid input range for this parameter is from 1 through 20000. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1311,13 +1426,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxRecipientsPerMessage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxRecipientsPerMessage parameter specifies the maximum number of recipients that can be included on an message. The default value is 100. The valid input range for this parameter is from 1 through 10000. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1327,13 +1444,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryPath parameter specifies the location of the Pickup directory. The Pickup directory is used by administrators and non-Microsoft applications to create and submit messages. The default location is %ExchangeInstallPath%TransportRoles\\Pickup. If the value of the PickupDirectoryPath parameter is set to $null, the Pickup directory is disabled. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1343,13 +1462,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. 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 @@ -1359,6 +1480,9 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\PipelineTracing. @@ -1378,7 +1502,6 @@ Pipeline tracing captures the complete contents of messages to the path specifie Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1388,13 +1511,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingSenderAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingSenderAddress parameter specifies the sender address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1404,13 +1529,15 @@ Accept wildcard characters: False ``` ### -PoisonMessageDetectionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PoisonMessageDetectionEnabled parameter specifies whether poison messages should be detected. The default value is $true. Poison messages are messages determined to be potentially harmful to the Exchange system after a server failure. Poison messages are put in the poison message queue. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1420,13 +1547,15 @@ Accept wildcard characters: False ``` ### -PoisonThreshold + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PoisonThreshold parameter specifies the number of times a message can be rejected before it's classified as a poison message. The default value is 2. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. The valid input range for this parameter is from 1 through 10. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1436,6 +1565,9 @@ Accept wildcard characters: False ``` ### -QueueMaxIdleTime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueMaxIdleTime parameter specifies the period of time an empty delivery queue can exist before the queue is removed. 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. @@ -1446,7 +1578,6 @@ For example, to specify 5 minutes for this parameter, use 00:05:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1456,6 +1587,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxAge parameter specifies the maximum age of the queue log files. Log files that are older than the specified value are deleted. The default value is 7 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. @@ -1466,7 +1600,6 @@ For example, to specify 10 days for this parameter, use 10.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1476,6 +1609,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 200 MB. When you enter a value, qualify the value with one of the following units: @@ -1494,7 +1630,6 @@ The value of the QueueLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1504,6 +1639,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxFileSize parameter specifies the maximum size of the queue log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1522,7 +1660,6 @@ The value of the QueueLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1532,13 +1669,15 @@ Accept wildcard characters: False ``` ### -QueueLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogPath parameter specifies the path of the queue log directory. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\QueueViewer. Setting the value of this parameter to $null disables queue logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1548,6 +1687,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxAge parameter specifies the maximum age of the Receive connector protocol log file. Log files that are older than the specified value are deleted. 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. @@ -1558,7 +1700,6 @@ For example, to specify 20 days for this parameter, use 20.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1568,6 +1709,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the Receive connector protocol log directory shared by all the Receive connectors that exist on the server. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -1586,7 +1730,6 @@ The value of the ReceiveProtocolLogMaxFileSize parameter must be less than or eq Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1596,6 +1739,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of the Receive connector protocol log files shared by all the Receive connectors that exist on the server. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1614,7 +1760,6 @@ The value of the ReceiveProtocolLogMaxFileSize parameter must be less than or eq Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1624,6 +1769,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogPath parameter specifies the path of the protocol log directory for all the Receive connectors that exist on the server. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\ProtocolLog\\SmtpReceive. @@ -1635,7 +1783,6 @@ Setting the value of this parameter to $null disables protocol logging for all R Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1645,13 +1792,15 @@ Accept wildcard characters: False ``` ### -RecipientValidationCacheEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientValidationCacheEnabled parameter specifies whether the recipient addresses used by transport agents, such as the Recipient Filtering agent, are cached. The default value is $true on Edge servers and $false for the Transport service on Mailbox servers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1661,13 +1810,15 @@ Accept wildcard characters: False ``` ### -ReplayDirectoryPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplayDirectoryPath parameter specifies the path of the Replay directory. The Replay directory is used to resubmit exported messages and to receive messages from foreign gateway servers. The default location is %ExchangeInstallPath%TransportRoles\\Replay. If the value of the ReplayDirectoryPath parameter is set to $null, the Replay directory is disabled. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1677,13 +1828,15 @@ Accept wildcard characters: False ``` ### -RootDropDirectoryPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1693,6 +1846,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 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. @@ -1703,7 +1859,6 @@ For example, to specify 5 days for this parameter, use 5.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1713,6 +1868,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 50 MB. When you enter a value, qualify the value with one of the following units: @@ -1731,7 +1889,6 @@ The valid input range for this parameter is from 1 through 9223372036854775807 b Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1741,6 +1898,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Routing. @@ -1752,7 +1912,6 @@ Setting the value of the RoutingTableLogPath parameter to $null disables routing Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1762,6 +1921,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxAge parameter specifies the Send connector protocol log file maximum age. Log files older than the specified value are deleted. 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. @@ -1772,7 +1934,6 @@ For example, to specify 25 days for this parameter, use 25.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1782,6 +1943,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the Send connector protocol log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 MB. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -1800,7 +1964,6 @@ The value of the SendProtocolLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1810,6 +1973,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxFileSize parameter specifies the maximum size of the Send connector protocol log files shared by all the Send connectors that exist on a server. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1828,7 +1994,6 @@ The value of the SendProtocolLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1838,6 +2003,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogPath parameter specifies the location of protocol log storage for the Send connectors. The default location depends on your version of Exchange: - Exchange 2010: The default location is %ExchangeInstallPath%TransportRoles\\Logs\\ProtocolLog\\SmtpSend. @@ -1849,7 +2017,6 @@ Setting the value of this parameter to $null disables protocol logging for all S Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1859,6 +2026,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxAge + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier. The ServerStatisticsLogMaxAge parameter specifies the maximum duration that the server statistics log files are kept. Log files older than the specified value are deleted. The default value is 30 days. @@ -1871,7 +2041,6 @@ For example, to specify 60 days for this parameter, use 60.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1881,6 +2050,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxDirectorySize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier. The ServerStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the server statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 MB. The default value is 250 MB. When you enter a value, qualify the value with one of the following: @@ -1899,7 +2071,6 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1909,6 +2080,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxFileSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier. The ServerStatisticsLogMaxFileSize parameter specifies the maximum file size for the server statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following: @@ -1927,7 +2101,6 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1937,6 +2110,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogPath + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier. The ServerStatisticsLogPath parameter specifies the location of the server statistics log. The default location depends on your version of Exchange: @@ -1950,7 +2126,6 @@ Setting the value of this parameter to $null disables server statistics logging. Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1960,13 +2135,15 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection, and the next connection attempt is controlled by the OutboundConnectionFailureRetryInterval 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 @@ -1976,6 +2153,9 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryInterval + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Transport service on a Mailbox server, the default value of the TransientFailureRetryInterval parameter is 5 minutes. On an Edge server, the default value is 10 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. @@ -1986,7 +2166,6 @@ For example, to specify 8 minutes for this parameter, use 00:08:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1996,6 +2175,9 @@ Accept wildcard characters: False ``` ### -UseDowngradedExchangeServerAuth + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled. Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there may be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required. @@ -2006,7 +2188,6 @@ If you set this parameter to $true, you also need to create a specific Receive c Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2016,13 +2197,15 @@ 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 @@ -2032,13 +2215,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2048,13 +2233,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2064,13 +2251,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2080,13 +2269,15 @@ Accept wildcard characters: False ``` ### -WlmLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-TransportService.md rename to exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md index ef182dd820..bd722014ee 100644 --- a/exchange/exchange-ps/exchange/Set-TransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-transportservice applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-TransportService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-transportservice +schema: 2.0.0 +title: Set-TransportService --- # Set-TransportService @@ -192,6 +193,9 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs ## 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 modify. You can use any value that uniquely identifies the server. For example: - Name @@ -205,7 +209,6 @@ You can't use this parameter on an Edge Transport server. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -215,6 +218,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxAge parameter specifies the maximum duration that the per user activity statistics log files are kept. Log files older than the specified value are deleted. 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. @@ -225,7 +231,6 @@ For example, to specify 10 days for this parameter, use 10.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -235,6 +240,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the per user activity statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 megabyte (MB). The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -253,7 +261,6 @@ The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -263,6 +270,9 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size for the per user activity statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -281,7 +291,6 @@ The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -291,13 +300,15 @@ Accept wildcard characters: False ``` ### -ActiveUserStatisticsLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveUserStatisticsLogPath parameter specifies the location of per user activity statistics log storage. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ActiveUsersStats. Setting the value of this parameter to $null disables server statistics logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -307,13 +318,15 @@ Accept wildcard characters: False ``` ### -AgentLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -323,6 +336,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -333,7 +349,6 @@ Setting the value of the AgentLogMaxAge parameter to 00:00:00 prevents the autom Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -343,6 +358,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -361,7 +379,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -371,6 +388,9 @@ Accept wildcard characters: False ``` ### -AgentLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -389,7 +409,6 @@ The value of the AgentLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -399,13 +418,15 @@ Accept wildcard characters: False ``` ### -AgentLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -415,6 +436,9 @@ Accept wildcard characters: False ``` ### -AntispamAgentsEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Transport service on Mailbox servers and $true on Edge Transport servers. You set this parameter by using a script. You shouldn't modify this parameter manually. @@ -423,7 +447,6 @@ You set this parameter by using a script. You shouldn't modify this parameter ma Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -433,6 +456,9 @@ 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`. @@ -442,7 +468,6 @@ 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 @@ -452,13 +477,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -468,6 +495,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. 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. @@ -478,7 +508,6 @@ For example, to specify 25 days for this parameter, use 25.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -488,6 +517,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB. When you enter a value, qualify the value with one of the following units: @@ -506,7 +538,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -516,6 +547,9 @@ Accept wildcard characters: False ``` ### -ConnectivityLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -534,7 +568,6 @@ The value of the ConnectivityLogMaxFileSize parameter must be less than or equal Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -544,13 +577,15 @@ Accept wildcard characters: False ``` ### -ConnectivityLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -560,6 +595,9 @@ Accept wildcard characters: False ``` ### -ContentConversionTracingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service on a Mailbox server or on the Edge Transport server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of email messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows: - Administrators: Full Control @@ -570,7 +608,6 @@ The ContentConversionTracingEnabled parameter specifies whether content conversi Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -580,6 +617,9 @@ Accept wildcard characters: False ``` ### -DelayNotificationTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DelayNotificationTimeout parameter specifies how long the server waits before it generates a delayed delivery status notification (DSN) message. The default value is 4 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. @@ -590,7 +630,6 @@ For example, to specify 3.5 hours for this parameter, use 03:30:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -600,13 +639,15 @@ Accept wildcard characters: False ``` ### -DnsLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -616,6 +657,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 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. @@ -626,7 +670,6 @@ Setting the value of the DnsLogMaxAge parameter to 00:00:00 prevents the automat Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -636,6 +679,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB. When you enter a value, qualify the value with one of the following units: @@ -654,7 +700,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -664,6 +709,9 @@ Accept wildcard characters: False ``` ### -DnsLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -682,7 +730,6 @@ The value of the DnsLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -692,13 +739,15 @@ Accept wildcard characters: False ``` ### -DnsLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks ("). ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -708,6 +757,9 @@ 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. @@ -716,7 +768,6 @@ 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 @@ -726,13 +777,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -742,6 +795,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSAdapterGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used. @@ -750,7 +806,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -760,13 +815,15 @@ Accept wildcard characters: False ``` ### -ExternalDNSProtocolOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any. ```yaml Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -776,6 +833,9 @@ Accept wildcard characters: False ``` ### -ExternalDNSServers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. DNS servers are specified by IP address. The default value is an empty list ({}). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -788,7 +848,6 @@ If the value of the ExternalDNSAdapterEnabled parameter is set to $true, the Ext Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -798,13 +857,15 @@ Accept wildcard characters: False ``` ### -ExternalIPAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Edge Transport server or the Transport service on a Mailbox server. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -814,13 +875,15 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -830,6 +893,9 @@ Accept wildcard characters: False ``` ### -InternalDNSAdapterGuid + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000. If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used. @@ -838,7 +904,6 @@ If the value of the InternalDNSAdapterEnabled parameter is set to $false, the va Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -848,13 +913,15 @@ Accept wildcard characters: False ``` ### -InternalDNSProtocolOption + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly.The default value is Any. ```yaml Type: ProtocolOption Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -864,6 +931,9 @@ Accept wildcard characters: False ``` ### -InternalDNSServers + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address. The default value is any empty list ({}). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -876,7 +946,6 @@ If the InternalDNSAdapterGuid parameter is set, and the value of the InternalDNS Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -886,6 +955,9 @@ Accept wildcard characters: False ``` ### -IntraOrgConnectorProtocolLoggingLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible intra-organization Send connector in the following transport services on the server: - The Transport service. @@ -900,7 +972,6 @@ Valid values are: Type: ProtocolLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -910,6 +981,9 @@ Accept wildcard characters: False ``` ### -IntraOrgConnectorSmtpMaxMessagesPerConnection + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IntraOrgConnectorSmtpMaxMessagesPerConnection parameter specifies the maximum number of messages per connection that are allowed on the implicit and invisible intra-organization Send connector in the Transport service on the server. A valid value is an integer from 0 to 2147483647. The default value is 20. @@ -918,7 +992,6 @@ A valid value is an integer from 0 to 2147483647. The default value is 20. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -928,6 +1001,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: - $true: Enable IRM logging @@ -937,7 +1013,6 @@ The IrmLogEnabled parameter enables logging of Information Rights Management (IR Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -947,6 +1022,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. 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. @@ -957,7 +1035,6 @@ The valid input range for this parameter is 00:00:00 to 24855.03:14:07. Setting Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -967,6 +1044,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB. When you enter a value, qualify the value with one of the following units: @@ -985,7 +1065,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -995,6 +1074,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1013,7 +1095,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1023,13 +1104,15 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled to $false. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1039,13 +1122,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxDeliveries + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1055,13 +1140,15 @@ Accept wildcard characters: False ``` ### -MaxConcurrentMailboxSubmissions + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1071,13 +1158,15 @@ Accept wildcard characters: False ``` ### -MaxConnectionRatePerMinute + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1087,13 +1176,15 @@ Accept wildcard characters: False ``` ### -MaxOutboundConnections + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxOutboundConnections parameter specifies the maximum number of outbound connections that can be open at a time. The default value is 1000. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections. The value of the MaxOutboundConnections parameter must be greater than or equal to the value of the MaxPerDomainOutboundConnections parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1103,13 +1194,15 @@ Accept wildcard characters: False ``` ### -MaxPerDomainOutboundConnections + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 40. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections per domain. The value of the MaxPerDomainOutboundConnections parameter must be less than or equal to the value of the MaxOutboundConnections parameter. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1119,6 +1212,9 @@ Accept wildcard characters: False ``` ### -MessageExpirationTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageExpirationTimeout parameter specifies the maximum time that a particular message can remain in a queue. If a message remains in the queue for longer than this period of time, the message is returned to the sender as a permanent failure. The default value is 2 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. @@ -1129,7 +1225,6 @@ For example, to specify 3 days for this parameter, use 3.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1139,6 +1234,9 @@ Accept wildcard characters: False ``` ### -MessageRetryInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. 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. @@ -1149,7 +1247,6 @@ For example, to specify 20 minutes for this parameter, use 00:20:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1159,13 +1256,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogEnabled parameter specifies whether message tracking is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1175,6 +1274,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxAge parameter specifies the message tracking log maximum file age. Log files older than the specified value are deleted. 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. @@ -1185,7 +1287,6 @@ For example, to specify 20 days for this parameter, use 20.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1195,6 +1296,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxDirectorySize parameter specifies the maximum size of the message tracking log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The maximum size of the message tracking log directory is calculated as the total size of all log files that have the same name prefix. Other files that don't follow the name prefix convention aren't counted in the total directory size calculation. Renaming old log files or copying other files into the message tracking log directory could cause the directory to exceed its specified maximum size. @@ -1219,7 +1323,6 @@ The value of the MessageTrackingLogMaxFileSize parameter must be less than or eq Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1229,6 +1332,9 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the message tracking log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1246,7 +1352,6 @@ The value of the MessageTrackingLogMaxFileSize parameter must be less than or eq Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1256,13 +1361,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogPath parameter specifies the location of the message tracking logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\MessageTracking. Setting the value of this parameter to $null disables message tracking. However, setting this parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true generates event log errors. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1272,13 +1379,15 @@ Accept wildcard characters: False ``` ### -MessageTrackingLogSubjectLoggingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MessageTrackingLogSubjectLoggingEnabled parameter specifies whether the message subject should be included in the message tracking log. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1288,6 +1397,9 @@ Accept wildcard characters: False ``` ### -OutboundConnectionFailureRetryInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutboundConnectionFailureRetryInterval parameter specifies the retry interval for subsequent connection attempts to a remote server where previous connection attempts have failed. The previously failed connection attempts are controlled by the TransientFailureRetryCount and TransientFailureRetryInterval parameters. For the Transport service on a Mailbox server, the default value of the OutboundConnectionFailureRetryInterval parameter is 10 minutes. On an Edge Transport server, 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. @@ -1298,7 +1410,6 @@ For example, to specify 15 minutes for this parameter, use 00:15:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1308,6 +1419,9 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxHeaderSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header size that can be submitted to the Pickup directory. The default value is 64 KB. When you enter a value, qualify the value with one of the following units: @@ -1325,7 +1439,6 @@ The valid input range for this parameter is from 32768 through 2147483647 bytes. Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1335,13 +1448,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxMessagesPerMinute + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxMessagesPerMinute parameter specifies the maximum number of messages processed per minute by the Pickup directory and by the Replay directory. Each directory can independently process message files at the rate specified by the PickupDirectoryMaxMessagesPerMinute parameter. The default value is 100. The valid input range for this parameter is from 1 through 20000. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1351,13 +1466,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryMaxRecipientsPerMessage + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryMaxRecipientsPerMessage parameter specifies the maximum number of recipients that can be included on an email message. The default value is 100. The valid input range for this parameter is from 1 through 10000. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1367,13 +1484,15 @@ Accept wildcard characters: False ``` ### -PickupDirectoryPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PickupDirectoryPath parameter specifies the location of the Pickup directory. The Pickup directory is used by administrators and non-Microsoft applications to create and submit messages. The default location is %ExchangeInstallPath%TransportRoles\\Pickup. If the value of the PickupDirectoryPath parameter is set to $null, the Pickup directory is disabled. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1383,13 +1502,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1399,6 +1520,9 @@ Accept wildcard characters: False ``` ### -PipelineTracingPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\PipelineTracing. The path must be local to the Exchange server. Setting the value of this parameter to $null disables pipeline tracing. However, setting this parameter to $null when the value of the PipelineTracingEnabled attribute is $true generates event log errors. The preferred method to disable pipeline tracing is to use the PipelineTracingEnabled parameter. @@ -1413,7 +1537,6 @@ Pipeline tracing captures the complete contents of email messages to the path sp Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1423,13 +1546,15 @@ Accept wildcard characters: False ``` ### -PipelineTracingSenderAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1439,13 +1564,15 @@ Accept wildcard characters: False ``` ### -PoisonMessageDetectionEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PoisonMessageDetectionEnabled parameter specifies whether poison messages should be detected. The default value is $true. Poison messages are messages determined to be potentially harmful to the Exchange system after a server failure. Poison messages are put in the poison message queue. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1455,13 +1582,15 @@ Accept wildcard characters: False ``` ### -PoisonThreshold + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PoisonThreshold parameter specifies the number of times a message can be rejected before it's classified as a poison message. The default value is 2. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. The valid input range for this parameter is from 1 through 10. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1471,6 +1600,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxAge parameter specifies the maximum age of the queue log files. Log files that are older than the specified value are deleted. The default value is 7 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. @@ -1481,7 +1613,6 @@ For example, to specify 10 days for this parameter, use 10.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1491,6 +1622,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 200 MB. When you enter a value, qualify the value with one of the following units: @@ -1509,7 +1643,6 @@ The value of the QueueLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1519,6 +1652,9 @@ Accept wildcard characters: False ``` ### -QueueLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogMaxFileSize parameter specifies the maximum size of the queue log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -1537,7 +1673,6 @@ The value of the QueueLogMaxFileSize parameter must be less than or equal to the Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1547,13 +1682,15 @@ Accept wildcard characters: False ``` ### -QueueLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueLogPath parameter specifies the path of the queue log directory. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\QueueViewer. Setting the value of this parameter to $null disables queue logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1563,6 +1700,9 @@ Accept wildcard characters: False ``` ### -QueueMaxIdleTime + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The QueueMaxIdleTime parameter specifies the period of time an empty delivery queue can exist before the queue is removed. 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. @@ -1573,7 +1713,6 @@ For example, to specify 5 minutes for this parameter, use 00:05:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1583,6 +1722,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Receive connectors in the Transport service on the server. Log files that are older than the specified value are automatically deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1595,7 +1737,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1605,6 +1746,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Receive connectors in the Transport service on the server. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -1627,7 +1771,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1637,6 +1780,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Receive connectors in the Transport on the server. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -1659,7 +1805,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1669,6 +1814,9 @@ Accept wildcard characters: False ``` ### -ReceiveProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for all Receive connectors in the Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpReceive. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for any Receive connector in the Transport service. To disable protocol logging for these Receive connectors, use the value None for the ProtocolLoggingLevel parameter on the Set-ReceiveConnector cmdlet for each Receive connector in the Transport service. @@ -1677,7 +1825,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1687,13 +1834,15 @@ Accept wildcard characters: False ``` ### -RecipientValidationCacheEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RecipientValidationCacheEnabled parameter specifies whether the recipient addresses used by transport agents, such as the Recipient Filtering agent, are cached. The default value is $true on Edge Transport servers and $false for the Transport service on Mailbox servers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1703,13 +1852,15 @@ Accept wildcard characters: False ``` ### -ReplayDirectoryPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ReplayDirectoryPath parameter specifies the path of the Replay directory. The Replay directory is used to resubmit exported messages and to receive messages from foreign gateway servers. The default location is %ExchangeInstallPath%TransportRoles\\Replay. If the value of the ReplayDirectoryPath parameter is set to $null, the Replay directory is disabled. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1719,13 +1870,15 @@ Accept wildcard characters: False ``` ### -RequestBrokerLogEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1735,13 +1888,15 @@ Accept wildcard characters: False ``` ### -RequestBrokerLogMaxAge + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1751,13 +1906,15 @@ Accept wildcard characters: False ``` ### -RequestBrokerLogMaxDirectorySize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1767,13 +1924,15 @@ Accept wildcard characters: False ``` ### -RequestBrokerLogMaxFileSize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1783,13 +1942,15 @@ Accept wildcard characters: False ``` ### -RequestBrokerLogPath + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1799,13 +1960,15 @@ Accept wildcard characters: False ``` ### -ResourceLogEnabled + +> 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 @@ -1815,13 +1978,15 @@ Accept wildcard characters: False ``` ### -ResourceLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1831,13 +1996,15 @@ Accept wildcard characters: False ``` ### -ResourceLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1847,13 +2014,15 @@ Accept wildcard characters: False ``` ### -ResourceLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -1863,13 +2032,15 @@ Accept wildcard characters: False ``` ### -ResourceLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1879,13 +2050,15 @@ Accept wildcard characters: False ``` ### -RootDropDirectoryPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1895,6 +2068,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 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. @@ -1905,7 +2081,6 @@ For example, to specify 5 days for this parameter, use 5.00:00:00. The valid inp Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1915,6 +2090,9 @@ Accept wildcard characters: False ``` ### -RoutingTableLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 50 MB. When you enter a value, qualify the value with one of the following units: @@ -1933,7 +2111,6 @@ The valid input range for this parameter is from 1 through 9223372036854775807 b Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1943,13 +2120,15 @@ Accept wildcard characters: False ``` ### -RoutingTableLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\Routing. Setting the value of the RoutingTableLogPath parameter to $null disables routing table logging. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1959,6 +2138,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Send connectors in the Transport service that have this server configured as a source server. Log files that are older than the specified value are automatically deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds. @@ -1971,7 +2153,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1981,6 +2162,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Send connectors in the Transport service that have this server configured as a source server. When the maximum directory size is reached, the server deletes the oldest log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -2003,7 +2187,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2013,6 +2196,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Send connectors in the Transport service that have this server configured as a source server. When a log file reaches its maximum file size, a new log file is created. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 10 megabytes (10485760 bytes). @@ -2035,7 +2221,6 @@ This parameter is only meaningful when protocol logging is enabled for at least Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2045,6 +2230,9 @@ Accept wildcard characters: False ``` ### -SendProtocolLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SendProtocolLogPath parameter specifies the location of the protocol log directory for all Send connectors in the Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpSend. Don't use the value $null for this parameter, because event log errors are generated if protocol logging is enabled for any Send connector in the Transport service that has this server configured as a source server. To disable protocol logging for these Send connectors, use the value None for the following parameters: @@ -2056,7 +2244,6 @@ Don't use the value $null for this parameter, because event log errors are gener Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2066,6 +2253,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2013 CU6 or earlier. The ServerStatisticsLogMaxAge parameter specifies the maximum duration that the server statistics log files are kept. Log files older than the specified value are deleted. The default value is 30 days. @@ -2078,7 +2268,6 @@ For example, to specify 60 days for this parameter, use 60.00:00:00. The valid i Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2088,6 +2277,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2013 CU6 or earlier. The ServerStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the server statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 MB. The default value is 250 MB. @@ -2108,7 +2300,6 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2118,6 +2309,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2013 CU6 or earlier. The ServerStatisticsLogMaxFileSize parameter specifies the maximum file size for the server statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. @@ -2138,7 +2332,6 @@ The value of the ServerStatisticsLogMaxFileSize parameter must be less than or e Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2148,6 +2341,9 @@ Accept wildcard characters: False ``` ### -ServerStatisticsLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2013 CU6 or earlier. The ServerStatisticsLogPath parameter specifies the location of server statistics log storage. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ServerStats. Setting the value of this parameter to $null disables server statistics logging. @@ -2156,7 +2352,6 @@ The ServerStatisticsLogPath parameter specifies the location of server statistic Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2166,13 +2361,15 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryCount + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection, and the next connection attempt is controlled by the OutboundConnectionFailureRetryInterval parameter. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2182,6 +2379,9 @@ Accept wildcard characters: False ``` ### -TransientFailureRetryInterval + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Transport service on a Mailbox server, the default value of the TransientFailureRetryInterval parameter is 5 minutes. On an Edge Transport server, the default value is 10 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. @@ -2192,7 +2392,6 @@ For example, to specify 8 minutes for this parameter, use 00:08:00. The valid in Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2202,13 +2401,15 @@ Accept wildcard characters: False ``` ### -TransportHttpLogEnabled + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2218,13 +2419,15 @@ Accept wildcard characters: False ``` ### -TransportHttpLogMaxAge + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2234,13 +2437,15 @@ Accept wildcard characters: False ``` ### -TransportHttpLogMaxDirectorySize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2250,13 +2455,15 @@ Accept wildcard characters: False ``` ### -TransportHttpLogMaxFileSize + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2266,13 +2473,15 @@ Accept wildcard characters: False ``` ### -TransportHttpLogPath + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2282,13 +2491,15 @@ Accept wildcard characters: False ``` ### -TransportMaintenanceLogEnabled + +> 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 @@ -2298,13 +2509,15 @@ Accept wildcard characters: False ``` ### -TransportMaintenanceLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2314,13 +2527,15 @@ Accept wildcard characters: False ``` ### -TransportMaintenanceLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2330,13 +2545,15 @@ Accept wildcard characters: False ``` ### -TransportMaintenanceLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2346,13 +2563,15 @@ Accept wildcard characters: False ``` ### -TransportMaintenanceLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2362,13 +2581,15 @@ Accept wildcard characters: False ``` ### -TransportSyncAccountsPoisonAccountThreshold + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2378,13 +2599,15 @@ Accept wildcard characters: False ``` ### -TransportSyncAccountsPoisonDetectionEnabled + +> 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 @@ -2394,13 +2617,15 @@ Accept wildcard characters: False ``` ### -TransportSyncAccountsPoisonItemThreshold + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2410,13 +2635,15 @@ Accept wildcard characters: False ``` ### -TransportSyncAccountsSuccessivePoisonItemThreshold + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2426,13 +2653,15 @@ Accept wildcard characters: False ``` ### -TransportSyncEnabled + +> 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 @@ -2442,13 +2671,15 @@ Accept wildcard characters: False ``` ### -TransportSyncExchangeEnabled + +> 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 @@ -2458,13 +2689,15 @@ Accept wildcard characters: False ``` ### -TransportSyncHubHealthLogEnabled + +> 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 @@ -2474,13 +2707,15 @@ Accept wildcard characters: False ``` ### -TransportSyncHubHealthLogFilePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2490,13 +2725,15 @@ Accept wildcard characters: False ``` ### -TransportSyncHubHealthLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2506,13 +2743,15 @@ Accept wildcard characters: False ``` ### -TransportSyncHubHealthLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2522,13 +2761,15 @@ Accept wildcard characters: False ``` ### -TransportSyncHubHealthLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2538,13 +2779,15 @@ Accept wildcard characters: False ``` ### -TransportSyncImapEnabled + +> 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 @@ -2554,13 +2797,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogEnabled + +> 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 @@ -2570,13 +2815,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogFilePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2586,13 +2833,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogLoggingLevel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SyncLogLoggingLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2602,13 +2851,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2618,13 +2869,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2634,13 +2887,15 @@ Accept wildcard characters: False ``` ### -TransportSyncLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2650,13 +2905,15 @@ Accept wildcard characters: False ``` ### -TransportSyncMaxDownloadItemsPerConnection + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2666,13 +2923,15 @@ Accept wildcard characters: False ``` ### -TransportSyncMaxDownloadSizePerConnection + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2682,13 +2941,15 @@ Accept wildcard characters: False ``` ### -TransportSyncMaxDownloadSizePerItem + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2698,13 +2959,15 @@ Accept wildcard characters: False ``` ### -TransportSyncPopEnabled + +> 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 @@ -2714,13 +2977,15 @@ Accept wildcard characters: False ``` ### -TransportSyncRemoteConnectionTimeout + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2730,6 +2995,9 @@ Accept wildcard characters: False ``` ### -UseDowngradedExchangeServerAuth + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled. Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there may be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required. @@ -2740,7 +3008,6 @@ If you set this parameter to $true, you also need to create a specific Receive c Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2750,13 +3017,15 @@ 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 @@ -2766,13 +3035,15 @@ Accept wildcard characters: False ``` ### -WindowsLiveHotmailTransportSyncEnabled + +> 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 @@ -2782,13 +3053,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -2798,13 +3071,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2814,13 +3089,15 @@ Accept wildcard characters: False ``` ### -WlmLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + 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 Required: False Position: Named @@ -2830,13 +3107,15 @@ Accept wildcard characters: False ``` ### -WlmLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-UMAutoAttendant.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md index c224bb9dc4..4a670e124f 100644 --- a/exchange/exchange-ps/exchange/Set-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umautoattendant applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMAutoAttendant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umautoattendant +schema: 2.0.0 +title: Set-UMAutoAttendant --- # Set-UMAutoAttendant @@ -102,13 +103,15 @@ This example configures the UM auto attendant MyAutoAttendant and enables busine ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM auto attendant being viewed. This parameter 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: True Position: 1 @@ -118,6 +121,9 @@ Accept wildcard characters: False ``` ### -AfterHoursKeyMapping + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursKeyMapping parameter specifies the key mappings to be used for after business hours for the UM auto attendant. A key mapping is defined as an entry in a table that has as many as 9 entries. The 0 key is reserved for a transfer to the operator. The following is an example for a custom table that has two entries: @@ -130,7 +136,6 @@ The default value is disabled. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -140,6 +145,9 @@ Accept wildcard characters: False ``` ### -AfterHoursKeyMappingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursKeyMappingEnabled parameter specifies whether to enable or disable key mappings for after business hours for the UM auto attendant. A key mapping is defined as an entry in a table that has as many as 9 entries. The 0 key is reserved for a transfer to the operator. The following is an example for a custom table that has two entries: @@ -150,7 +158,6 @@ The following is an example for a custom table that has two entries: Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -160,13 +167,15 @@ Accept wildcard characters: False ``` ### -AfterHoursMainMenuCustomPromptEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursMainMenuCustomPromptEnabled parameter specifies whether the after business hours custom main menu is enabled. The default value is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -176,13 +185,15 @@ Accept wildcard characters: False ``` ### -AfterHoursMainMenuCustomPromptFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursMainMenuCustomPromptFilename parameter specifies the .wav file to be used for the after business hours custom main menu prompt. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -192,13 +203,15 @@ Accept wildcard characters: False ``` ### -AfterHoursTransferToOperatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursTransferToOperatorEnabled parameter specifies whether to allow calls to be transferred to the operator's extension number after business hours. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -208,13 +221,15 @@ Accept wildcard characters: False ``` ### -AfterHoursWelcomeGreetingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursWelcomeGreetingEnabled parameter specifies whether the after hours greeting is enabled. The system default audio is used if this parameter is set to disabled. The default value is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -224,13 +239,15 @@ Accept wildcard characters: False ``` ### -AfterHoursWelcomeGreetingFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AfterHoursWelcomeGreetingFilename parameter specifies the .wav file to be used for the after hours greeting message. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -240,13 +257,15 @@ Accept wildcard characters: False ``` ### -AllowDialPlanSubscribers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowDialPlanSubscribers parameter specifies whether to allow the dial plan subscribers to dial numbers that are resolved to a subscriber in the same dial plan. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -256,13 +275,15 @@ Accept wildcard characters: False ``` ### -AllowedInCountryOrRegionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInCountryOrRegionGroups parameter specifies the list of in-country/region dial group names allowed. The names must match group names defined in the dial plan. The string must have fewer than 128 characters. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -272,13 +293,15 @@ Accept wildcard characters: False ``` ### -AllowedInternationalGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInternationalGroups parameter specifies the list of international dial group names allowed. The names must match group names defined in the dial plan. The string must have fewer than 128 characters. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -288,13 +311,15 @@ Accept wildcard characters: False ``` ### -AllowExtensions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowExtensions parameter specifies whether callers can make calls to extensions that have the same number of digits as the number specified on the dial plan object. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -304,6 +329,9 @@ Accept wildcard characters: False ``` ### -BusinessHoursKeyMapping + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursKeyMapping parameter specifies the key mappings for business hours for the UM auto attendant. A key mapping is defined as an entry in a table that has as many as 9 entries. The 0 key is reserved for a transfer to the operator. The following is an example for a custom table that has two entries: @@ -316,7 +344,6 @@ The default is disabled. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -326,13 +353,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursKeyMappingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursKeyMappingEnabled parameter specifies whether the custom menus for business hours are enabled or disabled. The default value is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -342,13 +371,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursMainMenuCustomPromptEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursMainMenuCustomPromptEnabled parameter specifies whether the business hours custom main menu prompt is enabled. The default value is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -358,13 +389,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursMainMenuCustomPromptFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursMainMenuCustomPromptFilename parameter specifies the .wav file to be used for the business hours custom main menu prompt. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -374,6 +407,9 @@ Accept wildcard characters: False ``` ### -BusinessHoursSchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursSchedule parameter specifies the hours the business is open. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can specify multiple schedules separated by commas: `"Schedule1","Schedule2",..."ScheduleN"`. @@ -401,7 +437,6 @@ Here are some examples: Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -411,13 +446,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursTransferToOperatorEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursTransferToOperatorEnabled parameter specifies whether to allow call transfers to the operator's extension number during business hours. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -427,13 +464,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursWelcomeGreetingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursWelcomeGreetingEnabled parameter specifies whether the custom business hours greeting is enabled. The system default audio is used if this parameter is set to disabled. The default value is disabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -443,13 +482,15 @@ Accept wildcard characters: False ``` ### -BusinessHoursWelcomeGreetingFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessHoursWelcomeGreetingFilename parameter specifies the .wav file to be used for the welcome message. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -459,13 +500,15 @@ Accept wildcard characters: False ``` ### -BusinessLocation + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessLocation parameter specifies what the Mailbox server should read to the caller who selected the business location option on a UM auto attendant menu. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -475,13 +518,15 @@ Accept wildcard characters: False ``` ### -BusinessName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The BusinessName parameter specifies the name of the company or organization being used to generate the UM auto attendant welcome greeting for callers. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -491,13 +536,15 @@ Accept wildcard characters: False ``` ### -CallSomeoneEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CallSomeoneEnabled parameter specifies whether the Call Someone feature is enabled. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -507,6 +554,9 @@ 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`. @@ -516,7 +566,6 @@ 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 @@ -526,13 +575,15 @@ Accept wildcard characters: False ``` ### -ContactAddressList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactAddressList parameter specifies the identity of the address list. If the ContactScope parameter is set to AddressList, this parameter defines the scope for directory searches. ```yaml Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -542,13 +593,15 @@ Accept wildcard characters: False ``` ### -ContactRecipientContainer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactRecipientContainer parameter specifies the name or identity of the container used for directory searches. ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -558,13 +611,15 @@ Accept wildcard characters: False ``` ### -ContactScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactScope parameter specifies the scope of the directory search given to callers when they access the UM auto attendant and specify a user's name. ```yaml Type: DialScopeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -574,13 +629,15 @@ 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 @@ -590,13 +647,15 @@ Accept wildcard characters: False ``` ### -DTMFFallbackAutoAttendant + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DTMFFallbackAutoAttendant parameter specifies the dual tone multi-frequency (DTMF) auto attendant used if the speech-enabled auto attendant is unavailable. If the SpeechEnabled parameter is set to $true, this auto attendant must have an associated DTMF auto attendant to use as the fallback auto attendant. ```yaml Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -606,13 +665,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 Required: False Position: Named @@ -622,6 +683,9 @@ Accept wildcard characters: False ``` ### -HolidaySchedule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The HolidaySchedule parameter specifies the holiday schedule for the organization. The schedule is formatted as an array of strings. Each string contains three parts: - Name, which is limited to 64 characters @@ -636,7 +700,6 @@ The following is an example: Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -646,13 +709,15 @@ Accept wildcard characters: False ``` ### -InfoAnnouncementEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InfoAnnouncementEnabled parameter specifies whether to enable the informational greeting. The default setting is $true. ```yaml Type: InfoAnnouncementEnabledEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -662,13 +727,15 @@ Accept wildcard characters: False ``` ### -InfoAnnouncementFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InfoAnnouncementFilename parameter specifies the .wav file to be used for the informational announcement. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -678,13 +745,15 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Language parameter specifies the language used by the UM auto attendant. This language is selected from the list of available dial plan languages. ```yaml Type: UMLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -694,6 +763,9 @@ Accept wildcard characters: False ``` ### -MatchedNameSelectionMethod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MatchedNameSelectionMethod parameter specifies the selection to use to differentiate between users who have names that match the touchtone or speech input. This setting can be set to the following: - Department @@ -707,7 +779,6 @@ The MatchedNameSelectionMethod parameter specifies the selection to use to diffe Type: AutoAttendantDisambiguationFieldEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -717,13 +788,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name to be used for the UM auto attendant. This name is limited to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -733,13 +806,15 @@ Accept wildcard characters: False ``` ### -NameLookupEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The NameLookupEnabled parameter specifies whether to allow callers to perform directory lookups by dialing the name or by speaking the name. This parameter can prevent callers from connecting to unknown extensions. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -749,13 +824,15 @@ Accept wildcard characters: False ``` ### -OperatorExtension + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The OperatorExtension parameter specifies the extension number of the operator. If this parameter isn't specified, the dial plan operator is used. If the dial plan operator isn't specified, the feature isn't enabled. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -765,13 +842,15 @@ Accept wildcard characters: False ``` ### -PilotIdentifierList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PilotIdentifierList parameter specifies a list of one or more pilot numbers. Pilot numbers are used to route incoming calls to Mailbox servers. The calls are then answered by the UM auto attendant. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -781,13 +860,15 @@ Accept wildcard characters: False ``` ### -SendVoiceMsgEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SendVoiceMsgEnabled parameter specifies whether to allow the Send Message feature. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -797,13 +878,15 @@ Accept wildcard characters: False ``` ### -SpeechEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SpeechEnabled parameter specifies whether the auto attendant is speech-enabled. The default setting on the UM auto attendant is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -813,13 +896,15 @@ Accept wildcard characters: False ``` ### -Timezone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Timezone parameter specifies the time zone used with the auto attendant. The default time zone is the time zone setting on the server. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -829,13 +914,15 @@ Accept wildcard characters: False ``` ### -Timezone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Timezone parameter specifies the time zone used with the auto attendant. The default time zone is the time zone setting on the server. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -845,13 +932,15 @@ Accept wildcard characters: False ``` ### -TimeZoneName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TimeZoneName parameter specifies all or part of a MicrosoftWindows time zone display name. The string is compared to the display names in the local system registry to determine a simple contains match. An error is returned if the time zone name isn't correct. ```yaml Type: UMTimeZone Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -861,13 +950,15 @@ Accept wildcard characters: False ``` ### -WeekStartDay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The WeekStartDay parameter specifies the starting day of the week. The valid values for this parameter are Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, and Saturday. ```yaml Type: DayOfWeek Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -877,13 +968,15 @@ 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/exchange/Set-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md index f5a3f24afa..2337a77645 100644 --- a/exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umcallansweringrule applicable: Exchange Server 2013, Exchange Server 2016 -title: Set-UMCallAnsweringRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umcallansweringrule +schema: 2.0.0 +title: Set-UMCallAnsweringRule --- # Set-UMCallAnsweringRule @@ -121,13 +122,15 @@ This example sets a custom period for the time of day on the call answering rule ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for a call answering rule being changed. ```yaml Type: UMCallAnsweringRuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -137,13 +140,15 @@ Accept wildcard characters: False ``` ### -CallerIds + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CallerIds parameter specifies an entry for the "If the Caller is" condition. Each entry for this parameter can contain a phone number, an Active Directory contact, a personal contact, or the personal Contacts folder. The parameter can contain 50 phone numbers or contact entries and no more than one entry for specifying the default Contacts folder. If the CallerIds parameter doesn't contain a condition, the condition isn't set and is ignored. The default value is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -153,13 +158,15 @@ Accept wildcard characters: False ``` ### -CallersCanInterruptGreeting + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CallersCanInterruptGreeting parameter specifies whether a caller can interrupt the voice mail greeting while it's being played. The default is $null. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -169,13 +176,15 @@ Accept wildcard characters: False ``` ### -CheckAutomaticReplies + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CheckAutomaticReplies parameter specifies an entry for the "If My Automatic Replies are Enabled" condition. The default is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -185,6 +194,9 @@ 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`. @@ -194,7 +206,6 @@ 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 @@ -204,13 +215,15 @@ 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 @@ -220,13 +233,15 @@ Accept wildcard characters: False ``` ### -ExtensionsDialed + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The ExtensionsDialed parameter specifies an entry for the "If the Caller Dials" condition. Each entry must be unique per call answering rule. Each extension must correspond to existing extension numbers assigned to UM-enabled users. The default is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -236,13 +251,15 @@ Accept wildcard characters: False ``` ### -KeyMappings + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The KeyMappings parameter specifies a key mapping entry for a call answering rule. The key mappings are those menu options offered to callers if the call answering rule is set to $true. You can configure a maximum of 10 entries. None of the defined key mappings can overlap. The default is $null. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -252,6 +269,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Mailbox parameter specifies the UM-enabled mailbox where the call answering rule will be changed. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -271,7 +291,6 @@ 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 @@ -281,13 +300,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the name of the UM call answering rule or Call Answering Rule ID being modified. The call answering ID or name must be unique per the user's UM-enabled mailbox. The name or ID for the call answering rule can contain up to 255 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -297,13 +318,15 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The Priority parameter specified the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -313,6 +336,9 @@ Accept wildcard characters: False ``` ### -ScheduleStatus + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The ScheduleStatus parameter specifies an entry for the "If my Schedule show that I am" condition. Users can specify their free/busy status to be checked. This parameter can be set from 0 through 15 and is interpreted as a 4-bit mask that represents the calendar status including Free, Tentative, Busy and Out of Office. The following settings can be used to set the schedule status: - None = 0x0 @@ -327,7 +353,6 @@ The default setting is $null. Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -337,13 +362,15 @@ Accept wildcard characters: False ``` ### -TimeOfDay + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The TimeOfDay parameter specifies an entry for the "If the Call Arrives During" condition for the call answering rule. You can specify working hours, non-working hours or custom hours. The default is $null. ```yaml Type: TimeOfDay Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -353,13 +380,15 @@ 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/exchange/Set-UMCallRouterSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md index e2d42d19d4..0fa3809edf 100644 --- a/exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umcallroutersettings applicable: Exchange Server 2013, Exchange Server 2016 -title: Set-UMCallRouterSettings -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umcallroutersettings +schema: 2.0.0 +title: Set-UMCallRouterSettings --- # Set-UMCallRouterSettings @@ -62,6 +63,9 @@ This example removes the Exchange server named UMCallRouter001 from all UM SIP d ## 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 @@ -75,7 +79,6 @@ 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 @@ -85,6 +88,9 @@ 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`. @@ -94,7 +100,6 @@ 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 @@ -104,6 +109,9 @@ Accept wildcard characters: False ``` ### -DialPlans + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The DialPlans parameter specifies the dial plan used by the Microsoft Exchange Unified Messaging Call Router service. The Exchange server only needs to be associated with a UM dial plan if Lync Server 2010, Lync Server 2013, or Skype for Business Server 2015 is used in your organization. To remove an Exchange server from a dial plan, use $null. The default is no dial plans assigned. To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -114,7 +122,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -124,13 +131,15 @@ 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 @@ -140,13 +149,15 @@ Accept wildcard characters: False ``` ### -IPAddressFamily + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. If set to IPv4Only, the UM IP gateway only uses IPv4 to communicate. If set to IPv6Only, the UM IP gateway only uses IPv6. If set to Any, IPv6 is used first, and then if necessary, it falls back to IPv4. The default is Any. ```yaml Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -156,13 +167,15 @@ Accept wildcard characters: False ``` ### -IPAddressFamilyConfigurable + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamilyConfigurable parameter specifies whether you're able to set the IPAddressFamily parameter to IPv6Only or Any. The default is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -172,13 +185,15 @@ Accept wildcard characters: False ``` ### -MaxCallsAllowed + +> Applicable: Exchange Server 2013, Exchange Server 2016 + This parameter has been deprecated and is no longer used. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -188,13 +203,15 @@ Accept wildcard characters: False ``` ### -SipTcpListeningPort + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The SipTcpListeningPort parameter specifies the TCP port that's used by the Microsoft Exchange Unified Messaging Call Router service to receive incoming calls. This TCP port is used when a UM dial plan isn't configured to use SIP Secured or Secured mode. The default is port 5060. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -204,13 +221,15 @@ Accept wildcard characters: False ``` ### -SipTlsListeningPort + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The SipTlsListeningPort parameter specifies the Transport Layer Security (TLS) port that's used by the Microsoft Exchange Unified Messaging Call Router service to receive incoming calls. This TLS port is used when a UM dial plan is configured to use SIP Secured or Secured mode. The default is port 5061. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -220,13 +239,15 @@ Accept wildcard characters: False ``` ### -UMStartupMode + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The UMStartupMode parameter specifies whether the Microsoft Exchange Unified Messaging Call Router service starts up in TCP, TLS, or Dual mode. If the Exchange server isn't associated with any UM dial plans or is being added to UM dial plans that have different security settings, you should choose Dual mode. In Dual mode, the Microsoft server can listen on ports 5060 and 5061 at the same time. If the startup mode is changed, the Microsoft Exchange Unified Messaging Call Router service must be restarted. ```yaml Type: UMStartupMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -236,13 +257,15 @@ 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/exchange/Set-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md similarity index 86% rename from exchange/exchange-ps/exchange/Set-UMDialPlan.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md index 0255771570..5e4d2abdec 100644 --- a/exchange/exchange-ps/exchange/Set-UMDialPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umdialplan applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMDialPlan -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umdialplan +schema: 2.0.0 +title: Set-UMDialPlan --- # Set-UMDialPlan @@ -114,13 +115,15 @@ This example configures the UM dial plan MyDialPlan with dialing rules. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the UM dial plan ID. This parameter is the directory object identifier for the UM dial plan. This parameter is used to link mailboxes and Mailbox and Client Access servers to dial plans. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -130,13 +133,15 @@ Accept wildcard characters: False ``` ### -AccessTelephoneNumbers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AccessTelephoneNumbers parameter specifies a single valid voice mail pilot number or a list of valid voice mail pilot numbers. This list is presented to you when a user is being enabled for Unified Messaging. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -146,13 +151,15 @@ Accept wildcard characters: False ``` ### -AllowDialPlanSubscribers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowDialPlanSubscribers parameter specifies whether to allow subscribers dial numbers that resolve to a subscriber within the same dial plan. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -162,13 +169,15 @@ Accept wildcard characters: False ``` ### -AllowedInCountryOrRegionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInCountryOrRegionGroups parameter specifies the list of in-country/region names from the same dial group that can be dialed. The name of the allowed in-country/region group must match the group name specified in the UM dial plan. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -178,13 +187,15 @@ Accept wildcard characters: False ``` ### -AllowedInternationalGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInternationalGroups parameter specifies the list of international dial group names allowed. The international dial group name must match the group name specified in the dial plan. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -194,13 +205,15 @@ Accept wildcard characters: False ``` ### -AllowExtensions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowExtensions parameter specifies whether to allow calls to dial plan extensions. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -210,13 +223,15 @@ Accept wildcard characters: False ``` ### -AllowHeuristicADCallingLineIdResolution + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowHeuristicADCallingLineIdResolution parameter specifies whether to allow calling line ID resolution using telephone number fields that may be configured in Active Directory. When this parameter is set to $true, the telephone numbers such as those defined in the Mobile or Home telephone number fields in Active Directory are used. Setting this parameter to $true allows for resolution of calling IDs for both UM-enabled and non-UM-enabled users. The default is $true. You may want to set this parameter to $false if the telephone numbers for users aren't in a standard format. If the telephone numbers aren't in a standard format, the Mailbox server may not be able to correctly resolve the caller ID to a name of a user in a consistent manner. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -226,13 +241,15 @@ Accept wildcard characters: False ``` ### -AudioCodec + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AudioCodec parameter specifies the audio codec used for recording. Mp3 is the default setting. ```yaml Type: AudioCodecEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -242,13 +259,15 @@ Accept wildcard characters: False ``` ### -AutomaticSpeechRecognitionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AutomaticSpeechRecognitionEnabled parameter specifies whether Automatic Speech Recognition (ASR) is enabled for users who are members of the dial plan. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -258,13 +277,15 @@ Accept wildcard characters: False ``` ### -CallAnsweringRulesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CallAnsweringRulesEnabled parameter specifies whether Call Answering Rules are enabled for UM-enabled users associated with the UM dial plan. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -274,13 +295,15 @@ Accept wildcard characters: False ``` ### -CallSomeoneEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CallSomeoneEnabled parameter specifies whether the Call Someone feature is enabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -290,6 +313,9 @@ Accept wildcard characters: False ``` ### -ConfiguredInCountryOrRegionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ConfiguredInCountryOrRegionGroups parameter specifies the in-country groups that can be used. Each string consists of four parts: - Group name (up to 32 characters) @@ -301,7 +327,6 @@ The ConfiguredInCountryOrRegionGroups parameter specifies the in-country groups Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -311,6 +336,9 @@ Accept wildcard characters: False ``` ### -ConfiguredInternationalGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ConfiguredInternationalGroups parameter specifies the international groups that can be used. Each string consists of four parts: - Group name (up to 32 characters) @@ -322,7 +350,6 @@ The ConfiguredInternationalGroups parameter specifies the international groups t Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -332,6 +359,9 @@ 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`. @@ -341,7 +371,6 @@ 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 @@ -351,13 +380,15 @@ Accept wildcard characters: False ``` ### -ContactAddressList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactAddressList parameter specifies the identity of the address list. If the ContactScope parameter is set to AddressList, this parameter defines the scope for directory searches. ```yaml Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -367,13 +398,15 @@ Accept wildcard characters: False ``` ### -ContactRecipientContainer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactRecipientContainer parameter specifies the name or identity of the container used for directory searches. ```yaml Type: OrganizationalUnitIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -383,13 +416,15 @@ Accept wildcard characters: False ``` ### -ContactScope + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ContactScope parameter specifies the scope of the directory search provided to callers when they access the UM dial plan and specify a user's name. ```yaml Type: CallSomeoneScopeEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -399,13 +434,15 @@ Accept wildcard characters: False ``` ### -CountryOrRegionCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CountryOrRegionCode parameter specifies the country or region code that precedes a telephone number used to place calls from other countries or regions to the country or region in which the UM dial plan is located. For example, 1 is the code used for North America, and 44 is the code used for the United Kingdom. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -415,13 +452,15 @@ Accept wildcard characters: False ``` ### -DefaultLanguage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DefaultLanguage parameter specifies the default language of the system. This default language is selected from the list of available languages. The default value is U.S. English. ```yaml Type: UMLanguage Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -431,13 +470,15 @@ Accept wildcard characters: False ``` ### -DialByNamePrimary + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DialByNamePrimary parameter specifies that the Dial by Name lookup key is to be created from the specified source. The default value is LastFirst. ```yaml Type: DialByNamePrimaryEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -447,13 +488,15 @@ Accept wildcard characters: False ``` ### -DialByNameSecondary + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DialByNameSecondary parameter specifies that the secondary Dial by Name lookup key is to be created from the specified source. The default value is SMTPAddress. ```yaml Type: DialByNameSecondaryEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -463,13 +506,15 @@ 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 @@ -479,13 +524,15 @@ Accept wildcard characters: False ``` ### -EquivalentDialPlanPhoneContexts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The EquivalentDialPlanPhoneContexts parameter specifies the name of an equivalency dial plan. This parameter can be used when two UM dial plans exist but are in different forests or when a Private Branch eXchange (PBX) numbering plan spans two UM dial plans. Adding the name of the equivalency dial plan allows name lookups using a caller ID to search in the user's dial plan but then also search for a name for the calling line ID in any equivalent dial plans that are configured. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -495,13 +542,15 @@ Accept wildcard characters: False ``` ### -Extension + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Extension parameter specifies the extension number used by the Call Someone feature when a call is transferred. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -511,13 +560,15 @@ Accept wildcard characters: False ``` ### -FaxEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The FaxEnabled parameter specifies whether the Mailbox servers associated with the UM dial plan answers and processes incoming fax calls. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -527,13 +578,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 Required: False Position: Named @@ -543,13 +596,15 @@ Accept wildcard characters: False ``` ### -InCountryOrRegionNumberFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InCountryOrRegionNumberFormat parameter specifies the prefix string to use and the number of digits to take from the directory. This number is used when dialing into this dial plan from inside the same country or region code. ```yaml Type: NumberFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -559,13 +614,15 @@ Accept wildcard characters: False ``` ### -InfoAnnouncementEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InfoAnnouncementEnabled parameter specifies whether an informational announcement is enabled. This parameter can be set to True, False, or Uninterruptible. The default value is False. ```yaml Type: InfoAnnouncementEnabledEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -575,13 +632,15 @@ Accept wildcard characters: False ``` ### -InfoAnnouncementFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InfoAnnouncementFilename parameter specifies the audio file name for an informational announcement. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -591,13 +650,15 @@ Accept wildcard characters: False ``` ### -InputFailuresBeforeDisconnect + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InputFailuresBeforeDisconnect parameter specifies the number of sequential user input errors allowed before the call is disconnected. The default value is 3. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -607,13 +668,15 @@ Accept wildcard characters: False ``` ### -InternationalAccessCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InternationalAccessCode parameter specifies the code that precedes a telephone number to dial international calls. For example, 011 is the code used to call the United States. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -623,13 +686,15 @@ Accept wildcard characters: False ``` ### -InternationalNumberFormat + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InternationalNumberFormat parameter specifies the prefix string to use and the number of digits to take from the directory, when dialing into this dial plan from a different country code. ```yaml Type: NumberFormat Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -639,13 +704,15 @@ Accept wildcard characters: False ``` ### -LegacyPromptPublishingPoint + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The LegacyPromptPublishingPoint parameter was used to specify the location of the prompt publishing point for Exchange Server 2007 Unified Messaging servers. This parameter was used in coexistence scenarios when Exchange 2007 Unified Messaging servers were also included in 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 @@ -655,13 +722,15 @@ Accept wildcard characters: False ``` ### -LogonFailuresBeforeDisconnect + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The LogonFailuresBeforeDisconnect parameter specifies the number of sequential unsuccessful logon attempts that can be made before the call is disconnected. The default value is 3. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -671,6 +740,9 @@ Accept wildcard characters: False ``` ### -MatchedNameSelectionMethod + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MatchedNameSelectionMethod parameter specifies the selection to use to differentiate between users who have names that match the touchtone or speech input. This setting can be set to the following: - Title @@ -683,7 +755,6 @@ The MatchedNameSelectionMethod parameter specifies the selection to use to diffe Type: DisambiguationFieldEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -693,13 +764,15 @@ Accept wildcard characters: False ``` ### -MaxCallDuration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MaxCallDuration parameter specifies the maximum length of time that a call can last before it's interrupted and the call is dropped. The default value is 30 minutes. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -709,13 +782,15 @@ Accept wildcard characters: False ``` ### -MaxRecordingDuration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MaxRecordingDuration parameter specifies the maximum length of time that messages can be recorded. This includes all kinds of calls. The default is 20 minutes. The value of this setting can be from 1 through 100. Setting this value too low can cause long voice messages to be disconnected before they are completed. Setting this value too high lets users save lengthy voice messages in their Inboxes. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -725,13 +800,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name to use for the UM dial plan. This name is limited to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -741,13 +818,15 @@ Accept wildcard characters: False ``` ### -NationalNumberPrefix + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The NationalNumberPrefix parameter specifies the dialing code that precedes a telephone number when placing calls from one local area to another within a specific country or region. For example, 1 is the code used within North America, and 0 is the code used within the United Kingdom. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -757,13 +836,15 @@ Accept wildcard characters: False ``` ### -NumberingPlanFormats + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The NumberingPlanFormats parameter specifies one or more phone number masks that can be used for resolving caller ID to names of users in Active Directory. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -773,13 +854,15 @@ Accept wildcard characters: False ``` ### -OperatorExtension + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The OperatorExtension parameter specifies the extension number of the operator. If this parameter isn't specified, the Do Not Allow Transfer to the Operator feature is unavailable. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -789,13 +872,15 @@ Accept wildcard characters: False ``` ### -OutsideLineAccessCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The OutsideLineAccessCode parameter specifies the code that precedes a telephone number to dial an external in-country telephone number. This code is also referred to as a trunk access code. The default value is 9. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -805,13 +890,15 @@ Accept wildcard characters: False ``` ### -PilotIdentifierList + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PilotIdentifierList parameter specifies the pilot numbers configured on the dial plan. A single dial plan can have multiple pilot numbers. The pilot numbers must be in the E.164 format. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -821,13 +908,15 @@ Accept wildcard characters: False ``` ### -RecordingIdleTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The RecordingIdleTimeout parameter specifies the length of time that a caller can be silent when recording a voice message before the recording is ended. The default value is 5 seconds. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -837,13 +926,15 @@ Accept wildcard characters: False ``` ### -SendVoiceMsgEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SendVoiceMsgEnabled parameter specifies whether the Send Message feature is enabled. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -853,13 +944,15 @@ Accept wildcard characters: False ``` ### -TUIPromptEditingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TUIPromptEditingEnabled parameter specifies whether authorized users are permitted to record UM dial plan or automated attendant prompts by using the Telephone User Interface (TUI). The default setting is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -869,13 +962,15 @@ Accept wildcard characters: False ``` ### -UMAutoAttendant + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMAutoAttendant parameter specifies the auto attendant run when the caller presses the star (\*) key. If this parameter is specified, it overrides the Call Someone feature. ```yaml Type: UMAutoAttendantIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -885,13 +980,15 @@ Accept wildcard characters: False ``` ### -VoIPSecurity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoIPSecurity parameter specifies whether the Voice over IP (VoIP) traffic is encrypted or that the signaling channel or the signaling and the media channels are encrypted by using mutual Transport Layer Security (TLS). The default setting is Unsecured. ```yaml Type: UMVoIPSecurityType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -901,13 +998,15 @@ Accept wildcard characters: False ``` ### -WelcomeGreetingEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The WelcomeGreetingEnabled parameter specifies whether a custom welcome greeting is enabled. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -917,13 +1016,15 @@ Accept wildcard characters: False ``` ### -WelcomeGreetingFilename + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The WelcomeGreetingFilename parameter specifies the audio file name for the welcome greeting. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -933,13 +1034,15 @@ 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/exchange/Set-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-UMIPGateway.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md index af9d1ffda1..fde5944673 100644 --- a/exchange/exchange-ps/exchange/Set-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umipgateway applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMIPGateway -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umipgateway +schema: 2.0.0 +title: Set-UMIPGateway --- # Set-UMIPGateway @@ -80,13 +81,15 @@ This example enables the UM IP gateway to function as an IP gateway simulator an ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM IP gateway being modified. 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 @@ -96,13 +99,15 @@ Accept wildcard characters: False ``` ### -Address + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Address parameter specifies the IP address or the fully qualified domain name (FQDN) configured on the UM IP gateway or SIP-enabled IP PBX. An FQDN is required if the UM dial plan associated with the UM IP gateway is operating in SIP Secured or Secured mode. If an FQDN is used, verify that the Domain Name System (DNS) has been configured correctly. ```yaml Type: UMSmartHost Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -112,6 +117,9 @@ 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`. @@ -121,7 +129,6 @@ 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 @@ -131,13 +138,15 @@ Accept wildcard characters: False ``` ### -DelayedSourcePartyInfoEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DelayedSourcePartyInfoEnabled parameter specifies whether Unified Messaging should delay the process of accepting an inbound call from the Voice over IP (VoIP) gateway if the corresponding SIP INVITE of the call contains no calling party and diversion information. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -147,13 +156,15 @@ 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 @@ -163,13 +174,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 Required: False Position: Named @@ -179,6 +192,9 @@ Accept wildcard characters: False ``` ### -IPAddressFamily + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are: - IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value. @@ -189,7 +205,6 @@ The IPAddressFamily parameter specifies whether the UM IP gateway will use Inter Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -199,13 +214,15 @@ Accept wildcard characters: False ``` ### -MessageWaitingIndicatorAllowed + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MessageWaitingIndicatorAllowed parameter specifies whether to enable the UM IP gateway to allow SIP NOTIFY messages to be sent to users associated with a UM dial plan and the UM IP gateway. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -215,13 +232,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the UM IP gateway. This display name is limited to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -231,13 +250,15 @@ Accept wildcard characters: False ``` ### -OutcallsAllowed + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The OutcallsAllowed parameter specifies whether to allow this UM IP gateway to be used for outgoing calls. This doesn't govern call transfers. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -247,13 +268,15 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Port parameter specifies the IP port on which the IP gateway or IP PBX is listening. By default, it's port 5060. The range for this parameter is from 0 through 65535. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -263,13 +286,15 @@ Accept wildcard characters: False ``` ### -Simulator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Simulator parameter specifies the simulator used for the UM IP gateway being viewed. A simulator allows a client to connect to the Mailbox server. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -279,6 +304,9 @@ Accept wildcard characters: False ``` ### -Status + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Status parameter specifies whether to enable or disable the UM IP gateway. Valid values are: - Enabled @@ -289,7 +317,6 @@ The Status parameter specifies whether to enable or disable the UM IP gateway. V Type: GatewayStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -299,13 +326,15 @@ 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/exchange/Set-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-UMMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md index 7e179f4bc5..e36a30d47d 100644 --- a/exchange/exchange-ps/exchange/Set-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailbox applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailbox +schema: 2.0.0 +title: Set-UMMailbox --- # Set-UMMailbox @@ -81,6 +82,9 @@ This example prevents the user tony@contoso.com from accessing his calendar and ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -98,7 +102,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -108,13 +111,15 @@ Accept wildcard characters: False ``` ### -AllowUMCallsFromNonUsers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowUMCallsFromNonUsers parameter specifies whether to exclude the mailbox from Unified Messaging directory searches. ```yaml Type: AllowUMCallsFromNonUsersFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -124,13 +129,15 @@ Accept wildcard characters: False ``` ### -AnonymousCallersCanLeaveMessages + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AnonymousCallersCanLeaveMessages parameter specifies whether diverted calls without a caller ID are allowed to leave a message. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -140,13 +147,15 @@ Accept wildcard characters: False ``` ### -AutomaticSpeechRecognitionEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AutomaticSpeechRecognitionEnabled parameter specifies whether users can use Automatic Speech Recognition (ASR) when they log on to their mailbox. This parameter can only be set to $true if there is ASR support for the language selected by the user in Microsoft Outlook on the web Options. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -156,13 +165,15 @@ Accept wildcard characters: False ``` ### -CallAnsweringAudioCodec + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CallAnsweringAudioCodec parameter specifies the audio codec used to encode voice mail messages left for the user. The audio codec used is the audio codec set on the UM dial plan. The default value is Mp3. ```yaml Type: AudioCodecEnum Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -172,13 +183,15 @@ Accept wildcard characters: False ``` ### -CallAnsweringRulesEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CallAnsweringRulesEnabled parameter specifies whether users can configure or set up Call Answering Rules for their accounts. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -188,6 +201,9 @@ 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`. @@ -197,7 +213,6 @@ 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 @@ -207,13 +222,15 @@ 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 @@ -223,13 +240,15 @@ Accept wildcard characters: False ``` ### -FaxEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The FaxEnabled parameter specifies whether a user is allowed to receive incoming faxes. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -239,6 +258,9 @@ 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: @@ -250,7 +272,6 @@ 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 @@ -260,6 +281,9 @@ Accept wildcard characters: False ``` ### -ImListMigrationCompleted + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The ImListMigrationCompleted parameter specifies whether the UM-enabled user's Lync or Skype for Business contact list is stored in their mailbox. Valid values are: @@ -275,7 +299,6 @@ If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's L Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -285,6 +308,9 @@ Accept wildcard characters: False ``` ### -MissedCallNotificationEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MissedCallNotificationEnabled parameter specifies whether to send missed call notifications. When you're integrating Unified Messaging and Lync Server or Skype for Business Server, missed call notifications aren't available to users who have mailboxes located on Exchange 2010 Mailbox servers. A missed call notification is generated when a user disconnects before the call is sent to a Mailbox server. @@ -293,7 +319,6 @@ When you're integrating Unified Messaging and Lync Server or Skype for Business Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -303,13 +328,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the user. The display name is limited to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -319,13 +346,15 @@ Accept wildcard characters: False ``` ### -OperatorNumber + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The OperatorNumber parameter specifies the string of digits for the personal operator. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -335,13 +364,15 @@ Accept wildcard characters: False ``` ### -PinlessAccessToVoiceMailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PinlessAccessToVoiceMailEnabled parameter specifies whether UM-enabled users are required to use a PIN to access their voice mail. A PIN is still required to access email and the calendar. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -351,13 +382,15 @@ Accept wildcard characters: False ``` ### -PlayOnPhoneEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PlayOnPhoneEnabled parameter specifies whether a user can use the Play on Phone feature to listen to voice messages. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -367,13 +400,15 @@ Accept wildcard characters: False ``` ### -SubscriberAccessEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SubscriberAccessEnabled parameter specifies whether the users are allowed subscriber access to their individual mailboxes. If it's set to $true, after users are authenticated, they're able to retrieve voice mail over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -383,13 +418,15 @@ Accept wildcard characters: False ``` ### -TUIAccessToCalendarEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TUIAccessToCalendarEnabled parameter specifies whether UM-enabled users can access and manage their individual calendar using the Microsoft Outlook Voice Access telephone user interface (TUI) or touchtone interface. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -399,13 +436,15 @@ Accept wildcard characters: False ``` ### -TUIAccessToEmailEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TUIAccessToEmailEnabled parameter specifies whether users can access their individual email messages over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -415,13 +454,15 @@ Accept wildcard characters: False ``` ### -UMMailboxPolicy + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMMailboxPolicy parameter specifies the UM mailbox policy associated with the UM-enabled user's mailbox. ```yaml Type: MailboxPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -431,13 +472,15 @@ Accept wildcard characters: False ``` ### -UMSMSNotificationOption + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMSMSNotificationOption parameter specifies whether a UM-enabled user gets SMS or text messaging notifications for voice mail only, voice mail and missed calls, or no notifications. The values for this parameter are: VoiceMail, VoiceMailAndMissedCalls, and None. The default value is None. ```yaml Type: UMSMSNotificationOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -447,13 +490,15 @@ Accept wildcard characters: False ``` ### -VoiceMailAnalysisEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The VoiceMailAnalysisEnabled parameter specifies whether a copy of each voice mail left for a UM-enabled user will be forwarded to Microsoft for analysis and improvement of speech recognition features. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -463,13 +508,15 @@ 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/exchange/Set-UMMailboxPIN.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md similarity index 91% rename from exchange/exchange-ps/exchange/Set-UMMailboxPIN.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md index bec81a4cf6..c71166169c 100644 --- a/exchange/exchange-ps/exchange/Set-UMMailboxPIN.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailboxpin applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMMailboxPIN -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailboxpin +schema: 2.0.0 +title: Set-UMMailboxPIN --- # Set-UMMailboxPIN @@ -74,6 +75,9 @@ This example unlocks the UM-enabled mailbox for tonysmith@contoso.com and allows ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -91,7 +95,6 @@ The Identity parameter specifies the mailbox that you want to modify. You can us Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: 1 @@ -101,6 +104,9 @@ 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`. @@ -110,7 +116,6 @@ 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 @@ -120,13 +125,15 @@ 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 @@ -136,6 +143,9 @@ 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: @@ -147,7 +157,6 @@ 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 @@ -157,13 +166,15 @@ Accept wildcard characters: False ``` ### -LockedOut + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The LockedOut parameter specifies whether the mailbox will continue to be locked. If set to $true, the mailbox is marked as locked out. By default, if this parameter is omitted or set to $false, the command clears the locked-out status on the mailbox. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -173,13 +184,15 @@ Accept wildcard characters: False ``` ### -NotifyEmail + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The NotifyEmail parameter specifies the email address to which the server sends the email message that contains the PIN reset information. By default, the message is sent to the SMTP address of the enabled user. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -189,13 +202,15 @@ Accept wildcard characters: False ``` ### -Pin + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Pin parameter specifies a new PIN for use with the mailbox. The PIN is checked against the PIN rules defined in the Unified Messaging mailbox policy. If the PIN isn't supplied, the command generates a new PIN for the mailbox and includes it in an email message sent to the user. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -205,13 +220,15 @@ 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 this parameter is supplied and is set to $false, the user isn't required to reset the PIN the next time that the user logs on. If the PIN isn't supplied, the PIN is treated as expired and the user is prompted to reset the PIN the next time that the user logs on. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -221,13 +238,15 @@ Accept wildcard characters: False ``` ### -SendEmail + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SendEmail parameter specifies whether to send a PIN to the user in an email message. The default is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -237,13 +256,15 @@ 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 @@ -253,13 +274,15 @@ 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 this parameter is supplied and is set to $false, the user isn't required to reset the PIN the next time that the user logs on. If the PIN isn't supplied, the PIN is treated as expired and the user is prompted to reset the PIN the next time that the user logs on. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md similarity index 87% rename from exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md index 789aabc713..969158d9e0 100644 --- a/exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailboxpolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Set-UMMailboxPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-ummailboxpolicy +schema: 2.0.0 +title: Set-UMMailboxPolicy --- # Set-UMMailboxPolicy @@ -106,13 +107,15 @@ This example configures the text of voice mail messages sent to UM-enabled users ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Identity parameter specifies the identifier for the UM mailbox policy being modified. 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: True Position: 1 @@ -122,13 +125,15 @@ Accept wildcard characters: False ``` ### -AllowAutomaticSpeechRecognition + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowAutomaticSpeechRecognition parameter specifies whether users associated with the UM mailbox policy can use Automatic Speech Recognition (ASR). The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -138,13 +143,15 @@ Accept wildcard characters: False ``` ### -AllowCallAnsweringRules + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowCallAnsweringRules parameter specifies whether users associated with the UM mailbox policy are allowed to configure or set up Call Answering Rules for their accounts. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -154,13 +161,15 @@ Accept wildcard characters: False ``` ### -AllowCommonPatterns + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowCommonPatterns parameter specifies whether to allow obvious PINs. Examples of obvious PINs include subsets of the telephone number, sequential numbers, or repeated numbers. If set to $false, sequential and repeated numbers and the suffix of the mailbox extension are rejected. If set to $true, only the suffix of the mailbox extension is rejected. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -170,13 +179,15 @@ Accept wildcard characters: False ``` ### -AllowDialPlanSubscribers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowDialPlanSubscribers parameter specifies whether to let subscribers in a dial plan dial a number that resolves to another subscriber within the same dial plan. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -186,13 +197,15 @@ Accept wildcard characters: False ``` ### -AllowedInCountryOrRegionGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInCountryOrRegionGroups parameter specifies whether to let subscribers dial the list of in-country/region dial group names. The names that subscribers are allowed to dial must match the group names defined in the UM dial plan. The string is limited to 128 characters. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -202,13 +215,15 @@ Accept wildcard characters: False ``` ### -AllowedInternationalGroups + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowedInternationalGroups parameter specifies whether to let subscribers dial the list of international dial group names. The names that subscribers dial must match the group names defined in the dial plan. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -218,13 +233,15 @@ Accept wildcard characters: False ``` ### -AllowExtensions + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowExtensions parameter specifies whether to let subscribers dial calls to the number of digits specified on the UM dial plan. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -234,13 +251,15 @@ Accept wildcard characters: False ``` ### -AllowFax + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowFax parameter specifies whether users associated with the UM mailbox policy are allowed to receive incoming faxes. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -250,13 +269,15 @@ Accept wildcard characters: False ``` ### -AllowMessageWaitingIndicator + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowMessageWaitingIndicator parameter specifies whether users associated with the UM mailbox policy can receive notifications that they've received a new voice mail message. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -266,6 +287,9 @@ Accept wildcard characters: False ``` ### -AllowMissedCallNotifications + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowMissedCallNotifications parameter specifies whether missed call notifications are enabled for users associated with the UM mailbox policy. The default value is $true. When you're integrating Unified Messaging and Lync Server or Skype for Business Server, missed call notifications aren't available to users who have mailboxes located on Exchange 2010 Mailbox servers. A missed call notification is generated when a user disconnects before the call is sent to a Mailbox server. @@ -274,7 +298,6 @@ When you're integrating Unified Messaging and Lync Server or Skype for Business Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -284,13 +307,15 @@ Accept wildcard characters: False ``` ### -AllowPinlessVoiceMailAccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowPinlessVoiceMailAccess parameter specifies whether users associated with the UM mailbox policy are required to use a PIN to access their voice mail. A PIN is still required to access their email and calendar. The default value is $false. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -300,13 +325,15 @@ Accept wildcard characters: False ``` ### -AllowPlayOnPhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowPlayOnPhone parameter specifies whether users associated with the UM mailbox policy can use the Play on Phone feature to listen to voice mail messages. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -316,13 +343,15 @@ Accept wildcard characters: False ``` ### -AllowSMSNotification + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowSMSNotification parameter specifies whether UM-enabled users associated with the UM mailbox policy are allowed to get SMS or text messages sent to their mobile phones. If this parameter is set to $true, you also want to set the Set-UMMailbox cmdlet UMSMSNotificationOption parameter for the UM-enabled user to either VoiceMail or VoiceMailAndMissedCalls. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -332,13 +361,15 @@ Accept wildcard characters: False ``` ### -AllowSubscriberAccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowSubscriberAccess parameter specifies whether users associated with the UM mailbox policy are allowed subscriber access to their individual mailboxes. If this parameter is set to $true, after users are authenticated, they're able to retrieve voice mail over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -348,13 +379,15 @@ Accept wildcard characters: False ``` ### -AllowTUIAccessToCalendar + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowTUIAccessToCalendar parameter specifies whether users associated with the UM mailbox policy can access their individual calendars over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -364,13 +397,15 @@ Accept wildcard characters: False ``` ### -AllowTUIAccessToDirectory + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowTUIAccessToDirectory parameter specifies whether users associated with the UM mailbox policy can access the directory over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -380,13 +415,15 @@ Accept wildcard characters: False ``` ### -AllowTUIAccessToEmail + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowTUIAccessToEmail parameter specifies whether users associated with the UM mailbox policy can access their individual email messages over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -396,13 +433,15 @@ Accept wildcard characters: False ``` ### -AllowTUIAccessToPersonalContacts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowTUIAccessToPersonalContacts parameter specifies whether users associated with the UM mailbox policy can access their personal contacts over the telephone. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -412,13 +451,15 @@ Accept wildcard characters: False ``` ### -AllowVoiceMailAnalysis + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowVoiceMailAnalysis parameter specifies whether a copy of each voice mail left for the users associated with the UM mailbox policy will be forwarded to Microsoft for analysis and improvement of our speech recognition features. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -428,13 +469,15 @@ Accept wildcard characters: False ``` ### -AllowVoiceMailPreview + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowVoiceMailPreview parameter specifies whether users associated with the UM mailbox policy are able to receive Voice Mail Previews for call-answered messages, or have Voice Mail Previews provided for voice mail messages that they send to other users in their mailbox. The default value is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -444,13 +487,15 @@ Accept wildcard characters: False ``` ### -AllowVoiceResponseToOtherMessageTypes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The AllowVoiceResponseToOtherMessageTypes parameter specifies whether UM-enabled users associated with the UM mailbox policy can record and attach a voice mail message when replying to email messages and calendar items. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -460,6 +505,9 @@ 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`. @@ -469,7 +517,6 @@ 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 @@ -479,13 +526,15 @@ 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 @@ -495,13 +544,15 @@ Accept wildcard characters: False ``` ### -FaxMessageText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The FaxMessageText parameter specifies the text included in the body part of fax messages. This text is limited to 512 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -511,13 +562,15 @@ Accept wildcard characters: False ``` ### -FaxServerURI + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The FaxServerURI parameter specifies the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for the fax solution that serves the UM-enabled users associated with the UM mailbox policy. This fax product or fax service accepts incoming fax calls that were redirected from Exchange Unified Messaging servers and creates inbound fax messages for the UM-enabled users associated with the UM mailbox policy. Although you can enter more than one fax server URI, only one URI will be used by the Unified Messaging server. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -527,13 +580,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. 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 Required: False Position: Named @@ -543,13 +598,15 @@ Accept wildcard characters: False ``` ### -InformCallerOfVoiceMailAnalysis + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The InformCallerOfVoiceMailAnalysis parameter specifies whether the callers leaving the voice mails will be informed about the possibility of their voice mails being forwarded to Microsoft for analysis. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -559,13 +616,15 @@ Accept wildcard characters: False ``` ### -LogonFailuresBeforePINReset + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The LogonFailuresBeforePINReset parameter specifies the number of sequential unsuccessful logon attempts before the mailbox PIN is automatically reset. To disable this feature, set this parameter to Unlimited. If this parameter isn't set to Unlimited, it must be set to less than the value of the MaxLogonAttempts parameter. The range is from 0 through 999. The default setting is 5. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -575,13 +634,15 @@ Accept wildcard characters: False ``` ### -MaxGreetingDuration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MaxGreetingDuration parameter specifies the maximum greeting length. The range is from 1 through 10 minutes. The default value is 5 minutes. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -591,13 +652,15 @@ Accept wildcard characters: False ``` ### -MaxLogonAttempts + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MaxLogonAttempts parameter specifies the number of times users can try unsuccessfully to log on, in sequence, before the UM mailboxes are locked. The range is from 1 through 999. The default value is 15. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -607,13 +670,15 @@ Accept wildcard characters: False ``` ### -MinPINLength + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MinPINLength parameter specifies the minimum number of digits required in a PIN for UM-enabled users. The range is from 4 through 24. The default value is 6. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -623,13 +688,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Name parameter specifies the display name for the UM mailbox policy. This setting is limited to 64 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -639,13 +706,15 @@ Accept wildcard characters: False ``` ### -PINHistoryCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PINHistoryCount parameter specifies the number of previous PINs that are remembered and aren't allowed during a PIN reset. This number includes the first time that the PIN was set. The range is from 1 through 20. The default value is 5. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -655,13 +724,15 @@ Accept wildcard characters: False ``` ### -PINLifetime + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PINLifetime parameter specifies the number of days until a new password is required. The range is from 1 through 999. The default value is 60. If you specify Unlimited, the users' PINs won't expire. ```yaml Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -671,13 +742,15 @@ Accept wildcard characters: False ``` ### -ProtectAuthenticatedVoiceMail + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ProtectAuthenticatedVoiceMail parameter specifies whether Mailbox servers that answer Outlook Voice Access calls for UM-enabled users associated with the UM mailbox policy create protected voice mail messages. The default setting is None. This means that no protection is applied to voice mail messages. If the value is set to Private, only messages marked as private are protected. If the value is set to All, every voice mail message is protected. ```yaml Type: DRMProtectionOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -687,13 +760,15 @@ Accept wildcard characters: False ``` ### -ProtectedVoiceMailText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ProtectedVoiceMailText parameter specifies the text included in the body part of the protected voice mail messages for UM-enabled users associated with the UM mailbox policy. This text can contain up to 512 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -703,13 +778,15 @@ Accept wildcard characters: False ``` ### -ProtectUnauthenticatedVoiceMail + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ProtectUnauthenticatedVoiceMail parameter specifies whether the Mailbox servers that answer calls for UM-enabled users associated with the UM mailbox policy create protected voice mail messages. This also applies when a message is sent from a UM auto attendant to a UM-enabled user associated with the UM mailbox policy. The default setting is None. This means that no protection is applied to voice mail messages. If the value is set to Private, only messages marked as private are protected. If the value is set to All, every voice mail message is protected. ```yaml Type: DRMProtectionOptions Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -719,13 +796,15 @@ Accept wildcard characters: False ``` ### -RequireProtectedPlayOnPhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The RequireProtectedPlayOnPhone parameter specifies whether users associated with the UM mailbox policy can only use Play on Phone for protected voice mail messages or whether users can use multimedia software to play the protected message. The default value is $false. When set to $false, users are able to use both methods to listen to protected voice mail messages. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -735,13 +814,15 @@ Accept wildcard characters: False ``` ### -ResetPINText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ResetPINText parameter specifies the text to be included in the PIN reset email message. This text is limited to 512 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -751,13 +832,15 @@ Accept wildcard characters: False ``` ### -SourceForestPolicyNames + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The SourceForestPolicyNames parameter specifies the name or names of the corresponding UM mailbox policy objects located in the source forest during a cross-forest migration. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -767,13 +850,15 @@ 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 the UM mailbox policy. ```yaml Type: UMDialPlanIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -783,13 +868,15 @@ Accept wildcard characters: False ``` ### -UMEnabledText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMEnabledText parameter specifies the text to be included when a user is enabled for Unified Messaging. This text is limited to 512 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -799,13 +886,15 @@ Accept wildcard characters: False ``` ### -VoiceMailPreviewPartnerAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoiceMailPreviewPartnerAddress parameter specifies the SMTP address of a Voice Mail Preview partner that's contracted to provide transcription services for UM-enabled users in this UM mailbox policy. The default value is $null. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -815,13 +904,15 @@ Accept wildcard characters: False ``` ### -VoiceMailPreviewPartnerAssignedID + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoiceMailPreviewPartnerAssignedID parameter specifies the identification string, if any, provided to the organization by the Voice Mail Preview partner that's contracted to provide transcription services for UM-enabled users in this UM mailbox policy. The default value is $null. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -831,13 +922,15 @@ Accept wildcard characters: False ``` ### -VoiceMailPreviewPartnerMaxDeliveryDelay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoiceMailPreviewPartnerMaxDeliveryDelay parameter specifies the number of seconds that a Mailbox server waits for a Voice Mail Preview partner system to return a message with a Voice Mail Preview. If this time is exceeded, the Mailbox server delivers the voice mail message without a preview. The default value is 1200. The minimum value for this parameter is 300. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -847,13 +940,15 @@ Accept wildcard characters: False ``` ### -VoiceMailPreviewPartnerMaxMessageDuration + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoiceMailPreviewPartnerMaxMessageDuration parameter specifies the maximum duration, in seconds, of voice mail messages sent to the Voice Mail Preview partner that's contracted to provide transcription services for UM-enabled users in this UM mailbox policy. The default value is 180. The minimum number for this parameter is 60. This setting should be set equal to the maximum value allowed by the Voice Mail Preview partner. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -863,13 +958,15 @@ Accept wildcard characters: False ``` ### -VoiceMailText + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The VoiceMailText parameter specifies the text to be included in the body part of voice mail messages. The parameter applies to call answering messages in addition to messages originated by an authenticated subscriber. This text is limited to 512 characters. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -879,13 +976,15 @@ 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/exchange/Set-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-UMService.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UMService.md index 51772cc547..71649d4242 100644 --- a/exchange/exchange-ps/exchange/Set-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umservice applicable: Exchange Server 2013, Exchange Server 2016 -title: Set-UMService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umservice +schema: 2.0.0 +title: Set-UMService --- # Set-UMService @@ -78,6 +79,9 @@ This example performs the following actions: ## 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 modify. You can use any value that uniquely identifies the server. For example: - Name @@ -89,7 +93,6 @@ 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: True Position: 1 @@ -99,6 +102,9 @@ 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`. @@ -108,7 +114,6 @@ 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 @@ -118,6 +123,9 @@ Accept wildcard characters: False ``` ### -DialPlans + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The DialPlans parameter specifies all dial plans that the Unified Messaging service handles incoming calls for. Exchange 2016 and Exchange 2013 servers can't be associated with a TelExt or E.164 UM dial plan, but can be associated or added to SIP dial plans. If you're integrating Unified Messaging with Lync Server 2010, Lync Server 2013, or Skype for Business Server 2015, you need to associate or add all Exchange 2016 and Exchange 2013 servers to SIP dial plans. @@ -132,7 +140,6 @@ To add or remove one or more values without affecting any existing entries, use Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -142,13 +149,15 @@ 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 @@ -158,6 +167,9 @@ Accept wildcard characters: False ``` ### -GrammarGenerationSchedule + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The GrammarGenerationSchedule parameter specifies the scheduled times to start speech grammar generation. This parameter allows only one start time per day. The default scheduled time for grammar generation is 02:00-02:30 local time each day. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can specify multiple schedules separated by commas: `"Schedule1","Schedule2",..."ScheduleN"`. @@ -185,7 +197,6 @@ Here are some examples: Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -195,6 +206,9 @@ Accept wildcard characters: False ``` ### -IPAddressFamily + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamily parameter specifies whether the UM IP gateway will use IPv4, IPv6, or both to communicate. Valid values are: - IPv4 @@ -205,7 +219,6 @@ The IPAddressFamily parameter specifies whether the UM IP gateway will use IPv4, Type: IPAddressFamily Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -215,13 +228,15 @@ Accept wildcard characters: False ``` ### -IPAddressFamilyConfigurable + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IPAddressFamilyConfigurable parameter specifies whether you're able to set the IPAddressFamily parameter to IPv6Only or Any. The default is $true. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -231,6 +246,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IrmLogEnabled parameter specifies whether to enable logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Valid values are: - $true: Enable IRM logging @@ -240,7 +258,6 @@ The IrmLogEnabled parameter specifies whether to enable logging of Information R Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -250,6 +267,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. 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. @@ -260,7 +280,6 @@ The valid input range for this parameter is from 00:00:00 through 24855.03:14:07 Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -270,6 +289,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 megabytes (MB). When you enter a value, qualify the value with one of the following units: @@ -288,7 +310,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -298,6 +319,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: @@ -316,7 +340,6 @@ The value of the IrmLogMaxFileSize parameter must be less than or equal to the v Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -326,6 +349,9 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%IRMLogs. If you set the value of this parameter to $null, you effectively disable IRM logging. However, setting this parameter to $null when the value of the IrmLogEnabled parameter is $true, generates errors in the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false. @@ -334,7 +360,6 @@ If you set the value of this parameter to $null, you effectively disable IRM log Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -344,13 +369,15 @@ Accept wildcard characters: False ``` ### -MaxCallsAllowed + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The MaxCallsAllowed parameter specifies the maximum number of concurrent voice calls that the Unified Messaging service allows. The default value is 100. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -360,6 +387,9 @@ Accept wildcard characters: False ``` ### -SIPAccessService + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The SIPAccessService parameter specifies the FQDN and TCP port of the nearest Lync Server Front End pool or Skype for Business Server Front End pool location for inbound and outbound calls from remote Lync or Skype for Business users located outside of the network. We recommend that you always use this parameter in Lync Server or Skype for Business Server deployments that span multiple geographic regions; otherwise, the Microsoft Exchange Unified Messaging service might select a pool for Real-Time Transport Protocol (RTP) media traffic that isn't the closest geographically to the remote user. @@ -370,7 +400,6 @@ You configure this parameter for each instance of the Unified Messaging service Type: ProtocolConnectionSettings Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -380,13 +409,15 @@ Accept wildcard characters: False ``` ### -Status + +> Applicable: Exchange Server 2013, Exchange Server 2016 + This parameter has been deprecated and is no longer used. ```yaml Type: ServerStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -396,6 +427,9 @@ Accept wildcard characters: False ``` ### -UMStartupMode + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The UMStartupMode parameter specifies the startup mode for the Unified Messaging service. Valid values are: - TCP (This is the default value) @@ -408,7 +442,6 @@ If you change the value of this parameter, you need to restart the Unified Messa Type: UMStartupMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -418,13 +451,15 @@ 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/exchange/Set-UmServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-UmServer.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-UmServer.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UmServer.md index 6fa2f340bf..5cbec644e7 100644 --- a/exchange/exchange-ps/exchange/Set-UmServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UmServer.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-umserver applicable: Exchange Server 2010 -title: Set-UmServer -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-umserver +schema: 2.0.0 +title: Set-UmServer --- # Set-UMServer @@ -82,6 +83,9 @@ This example changes the grammar generation schedule to 02:30-03:00 every day on ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter specifies the Unified Messaging server that you want to modify. You can use any value that uniquely identifies the server. For example: - Name @@ -93,7 +97,6 @@ The Identity parameter specifies the Unified Messaging server that you want to m Type: UMServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -103,6 +106,9 @@ 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`. @@ -112,7 +118,6 @@ 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 @@ -122,13 +127,15 @@ Accept wildcard characters: False ``` ### -DialPlans + +> Applicable: Exchange Server 2010 + The DialPlans parameter specifies all the dial plans for which this server will handle UM calls. If no dial plans are defined, the Unified Messaging server won't handle UM calls. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -138,13 +145,15 @@ 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 @@ -154,13 +163,15 @@ Accept wildcard characters: False ``` ### -ExternalServiceFqdn + +> Applicable: Exchange Server 2010 + The ExternalServiceFqdn parameter is the FQDN or host name of a load balancer servicing Unified Messaging servers. This parameter is useful when you're migrating Unified Messaging servers from within your organization to a Microsoft Exchange Server 2010 hosted environment. The external service host FQDN can contain up to 2,048 characters. ```yaml Type: UMSmartHost Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -170,6 +181,9 @@ Accept wildcard characters: False ``` ### -GrammarGenerationSchedule + +> Applicable: Exchange Server 2010 + The GrammarGenerationSchedule parameter specifies the scheduled times to start speech grammar generation. This parameter allows only one start time per day. The default scheduled time for grammar generation is 02:00-02:30 local time each day. The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`. You can specify multiple schedules separated by commas: `"Schedule1","Schedule2",..."ScheduleN"`. @@ -197,7 +211,6 @@ Here are some examples: Type: ScheduleInterval[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -207,6 +220,9 @@ Accept wildcard characters: False ``` ### -IrmLogEnabled + +> Applicable: Exchange Server 2010 + The IrmLogEnabled parameter specifies whether to enable logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include: - $true Enable IRM logging @@ -216,7 +232,6 @@ The IrmLogEnabled parameter specifies whether to enable logging of Information R Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -226,13 +241,15 @@ Accept wildcard characters: False ``` ### -IrmLogMaxAge + +> Applicable: Exchange Server 2010 + The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. The default value is 30 days. To specify a value, enter the value as a time span: dd.hh:mm:ss, where d = days, h = hours, m = minutes, and s = seconds. The valid input range for this parameter is from 00:00:00 through 24855.03:14:07. Setting the value of the IrmLogMaxAge parameter to 00:00:00 prevents the automatic removal of IRM log files because of their age. ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -242,6 +259,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxDirectorySize + +> Applicable: Exchange Server 2010 + The IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 megabytes (MB). When you enter a value, qualify the value with one of the following units: - B (bytes) @@ -256,7 +276,6 @@ Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize para Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -266,6 +285,9 @@ Accept wildcard characters: False ``` ### -IrmLogMaxFileSize + +> Applicable: Exchange Server 2010 + The IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB. When you enter a value, qualify the value with one of the following units: - B (bytes) @@ -280,7 +302,6 @@ Unqualified values are treated as bytes. The value of the IrmLogMaxFileSize para Type: ByteQuantifiedSize Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -290,13 +311,15 @@ Accept wildcard characters: False ``` ### -IrmLogPath + +> Applicable: Exchange Server 2010 + The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\V14. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled parameter to $false. ```yaml Type: LocalLongFullPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -306,13 +329,15 @@ Accept wildcard characters: False ``` ### -MaxCallsAllowed + +> Applicable: Exchange Server 2010 + The MaxCallsAllowed parameter specifies the maximum number of concurrent voice calls that the Unified Messaging server allows. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -322,6 +347,9 @@ Accept wildcard characters: False ``` ### -SIPAccessService + +> Applicable: Exchange Server 2010 + The SIPAccessService parameter specifies the FQDN and TCP port of the nearest Lync Server Edge pool or Skype for Business Server Edge pool location for inbound and outbound calls from remote Lync or Skype for Business users located outside of the network. We recommend that you always use this parameter in Lync Server or Skype for Business Server deployments that span multiple geographic regions; otherwise, the Unified Messaging server might select a pool for Real-Time Transport Protocol (RTP) media traffic that isn't the closest geographically to the remote user. @@ -332,7 +360,6 @@ You configure this parameter for each Unified Messaging server so the value iden Type: ProtocolConnectionSettings Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -342,13 +369,15 @@ Accept wildcard characters: False ``` ### -SipTcpListeningPort + +> Applicable: Exchange Server 2010 + The SipTcpListeningPort parameter specifies the TCP port used by the Unified Messaging server to receive incoming calls. This TCP port is used by Unified Messaging servers added to a UM dial plan that isn't configured to use SIP Secured or Secured mode. The default is port 5060. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -358,13 +387,15 @@ Accept wildcard characters: False ``` ### -SipTlsListeningPort + +> Applicable: Exchange Server 2010 + The SipTlsListeningPort parameter specifies the Transport Layer Security (TLS) port used by the Unified Messaging server to receive incoming calls. This TLS port is used by Unified Messaging servers that are added to a UM dial plan configured to use SIP Secured or Secured mode. The default is port 5061. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -374,13 +405,15 @@ Accept wildcard characters: False ``` ### -Status + +> Applicable: Exchange Server 2010 + The Status parameter specifies the Unified Messaging server status. The available options are Enabled, Disabled, and NoNewCalls. ```yaml Type: ServerStatus Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -390,13 +423,15 @@ Accept wildcard characters: False ``` ### -UMStartupMode + +> Applicable: Exchange Server 2010 + The UMStartupMode parameter specifies whether the Microsoft Exchange Unified Messaging service on a Unified Messaging server will start up in TCP, TLS, or Dual mode. If the Unified Messaging server is being added to UM dial plans that have different security settings, you should choose Dual mode. In Dual mode, the Unified Messaging server can listen on ports 5060 and 5061 at the same time. If the startup mode is changed, the Microsoft Exchange Unified Messaging service must be restarted. ```yaml Type: UMStartupMode Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -406,13 +441,15 @@ 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/exchange/Set-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md similarity index 95% rename from exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md index b54bb64a99..f20c51b15b 100644 --- a/exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-unifiedauditlogretentionpolicy applicable: Security & Compliance -title: Set-UnifiedAuditLogRetentionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-unifiedauditlogretentionpolicy +schema: 2.0.0 +title: Set-UnifiedAuditLogRetentionPolicy --- # Set-UnifiedAuditLogRetentionPolicy @@ -55,6 +56,9 @@ This example modifies an audit log retention policy and changes to retention dur ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the unified audit log retention policy that you want to modify. You can use any value that uniquely identifies the policy. For example: - Name @@ -65,7 +69,6 @@ The Identity parameter specifies the unified audit log retention policy that you Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -75,6 +78,9 @@ Accept wildcard characters: False ``` ### -Priority + +> Applicable: Security & Compliance + The Priority parameter specifies a priority value for the policy that determines the order of policy processing. A higher integer value indicates a lower priority. The value 1 is the highest priority, and the value 10000 is the lowest priority. No two policies can have the same priority value. This parameter is required when you modify an audit log retention policy, and you must use a unique priority value. @@ -83,7 +89,6 @@ This parameter is required when you modify an audit log retention policy, and yo Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -93,6 +98,9 @@ Accept wildcard characters: False ``` ### -RetentionDuration + +> Applicable: Security & Compliance + The RetentionDuration parameter specifies how long audit log records are kept. Valid values are: - ThreeMonths @@ -108,7 +116,6 @@ Type: UnifiedAuditLogRetentionDuration Parameter Sets: (All) Aliases: Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears -Applicable: Security & Compliance Required: True Position: Named @@ -118,6 +125,9 @@ 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,7 +137,6 @@ 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 @@ -137,13 +146,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Security & Compliance + The Description parameter specifies a description for the audit log retention 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: Security & Compliance Required: False Position: Named @@ -153,6 +164,9 @@ Accept wildcard characters: False ``` ### -Operations + +> Applicable: Security & Compliance + The Operations parameter specifies the audit log operations that are retained by the policy. The values you specify will overwrite any existing entries. 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"`. @@ -161,7 +175,6 @@ 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 @@ -171,6 +184,9 @@ Accept wildcard characters: False ``` ### -RecordTypes + +> Applicable: Security & Compliance + The RecordTypes parameter specifies the audit logs of a specific record type that are retained by 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). You can specify multiple values separated by commas. The values you specify will overwrite any existing entries. @@ -179,7 +195,6 @@ You can specify multiple values separated by commas. The values you specify will Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: Named @@ -189,6 +204,9 @@ Accept wildcard characters: False ``` ### -UserIds + +> Applicable: Security & Compliance + The UserIds parameter specifies the audit logs that are retained by the policy based on the ID of the user who performed the action. The values you specify will overwrite any existing entries. 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"`. @@ -197,7 +215,6 @@ 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 @@ -207,13 +224,15 @@ 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/exchange/Set-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/Set-UnifiedGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md index c592fda80d..645da9c3cd 100644 --- a/exchange/exchange-ps/exchange/Set-UnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-unifiedgroup applicable: Exchange Online, Exchange Online Protection -title: Set-UnifiedGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-unifiedgroup +schema: 2.0.0 +title: Set-UnifiedGroup --- # Set-UnifiedGroup @@ -112,6 +113,9 @@ This example changes the Microsoft 365 Group named Legal Department from a publi ## 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 @@ -125,7 +129,6 @@ 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 @@ -135,6 +138,9 @@ Accept wildcard characters: False ``` ### -AcceptMessagesOnlyFromSendersOrMembers + +> Applicable: Exchange Online, Exchange Online Protection + The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group are allowed to send messages to this recipient. @@ -156,7 +162,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -166,6 +171,9 @@ Accept wildcard characters: False ``` ### -AccessType + +> Applicable: Exchange Online, Exchange Online Protection + The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Valid values are: - Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. @@ -177,7 +185,6 @@ The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Type: ModernGroupTypeInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -187,6 +194,9 @@ Accept wildcard characters: False ``` ### -Alias + +> Applicable: Exchange Online, Exchange Online Protection + The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the Microsoft 365 Group. 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: @@ -200,7 +210,6 @@ The Alias value can contain letters, numbers and the following characters: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -210,6 +219,9 @@ Accept wildcard characters: False ``` ### -AlwaysSubscribeMembersToCalendarEvents + +> Applicable: Exchange Online, Exchange Online Protection + The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group. Changing this setting doesn't affect existing group members. - If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents. Previous events are not automatically added to their calendars. @@ -225,7 +237,6 @@ The AutoSubscribeNewMembers switch overrides this switch. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -235,6 +246,9 @@ Accept wildcard characters: False ``` ### -AuditLogAgeLimit + +> Applicable: Exchange Online, Exchange Online Protection + The AuditLogAgeLimit parameter specifies the maximum age of audit log entries for the Microsoft 365 Group. Log entries older than the specified value are removed. The default value is 90 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. @@ -245,7 +259,6 @@ For example, to specify 60 days for this parameter, use 60.00:00:00. Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -255,6 +268,9 @@ Accept wildcard characters: False ``` ### -AutoSubscribeNewMembers + +> Applicable: Exchange Online, Exchange Online Protection + The AutoSubscribeNewMembers switch specifies whether to automatically subscribe new members that are added to the Microsoft 365 Group to conversations and calendar events. Only users that are added to the group after you enable this setting are automatically subscribed to the group. - To subscribe new members to conversations and calendar events, use the AutoSubscribeNewMembers switch without a value. @@ -266,7 +282,6 @@ The AutoSubscribeNewMembers switch specifies whether to automatically subscribe Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -276,6 +291,9 @@ Accept wildcard characters: False ``` ### -CalendarMemberReadOnly + +> Applicable: Exchange Online, Exchange Online Protection + The CalendarMemberReadOnly switch specifies whether to set read-only Calendar permissions to the Microsoft 365 Group for members of the group. - To set read-only Calendar permissions, use the CalendarMemberReadOnly switch without a value. @@ -287,7 +305,6 @@ To view the current value of the CalendarMemberReadOnly property on a Microsoft Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -297,13 +314,15 @@ Accept wildcard characters: False ``` ### -Classification + +> Applicable: Exchange Online, Exchange Online Protection + The Classification parameter specifies the classification for the Microsoft 365 Group. You need to configure the list of available classifications in Microsoft Entra ID before you can specify a value for this parameter. For more information, see [Microsoft Entra cmdlets for configuring group settings](https://learn.microsoft.com/azure/active-directory/users-groups-roles/groups-settings-cmdlets). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -313,6 +332,9 @@ 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`. @@ -322,7 +344,6 @@ 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 @@ -332,6 +353,9 @@ Accept wildcard characters: False ``` ### -ConnectorsEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorsEnabled specifies whether to enable the ability to use connectors for the Microsoft 365 Group. - To enable connectors, use the ConnectorsEnabled switch without a value. @@ -345,7 +369,6 @@ For more information about connectors for Microsoft 365 Groups, see [Connect app Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -355,13 +378,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute1 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -371,13 +396,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute10 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -387,13 +414,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute11 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -403,13 +432,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute12 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -419,13 +450,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute13 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -435,13 +468,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute14 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -451,13 +486,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute15 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -467,13 +504,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute2 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -483,13 +522,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute3 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -499,13 +540,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute4 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -515,13 +558,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute5 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -531,13 +576,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute6 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -547,13 +594,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute7 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -563,13 +612,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute8 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -579,13 +630,15 @@ Accept wildcard characters: False ``` ### -CustomAttribute9 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 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 @@ -595,6 +648,9 @@ Accept wildcard characters: False ``` ### -DataEncryptionPolicy + +> Applicable: Exchange Online, Exchange Online Protection + The DataEncryptionPolicy parameter specifies the data encryption policy that's applied to the Microsoft 365 Group. You can use any value that uniquely identifies the policy. For example: - Name @@ -607,7 +663,6 @@ To remove an existing policy, use the value $null. Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -617,13 +672,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Online, Exchange Online Protection + The DisplayName parameter specifies the name of the Microsoft 365 Group. The display name is visible in the Exchange admin center, address lists, and Outlook. 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: False Position: Named @@ -633,6 +690,9 @@ Accept wildcard characters: False ``` ### -EmailAddresses + +> Applicable: Exchange Online, Exchange Online Protection + The EmailAddresses parameter specifies all email addresses (proxy addresses) for the Microsoft 365 Group, including the primary SMTP address. In cloud-based organizations, the primary SMTP address and other proxy addresses for Microsoft 365 Groups are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the Microsoft 365 Group. Valid syntax for this parameter is `"Type:EmailAddress1","Type:EmailAddress2",..."Type:EmailAddressN"`. The optional `Type` value specifies the type of email address. Examples of valid values include: @@ -657,7 +717,6 @@ To add or remove specify proxy addresses without affecting other existing values Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -667,6 +726,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute1 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -677,7 +739,6 @@ 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 @@ -687,6 +748,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute2 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -697,7 +761,6 @@ 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 @@ -707,6 +770,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute3 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -717,7 +783,6 @@ 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 @@ -727,6 +792,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute4 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -737,7 +805,6 @@ 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 @@ -747,6 +814,9 @@ Accept wildcard characters: False ``` ### -ExtensionCustomAttribute5 + +> Applicable: Exchange Online, Exchange Online Protection + This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas. To enter multiple values that overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value","Value2",..."ValueN"`. @@ -757,7 +827,6 @@ 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 @@ -767,13 +836,15 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Online, Exchange Online Protection + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -783,6 +854,9 @@ Accept wildcard characters: False ``` ### -GrantSendOnBehalfTo + +> Applicable: Exchange Online, Exchange Online Protection + The GrantSendOnBehalfTo parameter specifies who can send on behalf of this Microsoft 365 Group. Although messages that are sent on behalf of the group clearly show the sender in the From field (` on behalf of `), replies to these messages are delivered to the group, not the sender. The sender you specify for this parameter must a mailbox, mail user or mail-enabled security group (a mail-enabled security principal that can have permissions assigned). You can use any value that uniquely identifies the sender. For example: @@ -808,7 +882,6 @@ By default, this parameter is blank, which means no one else has permission to s Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -818,6 +891,9 @@ Accept wildcard characters: False ``` ### -HiddenFromAddressListsEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The HiddenFromAddressListsEnabled parameter specifies whether the Microsoft 365 Group appears in the global address list (GAL) and other address lists in your organization. Valid values are: - $true: The Microsoft 365 Group is hidden from the GAL and other address lists. The group can still receive messages, but users can't search for or browse to the group in Outlook or Outlook on the web. Users also can't find the group by using the Discover option in Outlook on the web. For users that are members of the Microsoft 365 Group, the group will still appear in the navigation pane in Outlook and Outlook on the web if HiddenFromExchangeClientsEnabled property is **NOT** enabled. @@ -827,7 +903,6 @@ The HiddenFromAddressListsEnabled parameter specifies whether the Microsoft 365 Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -837,6 +912,9 @@ Accept wildcard characters: False ``` ### -HiddenFromExchangeClientsEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The HiddenFromExchangeClientsEnabled switch specifies whether the Microsoft 365 Group is hidden from Outlook clients connected to Microsoft 365. - To enable this setting, you don't need to specify a value with this switch. The Microsoft 365 Group is hidden from Outlook experiences. The group isn't visible in the Outlook left-hand navigation and isn't visible in the global address list (GAL). The group name doesn't resolve during the creation of a new message in Outlook. The group can still receive messages, but users can't search for or browse to the group in Outlook or Outlook on the web. Users can't find the group by using the Discover option in Outlook on the web. The HiddenFromAddressListsEnabled property is set to the value True to prevent the group from showing in the GAL and in the Offline Address Book (OAB). @@ -847,7 +925,6 @@ The HiddenFromExchangeClientsEnabled switch specifies whether the Microsoft 365 Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -857,6 +934,9 @@ Accept wildcard characters: False ``` ### -InformationBarrierMode + +> Applicable: Exchange Online, Exchange Online Protection + The InformationBarrierMode parameter specifies the information barrier mode for the Microsoft 365 Group. Valid values are: - Explicit @@ -868,7 +948,6 @@ The InformationBarrierMode parameter specifies the information barrier mode for Type: GroupInformationBarrierMode Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -878,13 +957,15 @@ Accept wildcard characters: False ``` ### -IsMemberAllowedToEditContent + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill IsMemberAllowedToEditContent Description }} ```yaml Type: System.Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -894,6 +975,9 @@ Accept wildcard characters: False ``` ### -Language + +> Applicable: Exchange Online, Exchange Online Protection + The Language parameter specifies language preference for the Microsoft 365 Group. 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). @@ -902,7 +986,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -912,13 +995,15 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online, Exchange Online Protection + The MailboxRegion parameter specifies the preferred data location (PDL) for the Microsoft 365 Group in multi-geo environments. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -928,6 +1013,9 @@ Accept wildcard characters: False ``` ### -MailTip + +> Applicable: Exchange Online, Exchange Online Protection + The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks ("). When you add a MailTip to a recipient, two things happen: @@ -939,7 +1027,6 @@ When you add a MailTip to a recipient, two things happen: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -949,6 +1036,9 @@ Accept wildcard characters: False ``` ### -MailTipTranslations + +> Applicable: Exchange Online, Exchange Online Protection + The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters. To add or remove MailTip translations without affecting the default MailTip or other MailTip translations, use the following syntax: @@ -963,7 +1053,6 @@ For example, suppose this recipient currently has the MailTip text: "This mailbo Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -973,6 +1062,9 @@ Accept wildcard characters: False ``` ### -MaxReceiveSize + +> Applicable: Exchange Online, Exchange Online Protection + The MaxReceiveSize parameter specifies the maximum size of an email message that can be sent to this group. Messages that exceed the maximum size are rejected by the group. When you enter a value, qualify the value with one of the following units: @@ -992,7 +1084,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1002,6 +1093,9 @@ Accept wildcard characters: False ``` ### -MaxSendSize + +> Applicable: Exchange Online, Exchange Online Protection + The MaxSendSize parameter specifies the maximum size of an email message that can be sent by this group. When you enter a value, qualify the value with one of the following units: @@ -1021,7 +1115,6 @@ Base64 encoding increases the size of messages by approximately 33%, so specify Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1031,6 +1124,9 @@ Accept wildcard characters: False ``` ### -ModeratedBy + +> Applicable: 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 @@ -1048,7 +1144,6 @@ You need to use this parameter to specify at least one moderator when you set th Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1058,6 +1153,9 @@ Accept wildcard characters: False ``` ### -ModerationEnabled + +> Applicable: 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. @@ -1069,7 +1167,6 @@ You use the ModeratedBy parameter to specify the moderators. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1079,13 +1176,15 @@ Accept wildcard characters: False ``` ### -Notes + +> Applicable: Exchange Online, Exchange Online Protection + The Notes parameter specifies the description of the Microsoft 365 Group. 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 @@ -1095,13 +1194,15 @@ Accept wildcard characters: False ``` ### -PrimarySmtpAddress + +> Applicable: Exchange Online, Exchange Online Protection + The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1111,6 +1212,9 @@ Accept wildcard characters: False ``` ### -RejectMessagesFromSendersOrMembers + +> Applicable: Exchange Online, Exchange Online Protection + The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected. Valid values for this parameter are individual senders and groups in your organization. Individual senders are mailboxes, mail users, and mail contacts. Groups are distribution groups, mail-enabled security groups, and dynamic distribution groups. Specifying a group means all members of the group aren't allowed to send messages to this recipient. @@ -1136,7 +1240,6 @@ By default, this parameter is blank ($null), which allows this recipient to acce Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1146,6 +1249,9 @@ Accept wildcard characters: False ``` ### -RequireSenderAuthenticationEnabled + +> Applicable: 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. @@ -1155,7 +1261,6 @@ The RequireSenderAuthenticationEnabled parameter specifies whether to accept mes Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1165,6 +1270,9 @@ Accept wildcard characters: False ``` ### -SensitivityLabelId + +> Applicable: Exchange Online, Exchange Online Protection + The SensitivityLabelId parameter specifies the GUID value of the sensitivity label that's assigned to the Microsoft 365 Group. **Note**: In the output of the Get-UnifiedGroup cmdlet, this property is named SensitivityLabel, not SensitivityLabelId. @@ -1173,7 +1281,6 @@ The SensitivityLabelId parameter specifies the GUID value of the sensitivity lab Type: System.Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1183,6 +1290,9 @@ Accept wildcard characters: False ``` ### -SubscriptionEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The SubscriptionEnabled switch specifies whether the group owners can enable subscription to conversations and calendar events on the groups they own. This option can be set only in Exchange Online PowerShell. - To change the value to $true, use this switch without a value. @@ -1196,7 +1306,6 @@ The SubscriptionEnabled switch specifies whether the group owners can enable sub Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1206,6 +1315,9 @@ Accept wildcard characters: False ``` ### -UnifiedGroupWelcomeMessageEnabled + +> Applicable: Exchange Online, Exchange Online Protection + The UnifiedGroupWelcomeMessageEnabled switch specifies whether to enable or disable sending system-generated welcome messages to users who are added as members to the Microsoft 365 Group. - To enable this setting, you don't need to specify a value with this switch. @@ -1219,7 +1331,6 @@ This setting is enabled by default. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1229,13 +1340,15 @@ 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/exchange/Set-User.md b/exchange/exchange-ps/ExchangePowerShell/Set-User.md similarity index 82% rename from exchange/exchange-ps/exchange/Set-User.md rename to exchange/exchange-ps/ExchangePowerShell/Set-User.md index 09606906d6..9c1044b5df 100644 --- a/exchange/exchange-ps/exchange/Set-User.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-User.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-user applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Set-User -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-user +schema: 2.0.0 +title: Set-User --- # Set-User @@ -118,6 +119,9 @@ Performing this procedure on a linked mailbox removes all permissions on the mai ## 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 that you want to modify. You can use any value that uniquely identifies the user. For example: - Name @@ -131,7 +135,6 @@ The Identity parameter specifies the user that you want to modify. You can use a 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 @@ -141,6 +144,9 @@ Accept wildcard characters: False ``` ### -AllowUMCallsFromNonUsers + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllowUMCallsFromNonUsers parameter specifies whether to exclude the user from Unified Messaging directory searches. @@ -149,7 +155,6 @@ The AllowUMCallsFromNonUsers parameter specifies whether to exclude the user fro Type: AllowUMCallsFromNonUsersFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,6 +164,9 @@ 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 modify arbitration mailboxes. You don't need to specify a value with this switch. @@ -169,7 +177,6 @@ Arbitration mailboxes are system mailboxes that are used for storing different t Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -179,13 +186,15 @@ Accept wildcard characters: False ``` ### -AssistantName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AssistantName parameter specifies the name of the user's assistant. ```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 @@ -195,6 +204,9 @@ Accept wildcard characters: False ``` ### -AuthenticationPolicy + +> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection + The AuthenticationPolicy parameter specifies the authentication policy to apply to the user. You can use any value that uniquely identifies the policy. For example: - Name @@ -209,7 +221,6 @@ You create authentication policies with the New-AuthenticationPolicy cmdlet to b Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -219,6 +230,9 @@ Accept wildcard characters: False ``` ### -BlockCloudCache + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill BlockCloudCache Description }} @@ -227,7 +241,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -237,6 +250,9 @@ Accept wildcard characters: False ``` ### -CanHaveCloudCache + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill CanHaveCloudCache Description }} @@ -245,7 +261,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -255,6 +270,9 @@ Accept wildcard characters: False ``` ### -CertificateSubject + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CertificateSubject parameter specifies the value of the subject field of the user's digital certificate. @@ -263,7 +281,6 @@ The CertificateSubject parameter specifies the value of the subject field of the Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -273,13 +290,15 @@ Accept wildcard characters: False ``` ### -City + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The City parameter specifies the user's city. ```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 @@ -289,6 +308,9 @@ Accept wildcard characters: False ``` ### -ClearDataEncryptionPolicy + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill ClearDataEncryptionPolicy Description }} @@ -297,7 +319,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -307,13 +328,15 @@ Accept wildcard characters: False ``` ### -Company + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Company parameter specifies the user's company. ```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 @@ -323,6 +346,9 @@ 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`. @@ -332,7 +358,6 @@ 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 @@ -342,6 +367,9 @@ Accept wildcard characters: False ``` ### -CountryOrRegion + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The CountryOrRegion parameter specifies the user's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name). A reference for two-letter country codes is available at [Country Codes List](https://www.nationsonline.org/oneworld/country_code_list.htm). @@ -352,7 +380,6 @@ The friendly name is returned in the CountryOrRegion property value by the Get-U Type: CountryInfo 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 @@ -362,6 +389,9 @@ Accept wildcard characters: False ``` ### -CreateDTMFMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are: @@ -373,7 +403,6 @@ The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-fre Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -383,13 +412,15 @@ Accept wildcard characters: False ``` ### -Department + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Department parameter specifies the user's department. ```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 @@ -399,6 +430,9 @@ Accept wildcard characters: False ``` ### -DesiredWorkloads + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill DesiredWorkloads Description }} @@ -407,7 +441,6 @@ This parameter is available only in the cloud-based service. Type: Microsoft.Exchange.Data.MailboxWorkloadFlags Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -417,13 +450,15 @@ 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 user. The display name is visible in the Exchange admin center and in Active Directory. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -433,6 +468,9 @@ 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. @@ -441,7 +479,6 @@ 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 @@ -451,6 +488,9 @@ Accept wildcard characters: False ``` ### -EXOModuleEnabled + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The EXOModuleEnabled parameter specifies whether the user can connect to Exchange Online PowerShell in Microsoft 365 organizations using the Exchange Online PowerShell V3 module. Valid values are: @@ -466,7 +506,6 @@ The default value depends on the management roles that are assigned to the user. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -476,13 +515,15 @@ Accept wildcard characters: False ``` ### -Fax + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Fax parameter specifies the user's fax number. ```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 @@ -492,13 +533,15 @@ Accept wildcard characters: False ``` ### -FirstName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The FirstName parameter specifies the user's first name. ```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 @@ -508,6 +551,9 @@ 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. @@ -518,7 +564,6 @@ 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 @@ -528,6 +573,9 @@ Accept wildcard characters: False ``` ### -GeoCoordinates + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The GeoCoordinates parameter specifies the user's location in latitude, longitude and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats: - Latitude and longitude: For example, "47.644125;-122.122411" @@ -539,7 +587,6 @@ The GeoCoordinates parameter specifies the user's location in latitude, longitud Type: GeoCoordinates Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -549,13 +596,15 @@ Accept wildcard characters: False ``` ### -HomePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The HomePhone parameter specifies the user's home telephone number. ```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 @@ -565,6 +614,9 @@ 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. @@ -578,7 +630,6 @@ 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 @@ -588,13 +639,15 @@ Accept wildcard characters: False ``` ### -Initials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Initials parameter specifies the user's middle initials. ```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 @@ -604,6 +657,9 @@ Accept wildcard characters: False ``` ### -IsShadowMailbox + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill IsShadowMailbox Description }} @@ -612,7 +668,6 @@ This parameter is available only in the cloud-based service. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -622,13 +677,15 @@ Accept wildcard characters: False ``` ### -LastName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The LastName parameter specifies the user's last name. ```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 @@ -638,6 +695,9 @@ 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 username and password that's used to access the domain controller specified by the LinkedDomainController parameter. @@ -650,7 +710,6 @@ You can only use the LinkedCredential parameter with a linked user. Type: PSCredential Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -660,6 +719,9 @@ 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 this user is a linked user. 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. @@ -670,7 +732,6 @@ This parameter is required only if you're connecting a linked user. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -680,6 +741,9 @@ 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 this user is a linked user. The master account is the account to which the user links. The master account grants access to the user. You can use one of the following values: @@ -701,7 +765,6 @@ This parameter is required only if you're connecting a linked user. Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -711,6 +774,9 @@ Accept wildcard characters: False ``` ### -MailboxRegion + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MailboxRegion Description }} @@ -719,7 +785,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -729,6 +794,9 @@ Accept wildcard characters: False ``` ### -MailboxRegionSuffix + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill MailboxRegionSuffix Description }} @@ -737,7 +805,6 @@ This parameter is available only in the cloud-based service. Type: MailboxRegionSuffixValue Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -747,6 +814,9 @@ Accept wildcard characters: False ``` ### -ManagedOnboardingType + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. {{ Fill ManagedOnboardingType Description }} @@ -755,7 +825,6 @@ This parameter is available only in the cloud-based service. Type: ManagedOnboardingType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -765,13 +834,15 @@ Accept wildcard characters: False ``` ### -Manager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Manager parameter specifies the user's manager. ```yaml Type: UserContactIdParameter 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 @@ -781,6 +852,9 @@ Accept wildcard characters: False ``` ### -MobilePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The MobilePhone parameter specifies the user's primary mobile phone number. **Note**: In Exchange Online, you can't use this parameter. Instead, use the MobilePhone parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. @@ -789,7 +863,6 @@ The MobilePhone parameter specifies the user's primary mobile phone number. 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 @@ -799,13 +872,15 @@ Accept wildcard characters: False ``` ### -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 user. 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, Exchange Online Protection Required: False Position: Named @@ -815,13 +890,15 @@ 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 @@ -831,13 +908,15 @@ Accept wildcard characters: False ``` ### -Office + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Office parameter specifies the user's physical office name or number. ```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 @@ -847,13 +926,15 @@ Accept wildcard characters: False ``` ### -OtherFax + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherFax parameter specifies the user's alternative fax number. ```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 @@ -863,13 +944,15 @@ Accept wildcard characters: False ``` ### -OtherHomePhone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherHomePhone parameter specifies the user's alternative home telephone number. ```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 @@ -879,13 +962,15 @@ Accept wildcard characters: False ``` ### -OtherTelephone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OtherTelephone parameter specifies the user's alternative telephone number. ```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 @@ -895,13 +980,15 @@ Accept wildcard characters: False ``` ### -Pager + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Pager parameter specifies the user's pager number. ```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 @@ -911,6 +998,9 @@ Accept wildcard characters: False ``` ### -PermanentlyClearPreviousMailboxInfo + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + This parameter is functional only in the cloud-based service. The PermanentlyClearPreviousMailboxInfo switch specifies whether to clear the Exchange Online mailbox attributes on a user. You don't need to specify a value with this switch. @@ -923,7 +1013,6 @@ Clearing these attributes might be required in mailbox move and re-licensing sce Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -933,6 +1022,9 @@ Accept wildcard characters: False ``` ### -Phone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Phone parameter specifies the user's office telephone number. **Note**: In Exchange Online, you can't use this parameter. Instead, use the BusinessPhones parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell. @@ -941,7 +1033,6 @@ The Phone parameter specifies the user's office telephone number. 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 @@ -951,13 +1042,15 @@ Accept wildcard characters: False ``` ### -PhoneticDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. 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, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -967,13 +1060,15 @@ Accept wildcard characters: False ``` ### -PostalCode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PostalCode parameter specifies the user's zip code or postal code. ```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 @@ -983,13 +1078,15 @@ Accept wildcard characters: False ``` ### -PostOfficeBox + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PostOfficeBox parameter specifies the user's post office box number. ```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 @@ -999,6 +1096,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The PublicFolder switch is required to modify public folder mailboxes. 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. @@ -1007,7 +1107,6 @@ 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, Exchange Online Protection Required: False Position: Named @@ -1017,6 +1116,9 @@ Accept wildcard characters: False ``` ### -RemotePowerShellEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + **Note**: In cloud-based environments, this parameter is being deprecated, so use the EXOModuleEnabled parameter instead. The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are: @@ -1034,7 +1136,6 @@ A user's experience in any of these management interfaces is still controlled by 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 @@ -1044,6 +1145,9 @@ Accept wildcard characters: False ``` ### -RemoveMailboxProvisioningConstraint + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -1052,7 +1156,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1062,6 +1165,9 @@ Accept wildcard characters: False ``` ### -ResetPasswordOnNextLogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are: - $true: The user is required to change their password the next time they log on. @@ -1071,7 +1177,6 @@ The ResetPasswordOnNextLogon parameter specifies whether the user must change th 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 @@ -1081,6 +1186,9 @@ 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). The maximum length is 20 characters. @@ -1089,7 +1197,6 @@ 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 @@ -1099,13 +1206,15 @@ Accept wildcard characters: False ``` ### -SeniorityIndex + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SeniorityIndex parameter specifies the order in which this user will display in a hierarchical address book. A user with a value of 2 will display higher in an address book than a user with a value of 1. ```yaml Type: Int32 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 @@ -1115,6 +1224,9 @@ Accept wildcard characters: False ``` ### -SimpleDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are: - a - z @@ -1127,7 +1239,6 @@ The SimpleDisplayName parameter is used to display an alternative description of 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 @@ -1137,6 +1248,9 @@ Accept wildcard characters: False ``` ### -SkipDualWrite + +> Applicable: Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. This parameter is reserved for internal Microsoft use. @@ -1145,7 +1259,6 @@ 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 @@ -1155,13 +1268,15 @@ Accept wildcard characters: False ``` ### -StateOrProvince + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The StateOrProvince parameter specifies the user's state or province. ```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 @@ -1171,13 +1286,15 @@ Accept wildcard characters: False ``` ### -StreetAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The StreetAddress parameter specifies the user's physical address. ```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 @@ -1187,6 +1304,9 @@ Accept wildcard characters: False ``` ### -StsRefreshTokensValidFrom + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The StsRefreshTokensValidFrom specifies the date-time that the user's STS refresh tokens are valid from. @@ -1197,7 +1317,6 @@ 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 @@ -1207,6 +1326,9 @@ Accept wildcard characters: False ``` ### -TelephoneAssistant + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The TelephoneAssistant parameter specifies the telephone number of the user's assistant. @@ -1215,7 +1337,6 @@ The TelephoneAssistant parameter specifies the telephone number of the user's as Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1225,13 +1346,15 @@ Accept wildcard characters: False ``` ### -Title + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Title parameter specifies the user's title. ```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 @@ -1241,6 +1364,9 @@ Accept wildcard characters: False ``` ### -UMCallingLineIds + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. This parameter accepts digits less than 128 characters in length and may include an optional plus sign (+) preceding the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value. @@ -1249,7 +1375,6 @@ The UMCallingLineIds parameter specifies telephone numbers or extensions that ca Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1259,6 +1384,9 @@ Accept wildcard characters: False ``` ### -UMDtmfMap + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UMDtmfMap parameter specifies the dual-tone multiple-frequency (DTMF) map values for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Typically, these DTMF values are automatically created and updated, but you can use this parameter to make changes manually. This parameter uses the following syntax: @@ -1279,7 +1407,6 @@ If you use this syntax, you don't need to specify all of the DTMF map values, an Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1289,6 +1416,9 @@ Accept wildcard characters: False ``` ### -UserPrincipalName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides. @@ -1297,7 +1427,6 @@ The UserPrincipalName parameter specifies the logon name for the user account. T Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -1307,6 +1436,9 @@ Accept wildcard characters: False ``` ### -VIP + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The VIP parameter specifies whether the user is a priority account. Valid values are: @@ -1320,7 +1452,6 @@ For more information about priority accounts, see [Manage and monitor priority a Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -1330,13 +1461,15 @@ Accept wildcard characters: False ``` ### -WebPage + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WebPage parameter specifies the user's Web page. ```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 @@ -1346,13 +1479,15 @@ 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 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, Exchange Online Protection Required: False Position: Named @@ -1362,6 +1497,9 @@ Accept wildcard characters: False ``` ### -WindowsEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results: - In environments where the recipient is subject to email address policies (the EmailAddressPolicyEnabled property is set to the value True for the recipient), the WindowsEmailAddress parameter has no effect on the WindowsEmailAddress property or the primary email address value. @@ -1373,7 +1511,6 @@ The WindowsEmailAddress property is visible for the recipient in Active Director 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 diff --git a/exchange/exchange-ps/exchange/Set-UserBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-UserBriefingConfig.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md index d036882c11..d3d051bd49 100644 --- a/exchange/exchange-ps/exchange/Set-UserBriefingConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://learn.microsoft.com/powershell/module/exchange/set-userbriefingconfig applicable: Exchange Online -title: Set-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/exchange/set-userbriefingconfig +schema: 2.0.0 +title: Set-UserBriefingConfig --- # Set-UserBriefingConfig @@ -53,13 +54,15 @@ This example enables the Briefing email for lila@contoso.com. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the user that you want to modify (for example, lila@contoso.onmicrosoft.com). ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter specifies whether to enable or disable the Briefing email for a specified user's mailbox. Valid values are: - $true: The daily briefing message is enabled. @@ -78,7 +84,6 @@ The Enabled parameter specifies whether to enable or disable the Briefing email Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -88,13 +93,15 @@ 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/exchange/Set-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-UserPhoto.md rename to exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md index d2c06bedea..ee07da9629 100644 --- a/exchange/exchange-ps/exchange/Set-UserPhoto.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-userphoto applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-UserPhoto -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-userphoto +schema: 2.0.0 +title: Set-UserPhoto --- # Set-UserPhoto @@ -129,6 +130,9 @@ This example deletes the preview photo that was uploaded in the previous example ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example: - Name @@ -146,7 +150,6 @@ The Identity parameter specifies the identity of the user. You can use any value Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -156,6 +159,9 @@ Accept wildcard characters: False ``` ### -Cancel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Cancel switch deletes the photo that's currently uploaded as the preview photo. You don't need to specify a value with this switch. To delete the photo that's currently associated with a user's account, use the Remove-UserPhoto cmdlet. The Cancel switch only deletes the preview photo. @@ -164,7 +170,6 @@ To delete the photo that's currently associated with a user's account, use the R Type: SwitchParameter Parameter Sets: CancelPhoto Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -174,15 +179,17 @@ Accept wildcard characters: False ``` ### -PictureData + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PictureData parameter specifies the photo file that will be uploaded to the user's account. 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`). ```yaml Type: Byte[] -Parameter Sets: UploadPhotoData +Parameter Sets: UploadPhotoData, UploadPreview Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -191,27 +198,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Byte[] -Parameter Sets: UploadPreview -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -PictureStream -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -PictureStream The PictureStream parameter specifies the photo that will be uploaded to the user's account. This parameter is used by client applications such as Outlook on the web when users add a photo. To upload a photo using PowerShell, use the PictureData parameter to specify the photo file. ```yaml Type: Stream -Parameter Sets: UploadPhotoStream +Parameter Sets: UploadPhotoStream, UploadPreview Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -220,20 +216,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Stream -Parameter Sets: UploadPreview -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -Preview -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -### -Preview The Preview switch uploads a preview photo for the user account. You don't need to specify a value with this switch. A preview photo is the photo object that is uploaded to the user's account, but isn't saved. For example, if a user uploads a photo in Outlook on the web Options to preview before saving it. If you use the Preview switch to upload a preview photo, you need to run the command `Set-UserPhoto -Save` to save it as the user's photo. @@ -242,7 +228,6 @@ A preview photo is the photo object that is uploaded to the user's account, but Type: SwitchParameter Parameter Sets: UploadPreview Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -252,13 +237,15 @@ Accept wildcard characters: False ``` ### -Save + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Save switch specifies that the photo that's uploaded to the user's account will be saved as the user's photo. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: SavePhoto Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -268,6 +255,9 @@ 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`. @@ -279,7 +269,6 @@ 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 @@ -289,13 +278,15 @@ 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 @@ -305,13 +296,15 @@ Accept wildcard characters: False ``` ### -GroupMailbox + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The GroupMailbox switch is required to modify Microsoft 365 Groups. 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 @@ -321,6 +314,9 @@ 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: @@ -332,7 +328,6 @@ 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 @@ -342,13 +337,15 @@ 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 @@ -358,13 +355,15 @@ 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/exchange/Set-VivaInsightsSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-VivaInsightsSettings.md similarity index 96% rename from exchange/exchange-ps/exchange/Set-VivaInsightsSettings.md rename to exchange/exchange-ps/ExchangePowerShell/Set-VivaInsightsSettings.md index d794753e4e..183bc07f30 100644 --- a/exchange/exchange-ps/exchange/Set-VivaInsightsSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-VivaInsightsSettings.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml -Module Name: ExchangeOnlineManagement -online version: https://learn.microsoft.com/powershell/module/exchange/set-vivainsightssettings applicable: Exchange Online -title: Set-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/exchange/set-vivainsightssettings +schema: 2.0.0 +title: Set-VivaInsightsSettings --- # Set-VivaInsightsSettings @@ -54,13 +55,15 @@ This example disables access to all the Headspace features in Microsoft Viva Ins ## PARAMETERS ### -Identity + +> Applicable: Exchange Online + The Identity parameter specifies the user that you want to modify. 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 @@ -70,6 +73,9 @@ Accept wildcard characters: False ``` ### -Enabled + +> Applicable: Exchange Online + The Enabled parameter enables or disables access to specific features of Microsoft Viva Insights in Microsoft Teams for the user. Valid values are: - $true: The specified features in Microsoft Viva Insights in Microsoft Teams are enabled for the user. @@ -79,7 +85,6 @@ The Enabled parameter enables or disables access to specific features of Microso Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -89,6 +94,9 @@ Accept wildcard characters: False ``` ### -Feature + +> Applicable: Exchange Online + The Feature parameter specifies the feature of Microsoft Viva Insights in Microsoft Teams for the user. Valid values are: - Headspace: Represents all features of Headspace. @@ -99,7 +107,6 @@ Type: String Parameter Sets: (All) Aliases: Accepted values: headspace -Applicable: Exchange Online Required: True Position: Named @@ -109,13 +116,15 @@ 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/exchange/Set-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md similarity index 89% rename from exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md rename to exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md index 09636df6f4..eeb794a115 100644 --- a/exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-webservicesvirtualdirectory applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-WebServicesVirtualDirectory -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-webservicesvirtualdirectory +schema: 2.0.0 +title: Set-WebServicesVirtualDirectory --- # Set-WebServicesVirtualDirectory @@ -73,6 +74,9 @@ This example enables MRSProxy on the EWS default website. MRSProxy is the servic ## 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 modify. You can use any value that uniquely identifies the virtual directory. For example: - Name or Server\\Name @@ -85,7 +89,6 @@ The Name value uses the syntax `"VirtualDirectoryName (WebsiteName)"` from the p Type: VirtualDirectoryIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -95,6 +98,9 @@ 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. @@ -104,7 +110,6 @@ 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 @@ -114,13 +119,15 @@ Accept wildcard characters: False ``` ### -CertificateAuthentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CertificateAuthentication parameter specifies whether certificate authentication is enabled. This parameter affects the `/ews/management/` virtual directory. It doesn't affect the `/ews/` virtual directory. ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,6 +137,9 @@ 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`. @@ -139,7 +149,6 @@ 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,6 +158,9 @@ 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. @@ -158,7 +170,6 @@ 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 @@ -168,13 +179,15 @@ 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 @@ -184,6 +197,9 @@ 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. @@ -196,7 +212,6 @@ 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 @@ -206,6 +221,9 @@ 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. @@ -215,7 +233,6 @@ 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,6 +242,9 @@ 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. @@ -237,7 +257,6 @@ 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 @@ -247,6 +266,9 @@ 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. @@ -255,7 +277,6 @@ This setting is important when Secure Sockets Layer (SSL) is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -265,6 +286,9 @@ 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. @@ -273,7 +297,6 @@ 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 @@ -283,6 +306,9 @@ Accept wildcard characters: False ``` ### -GzipLevel + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are: - Off: No compression. @@ -294,7 +320,6 @@ The GzipLevel parameter sets the Gzip configuration for the Exchange Web Service Type: GzipLevel Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -304,6 +329,9 @@ Accept wildcard characters: False ``` ### -InternalNLBBypassUrl + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + **Note:** This parameter applies only to Exchange 2010. By default, Exchange 2013 or later already has the InternalNLBBypassUrl value configured on the backend Exchange Web Services (EWS) virtual directory on Mailbox servers. The InternalNLBBypassUrl parameter specifies the URL of the Exchange server that has the Client Access server role installed, regardless of whether it's behind a Network Load Balancing (NLB) array or not. @@ -314,7 +342,6 @@ When you set the InternalUrl parameter to the URL of the NLB array, you should s Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -324,6 +351,9 @@ 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. @@ -332,7 +362,6 @@ This setting is important when SSL is used. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -342,13 +371,15 @@ Accept wildcard characters: False ``` ### -MRSProxyEnabled + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Exchange Web Services virtual directory on Exchange servers that have the Client Access server role installed. MRSProxy helps to proxy mailbox moves between Active Directory forests. 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 @@ -358,6 +389,9 @@ Accept wildcard characters: False ``` ### -MRSProxyMaxConnections + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)). @@ -366,7 +400,6 @@ The MRSProxyMaxConnections parameter specifies the maximum number of simultaneou Type: Unlimited Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -376,6 +409,9 @@ 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. @@ -385,7 +421,6 @@ 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 @@ -395,13 +430,15 @@ 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 @@ -411,6 +448,9 @@ 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. @@ -420,7 +460,6 @@ 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 @@ -430,6 +469,9 @@ 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. @@ -439,7 +481,6 @@ 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/exchange/Set-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md similarity index 90% rename from exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md rename to exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md index 30872ecd30..b1bef64376 100644 --- a/exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/set-x400authoritativedomain applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Set-X400AuthoritativeDomain -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/set-x400authoritativedomain +schema: 2.0.0 +title: Set-X400AuthoritativeDomain --- # Set-X400AuthoritativeDomain @@ -83,6 +84,9 @@ This example makes the following changes to an existing X.400 authoritative doma ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the X.400 authoritative domain that you want to modify. You can use any value that uniquely identifies the domain. For example: - Name @@ -93,7 +97,6 @@ The Identity parameter specifies the X.400 authoritative domain that you want to Type: X400AuthoritativeDomainIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -103,6 +106,9 @@ 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`. @@ -112,7 +118,6 @@ 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,6 +127,9 @@ 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. @@ -130,7 +138,6 @@ 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 @@ -140,13 +147,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Name parameter specifies the unique name for the X.400 authoritative domain. 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 Required: False Position: Named @@ -156,13 +165,15 @@ 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 @@ -172,6 +183,9 @@ Accept wildcard characters: False ``` ### -X400DomainName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X400DomainName parameter specifies the X.400 namespace that can only include the X.400 organizational components. Specifically, only the following attribute types are supported: - C (Country) @@ -189,7 +203,6 @@ Separate the address attributes with semicolons and enclose the entire address i Type: X400Domain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -199,13 +212,15 @@ Accept wildcard characters: False ``` ### -X400ExternalRelay + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The X400ExternalRelay parameter specifies whether this authoritative domain is an external relay domain. If you set the X400ExternalRelay parameter to $true, Exchange routes to the external address and doesn't treat resolution failures to this subdomain as errors. ```yaml 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/exchange/Start-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md similarity index 91% rename from exchange/exchange-ps/exchange/Start-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md index ddcb34db75..1cef59c148 100644 --- a/exchange/exchange-ps/exchange/Start-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-compliancesearch applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Start-ComplianceSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-compliancesearch +schema: 2.0.0 +title: Start-ComplianceSearch --- # Start-ComplianceSearch @@ -48,6 +49,9 @@ This example starts 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 start. You can use any value that uniquely identifies the compliance search. For example: @@ -61,7 +65,6 @@ You can find these values by running the command Get-ComplianceSearch | Format-T Type: ComplianceSearchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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. @@ -98,7 +106,6 @@ 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 @@ -108,13 +115,15 @@ Accept wildcard characters: False ``` ### -RetryOnError + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The RetryOnError switch specifies whether to retry the search on any items that failed without re-running the entire search 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 @@ -124,6 +133,9 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance + The WhatIf parameter doesn't work in the Microsoft Purview compliance portal. 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. @@ -132,7 +144,6 @@ 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/exchange/Start-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md similarity index 89% rename from exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md index 771a794112..01a45f83ff 100644 --- a/exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-databaseavailabilitygroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Start-DatabaseAvailabilityGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-databaseavailabilitygroup +schema: 2.0.0 +title: Start-DatabaseAvailabilityGroup --- # Start-DatabaseAvailabilityGroup @@ -64,13 +65,15 @@ This example starts the members of the DAG DAG1 in the Active Directory site Red ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the DAG being started. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -80,13 +83,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectorySite + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectorySite parameter specifies whether to start all DAG members in the specified site. ```yaml Type: AdSiteIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -96,13 +101,15 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies whether to start a single DAG member. ```yaml Type: MailboxServerIdParameter Parameter Sets: MailboxSet Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -112,13 +119,15 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConfigurationOnly switch specifies whether to update the Active Directory properties with the start action, but doesn't perform a start of the DAG or any members. 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 @@ -128,6 +137,9 @@ 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`. @@ -137,7 +149,6 @@ 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 @@ -147,13 +158,15 @@ 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 @@ -163,13 +176,15 @@ 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/exchange/Start-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md similarity index 90% rename from exchange/exchange-ps/exchange/Start-EdgeSynchronization.md rename to exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md index a61cfb7896..8f0ce16ec3 100644 --- a/exchange/exchange-ps/exchange/Start-EdgeSynchronization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-edgesynchronization applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Start-EdgeSynchronization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-edgesynchronization +schema: 2.0.0 +title: Start-EdgeSynchronization --- # Start-EdgeSynchronization @@ -47,6 +48,9 @@ This example starts edge synchronization on the Mailbox server named Mailbox01. ## 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`. @@ -56,7 +60,6 @@ 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,6 +69,9 @@ Accept wildcard characters: False ``` ### -ForceFullSync + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceFullSync switch specifies whether to initiate a full edge synchronization. You don't need to specify a value with this switch. If you don't use this switch, only changes since the last replication are synchronized. If you use this switch, the entire configuration information and recipient data are synchronized. @@ -74,7 +80,6 @@ If you don't use this switch, only changes since the last replication are synchr Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -84,6 +89,9 @@ Accept wildcard characters: False ``` ### -ForceUpdateCookie + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ForceUpdateCookie switch specifies whether to force the Microsoft Exchange EdgeSync service to update the replication cookie even if it encounters an error. You don't need to specify a value with this switch. The cookie maintains the changes in Active Directory since the previous EdgeSync replication. Normally, the Microsoft Exchange EdgeSync service doesn't update the cookie if it encounters any errors during replication. @@ -92,7 +100,6 @@ The cookie maintains the changes in Active Directory since the previous EdgeSync Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -102,6 +109,9 @@ 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 @@ -115,7 +125,6 @@ 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 @@ -125,6 +134,9 @@ Accept wildcard characters: False ``` ### -TargetServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized. You may want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server has been installed or if that Edge Transport server has been unavailable for some time. @@ -133,7 +145,6 @@ You may want to use this parameter to specify a single Edge Transport server for Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -143,13 +154,15 @@ 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/exchange/Start-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md similarity index 91% rename from exchange/exchange-ps/exchange/Start-HistoricalSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md index 598f93159b..6471dc218d 100644 --- a/exchange/exchange-ps/exchange/Start-HistoricalSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-historicalsearch applicable: Exchange Online, Exchange Online Protection -title: Start-HistoricalSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-historicalsearch +schema: 2.0.0 +title: Start-HistoricalSearch --- # Start-HistoricalSearch @@ -68,6 +69,9 @@ This example starts a new historical search named "Fabrikam Search" that has the ## 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". @@ -80,7 +84,6 @@ You also need to use at least one of the following parameters in the command: Me Type: DateTime Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -90,6 +93,9 @@ Accept wildcard characters: False ``` ### -ReportTitle + +> Applicable: Exchange Online, Exchange Online Protection + The ReportTitle parameter specifies a descriptive name for the historical search. If the value contains spaces, enclose the value in quotation marks ("). You also need to use at least one of the following parameters in the command: MessageID, RecipientAddress, or SenderAddress. @@ -98,7 +104,6 @@ You also need to use at least one of the following parameters in the command: Me Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -108,6 +113,9 @@ Accept wildcard characters: False ``` ### -ReportType + +> Applicable: Exchange Online, Exchange Online Protection + The ReportType parameter specifies the type of historical search that you want to perform. You can use one of the following values: - ATPReport: Defender for Office 365 File types report and Defender for Office 365 Message disposition report @@ -128,7 +136,6 @@ You also need to use at least one of the following parameters in the command: Me Type: HistoricalSearchReportType Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -138,6 +145,9 @@ 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". @@ -146,7 +156,6 @@ 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: True Position: Named @@ -156,13 +165,15 @@ Accept wildcard characters: False ``` ### -BlockStatus + +> Applicable: Exchange Online, Exchange Online Protection + The BlockStatus parameter filters the results in OutboundSecurityReport reports by the status of messages sent externally, messages blocked due to security checks, or messages sent successfully. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -172,13 +183,15 @@ Accept wildcard characters: False ``` ### -CompressFile + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill CompressFile Description }} ```yaml Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -188,6 +201,9 @@ Accept wildcard characters: False ``` ### -ConnectorType + +> Applicable: Exchange Online, Exchange Online Protection + The ConnectorType parameter filters the results in ConnectorReport reports by the connector type. Valid values are: - OnPremises @@ -198,7 +214,6 @@ The ConnectorType parameter filters the results in ConnectorReport reports by th Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -208,6 +223,9 @@ Accept wildcard characters: False ``` ### -DeliveryStatus + +> Applicable: Exchange Online, Exchange Online Protection + The DeliveryStatus parameter filters the results by the delivery status of the message. You can use one of the following values: - Delivered @@ -218,7 +236,6 @@ The DeliveryStatus parameter filters the results by the delivery status of the m Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -228,6 +245,9 @@ Accept wildcard characters: False ``` ### -Direction + +> Applicable: Exchange Online, Exchange Online Protection + The Direction parameter filters the results by the direction of the message. Valid values are: - All: Incoming and outgoing messages. @@ -238,7 +258,6 @@ The Direction parameter filters the results by the direction of the message. Val Type: MessageDirection Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -248,13 +267,15 @@ Accept wildcard characters: False ``` ### -DLPPolicy + +> Applicable: Exchange Online, Exchange Online Protection + The DLPPolicy parameter filters the results by the name of the DLP policy that acted on the message. You can specify multiple DLP policies separated by commas. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -264,13 +285,15 @@ Accept wildcard characters: False ``` ### -EncryptionTemplate + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill EncryptionTemplate Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -280,13 +303,15 @@ Accept wildcard characters: False ``` ### -EncryptionType + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill EncryptionType Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -296,6 +321,9 @@ Accept wildcard characters: False ``` ### -Locale + +> Applicable: Exchange Online, Exchange Online Protection + The Locale parameter filters the results by the locale of the message. 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). @@ -304,7 +332,6 @@ Valid input for this parameter is a supported culture code value from the Micros Type: CultureInfo Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -314,13 +341,15 @@ 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 @@ -330,13 +359,15 @@ Accept wildcard characters: False ``` ### -NetworkMessageID + +> Applicable: Exchange Online, Exchange Online Protection + 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: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -346,6 +377,9 @@ Accept wildcard characters: False ``` ### -NotifyAddress + +> Applicable: Exchange Online, Exchange Online Protection + The NotifyAddress parameter specifies the email addresses of internal recipients to notify when the historical search is complete. The email address must be in an accepted domain that's configured for your organization. You can enter multiple email addresses separated by commas. To view the results of the historical search, you need to specify at least one email address for the NotifyAddress parameter. Otherwise, you need to click on the completed message trace in the Exchange admin center at **Mail flow** \> **Message trace**. @@ -354,7 +388,6 @@ To view the results of the historical search, you need to specify at least one e Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -364,13 +397,15 @@ Accept wildcard characters: False ``` ### -OriginalClientIP + +> Applicable: Exchange Online, Exchange Online Protection + The OriginalClientIP parameter filters the results by the original IP address of the message. For incoming messages, the OriginalClientIP value is the sender's IP address. For outgoing messages, the OriginalClientIP value is the IP address of the external SMTP server that received the message. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -380,13 +415,15 @@ 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. The maximum number of addresses is 100. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -396,13 +433,15 @@ Accept wildcard characters: True ``` ### -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. The maximum number of addresses is 100. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -412,13 +451,15 @@ Accept wildcard characters: False ``` ### -SmtpSecurityError + +> Applicable: Exchange Online, Exchange Online Protection + The SmtpSecurityError parameter filters the results in OutboundSecurityReport reports by the error type of blocked messages when sent externally. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -428,6 +469,9 @@ Accept wildcard characters: False ``` ### -TLSUsed + +> Applicable: Exchange Online, Exchange Online Protection + The TLSUsed parameter filters the results in ConnectorReport reports by the TLS version. Valid values are: - No Tls @@ -438,7 +482,6 @@ The TLSUsed parameter filters the results in ConnectorReport reports by the TLS Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -448,13 +491,15 @@ Accept wildcard characters: False ``` ### -TransportRule + +> Applicable: Exchange Online, Exchange Online Protection + The TransportRule parameter filters the results by the name of the Exchange mail flow rule (also known as a transport rule) that acted on the message. You can specify multiple transport rules separated by commas. ```yaml Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -464,13 +509,15 @@ Accept wildcard characters: False ``` ### -Url + +> Applicable: Exchange Online, Exchange Online Protection + {{ Fill Url Description }} ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/ExchangePowerShell/Start-InformationBarrierPoliciesApplication.md similarity index 95% rename from exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md rename to exchange/exchange-ps/ExchangePowerShell/Start-InformationBarrierPoliciesApplication.md index 2afb3f3ca7..ae7929d08d 100644 --- a/exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-InformationBarrierPoliciesApplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-informationbarrierpoliciesapplication applicable: Security & Compliance -title: Start-InformationBarrierPoliciesApplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-informationbarrierpoliciesapplication +schema: 2.0.0 +title: Start-InformationBarrierPoliciesApplication --- # Start-InformationBarrierPoliciesApplication @@ -43,13 +44,15 @@ This applies all active information barrier policies. ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + This parameter is reserved for internal Microsoft use. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: False Position: 0 @@ -59,13 +62,15 @@ Accept wildcard characters: False ``` ### -CleanupGroupSegmentLink + +> Applicable: Security & Compliance + The CleanupGroupSegmentLink switch specifies whether to remove group segment links. 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 @@ -75,6 +80,9 @@ 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,7 +92,6 @@ 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 @@ -94,13 +101,15 @@ 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/exchange/Start-MailboxAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md similarity index 94% rename from exchange/exchange-ps/exchange/Start-MailboxAssistant.md rename to exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md index 52a05e9bcb..0ea5aed2bd 100644 --- a/exchange/exchange-ps/exchange/Start-MailboxAssistant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-mailboxassistant applicable: Exchange Server 2019 -title: Start-MailboxAssistant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-mailboxassistant +schema: 2.0.0 +title: Start-MailboxAssistant --- # Start-MailboxAssistant @@ -46,6 +47,9 @@ This example starts the `BigFunnelRetryFeederTimeBasedAssistant` assistant and l ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2019 + The Identity parameter specifies the user whose mailbox should be processed by the Mailbox Assistant. Valid values are: - Distinguished name (DN) @@ -56,7 +60,6 @@ The Identity parameter specifies the user whose mailbox should be processed by t Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: True Position: 0 @@ -66,6 +69,9 @@ Accept wildcard characters: False ``` ### -AssistantName + +> Applicable: Exchange Server 2019 + The AssistantName parameter specifies the assistant that should process the mailbox. Valid values are: - BigFunnelRetryFeederTimeBasedAssistant @@ -76,7 +82,6 @@ Values are case sensitive. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: True Position: Named @@ -86,6 +91,9 @@ 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`. @@ -95,7 +103,6 @@ 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 @@ -105,13 +112,15 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: 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 2019 Required: False Position: Named @@ -121,13 +130,15 @@ Accept wildcard characters: False ``` ### -Parameters + +> Applicable: Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -137,6 +148,9 @@ Accept wildcard characters: False ``` ### -SoftDeletedMailbox + +> Applicable: Exchange Server 2019 + The SoftDeletedMailbox switch specifies that the mailbox to be processed by the assistant is a soft-deleted mailbox. Soft-deleted mailboxes are deleted mailboxes that are still recoverable. @@ -145,7 +159,6 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -155,13 +168,15 @@ 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/exchange/Start-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md similarity index 89% rename from exchange/exchange-ps/exchange/Start-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md index a84f5ccd78..9c1c342381 100644 --- a/exchange/exchange-ps/exchange/Start-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-mailboxsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Start-MailboxSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-mailboxsearch +schema: 2.0.0 +title: Start-MailboxSearch --- # Start-MailboxSearch @@ -56,13 +57,15 @@ This example starts the mailbox search ProjectContoso. ## 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 search. The name is referenced when starting, stopping, or removing the search. ```yaml Type: SearchObjectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,6 +96,9 @@ 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,7 +107,6 @@ 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,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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 Required: False Position: Named @@ -127,6 +136,9 @@ Accept wildcard characters: False ``` ### -Resume + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Resume switch resumes a stopped, failed, or partially succeeded search from the point it stopped. You don't need to specify a value with this switch. If you use this switch to resume a search, previous search results aren't removed from the target mailbox. @@ -135,7 +147,6 @@ If you use this switch to resume a search, previous search results aren't remove 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 @@ -145,13 +156,15 @@ Accept wildcard characters: False ``` ### -StatisticsStartIndex + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The StatisticsStartIndex parameter is used by the EAC to retrieve keyword statistics in a paged operation. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -161,13 +174,15 @@ 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/exchange/Start-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md similarity index 93% rename from exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md rename to exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md index 2e90b4cf4d..09ae1e894c 100644 --- a/exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-managedfolderassistant applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Start-ManagedFolderAssistant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-managedfolderassistant +schema: 2.0.0 +title: Start-ManagedFolderAssistant --- # Start-ManagedFolderAssistant @@ -137,6 +138,9 @@ This example uses the Get-Mailbox command to retrieve all the mailboxes that res ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the mailbox to be processed. In cross-premises deployments, you can also specify a mail user who has a mailbox in the cloud. You can use any value that uniquely identifies the mailbox or mail user. For example: - Name @@ -156,7 +160,6 @@ The Identity parameter specifies the mailbox to be processed. In cross-premises Type: MailboxOrMailUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -166,6 +169,9 @@ Accept wildcard characters: False ``` ### -AdaptiveScope + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill AdaptiveScope Description }} @@ -174,7 +180,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ComplianceBoundaryAssistantParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -184,6 +189,9 @@ Accept wildcard characters: False ``` ### -AggMailboxCleanup + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The AggMailboxCleanup switch specifies aggregate mailbox cleanup. You don't need to specify a value with this switch. This switch cleans up aggregate mailboxes, audits, and calendar logging. @@ -192,7 +200,6 @@ This switch cleans up aggregate mailboxes, audits, and calendar logging. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -202,6 +209,9 @@ Accept wildcard characters: False ``` ### -B2DumpsterArchiver + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill B2DumpsterArchiver Description }} @@ -210,7 +220,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ElcB2DumpsterArchiverAssistantParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -220,6 +229,9 @@ Accept wildcard characters: False ``` ### -B2IPMArchiver + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. {{ Fill B2IPMArchiver Description }} @@ -228,7 +240,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ElcB2IPMArchiverAssistantParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -238,6 +249,9 @@ Accept wildcard characters: False ``` ### -ComplianceJob + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -246,7 +260,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: ComplianceJobAssistantParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -256,6 +269,9 @@ 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`. @@ -265,7 +281,6 @@ 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 @@ -275,6 +290,9 @@ Accept wildcard characters: False ``` ### -DataGovernance + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -283,7 +301,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: DataGovernanceAssistantParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -293,6 +310,9 @@ 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. @@ -301,7 +321,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -311,6 +330,9 @@ Accept wildcard characters: False ``` ### -FullCrawl + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The FullCrawl switch recalculates the application of tags across the whole mailbox. You don't need to specify a value with this switch. @@ -319,7 +341,6 @@ The FullCrawl switch recalculates the application of tags across the whole mailb Type: SwitchParameter Parameter Sets: ComplianceBoundaryAssistantParameterSet, ComplianceJobAssistantParameterSet, DataGovernanceAssistantParameterSet, ElcB2DumpsterArchiverAssistantParameterSet, ElcB2IPMArchiverAssistantParameterSet, HoldCleanupParameterSet, StopHoldCleanupParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -329,6 +350,9 @@ Accept wildcard characters: False ``` ### -HoldCleanup + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that may have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch. Removing duplicate items from the Recoverable Items folder reduces the folder size and may help prevent reaching Recoverable Items quota limits. For more details about Recoverable Items quota limits, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder). @@ -337,7 +361,6 @@ Removing duplicate items from the Recoverable Items folder reduces the folder si Type: SwitchParameter Parameter Sets: Identity, HoldCleanupParameterSet Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -347,6 +370,9 @@ Accept wildcard characters: False ``` ### -InactiveMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The InactiveMailbox switch runs the command only on inactive mailboxes. You don't need to specify a value with this switch. @@ -359,7 +385,6 @@ When you use this switch, items aren't moved from the inactive mailbox to the ar Type: SwitchParameter Parameter Sets: ComplianceBoundaryAssistantParameterSet, ComplianceJobAssistantParameterSet, DataGovernanceAssistantParameterSet, ElcB2DumpsterArchiverAssistantParameterSet, ElcB2IPMArchiverAssistantParameterSet, HoldCleanupParameterSet, StopHoldCleanupParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -369,6 +394,9 @@ Accept wildcard characters: False ``` ### -StopHoldCleanup + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The StopHoldCleanup switch stops a previous hold clean-up command that was issued on the mailbox. You don't need to specify a value with this switch. @@ -379,7 +407,6 @@ A hold clean-up command will run until it completely scans the Recoverable Items Type: SwitchParameter Parameter Sets: StopHoldCleanupParameterSet Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -389,13 +416,15 @@ 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/exchange/Start-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md similarity index 91% rename from exchange/exchange-ps/exchange/Start-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md index cf1d3e9731..378d180393 100644 --- a/exchange/exchange-ps/exchange/Start-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-migrationbatch applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Start-MigrationBatch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-migrationbatch +schema: 2.0.0 +title: Start-MigrationBatch --- # Start-MigrationBatch @@ -51,13 +52,15 @@ This example starts the migration batch SEM1. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter identifies the migration batch that you want to start. Use the migration batch Name parameter as the value for this parameter. Use the Get-MigrationBatch cmdlet to identify the name of 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 @@ -67,6 +70,9 @@ 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`. @@ -76,7 +82,6 @@ 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 @@ -86,6 +91,9 @@ 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,7 +102,6 @@ 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 @@ -104,6 +111,9 @@ 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. @@ -112,7 +122,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -122,6 +131,9 @@ Accept wildcard characters: False ``` ### -Validate + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The Validate switch starts the migration batch in the validation stage of the migration process. You don't need to specify a value with this switch. @@ -132,7 +144,6 @@ If you use this switch, the migration performs a validation check of the mailbox Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,13 +153,15 @@ 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/exchange/Start-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md similarity index 92% rename from exchange/exchange-ps/exchange/Start-MigrationUser.md rename to exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md index be88fe1878..b0d711c10c 100644 --- a/exchange/exchange-ps/exchange/Start-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-migrationuser applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Start-MigrationUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-migrationuser +schema: 2.0.0 +title: Start-MigrationUser --- # Start-MigrationUser @@ -44,6 +45,9 @@ This example starts the migration of the user named laura@contoso.com ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the email address of the user that's being migrated. You can also identify the user by the GUID value in the MigrationUser property from the output of the Get-MigrationUser cmdlet. This identification method is useful if you accidentally submitted the same user in multiple batches. @@ -52,7 +56,6 @@ You can also identify the user by the GUID value in the MigrationUser property f Type: MigrationUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,6 +86,9 @@ 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. @@ -89,7 +97,6 @@ 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 @@ -99,6 +106,9 @@ 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. @@ -107,7 +117,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -117,13 +126,15 @@ 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/exchange/Start-RetentionAutoTagLearning.md b/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md similarity index 95% rename from exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md rename to exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md index 3ad1a2652d..8d716b1986 100644 --- a/exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md +++ b/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/start-retentionautotaglearning applicable: Exchange Server 2010 -title: Start-RetentionAutoTagLearning -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/start-retentionautotaglearning +schema: 2.0.0 +title: Start-RetentionAutoTagLearning --- # Start-RetentionAutoTagLearning @@ -73,6 +74,9 @@ This example sets user Joe Healy's mailbox to clear all retention policy tags as ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + The Identity parameter identifies the mailbox. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -90,7 +94,6 @@ The Identity parameter identifies the mailbox. You can use any value that unique Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -100,13 +103,15 @@ Accept wildcard characters: False ``` ### -CrossValidate + +> Applicable: Exchange Server 2010 + The CrossValidate switch specifies whether items in the specified mailbox are being auto-tagged. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: CrossValidate Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -116,13 +121,15 @@ Accept wildcard characters: False ``` ### -Clear + +> Applicable: Exchange Server 2010 + The Clear switch specifies whether to clear auto-tags from the specified mailbox. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Train Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -132,6 +139,9 @@ 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`. @@ -141,7 +151,6 @@ 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 @@ -151,13 +160,15 @@ 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 @@ -167,6 +178,9 @@ Accept wildcard characters: False ``` ### -NumberOfSegments + +> Applicable: Exchange Server 2010 + The NumberOfSegments parameter specifies the number of segments. Auto-tagging divides a mailbox into the number of segments specified and learns tagging behavior from n-1 segments. Tags are then predicted for items in the remaining segment based on this behavior. This is done for each segment. The default value is 10. @@ -179,7 +193,6 @@ You csn only use this parameter with the CrossValidate parameter. Type: Int32 Parameter Sets: CrossValidate Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -189,6 +202,9 @@ Accept wildcard characters: False ``` ### -Train + +> Applicable: Exchange Server 2010 + The Train switch specifies whether to start the training algorithm for auto-tagging on the specified mailbox. You don't need to specify a value with this switch. This switch is especially useful for retraining. @@ -197,7 +213,6 @@ This switch is especially useful for retraining. Type: SwitchParameter Parameter Sets: Train Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -207,13 +222,15 @@ 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/exchange/Stop-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md similarity index 93% rename from exchange/exchange-ps/exchange/Stop-ComplianceSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md index a0b52107ee..7e67a57cf5 100644 --- a/exchange/exchange-ps/exchange/Stop-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-compliancesearch applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance -title: Stop-ComplianceSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-compliancesearch +schema: 2.0.0 +title: Stop-ComplianceSearch --- # Stop-ComplianceSearch @@ -46,6 +47,9 @@ This example stops the active 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 stop. You can use any value that uniquely identifies the compliance search. For example: @@ -59,7 +63,6 @@ You can find these values by running the command Get-ComplianceSearch | Format-T Type: ComplianceSearchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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. @@ -96,7 +104,6 @@ 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/exchange/Stop-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md similarity index 90% rename from exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md index c9f3ae6135..4a32f64329 100644 --- a/exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-databaseavailabilitygroup applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Stop-DatabaseAvailabilityGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-databaseavailabilitygroup +schema: 2.0.0 +title: Stop-DatabaseAvailabilityGroup --- # Stop-DatabaseAvailabilityGroup @@ -71,13 +72,15 @@ This example stops the Mailbox server MBX3, which is currently offline, in the D ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the name of the DAG being stopped. ```yaml Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -87,13 +90,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectorySite + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectorySite parameter specifies the Active Directory site containing the DAG members to stop (for example, stop all DAG members in a particular Active Directory site). ```yaml Type: AdSiteIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -103,13 +108,15 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies a single DAG member to stop. If Datacenter Activation Coordination mode is enabled for the DAG and all DAG members are in the same Active Directory site, use the MailboxServer parameter to stop individual DAG members instead of the ActiveDirectorySite parameter when stopping failed DAG members. ```yaml Type: MailboxServerIdParameter Parameter Sets: MailboxSet Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -119,6 +126,9 @@ Accept wildcard characters: False ``` ### -ConfigurationOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConfigurationOnly switch updates the Active Directory properties with the stop action, but doesn't perform a stop of the DAG or any members. You don't need to specify a value with this switch. You eed to use this switch when the DAG member servers are offline, but Active Directory is up and accessible in the primary datacenter. @@ -127,7 +137,6 @@ You eed to use this switch when the DAG member servers are offline, but Active D Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -137,6 +146,9 @@ 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`. @@ -146,7 +158,6 @@ 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,13 +167,15 @@ 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 @@ -172,13 +185,15 @@ 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/exchange/Stop-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md similarity index 96% rename from exchange/exchange-ps/exchange/Stop-HistoricalSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md index 314339dd93..3a8d4cf16d 100644 --- a/exchange/exchange-ps/exchange/Stop-HistoricalSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-historicalsearch applicable: Exchange Online, Exchange Online Protection -title: Stop-HistoricalSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-historicalsearch +schema: 2.0.0 +title: Stop-HistoricalSearch --- # Stop-HistoricalSearch @@ -44,13 +45,15 @@ This example stops the historical search that has the JobId value f9c66f83-b5c8- ## PARAMETERS ### -JobId + +> Applicable: Exchange Online, Exchange Online Protection + The JobId parameter specifies the identity GUID value of the historical search that you want to stop. ```yaml Type: Guid Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md b/exchange/exchange-ps/ExchangePowerShell/Stop-InformationBarrierPoliciesApplication.md similarity index 96% rename from exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-InformationBarrierPoliciesApplication.md index 00b91d2c2c..81ac30ccc6 100644 --- a/exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-InformationBarrierPoliciesApplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-informationbarrierpoliciesapplication applicable: Security & Compliance -title: Stop-InformationBarrierPoliciesApplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-informationbarrierpoliciesapplication +schema: 2.0.0 +title: Stop-InformationBarrierPoliciesApplication --- # Stop-InformationBarrierPoliciesApplication @@ -42,13 +43,15 @@ This example stops the application of information barrier policies per the polic ## PARAMETERS ### -Identity + +> Applicable: Security & Compliance + The Identity parameter specifies the active application of information barrier policies that you want to stop. This value is a GUID that's assigned when you run the Start-InformationBarrierPoliciesApplication cmdlet (for example, 46237888-12ca-42e3-a541-3fcb7b5231d1). You can also find the Identity value of the most recent policy application running the command Get-InformationBarrierPoliciesApplicationStatus. ```yaml Type: PolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 0 @@ -58,6 +61,9 @@ 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`. @@ -67,7 +73,6 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Stop-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md similarity index 90% rename from exchange/exchange-ps/exchange/Stop-MailboxSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md index b78b8cb8b3..f3574be842 100644 --- a/exchange/exchange-ps/exchange/Stop-MailboxSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-mailboxsearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Stop-MailboxSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-mailboxsearch +schema: 2.0.0 +title: Stop-MailboxSearch --- # Stop-MailboxSearch @@ -47,13 +48,15 @@ This example stops the mailbox search 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 mailbox search. ```yaml Type: SearchObjectIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,6 +87,9 @@ 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,7 +98,6 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Stop-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md similarity index 92% rename from exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md index 0b03abf051..279639ab37 100644 --- a/exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-managedfolderassistant applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Stop-ManagedFolderAssistant -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-managedfolderassistant +schema: 2.0.0 +title: Stop-ManagedFolderAssistant --- # Stop-ManagedFolderAssistant @@ -52,6 +53,9 @@ This example stops the Managed Folder Assistant on the servers ExchSrvr1 and Exc ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, 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 @@ -65,7 +69,6 @@ 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: 1 @@ -75,6 +78,9 @@ 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,7 +90,6 @@ 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,13 +99,15 @@ 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 @@ -110,13 +117,15 @@ 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/exchange/Stop-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md similarity index 92% rename from exchange/exchange-ps/exchange/Stop-MigrationBatch.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md index 2c68616341..1a5fedfb04 100644 --- a/exchange/exchange-ps/exchange/Stop-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-migrationbatch applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Stop-MigrationBatch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-migrationbatch +schema: 2.0.0 +title: Stop-MigrationBatch --- # Stop-MigrationBatch @@ -53,13 +54,15 @@ This example stops the migration batch MigrationBatch1. ## 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. ```yaml Type: MigrationBatchIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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,7 +104,6 @@ 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 @@ -106,6 +113,9 @@ 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. @@ -114,7 +124,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -124,13 +133,15 @@ 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/exchange/Stop-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md similarity index 92% rename from exchange/exchange-ps/exchange/Stop-MigrationUser.md rename to exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md index ccaca8fe4d..ae78f85ad8 100644 --- a/exchange/exchange-ps/exchange/Stop-MigrationUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/stop-migrationuser applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Stop-MigrationUser -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/stop-migrationuser +schema: 2.0.0 +title: Stop-MigrationUser --- # Stop-MigrationUser @@ -44,6 +45,9 @@ This example stops the migration of the user laura@contoso.com. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the email address of the user that's being migrated. You can also identify the user by the GUID value in the MigrationUser property from the output of the Get-MigrationUser cmdlet. This identification method is useful if you accidentally submitted the same user in multiple batches. @@ -52,7 +56,6 @@ You can also identify the user by the GUID value in the MigrationUser property f Type: MigrationUserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,6 +86,9 @@ 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. @@ -89,7 +97,6 @@ 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 @@ -99,6 +106,9 @@ 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. @@ -107,7 +117,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -117,13 +126,15 @@ 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/exchange/Suspend-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md similarity index 89% rename from exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md index bbd7d1ecfa..917a98ccea 100644 --- a/exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxdatabasecopy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-MailboxDatabaseCopy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxdatabasecopy +schema: 2.0.0 +title: Suspend-MailboxDatabaseCopy --- # Suspend-MailboxDatabaseCopy @@ -63,13 +64,15 @@ This example only suspends activation for the copy of the database DB3 hosted on ## 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 being suspended. ```yaml Type: DatabaseCopyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -79,13 +82,15 @@ Accept wildcard characters: False ``` ### -ActivationOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActivationOnly switch specifies whether to suspend only activation for the mailbox database copy. 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 @@ -95,6 +100,9 @@ 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,7 +112,6 @@ 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 @@ -114,13 +121,15 @@ 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,13 +139,15 @@ Accept wildcard characters: False ``` ### -EnableReplayLag + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: EnableReplayLag Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -146,13 +157,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies the reason that the database copy is being suspended. This parameter is limited to 512 characters. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -162,13 +175,15 @@ 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/exchange/Suspend-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md index 5f063c4f44..ca2152393e 100644 --- a/exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxexportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-MailboxExportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxexportrequest +schema: 2.0.0 +title: Suspend-MailboxExportRequest --- # Suspend-MailboxExportRequest @@ -53,13 +54,15 @@ This example suspends all export requests that are in progress by using the Get- ## 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). Use the following syntax: `Alias\Name`. ```yaml Type: MailboxExportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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 @@ -104,13 +111,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend 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 @@ -120,13 +129,15 @@ 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/exchange/Suspend-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md index 41e44b0123..28164e5104 100644 --- a/exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboximportrequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Suspend-MailboxImportRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboximportrequest +schema: 2.0.0 +title: Suspend-MailboxImportRequest --- # Suspend-MailboxImportRequest @@ -55,13 +56,15 @@ This example suspends all import requests that are in progress by using the Get- ## 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 created the request by using the Name parameter, use the following syntax: `Alias\Name`. ```yaml Type: MailboxImportRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -71,6 +74,9 @@ 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`. @@ -80,7 +86,6 @@ 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 @@ -90,6 +95,9 @@ 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,7 +106,6 @@ 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,13 +115,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```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 @@ -124,13 +133,15 @@ 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/exchange/Suspend-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md index ca7cdcbde0..ad8afda380 100644 --- a/exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxrestorerequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Suspend-MailboxRestoreRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-mailboxrestorerequest +schema: 2.0.0 +title: Suspend-MailboxRestoreRequest --- # Suspend-MailboxRestoreRequest @@ -51,6 +52,9 @@ This example suspends all restore requests that are in progress by using the Get ## 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). @@ -59,7 +63,6 @@ If you didn't specify a name for the restore request when it was created, Exchan Type: MailboxRestoreRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -69,6 +72,9 @@ 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,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ 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,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description about why the request was suspended. ```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 @@ -122,13 +131,15 @@ 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/exchange/Suspend-Message.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md similarity index 92% rename from exchange/exchange-ps/exchange/Suspend-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md index e978e8d3de..9baa60bda4 100644 --- a/exchange/exchange-ps/exchange/Suspend-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-message applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-Message -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-message +schema: 2.0.0 +title: Suspend-Message --- # Suspend-Message @@ -61,13 +62,15 @@ This example prevents delivery of all messages for which the following condition ## 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: True Position: 1 @@ -77,6 +80,9 @@ 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 ("). @@ -85,7 +91,6 @@ 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: True Position: Named @@ -95,6 +100,9 @@ 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,7 +112,6 @@ 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 @@ -114,6 +121,9 @@ 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 @@ -129,7 +139,6 @@ 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 @@ -139,13 +148,15 @@ 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/exchange/Suspend-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md similarity index 90% rename from exchange/exchange-ps/exchange/Suspend-MoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md index 852bd02d0b..85bdc68daa 100644 --- a/exchange/exchange-ps/exchange/Suspend-MoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-moverequest applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Suspend-MoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-moverequest +schema: 2.0.0 +title: Suspend-MoveRequest --- # Suspend-MoveRequest @@ -52,6 +53,9 @@ This example suspends all move requests that are in progress by using the Get-Mo ## 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 @@ -66,7 +70,6 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c Type: MoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -76,6 +79,9 @@ 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,7 +91,6 @@ 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,6 +100,9 @@ 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,7 +111,6 @@ 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,6 +120,9 @@ Accept wildcard characters: False ``` ### -ProxyToMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ProxyToMailbox parameter specifies the move destination by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example: @@ -132,7 +142,6 @@ The ProxyToMailbox parameter specifies the move destination by the location of t Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -142,13 +151,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a description as to why the request was suspended. ```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 @@ -158,13 +169,15 @@ 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/exchange/Suspend-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md index 6e8a63fbb7..64c756ef6a 100644 --- a/exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermailboxmigrationrequest applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Suspend-PublicFolderMailboxMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermailboxmigrationrequest +schema: 2.0.0 +title: Suspend-PublicFolderMailboxMigrationRequest --- # Suspend-PublicFolderMailboxMigrationRequest @@ -44,13 +45,15 @@ This example suspends the specified public folder mailbox migration request. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the public folder mailbox migration request that you want to suspend. This value uses the syntax `\PublicFolderMailboxMigration` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`). ```yaml Type: PublicFolderMailboxMigrationRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,6 +84,9 @@ 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. @@ -87,7 +95,6 @@ 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 @@ -97,13 +104,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuspendComment parameter specifies a descriptive reason for why you suspended the public folder mailbox migration. 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 @@ -113,13 +122,15 @@ 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/exchange/Suspend-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md similarity index 92% rename from exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md index 824fe531ac..907d73d325 100644 --- a/exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermigrationrequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-PublicFolderMigrationRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermigrationrequest +schema: 2.0.0 +title: Suspend-PublicFolderMigrationRequest --- # Suspend-PublicFolderMigrationRequest @@ -53,6 +54,9 @@ This example suspends all migration requests that are in progress by using the G ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the migration request that you want to suspend. You can use the following values: - Name @@ -62,7 +66,6 @@ The Identity parameter specifies the migration request that you want to suspend. Type: PublicFolderMigrationRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -72,6 +75,9 @@ 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`. @@ -81,7 +87,6 @@ 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 @@ -91,13 +96,15 @@ 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,13 +114,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies a description as to why the request was suspended. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -123,13 +132,15 @@ 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/exchange/Suspend-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md similarity index 91% rename from exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md index fc298d21c8..c700dba43a 100644 --- a/exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermoverequest applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-PublicFolderMoveRequest -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfoldermoverequest +schema: 2.0.0 +title: Suspend-PublicFolderMoveRequest --- # Suspend-PublicFolderMoveRequest @@ -44,13 +45,15 @@ This example suspends the public folder move request \\PublicFolderMove. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the identity of the public folder move request. The default identity is \\PublicFolderMove. ```yaml Type: PublicFolderMoveRequestIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -60,6 +63,9 @@ 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`. @@ -69,7 +75,6 @@ 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 @@ -79,13 +84,15 @@ 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 @@ -95,13 +102,15 @@ Accept wildcard characters: False ``` ### -SuspendComment + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -111,13 +120,15 @@ 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/exchange/Suspend-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md similarity index 96% rename from exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md index 8819989303..208db85458 100644 --- a/exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfolderreplication applicable: Exchange Server 2010 -title: Suspend-PublicFolderReplication -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-publicfolderreplication +schema: 2.0.0 +title: Suspend-PublicFolderReplication --- # Suspend-PublicFolderReplication @@ -42,6 +43,9 @@ This example stops public folder replication for the organization. ## PARAMETERS ### -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`. @@ -51,7 +55,6 @@ 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 @@ -61,13 +64,15 @@ 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 @@ -77,13 +82,15 @@ 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/exchange/Suspend-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md similarity index 92% rename from exchange/exchange-ps/exchange/Suspend-Queue.md rename to exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md index 14102cc59b..5cf775e35d 100644 --- a/exchange/exchange-ps/exchange/Suspend-Queue.md +++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/suspend-queue applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Suspend-Queue -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/suspend-queue +schema: 2.0.0 +title: Suspend-Queue --- # Suspend-Queue @@ -63,13 +64,15 @@ This example suspends processing on all queues on the server Server1.contoso.com ## 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: True Position: 1 @@ -79,6 +82,9 @@ 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 ("). @@ -87,7 +93,6 @@ 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: True Position: Named @@ -97,6 +102,9 @@ 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`. @@ -106,7 +114,6 @@ 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,6 +123,9 @@ 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,7 +141,6 @@ 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 @@ -141,13 +150,15 @@ 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/exchange/Test-ActiveSyncConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md index 48f24eefda..72874c83e9 100644 --- a/exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-activesyncconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ActiveSyncConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-activesyncconnectivity +schema: 2.0.0 +title: Test-ActiveSyncConnectivity --- # Test-ActiveSyncConnectivity @@ -79,6 +80,9 @@ This example tests the Exchange ActiveSync connectivity for the mailbox PaulS us ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -94,7 +98,6 @@ You can't use this parameter with the Url parameter. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -104,6 +107,9 @@ Accept wildcard characters: False ``` ### -URL + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The URL parameter specifies the URL that's used to connect to the Exchange ActiveSync virtual directory. You can't use this parameter with the ClientAccessServer parameter. @@ -112,7 +118,6 @@ You can't use this parameter with the ClientAccessServer parameter. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -122,13 +127,15 @@ Accept wildcard characters: False ``` ### -AllowUnsecureAccess + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AllowUnsecureAccess switch allows the test to continue over an unsecured channel that doesn't require Secure Sockets Layer (SSL). 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 @@ -138,6 +145,9 @@ 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,7 +157,6 @@ 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 @@ -157,13 +166,15 @@ 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 @@ -173,6 +184,9 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LightMode switch tells the command to perform only a subset of the tests. You don't need to specify a value with this switch. When you use this switch, only the Options test is run. @@ -183,7 +197,6 @@ If you don't use this switch, the First Sync, GetItemEstimate, Sync Data, Ping a Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -193,6 +206,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test. 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). @@ -201,7 +217,6 @@ 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 @@ -211,6 +226,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -226,7 +244,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,6 +253,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -244,7 +264,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -254,13 +273,15 @@ Accept wildcard characters: False ``` ### -MonitoringInstance + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringInstance parameter specifies an identifier for this task when the test is run from Microsoft System Center Operations Manager (SCOM). This parameter is important because SCOM may run multiple instances of the test from the same server at the same time. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -270,6 +291,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -278,7 +302,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -288,13 +311,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Timeout parameter specifies the amount of time (in seconds) to wait for a response from the command. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -304,6 +329,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -312,7 +340,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -322,13 +349,15 @@ Accept wildcard characters: False ``` ### -UseAutodiscoverForClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseAutodiscoverForClientAccessServer switch specifies whether the test should use the Autodiscover service to locate the Exchange ActiveSync virtual directory. 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 @@ -338,13 +367,15 @@ 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/exchange/Test-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md similarity index 94% rename from exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md index 24d8280b0b..7aee38bab6 100644 --- a/exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-applicationaccesspolicy applicable: Exchange Online, Exchange Online Protection -title: Test-ApplicationAccessPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-applicationaccesspolicy +schema: 2.0.0 +title: Test-ApplicationAccessPolicy --- # Test-ApplicationAccessPolicy @@ -49,6 +50,9 @@ This example tests access to the user RandomUser9911@AppPolicyTest2.com for the ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the recipient to test. You can use any value that uniquely identifies the recipient. For example: - Name @@ -61,7 +65,6 @@ The Identity parameter specifies the recipient to test. You can use any value th Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -71,6 +74,9 @@ Accept wildcard characters: False ``` ### -AppId + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the GUID of the app that you want to test. 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. @@ -79,7 +85,6 @@ You can specify multiple app GUID values separated by commas. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md similarity index 91% rename from exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md index 219f178aa0..7cb120ec2c 100644 --- a/exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-archiveconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ArchiveConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-archiveconnectivity +schema: 2.0.0 +title: Test-ArchiveConnectivity --- # Test-ArchiveConnectivity @@ -53,13 +54,15 @@ This command retrieves mailboxes that have a cloud-based archive provisioned and ## PARAMETERS ### -UserSmtp + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UserSmtp parameter specifies the SMTP address of the mailbox. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -69,6 +72,9 @@ 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`. @@ -78,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ Accept wildcard characters: False ``` ### -IncludeArchiveMRMConfiguration + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IncludeArchiveMRMConfiguration switch retrieves retention tags that are provisioned in the user's archive mailbox and the last time the archive was processed by the Managed Folder Assistant. 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 @@ -104,13 +111,15 @@ Accept wildcard characters: False ``` ### -MessageId + +> Applicable: 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -120,13 +129,15 @@ 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/exchange/Test-AssistantHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-AssistantHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md index 95868838da..04749a66a1 100644 --- a/exchange/exchange-ps/exchange/Test-AssistantHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-assistanthealth applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-AssistantHealth -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-assistanthealth +schema: 2.0.0 +title: Test-AssistantHealth --- # Test-AssistantHealth @@ -58,6 +59,9 @@ This example detects the mailbox assistant's health on the local Mailbox server. ## PARAMETERS ### -ServerName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ServerName parameter specifies the Mailbox server where you want to run this command. You can use any value that uniquely identifies the server. For example: - Name @@ -71,7 +75,6 @@ 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: 1 @@ -81,6 +84,9 @@ 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`. @@ -90,7 +96,6 @@ 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 @@ -100,6 +105,9 @@ Accept wildcard characters: False ``` ### -IncludeCrashDump + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IncludeCrashDump switch specifies that the command should take an error report prior to taking any recovery actions. You don't need to specify a value with this switch. You should only use this switch on the local computer. If you use this switch while connected remotely, the command will fail. @@ -108,7 +116,6 @@ You should only use this switch on the local computer. If you use this switch wh Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,13 +125,15 @@ Accept wildcard characters: False ``` ### -MaxProcessingTimeInMinutes + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxProcessingTimeInMinutes parameter specifies the maximum amount of time the MSExchangeMailboxAssistants service is allowed to process an event without responding. You can specify a value from 1 through 3600 minutes. The default value is 15 minutes. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -134,6 +143,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -142,7 +154,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -152,6 +163,9 @@ Accept wildcard characters: False ``` ### -ResolveProblems + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This ResolveProblems switch specifies that if the command detects an issue, it attempts to fix it. You don't need to specify a value with this switch. This command attempts to fix the following issues: @@ -163,7 +177,6 @@ This command attempts to fix the following issues: Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -173,6 +186,9 @@ Accept wildcard characters: False ``` ### -WatermarkBehindWarningThreholdInMinutes + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The WatermarkBehindWarningThreholdInMinutes parameter specifies the threshold for watermark age. Event watermarks indicate the last time that events were successfully processed by an assistant. An event watermark that hasn't been updated in a while may indicate a problem. For each Mailbox Assistant, the Test-AssistantHealth cmdlet compares the current time with the time stamp of the last event watermark to determine the watermark age. If that age exceeds the value set by the WatermarkBehindWarningThreholdInMinutes parameter, a warning is generated. You can specify a value from 1 through 10080 minutes. The default value is 60 minutes. @@ -181,7 +197,6 @@ You can specify a value from 1 through 10080 minutes. The default value is 60 mi Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -191,13 +206,15 @@ 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/exchange/Test-CalendarConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-CalendarConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md index c2836a32a6..fd936c900e 100644 --- a/exchange/exchange-ps/exchange/Test-CalendarConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-calendarconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-CalendarConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-calendarconnectivity +schema: 2.0.0 +title: Test-CalendarConnectivity --- # Test-CalendarConnectivity @@ -72,6 +73,9 @@ This example tests the anonymous calendar sharing for the server named MBX01. ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -85,7 +89,6 @@ 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: 1 @@ -95,6 +98,9 @@ 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,7 +110,6 @@ 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 @@ -114,13 +119,15 @@ 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,13 +137,15 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -146,6 +155,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -161,7 +173,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,6 +182,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -179,7 +193,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -189,6 +202,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -197,7 +213,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -207,13 +222,15 @@ Accept wildcard characters: False ``` ### -TestType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal. ```yaml Type: OwaConnectivityTestType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -223,13 +240,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -239,13 +258,15 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -255,6 +276,9 @@ Accept wildcard characters: False ``` ### -VirtualDirectoryName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The VirtualDirectoryName parameter specifies the name of the Outlook on the web virtual directory that you want to test. Enclose values that contain spaces in quotation marks ("). If you don't use this parameter, all available Outlook on the web virtual directories are tested. @@ -263,7 +287,6 @@ If you don't use this parameter, all available Outlook on the web virtual direct Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -273,13 +296,15 @@ 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/exchange/Test-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-ClientAccessRule.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md index 3389d80031..482ffc6713 100644 --- a/exchange/exchange-ps/exchange/Test-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-clientaccessrule applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Test-ClientAccessRule -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-clientaccessrule +schema: 2.0.0 +title: Test-ClientAccessRule --- # Test-ClientAccessRule @@ -61,6 +62,9 @@ This example tests client access by using the following client properties: ## PARAMETERS ### -AuthenticationType + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The AuthenticationType parameter specifies the client authentication type to test. Valid values for this parameter are: @@ -77,7 +81,6 @@ In client access rules, authentication types are defined by the AnyOfAuthenticat Type: ClientAccessAuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -87,6 +90,9 @@ Accept wildcard characters: False ``` ### -Protocol + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Protocol parameter specifies the client protocol to test. Valid values for this parameter are: @@ -109,7 +115,6 @@ In client access rules, protocol types are defined by the AnyOfProtocols and Exc Type: ClientAccessProtocol Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -119,6 +124,9 @@ Accept wildcard characters: False ``` ### -RemoteAddress + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RemoteAddress parameter specifies the client IP address to test. Valid input for this parameter is an IP address. For example, 192.168.1.50. In client access rules, IP addresses are defined by the AnyOfClientIPAddressesOrRanges and ExceptAnyOfClientIPAddressesOrRanges parameters. @@ -127,7 +135,6 @@ In client access rules, IP addresses are defined by the AnyOfClientIPAddressesOr Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -137,13 +144,15 @@ Accept wildcard characters: False ``` ### -RemotePort + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The RemotePort parameter specifies the client TCP port to test. Valid input for this parameter is an integer from 1 to 65535. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -153,6 +162,9 @@ Accept wildcard characters: False ``` ### -User + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The User parameter specifies the user account to test. For the best results, we recommend using the following values: @@ -179,7 +191,6 @@ In client access rules, users are defined by the UsernameMatchesAnyOfPatterns, U Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -189,6 +200,9 @@ 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`. @@ -198,7 +212,6 @@ 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 @@ -208,13 +221,15 @@ Accept wildcard characters: False ``` ### -OAuthClaims + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The OAuthClaims parameter specifies the OAuth claims token of a middle-tier app. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -224,13 +239,15 @@ 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/exchange/Test-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-DataClassification.md rename to exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md index 7d9109fd68..994b3421f1 100644 --- a/exchange/exchange-ps/exchange/Test-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-dataclassification applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance -title: Test-DataClassification -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-dataclassification +schema: 2.0.0 +title: Test-DataClassification --- # Test-DataClassification @@ -49,6 +50,9 @@ This example lists all sensitive info types, their count, and confidence in the ## PARAMETERS ### -ClassificationNames + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + The ClassificationNames parameter specifies the sensitive information type that you want to find in the text specified by the TextToClassify parameter. Valid values are: - Name @@ -60,7 +64,6 @@ You can specify multiple values separated by commas. Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: False Position: Named @@ -70,6 +73,9 @@ 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. @@ -78,7 +84,6 @@ 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 @@ -88,6 +93,9 @@ Accept wildcard characters: False ``` ### -FileExtension + +> Applicable: Exchange Online, Security & Compliance + This parameter is available only in the cloud-based service. {{ Fill FileExtension Description }} @@ -96,7 +104,6 @@ This parameter is available only in the cloud-based service. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: False Position: Named @@ -106,13 +113,15 @@ Accept wildcard characters: False ``` ### -TestTextExtractionResults + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + The TestTextExtractionResults parameter specifies the extracted text from the Test-TextExtraction cmdlet as the input text stream. ```yaml Type: TestTextExtractionResult[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: False Position: Named @@ -122,13 +131,15 @@ Accept wildcard characters: False ``` ### -TextToClassify + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + The TextToClassify parameter specifies the text string for which classification results need to be shown. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Test-EcpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-EcpConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md index 81cf892ecd..d75c13f206 100644 --- a/exchange/exchange-ps/exchange/Test-EcpConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-ecpconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-EcpConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-ecpconnectivity +schema: 2.0.0 +title: Test-EcpConnectivity --- # Test-EcpConnectivity @@ -71,6 +72,9 @@ This example tests user connectivity to the Exchange admin center on Server01. ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -84,7 +88,6 @@ 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: 1 @@ -94,6 +97,9 @@ 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,7 +109,6 @@ 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,13 +118,15 @@ 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 @@ -129,13 +136,15 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -145,6 +154,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -160,7 +172,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -170,6 +181,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -178,7 +192,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,6 +201,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -196,7 +212,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -206,13 +221,15 @@ Accept wildcard characters: False ``` ### -RSTEndpoint + +> 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 @@ -222,13 +239,15 @@ Accept wildcard characters: False ``` ### -TestType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal. ```yaml Type: OwaConnectivityTestType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,13 +257,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. The default value for the Timeout parameter is 30 seconds. You must specify a time-out value greater than 0 seconds and less than 1 hour (3,600 seconds). We recommend that you always configure this parameter with a value of 5 seconds or more. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -254,6 +275,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -262,7 +286,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -272,6 +295,9 @@ Accept wildcard characters: False ``` ### -VirtualDirectoryName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The VirtualDirectoryName parameter specifies the name of the EAC virtual directory that you want to test. Enclose values that contain spaces in quotation marks ("). If you don't use this parameter, all available EAC virtual directories are tested. @@ -280,7 +306,6 @@ If you don't use this parameter, all available EAC virtual directories are teste Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -290,13 +315,15 @@ 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/exchange/Test-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-EdgeSynchronization.md rename to exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md index 8f9a1e1fb9..e3c3c6ee47 100644 --- a/exchange/exchange-ps/exchange/Test-EdgeSynchronization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-edgesynchronization applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-EdgeSynchronization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-edgesynchronization +schema: 2.0.0 +title: Test-EdgeSynchronization --- # Test-EdgeSynchronization @@ -68,13 +69,15 @@ This example verifies the synchronization status of the single recipient kate@co ## PARAMETERS ### -VerifyRecipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The VerifyRecipient parameter specifies a single recipient with which to verify the synchronization status. You identify the recipient by specifying a proxy address assigned to the recipient. The proxy address is the recipient's email address. The recipient verification test is mutually exclusive of the test that verifies synchronization of configuration data. ```yaml Type: ProxyAddress Parameter Sets: SingleValidation Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -84,6 +87,9 @@ 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`. @@ -93,7 +99,6 @@ 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,13 +108,15 @@ 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 @@ -119,6 +126,9 @@ Accept wildcard characters: False ``` ### -ExcludeRecipientTest + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExcludeRecipientTest switch specifies whether to exclude validation of recipient data synchronization. You don't need to specify a value with this switch. If you use this switch, only the synchronization of configuration objects is validated. Validating that recipient data is synchronized takes longer than validating only configuration data. @@ -127,7 +137,6 @@ If you use this switch, only the synchronization of configuration objects is val Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -137,6 +146,9 @@ Accept wildcard characters: False ``` ### -FullCompareMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FullCompareMode switch specifies whether a full comparison of the configuration data between Active Directory and AD LDS instance on the target Edge Transport server is performed. You don't need to specify a value with this switch. If you don't use this switch, a full comparison of replicated configuration data is skipped and the command only tests the Edge synchronization by verifying the replication cookie. @@ -145,7 +157,6 @@ If you don't use this switch, a full comparison of replicated configuration data Type: SwitchParameter Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -155,13 +166,15 @@ Accept wildcard characters: False ``` ### -MaxReportSize + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxReportSize parameter specifies the total number of objects and properties listed in the results. The results output by this command include a list of all out-of-sync objects and properties in both AD LDS and Active Directory. If the directory services aren't synchronized, a large amount of data can result. If you don't specify a value for this parameter, the default value of 1,000 is used. The minimum value for this parameter is 1. The maximum value for this parameter is unlimited. ```yaml Type: Unlimited Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,6 +184,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -180,7 +196,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -190,6 +205,9 @@ Accept wildcard characters: False ``` ### -TargetServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized. You may want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server has been installed or if that Edge Transport server has been unavailable for some time. @@ -198,7 +216,6 @@ You may want to use this parameter to specify a single Edge Transport server for Type: String Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -208,13 +225,15 @@ 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/exchange/Test-ExchangeSearch.md b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-ExchangeSearch.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md index de07b2a9a7..9313c030c8 100644 --- a/exchange/exchange-ps/exchange/Test-ExchangeSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-exchangesearch applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ExchangeSearch -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-exchangesearch +schema: 2.0.0 +title: Test-ExchangeSearch --- # Test-ExchangeSearch @@ -80,6 +81,9 @@ This example tests Exchange Search results for the mailbox database on which the ## 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 test Exchange Search against. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -99,7 +103,6 @@ You can't use this parameter with the MailboxDatabase or Server parameters. Type: MailboxIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -109,13 +112,15 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Archive switch specifies that the test is run against the archive mailbox for the mailbox user 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 Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -125,6 +130,9 @@ 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,7 +142,6 @@ 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,13 +151,15 @@ 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 @@ -160,13 +169,15 @@ Accept wildcard characters: False ``` ### -IndexingTimeoutInSeconds + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IndexingTimeoutInSeconds parameter specifies, in seconds, the maximum amount of time to wait between adding the new email message to the test mailbox and waiting for it to be returned in a search result. The default value is 120 seconds. If this parameter isn't specified, the default interval is used. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -176,6 +187,9 @@ Accept wildcard characters: False ``` ### -MailboxDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010 and 2013. The MailboxDatabase parameter specifies the mailbox database to test Exchange Search against. You can use any value that uniquely identifies the database. For example: @@ -190,7 +204,6 @@ 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: False Position: Named @@ -200,6 +213,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -208,7 +224,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -218,6 +233,9 @@ 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 for the recipient that you want to test Exchange Search against. You can use any value that uniquely identifies the server. For example: - Name @@ -231,7 +249,6 @@ You can't use this parameter with the MailboxDatabase or Identity parameters. Type: ServerIdParameter Parameter Sets: Server Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,13 +258,15 @@ 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/exchange/Test-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md similarity index 91% rename from exchange/exchange-ps/exchange/Test-FederationTrust.md rename to exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md index d8910cf09d..9a591371f8 100644 --- a/exchange/exchange-ps/exchange/Test-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-federationtrust applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-FederationTrust -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-federationtrust +schema: 2.0.0 +title: Test-FederationTrust --- # Test-FederationTrust @@ -56,6 +57,9 @@ This example validates the federation trust deployed in the Exchange organizatio ## 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`. @@ -65,7 +69,6 @@ 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 @@ -75,13 +78,15 @@ 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 @@ -91,6 +96,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -100,7 +108,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -110,6 +117,9 @@ Accept wildcard characters: False ``` ### -UserIdentity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UserIdentity parameter specifies a mailbox user to request a token for. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -125,7 +135,6 @@ If you don't specify a mailbox, the command uses the default test mailbox. Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -135,13 +144,15 @@ 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/exchange/Test-FederationTrustCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md similarity index 92% rename from exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md rename to exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md index d26350dd00..ba14655771 100644 --- a/exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-federationtrustcertificate applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-FederationTrustCertificate -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-federationtrustcertificate +schema: 2.0.0 +title: Test-FederationTrustCertificate --- # Test-FederationTrustCertificate @@ -44,6 +45,9 @@ This example reports the status of federation certificates. ## 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`. @@ -53,7 +57,6 @@ 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 @@ -63,13 +66,15 @@ 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,13 +84,15 @@ 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/exchange/Test-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-IPAllowListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md index 4b2de63622..aa00f84340 100644 --- a/exchange/exchange-ps/exchange/Test-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-ipallowlistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-IPAllowListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-ipallowlistprovider +schema: 2.0.0 +title: Test-IPAllowListProvider --- # Test-IPAllowListProvider @@ -46,6 +47,9 @@ This example tests the existing IP Allow list provider named Contoso,com by send ## 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 test. You can use any value that uniquely identifies the IP Allow list provider. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the IP Allow list provider that you want to tes Type: IPAllowListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,13 +69,15 @@ 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 be used in testing the IP Allow list provider. You need to use a known allowed IP address. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ 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. @@ -109,7 +119,6 @@ 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,6 +128,9 @@ 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 @@ -134,7 +146,6 @@ 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 @@ -144,13 +155,15 @@ 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/exchange/Test-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-IPBlockListProvider.md rename to exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md index 7ab51aad23..a419bf1295 100644 --- a/exchange/exchange-ps/exchange/Test-IPBlockListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-ipblocklistprovider applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-IPBlockListProvider -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-ipblocklistprovider +schema: 2.0.0 +title: Test-IPBlockListProvider --- # Test-IPBlockListProvider @@ -46,6 +47,9 @@ This example tests the existing IP Block list provider named Contoso.com by send ## 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 test. You can use any value that uniquely identifies the IP Block list provider. For example: - Name @@ -56,7 +60,6 @@ The Identity parameter specifies the IP Block list provider that you want to tes Type: IPBlockListProviderIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,13 +69,15 @@ 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 be used in testing the IP Block list provider. You need to use a known blocked IP address. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -82,6 +87,9 @@ 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`. @@ -91,7 +99,6 @@ 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 @@ -101,6 +108,9 @@ 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. @@ -109,7 +119,6 @@ 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,6 +128,9 @@ 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 @@ -134,7 +146,6 @@ 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 @@ -144,13 +155,15 @@ 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/exchange/Test-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-IRMConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md index c3b0a5ae4e..898b017a8e 100644 --- a/exchange/exchange-ps/exchange/Test-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-irmconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Test-IRMConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-irmconfiguration +schema: 2.0.0 +title: Test-IRMConfiguration --- # Test-IRMConfiguration @@ -54,6 +55,9 @@ This example tests the IRM configuration in the cloud-based service for messages ## 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,7 +66,6 @@ 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 @@ -72,13 +75,15 @@ Accept wildcard characters: False ``` ### -Sender + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Sender parameter specifies the email address of the sender to test. ```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: True Position: Named @@ -88,6 +93,9 @@ 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`. @@ -97,7 +105,6 @@ 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 @@ -107,6 +114,9 @@ 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. @@ -115,7 +125,6 @@ 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,6 +134,9 @@ Accept wildcard characters: False ``` ### -Recipient + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Recipient parameter specifies the email address of the recipient to test. You can specify multiple email addresses separated by commas. This parameter is required in the cloud-based service. @@ -135,7 +147,6 @@ In on-premises Exchange, if you don't use this parameter, the sender address tha 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 @@ -145,6 +156,9 @@ Accept wildcard characters: False ``` ### -RMSOnline + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is available only in the cloud-based service. The RMSOnline switch specifies whether to test connectivity from Exchange Online to RMS Online, obtain your Exchange Online organization's TPD, and test its validity. You don't need to specify a value with this switch. @@ -153,7 +167,6 @@ The RMSOnline switch specifies whether to test connectivity from Exchange Online Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -163,13 +176,15 @@ 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/exchange/Test-ImapConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-ImapConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md index 44bf2c9053..ab28c99b05 100644 --- a/exchange/exchange-ps/exchange/Test-ImapConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-imapconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ImapConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-imapconnectivity +schema: 2.0.0 +title: Test-ImapConnectivity --- # Test-ImapConnectivity @@ -85,6 +86,9 @@ This example tests the client IMAP4 connectivity of the server named Contoso12 a ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -98,7 +102,6 @@ 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: 1 @@ -108,6 +111,9 @@ 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`. @@ -117,7 +123,6 @@ 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 @@ -127,6 +132,9 @@ Accept wildcard characters: False ``` ### -ConnectionType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionType parameter specifies the type of connection that's used to connect to the IMAP4 service. Valid values are: - Plaintext @@ -137,7 +145,6 @@ The ConnectionType parameter specifies the type of connection that's used to con Type: ProtocolConnectionType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -147,13 +154,15 @@ 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 @@ -163,6 +172,9 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LightMode switch tells the command to perform only a test logon to the server by using the IMAP4 protocol. You don't need to specify a value with this switch. If you don't use this switch, the command also tests sending and receiving a message using the IMAP4 protocol. @@ -171,7 +183,6 @@ If you don't use this switch, the command also tests sending and receiving a mes Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,6 +192,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test. 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). @@ -189,7 +203,6 @@ 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 @@ -199,6 +212,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -214,7 +230,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -224,6 +239,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -232,7 +250,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -242,6 +259,9 @@ Accept wildcard characters: False ``` ### -PerConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PerConnectionTimeout parameter specifies the amount of time, in seconds, to wait per connection for the test operation to finish. Valid values are between 0 and 120 seconds. The default value is 120 seconds. We recommend that you configure this parameter with a value of 5 seconds or more. @@ -250,7 +270,6 @@ We recommend that you configure this parameter with a value of 5 seconds or more Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,13 +279,15 @@ Accept wildcard characters: False ``` ### -PortClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PortClientAccessServer parameter specifies the port to use to connect to the Client Access server. The default port is 143 for IMAP4. The valid range is from 0 through 65,535. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -276,6 +297,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -284,7 +308,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -294,6 +317,9 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. Valid values are between 0 and 3600 seconds (1 hour). The default value is 180 seconds (3 minutes). We recommend that you configure this parameter with a value of 5 seconds or more. @@ -302,7 +328,6 @@ We recommend that you configure this parameter with a value of 5 seconds or more Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -312,6 +337,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -320,7 +348,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -330,13 +357,15 @@ 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/exchange/Test-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md similarity index 93% rename from exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md index f166b0c365..4e2db92f88 100644 --- a/exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-m365dataatrestencryptionpolicy applicable: Exchange Online, Exchange Online Protection -title: Test-M365DataAtRestEncryptionPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-m365dataatrestencryptionpolicy +schema: 2.0.0 +title: Test-M365DataAtRestEncryptionPolicy --- # Test-M365DataAtRestEncryptionPolicy @@ -43,6 +44,9 @@ This example tests the Microsoft 365 data-at-rest encryption policy named Contos ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the Microsoft 365 data-at-rest encryption policy that you want to test. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ You can find the existing data-at-rest encryption policies by using the Get-M365 Type: DataEncryptionPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: 0 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,13 +89,15 @@ 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 @@ -100,13 +107,15 @@ 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/exchange/Test-MAPIConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-MAPIConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md index 0b615b567c..0227d41dba 100644 --- a/exchange/exchange-ps/exchange/Test-MAPIConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-mapiconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Test-MAPIConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-mapiconnectivity +schema: 2.0.0 +title: Test-MAPIConnectivity --- # Test-MAPIConnectivity @@ -95,6 +96,9 @@ This example tests connectivity to a mailbox, specified as a domain name and use ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies a mailbox to test. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -118,7 +122,6 @@ You can't use the Identity, Database, or Server parameters in the same command. Type: MailboxIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -128,6 +131,9 @@ 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 database on which to test the connectivity to the system mailbox. You can use any value that uniquely identifies the database. For example: @@ -144,7 +150,6 @@ You can't use the Identity, Database, or Server parameters in the same command. Type: DatabaseIdParameter Parameter Sets: Database Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -154,6 +159,9 @@ Accept wildcard characters: False ``` ### -ActiveDirectoryTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The ActiveDirectoryTimeout parameter specifies the amount of time, in seconds, allowed for each Active Directory operation to complete before the operation times out. The default value is 15 seconds. @@ -162,7 +170,6 @@ The ActiveDirectoryTimeout parameter specifies the amount of time, in seconds, a Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -172,6 +179,9 @@ Accept wildcard characters: False ``` ### -AllConnectionsTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The AllConnectionsTimeout parameter specifies the amount of time, in seconds, allowed for all connections to complete before the cmdlet times out. The time-out countdown doesn't begin until all information necessary to perform the connections is gathered from Active Directory.The default value is 90 seconds. @@ -180,7 +190,6 @@ The AllConnectionsTimeout parameter specifies the amount of time, in seconds, al Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -190,6 +199,9 @@ 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 test the MAPI connectivity of the personal archive that's associated with the specified mailbox. You don't need to specify a value with this switch. If you don't use this switch, only the primary mailbox is tested. @@ -198,7 +210,6 @@ If you don't use this switch, only the primary mailbox is tested. 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 @@ -208,6 +219,9 @@ 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`. @@ -217,7 +231,6 @@ 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 @@ -227,6 +240,9 @@ 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 specifies the Mailbox server that holds the specific database copy to test. You can use any value that uniquely identifies the server. For example: @@ -242,7 +258,6 @@ You can only use this parameter with the Server parameter, not the Identify or D Type: ServerIdParameter Parameter Sets: Database, Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -252,6 +267,9 @@ 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. @@ -260,7 +278,6 @@ 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 @@ -270,6 +287,9 @@ 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 tests MAPI connectivity from all active and passive database copies. You don't need to specify a value with this switch. @@ -280,7 +300,6 @@ If you don't use this switch, the command tests MAPI connectivity from active da Type: SwitchParameter Parameter Sets: Server Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -290,6 +309,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: @@ -301,7 +323,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -311,6 +332,9 @@ Accept wildcard characters: False ``` ### -PerConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is available only in on-premises Exchange. The PerConnectionTimeout parameter specifies the amount of time, in seconds, allowed for each connection to complete before the connection times out. The default value is 10 seconds. @@ -319,7 +343,6 @@ The PerConnectionTimeout parameter specifies the amount of time, in seconds, all Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -329,6 +352,9 @@ 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 on which you will test the MAPI connectivity. The command tests the MAPI connectivity to each system mailbox hosted on active databases on the specified server. You can use any value that uniquely identifies the server. For example: @@ -346,7 +372,6 @@ You can't use the Identity, Database, or Server 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: False Position: Named @@ -356,13 +381,15 @@ 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/exchange/Test-MRSHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md similarity index 91% rename from exchange/exchange-ps/exchange/Test-MRSHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md index c4208ccf1f..b170121827 100644 --- a/exchange/exchange-ps/exchange/Test-MRSHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-mrshealth applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-MRSHealth -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-mrshealth +schema: 2.0.0 +title: Test-MRSHealth --- # Test-MRSHealth @@ -56,6 +57,9 @@ This example tests the health of the Mailbox Replication service on the Mailbox ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the server on which to perform the health test. You can use any value that uniquely identifies the server. For example: - Name @@ -69,7 +73,6 @@ If you don't specify the server, the command runs 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 @@ -79,6 +82,9 @@ 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,7 +94,6 @@ 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,13 +103,15 @@ 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,13 +121,15 @@ Accept wildcard characters: False ``` ### -MaxQueueScanAgeSeconds + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaxQueueScanAgeSeconds parameter specifies the threshold for the last queue scan property. If the time stamp on the last queue scan property is older than the value specified by this parameter, an error event is created that shows the Mailbox Replication service isn't scanning mailbox database queues. The default value is 1800 seconds (30 minutes). ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,6 +139,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -139,7 +151,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -149,6 +160,9 @@ Accept wildcard characters: False ``` ### -MRSProxyCredentials + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MRSProxyCredentials parameter specifies the credentials that are required for the MRSProxyPingCheck test on the server that's specified by the MRSProxyServer parameter. 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). @@ -157,7 +171,6 @@ 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 @@ -167,6 +180,9 @@ Accept wildcard characters: False ``` ### -MRSProxyServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MRSProxyServer parameter specifies the fully qualified domain name (FQDN) of the target server for the MRSProxyPingCheck test. The Microsoft Replication proxy service is part of the Mailbox Replication service, and is used for remote mailbox moves. However, the Mailbox Replication proxy service communicates only with the Mailbox Replication service on another server. You can test the Mailbox Replication proxy service in the following ways: @@ -179,7 +195,6 @@ The Microsoft Replication proxy service is part of the Mailbox Replication servi Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -189,13 +204,15 @@ 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/exchange/Test-Mailflow.md b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-Mailflow.md rename to exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md index 628848623e..3b38d13dfb 100644 --- a/exchange/exchange-ps/exchange/Test-Mailflow.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-mailflow applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-Mailflow -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-mailflow +schema: 2.0.0 +title: Test-Mailflow --- # Test-Mailflow @@ -135,6 +136,9 @@ This example tests message flow from the local Mailbox server where you're runni ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the source Mailbox server name from which a test message is sent. You can use any value that uniquely identifies the server. For example: - Name @@ -148,7 +152,6 @@ If you don't use this parameter, the local Mailbox server is used. Type: ServerIdParameter Parameter Sets: AutoDiscoverTargetMailboxServer, TargetDatabase, TargetEmailAddress, TargetMailboxServer, SourceServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -158,6 +161,9 @@ Accept wildcard characters: False ``` ### -AutoDiscoverTargetMailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverTargetMailboxServer switch specifies whether to automatically populate a list of target Mailbox servers to which to send a test message. You don't need to specify a value with this switch. The task queries Active Directory to discover all Mailbox servers and then sends each server a test message. @@ -168,7 +174,6 @@ When you use this switch, you can't use the CrossPremises, TargetDatabase, Targe Type: SwitchParameter Parameter Sets: AutoDiscoverTargetMailboxServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -178,6 +183,9 @@ Accept wildcard characters: False ``` ### -CrossPremises + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CrossPremises parameter specifies whether the mail flow test will be conducted in cross-premises mode. Set this parameter to $true if your organization is using a cross-premises deployment and you want to verify cross-premises mail flow. @@ -188,7 +196,6 @@ When you use this parameter, you can't use the AutoDiscoverTargetMailboxServer, Type: Boolean Parameter Sets: CrossPremises Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -198,6 +205,9 @@ Accept wildcard characters: False ``` ### -TargetDatabase + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetDatabase parameter specifies the mailbox database to which test messages are sent. You can use any value that uniquely identifies the database. For example: - Name @@ -210,7 +220,6 @@ You can't use this parameter with the AutoDiscoverTargetMailboxServer, CrossPrem Type: DatabaseIdParameter Parameter Sets: TargetDatabase Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -220,6 +229,9 @@ Accept wildcard characters: False ``` ### -TargetEmailAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetEmailAddress parameter specifies the SMTP address of the mailbox to which test messages are sent. Use this parameter to send test messages to a Mailbox server in a remote forest. If this parameter is used, the test is always a remote test. When you use this parameter, you can't use the AutoDiscoverTargetMailboxServer, CrossPremises, TargetDatabase or TargetMailboxServer parameters. @@ -228,7 +240,6 @@ When you use this parameter, you can't use the AutoDiscoverTargetMailboxServer, Type: String Parameter Sets: TargetEmailAddress Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -238,6 +249,9 @@ Accept wildcard characters: False ``` ### -TargetMailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetMailboxServer parameter specifies one or more Mailbox servers in the local Exchange organization to send test messages to. You can use any value that uniquely identifies the server. For example: - Name @@ -251,7 +265,6 @@ When you use this parameter, you can't use the AutoDiscoverTargetMailboxServer, Type: ServerIdParameter Parameter Sets: TargetMailboxServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -261,13 +274,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectoryTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectoryTimeout parameter specifies the number of seconds that elapse before the task provides an informational message about the delay. The default value is 15 seconds. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,6 +292,9 @@ 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`. @@ -286,7 +304,6 @@ 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 @@ -296,13 +313,15 @@ Accept wildcard characters: False ``` ### -CrossPremisesExpirationTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CrossPremisesExpirationTimeout parameter is used when this cmdlet is run by Microsoft System Center Operations Manager 2007 agents for asynchronous monitoring. We don't recommend using this parameter when running this cmdlet manually. ```yaml Type: EnhancedTimeSpan Parameter Sets: CrossPremises Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -312,13 +331,15 @@ Accept wildcard characters: False ``` ### -CrossPremisesPendingErrorCount + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CrossPremisesPendingErrorCount parameter is used when this cmdlet is run by System Center Operations Manager 2007 agents for asynchronous monitoring. We don't recommend using this parameter when running this cmdlet manually. ```yaml Type: Int32 Parameter Sets: CrossPremises Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -328,13 +349,15 @@ 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 @@ -344,13 +367,15 @@ Accept wildcard characters: False ``` ### -ErrorLatency + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ErrorLatency parameter specifies how long to wait for a test message to be delivered before an error event is logged in Microsoft System Center Operations Manager 2007. The default value when a test message is sent to the local Mailbox server is 15 seconds and 180 seconds when a test message is sent to a remote Mailbox server. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -360,13 +385,15 @@ Accept wildcard characters: False ``` ### -ExecutionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ExecutionTimeout parameter specifies the maximum time that this task can run before the test is determined to be a failure. If no test message or delivery report arrives before this time expires, the task ends and an error is reported. When the task is run in the Exchange Management Shell, the default setting is 240 seconds. When the MonitoringContext parameter is used, the default setting is 15 seconds. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -376,6 +403,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -385,7 +415,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -395,6 +424,9 @@ Accept wildcard characters: False ``` ### -TargetEmailAddressDisplayName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TargetEmailAddressDisplayName parameter specifies a custom display name that's used on events and reports in Microsoft System Center Operations Manager 2007 when the TargetEmailAddress parameter is used. If you don't use the TargetEmailAddressDisplayName parameter, the events and reports use the email address value specified by the TargetEmailAddress parameter. This parameter is available only with the TargetEmailAddress parameter and has no effect on the output of the cmdlet outside of Microsoft System Center Operations Manager. @@ -403,7 +435,6 @@ This parameter is available only with the TargetEmailAddress parameter and has n Type: String Parameter Sets: TargetEmailAddress Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -413,13 +444,15 @@ 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/exchange/Test-Message.md b/exchange/exchange-ps/ExchangePowerShell/Test-Message.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-Message.md rename to exchange/exchange-ps/ExchangePowerShell/Test-Message.md index c4b62c4ac7..9ac94513f0 100644 --- a/exchange/exchange-ps/exchange/Test-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-Message.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-message applicable: Exchange Server 2013, Exchange Online, Exchange Online Protection -title: Test-Message -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-message +schema: 2.0.0 +title: Test-Message --- # Test-Message @@ -60,6 +61,9 @@ This example uses the test.eml message file at C:\Data to test mail flow rules a ## PARAMETERS ### -Recipients + +> Applicable: Exchange Online, Exchange Online Protection + The Recipients parameter specifies the recipient email address to use for the test message. You can specify multiple email addresses separated by commas. @@ -68,7 +72,6 @@ You can specify multiple email addresses separated by commas. Type: ProxyAddressCollection Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -78,13 +81,15 @@ Accept wildcard characters: False ``` ### -SendReportTo + +> Applicable: Exchange Online, Exchange Online Protection + The SendReportTo parameter specifies the target email address for the command results. ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -94,13 +99,15 @@ Accept wildcard characters: False ``` ### -TransportRules + +> Applicable: Exchange Server 2013, Exchange Online, Exchange Online Protection + The TransportRules switch specifies that you want to test mail flow rules. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: TransportRules Aliases: -Applicable: Exchange Server 2013, Exchange Online, Exchange Online Protection Required: True Position: Named @@ -110,13 +117,15 @@ Accept wildcard characters: False ``` ### -UnifiedDlpRules + +> Applicable: Exchange Online, Exchange Online Protection + The UnifiedDlpRules switch specifies that you want to unified DLP rules. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter -Parameter Sets: UnifiedDLPRules +Parameter Sets: UnifiedDLPRules, TransportRules Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -125,20 +134,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SwitchParameter -Parameter Sets: TransportRules -Aliases: -Applicable: Exchange Online +### -Confirm -Required: False -Position: Named -Default value: False -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Online, Exchange Online Protection -### -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`. @@ -148,7 +147,6 @@ 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 Online, Exchange Online Protection Required: False Position: Named @@ -158,13 +156,15 @@ Accept wildcard characters: False ``` ### -Force + +> Applicable: Exchange Online, Exchange Online Protection + The Force switch specifies whether to suppress warning or confirmation messages. You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -174,6 +174,9 @@ Accept wildcard characters: False ``` ### -MessageFileData + +> Applicable: Exchange Online, Exchange Online Protection + The MessageFileData parameter specifies the .eml message file to test. 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,7 +185,6 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -192,13 +194,15 @@ Accept wildcard characters: False ``` ### -Sender + +> Applicable: Exchange Online, Exchange Online Protection + The Sender parameter specifies the sender email address to use for the test message. ```yaml Type: SmtpAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -208,13 +212,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Server 2013, 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 Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md rename to exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md index d37917bd9e..8a0895abe4 100644 --- a/exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-migrationserveravailability applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Test-MigrationServerAvailability -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-migrationserveravailability +schema: 2.0.0 +title: Test-MigrationServerAvailability --- # Test-MigrationServerAvailability @@ -226,13 +227,15 @@ This example tests multiple existing endpoints. ## PARAMETERS ### -Autodiscover + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Autodiscover switch specifies that the command should use the Autodiscover service to obtain the connection settings for the target server. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -242,13 +245,15 @@ Accept wildcard characters: False ``` ### -Compliance + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The Compliance switch specifies that the endpoint type is compliance. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Compliance Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -258,15 +263,17 @@ Accept wildcard characters: False ``` ### -Credentials + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Credentials parameter specifies the username and password for an account that can access mailboxes on the target server. Specify the username in the domain\\username format or the user principal name (UPN) format (for example, `user@contoso.com`). 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). ```yaml Type: PSCredential -Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, PSTImport, ExchangeOutlookAnywhere, PublicFolder, Compliance, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup, MrsProxyPublicFolder +Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, PSTImport, ExchangeOutlookAnywhere, PublicFolder, Compliance, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup, MrsProxyPublicFolder, ExchangeRemoteMove Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -275,27 +282,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: PSCredential -Parameter Sets: ExchangeRemoteMove -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -EmailAddress -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -EmailAddress The EmailAddress parameter specifies the email address of an administrator account that can access the remote server. This parameter is required when you use the Autodiscover parameter. ```yaml Type: SmtpAddress -Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover +Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -304,27 +300,16 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SmtpAddress -Parameter Sets: ExchangeOutlookAnywhere, Gmail -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Endpoint -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -Endpoint The Endpoint parameter specifies the name of the migration endpoint to connect to. A migration endpoint contains the connection settings and other migration configuration settings. If you include this parameter, the Test-MigrationServerAvailability cmdlet attempts to verify the ability to connect to the remote server using the settings in the migration endpoint. ```yaml Type: MigrationEndpointIdParameter Parameter Sets: TestEndpoint Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -334,6 +319,9 @@ Accept wildcard characters: False ``` ### -ExchangeOutlookAnywhere + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeOutlookAnywhere switch specifies a migration type for migrating on-premises mailboxes to Exchange Online. You don't need to specify a value with this switch. @@ -344,7 +332,6 @@ Use this switch if you plan to migrate mailboxes to Exchange Online using a stag Type: SwitchParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -354,6 +341,9 @@ Accept wildcard characters: False ``` ### -ExchangeRemoteMove + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ExchangeRemoteMove switch specifies a migration type where mailboxes are moved with full fidelity between two on-premises forests or between an on-premises forest and Exchange Online. You don't need to specify a value with this switch. Use this switch if you plan to perform a cross-forest move or migrate mailboxes between an on-premises Exchange organization and Exchange Online in a hybrid deployment. @@ -362,7 +352,6 @@ Use this switch if you plan to perform a cross-forest move or migrate mailboxes Type: SwitchParameter Parameter Sets: ExchangeRemoteMoveAutoDiscover, ExchangeRemoteMove Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -372,6 +361,9 @@ Accept wildcard characters: False ``` ### -ExchangeServer + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server. Use this parameter when you plan to perform a staged Exchange migration or a cutover Exchange migration. This parameter is required if you don't use the Autodiscover parameter. @@ -380,7 +372,6 @@ The ExchangeServer parameter specifies the FQDN of the on-premises Exchange serv Type: String Parameter Sets: ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -390,6 +381,9 @@ Accept wildcard characters: False ``` ### -Imap + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Imap parameter specifies an IMAP migration type. You don't need to specify a value with this switch. @@ -400,7 +394,6 @@ This switch is required when you want to migrate data from an IMAP mail server t Type: SwitchParameter Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -410,6 +403,9 @@ Accept wildcard characters: False ``` ### -Gmail + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Gmail parameter specifies Gmail as the migration type. You don't need to specify a value with this switch. @@ -420,7 +416,6 @@ This switch is required when you want to migrate data from a Google Workspace (f Type: SwitchParameter Parameter Sets: Gmail Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -430,6 +425,9 @@ Accept wildcard characters: False ``` ### -Port + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Port parameter specifies the TCP port number used by the IMAP migration process to connect to the target server. This parameter is required only for IMAP migrations. @@ -440,7 +438,6 @@ The standard is to use port 143 for unencrypted connections, port 143 for Transp Type: Int32 Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -450,6 +447,9 @@ Accept wildcard characters: False ``` ### -PSTImport + +> 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. @@ -458,7 +458,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -468,6 +467,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -476,7 +478,6 @@ This parameter is reserved for internal Microsoft use. Type: SwitchParameter Parameter Sets: PublicFolder, MrsProxyPublicFolder Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -486,6 +487,9 @@ Accept wildcard characters: False ``` ### -PublicFolderDatabaseServerLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. This parameter is reserved for internal Microsoft use. @@ -494,7 +498,6 @@ This parameter is reserved for internal Microsoft use. Type: String Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -504,13 +507,15 @@ Accept wildcard characters: False ``` ### -PublicFolderToUnifiedGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Microsoft 365 Groups. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -520,6 +525,9 @@ Accept wildcard characters: False ``` ### -RemoteServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The RemoteServer parameter specifies the FQDN of the on-premises mail server. This parameter is required when you want to perform one of the following migration types: - Cross-forest move @@ -528,9 +536,8 @@ The RemoteServer parameter specifies the FQDN of the on-premises mail server. Th ```yaml Type: Fqdn -Parameter Sets: PSTImport, ExchangeRemoteMove, IMAP, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder +Parameter Sets: PSTImport, ExchangeRemoteMove, IMAP, MrsProxyPublicFolderToUnifiedGroup, MrsProxyPublicFolder, Compliance Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -539,20 +546,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: Fqdn -Parameter Sets: Compliance -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -RPCProxyServer -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -RPCProxyServer This parameter is available only in the cloud-based service. The RPCProxyServer parameter specifies the FQDN of the RPC proxy server for the on-premises Exchange server. This parameter is required when you don't use the Autodiscover parameter. Use this parameter if you plan to perform a staged Exchange migration or a cutover Exchange migration to migrate mailboxes to Exchange Online. @@ -561,7 +558,6 @@ The RPCProxyServer parameter specifies the FQDN of the RPC proxy server for the Type: Fqdn Parameter Sets: ExchangeOutlookAnywhere, PublicFolder, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -571,6 +567,9 @@ Accept wildcard characters: False ``` ### -ServiceAccountKeyFileData + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created. @@ -581,7 +580,6 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: Gmail Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -591,15 +589,17 @@ Accept wildcard characters: False ``` ### -SourceMailboxLegacyDN + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Use the LegacyExchangeDN for the on-premises test mailbox as the value for this parameter. The cmdlet will attempt to access this mailbox using the credentials for the administrator account on the target server. ```yaml Type: String -Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup +Parameter Sets: PublicFolder, LegacyPublicFolderToUnifiedGroup, ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -608,20 +608,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: String -Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere -Aliases: -Applicable: Exchange Online +### -AcceptUntrustedCertificates -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Online -### -AcceptUntrustedCertificates This parameter is available only in the cloud-based service. {{ Fill AcceptUntrustedCertificates Description }} @@ -630,7 +620,6 @@ This parameter is available only in the cloud-based service. Type: SwitchParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, IMAP Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -640,6 +629,9 @@ Accept wildcard characters: False ``` ### -Authentication + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The Authentication parameter specifies the authentication method used by the on-premises mail server. Use Basic or NTLM. If you don't include this parameter, Basic authentication is used. @@ -650,7 +642,6 @@ The parameter is only used for cutover Exchange migrations and staged Exchange m Type: AuthenticationMethod Parameter Sets: ExchangeOutlookAnywhere, PublicFolder, IMAP, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -660,6 +651,9 @@ 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`. @@ -669,7 +663,6 @@ 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 @@ -679,13 +672,15 @@ Accept wildcard characters: False ``` ### -FilePath + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FilePath parameter specifies the path containing the PST files when testing a PST Import migration endpoint. ```yaml Type: String Parameter Sets: PSTImport Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -695,6 +690,9 @@ Accept wildcard characters: False ``` ### -MailboxPermission + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The MailboxPermission parameter specifies what permissions are assigned to the migration administrator account defined by the Credentials parameter. You make the permissions assignment to test the connectivity to a user mailbox on the source mail server when you're testing the connection settings in preparation for a staged or cutover Exchange migration or for creating an Exchange Outlook Anywhere migration endpoint. @@ -710,7 +708,6 @@ This parameter isn't used for testing the connection to the remote server for a Type: MigrationMailboxPermission Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -720,6 +717,9 @@ 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. @@ -728,7 +728,6 @@ This parameter is reserved for internal Microsoft use. Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -738,6 +737,9 @@ Accept wildcard characters: False ``` ### -Security + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. For an IMAP migration, the Security parameter specifies the encryption method used by the remote mail server. The options are None, Tls, or Ssl. @@ -746,7 +748,6 @@ For an IMAP migration, the Security parameter specifies the encryption method us Type: IMAPSecurityMechanism Parameter Sets: IMAP Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -756,6 +757,9 @@ Accept wildcard characters: False ``` ### -TestMailbox + +> Applicable: Exchange Online + This parameter is available only in the cloud-based service. The TestMailbox parameter specifies a mailbox on the target server. Use the primary SMTP address as the value for this parameter. The cmdlet will attempt to access this mailbox using the credentials for the administrator account on the target server. @@ -764,7 +768,6 @@ The TestMailbox parameter specifies a mailbox on the target server. Use the prim Type: MailboxIdParameter Parameter Sets: ExchangeOutlookAnywhereAutoDiscover, ExchangeOutlookAnywhere, Gmail, PublicFolder, MrsProxyPublicFolderToUnifiedGroup, LegacyPublicFolderToUnifiedGroup Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -774,13 +777,15 @@ 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/exchange/Test-OAuthConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-OAuthConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md index 69c08e2c8a..0ad49f4e13 100644 --- a/exchange/exchange-ps/exchange/Test-OAuthConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-oauthconnectivity applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Test-OAuthConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-oauthconnectivity +schema: 2.0.0 +title: Test-OAuthConnectivity --- # Test-OAuthConnectivity @@ -48,6 +49,9 @@ This example tests OAuth connectivity with Exchange for Gurinder Singh. ## PARAMETERS ### -Service + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Service parameter specifies the partner application. Valid values for this parameter are: - EWS @@ -58,7 +62,6 @@ The Service parameter specifies the partner application. Valid values for this p Type: ModServiceType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -68,13 +71,15 @@ Accept wildcard characters: False ``` ### -TargetUri + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TargetUri parameter specifies the URL for the service you want to test OAuth connectivity with. ```yaml Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -84,13 +89,15 @@ Accept wildcard characters: False ``` ### -AppOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The AppOnly switch specifies the cmdlet will authenticate to the specified service as Exchange without any user context. 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 @@ -100,6 +107,9 @@ 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`. @@ -109,7 +119,6 @@ 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 @@ -119,6 +128,9 @@ Accept wildcard characters: False ``` ### -Mailbox + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Mailbox parameter specifies the mailbox for which you want to test OAuth connectivity to the specified partner application. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -136,7 +148,6 @@ The Mailbox parameter specifies the mailbox for which you want to test OAuth con Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -146,6 +157,9 @@ Accept wildcard characters: False ``` ### -ReloadConfig + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReloadConfig switch reloads all the configuration settings from the Exchange configuration objects. You don't need to specify a value with this switch. If you don't use this switch, the cached configuration settings are used. @@ -154,7 +168,6 @@ If you don't use this switch, the cached configuration settings are used. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -164,13 +177,15 @@ Accept wildcard characters: False ``` ### -UseCachedToken + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The UseCachedToken switch specifies that OAuth will try to use an existing, cached authorization token. 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 @@ -180,13 +195,15 @@ 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/exchange/Test-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-OrganizationRelationship.md rename to exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md index 79352a03a2..5f19b21b9b 100644 --- a/exchange/exchange-ps/exchange/Test-OrganizationRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-organizationrelationship applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Test-OrganizationRelationship -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-organizationrelationship +schema: 2.0.0 +title: Test-OrganizationRelationship --- # Test-OrganizationRelationship @@ -47,6 +48,9 @@ This example validates the organization relationship deployed in the fabrikam.co ## 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 relationship to be tested. You can use the following values: - Canonical name @@ -57,7 +61,6 @@ The Identity parameter specifies the organization relationship to be tested. You 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 @@ -67,6 +70,9 @@ Accept wildcard characters: False ``` ### -UserIdentity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The UserIdentity parameter specifies the mailbox for which a delegation token is requested to access the external organization's configuration information. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -80,7 +86,6 @@ The UserIdentity parameter specifies the mailbox for which a delegation token is Type: RecipientIdParameter 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 @@ -90,6 +95,9 @@ 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`. @@ -99,7 +107,6 @@ 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 @@ -109,6 +116,9 @@ 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. @@ -117,7 +127,6 @@ 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 @@ -127,13 +136,15 @@ 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/exchange/Test-OutlookConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md similarity index 95% rename from exchange/exchange-ps/exchange/Test-OutlookConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md index 2443888dbc..1da29b97c4 100644 --- a/exchange/exchange-ps/exchange/Test-OutlookConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-outlookconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-OutlookConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-outlookconnectivity +schema: 2.0.0 +title: Test-OutlookConnectivity --- # Test-OutlookConnectivity @@ -150,6 +151,9 @@ In Exchange 2010, this example validates Outlook connectivity through RpcProxy o ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Identity parameter specifies a target user mailbox. You can use any value that uniquely identifies the mailbox. For example: @@ -171,7 +175,6 @@ If you don't use this parameter, the command looks for a test user in Active Dir Type: MailboxIdParameter Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: 1 @@ -181,6 +184,9 @@ Accept wildcard characters: False ``` ### -ProbeIdentity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ProbeIdentity parameter specifies the probe to use. Valid values are: Outlook Anywhere (RPC over HTTP) probes: @@ -199,7 +205,6 @@ MAPI over HTTP probes: Type: String Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -209,6 +214,9 @@ Accept wildcard characters: False ``` ### -GetDefaultsFromAutodiscover + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The GetDefaultsFromAutodiscover parameter specifies whether to get default values for all of the other parameters for the command from the Autodiscover service settings. If you run the command specifying values for other parameters, those values override the default values from the Autodiscover service. The default value for this parameter is $true. @@ -217,7 +225,6 @@ The GetDefaultsFromAutodiscover parameter specifies whether to get default value Type: Boolean Parameter Sets: RpcProxyServer Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -227,6 +234,9 @@ Accept wildcard characters: False ``` ### -Protocol + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Protocol parameter specifies whether to test for Outlook Anywhere connectivity or directly test for RPC or TCP/IP connectivity. The value is either HTTP or TCP. @@ -235,7 +245,6 @@ The Protocol parameter specifies whether to test for Outlook Anywhere connectivi Type: Protocol Parameter Sets: Protocol Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -245,6 +254,9 @@ Accept wildcard characters: False ``` ### -RpcTestType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcTestType parameter specifies which type of RPC endpoint the command should test. Valid values are: @@ -256,7 +268,6 @@ The RpcTestType parameter specifies which type of RPC endpoint the command shoul Type: RpcTestType Parameter Sets: RpcTestType Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -266,6 +277,9 @@ Accept wildcard characters: False ``` ### -WSTestType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The WSTestType parameter specifies type of servers that you want to include in your Outlook connectivity test. You can use the following values: @@ -278,7 +292,6 @@ The WSTestType parameter specifies type of servers that you want to include in y Type: VirtualDirectoryUriScope Parameter Sets: WSTestType Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -288,6 +301,9 @@ Accept wildcard characters: False ``` ### -Archive + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The Archive parameter specifies whether tests should be performed to connect to the user's on-premises archive mailbox. Valid values are: @@ -300,7 +316,6 @@ $false: Don't connect to the user's on-premises mailbox. This is the default val Type: Boolean Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -310,6 +325,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: Exchange Server 2010 + This parameter is available only in 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. @@ -321,7 +339,6 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: cf -Applicable: Exchange Server 2010 Required: False Position: Named @@ -331,6 +348,9 @@ Accept wildcard characters: False ``` ### -Credential + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Credential parameter specifies the credential used by the probe. The system's test credentials are used by default 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). @@ -339,7 +359,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -349,13 +368,15 @@ Accept wildcard characters: False ``` ### -Hostname + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + TheHostname parameter specifies the protocol endpoint target of the probe. You can use a specific Mailbox server or route through Distributed Name Service server. ```yaml Type: String Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -365,6 +386,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MailboxCredential parameter specifies certain credentials to allow logon access to a user's mailbox. Use the parameter along with the Identity parameter to access a user's mailbox when you don't have access permissions. @@ -375,7 +399,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -385,6 +408,9 @@ Accept wildcard characters: False ``` ### -MailboxId + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxID parameter specifies the target mailbox. In Exchange 2013 or later, the Identity parameter specifies a target user mailbox. You can use any value that uniquely identifies the mailbox. For example: @@ -406,7 +432,6 @@ If you don't use this parameter, the command uses the test account. Type: MailboxIdParameter Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -416,6 +441,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. @@ -426,7 +454,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -436,6 +463,9 @@ Accept wildcard characters: False ``` ### -RpcAuthenticationType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcAuthenticationType parameter specifies the authentication setting to test for the RPC layer. Using this parameter is helpful if a different authentication type is set at the RPC proxy virtual directory. You can use the following values: @@ -450,7 +480,6 @@ The default value is Negotiate. Type: RpcAuthenticationType Parameter Sets: RpcProxyServer, RpcTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -460,6 +489,9 @@ Accept wildcard characters: False ``` ### -RpcClientAccessServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcClientAccessServer parameter specifies the target server with the Client Access server role installed that you want to test. This can be a server fully qualified domain name (FQDN) or a GUID. @@ -468,7 +500,6 @@ The RpcClientAccessServer parameter specifies the target server with the Client Type: ClientAccessServerIdParameter Parameter Sets: RpcProxyServer, RpcTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -478,6 +509,9 @@ Accept wildcard characters: False ``` ### -RpcProxyAuthenticationType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcProxyAuthenticationType parameter specifies the authentication setting for the RPC Proxy endpoint. The value can be specified as Basic, NTLM, or Negotiate. There is no default value unless used with the GetDefaultsFromAutodiscover parameter. @@ -486,7 +520,6 @@ The RpcProxyAuthenticationType parameter specifies the authentication setting fo Type: RPCProxyAuthenticationType Parameter Sets: RpcProxyServer, RpcTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -496,6 +529,9 @@ Accept wildcard characters: False ``` ### -RpcProxyServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcProxyServer parameter specifies whether to set the target RpcProxy server for testing. This parameter can be used when the RpcProxy server is different from the Client Access server. @@ -504,7 +540,6 @@ The RpcProxyServer parameter specifies whether to set the target RpcProxy server Type: ServerIdParameter Parameter Sets: RpcProxyServer Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -514,6 +549,9 @@ Accept wildcard characters: False ``` ### -RpcProxyTestType + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The RpcProxyTestType parameter specifies which HTTP endpoint the command should connect to. Valid values are: @@ -525,7 +563,6 @@ The RpcProxyTestType parameter specifies which HTTP endpoint the command should Type: RpcProxyTestType Parameter Sets: RpcTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -535,13 +572,15 @@ Accept wildcard characters: False ``` ### -RunFromServerId + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RunFromServerID parameter specifies the server on which the probe should be run. ```yaml Type: ServerIdParameter Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -551,13 +590,15 @@ Accept wildcard characters: False ``` ### -TimeOutSeconds + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TimeOutSeconds parameter specifies the timeout period in seconds before the probe is ended. The default value is 30 seconds. The digits can be entered with or with the use of quotation marks. Either 10 or "10" will work. Any input error will default back to 30 seconds. ```yaml Type: String Parameter Sets: Probe Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -567,6 +608,9 @@ Accept wildcard characters: False ``` ### -TotalTimeoutInMinutes + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The TotalTimeoutInMinutes parameter specifies the time limit, in minutes, for the command to wait for test results before ending the request. The default value is two minutes. @@ -575,7 +619,6 @@ The TotalTimeoutInMinutes parameter specifies the time limit, in minutes, for th Type: Int32 Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -585,6 +628,9 @@ Accept wildcard characters: False ``` ### -TrustAnySslCert + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch. @@ -595,7 +641,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -605,6 +650,9 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Server 2010 + This parameter is available only in 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. @@ -613,7 +661,6 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: RpcProxyServer, Protocol, RpcTestType, WSTestType Aliases: wi -Applicable: Exchange Server 2010 Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Test-OutlookWebServices.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md similarity index 92% rename from exchange/exchange-ps/exchange/Test-OutlookWebServices.md rename to exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md index a9eae33fd1..e8ddb4de20 100644 --- a/exchange/exchange-ps/exchange/Test-OutlookWebServices.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-outlookwebservices applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-OutlookWebServices -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-outlookwebservices +schema: 2.0.0 +title: Test-OutlookWebServices --- # Test-OutlookWebServices @@ -86,13 +87,15 @@ The example tests for a connection to each service. The example also submits a r ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies any valid address in the forest. If you specify this parameter, incorrectly formed addresses and addresses that are outside the forest are rejected. This address is used to test the Outlook provider. This property accepts the domain and username in the domain\\username format or an Active Directory GUID and resolves them to the SMTP address that's needed to authenticate. ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -102,6 +105,9 @@ Accept wildcard characters: False ``` ### -AutoDiscoverServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverServer parameter specifies the server with the Client Access server role installed that's used for Autodiscover. You can use any value that uniquely identifies the server. For example: @@ -117,7 +123,6 @@ You can't use this parameter with the ClientAccessServer parameter. Type: ClientAccessServerIdParameter Parameter Sets: AutoDiscoverServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -127,6 +132,9 @@ Accept wildcard characters: False ``` ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is functional only in Exchange Server 2010. The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections. @@ -144,7 +152,6 @@ You can't use this parameter with the AutoDiscoverServer parameter. Type: ClientAccessServerIdParameter Parameter Sets: Default, ClientAccessServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -154,6 +161,9 @@ 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,7 +173,6 @@ 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 @@ -173,13 +182,15 @@ 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: Default Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -189,6 +200,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test. 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). @@ -197,7 +211,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: AutoDiscoverServer, ClientAccessServer, MonitoringContext Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -207,6 +220,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -216,7 +232,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -226,13 +241,15 @@ Accept wildcard characters: False ``` ### -TargetAddress + +> Applicable: Exchange Server 2010 + The TargetAddress parameter specifies the recipient that's used to test whether Availability service data can be retrieved. ```yaml Type: RecipientIdParameter[] Parameter Sets: Default Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -242,6 +259,9 @@ 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -250,7 +270,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: AutoDiscoverServer, ClientAccessServer, MonitoringContext Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -260,13 +279,15 @@ 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/exchange/Test-OwaConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md similarity index 95% rename from exchange/exchange-ps/exchange/Test-OwaConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md index 3f6dbf78e8..04024043cc 100644 --- a/exchange/exchange-ps/exchange/Test-OwaConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-owaconnectivity applicable: Exchange Server 2010 -title: Test-OwaConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-owaconnectivity +schema: 2.0.0 +title: Test-OwaConnectivity --- # Test-OwaConnectivity @@ -89,6 +90,9 @@ This example tests the connectivity of a specific Client Access server Contoso12 ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010 The ClientAccessServer parameter specifies the name of the Client Access server to test. If this parameter is included, all Exchange Outlook Web App virtual directories on the Client Access server are tested against all Exchange Mailbox servers in the local Active Directory site. @@ -99,7 +103,6 @@ Don't use this parameter with the URL parameter. Type: ServerIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: 1 @@ -109,6 +112,9 @@ Accept wildcard characters: False ``` ### -URL + +> Applicable: Exchange Server 2010 + The URL parameter specifies the URL to test. This parameter is required only when you want to test a single Outlook Web App URL. If this parameter is used, the MailboxCredential parameter is also required. @@ -119,7 +125,6 @@ You can't use the URL parameter with the TestType or ClientAccessServer paramete Type: String Parameter Sets: URL Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -129,6 +134,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010 + The MailboxCredential parameter specifies the mailbox credential for a single URL test. 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). @@ -139,7 +147,6 @@ The MailboxCredential parameter is required only when using the URL parameter. Type: PSCredential Parameter Sets: URL Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -149,6 +156,9 @@ Accept wildcard characters: False ``` ### -AllowUnsecureAccess + +> Applicable: Exchange Server 2010 + The AllowUnsecureAccess switch specifies whether virtual directories that don't require SSL are tested. You don't need to specify a value with this switch. If you don't use this switch, the command skips virtual directories that don't require SSL, and an error is generated. @@ -157,7 +167,6 @@ If you don't use this switch, the command skips virtual directories that don't r Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -167,6 +176,9 @@ 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`. @@ -176,7 +188,6 @@ 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 @@ -186,13 +197,15 @@ 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 @@ -202,6 +215,9 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010 + The LightMode parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of the command. This parameter is implemented for other Exchange diagnostic commands where it's used to run a less intensive version of a command. @@ -210,7 +226,6 @@ This parameter is implemented for other Exchange diagnostic commands where it's Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -220,13 +235,15 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010 + The MailboxServer parameter specifies the name of the Mailbox server to test. If not specified, all Mailbox servers in the local Active Directory site are tested. ```yaml Type: ServerIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -236,6 +253,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -244,7 +264,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -254,6 +273,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -262,7 +284,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -272,13 +293,15 @@ Accept wildcard characters: False ``` ### -RSTEndpoint + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -288,13 +311,15 @@ Accept wildcard characters: False ``` ### -TestType + +> Applicable: Exchange Server 2010 + The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. You can't use this parameter with the URL parameter. When neither the TestType parameter nor the URL parameter is specified, the default is TestType:Internal. ```yaml Type: OwaConnectivityTestType Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -304,13 +329,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010 + The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. The default value for the Timeout parameter is 30 seconds. You must specify a time-out value greater than 0 seconds and less than 1 hour (3,600 seconds). We recommend that you always configure this parameter with a value of 5 seconds or more. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -320,6 +347,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010 + The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -328,7 +358,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -338,13 +367,15 @@ Accept wildcard characters: False ``` ### -VirtualDirectoryName + +> Applicable: Exchange Server 2010 + The VirtualDirectoryName parameter specifies the name of the virtual directory to test on a particular Client Access server. If this parameter isn't included, all Exchange Outlook Web App virtual directories that support Exchange mailboxes are tested. ```yaml Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -354,13 +385,15 @@ 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/exchange/Test-PopConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-PopConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md index fedc41347a..2d7306ee66 100644 --- a/exchange/exchange-ps/exchange/Test-PopConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-popconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-PopConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-popconnectivity +schema: 2.0.0 +title: Test-PopConnectivity --- # Test-PopConnectivity @@ -79,6 +80,9 @@ This example tests the client POP3 connectivity of the specific server named Con ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -92,7 +96,6 @@ 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: 1 @@ -102,6 +105,9 @@ 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,7 +117,6 @@ 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 @@ -121,6 +126,9 @@ Accept wildcard characters: False ``` ### -ConnectionType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionType parameter specifies the type of connection that's used to connect to the POP3 service. Valid values are: - Plaintext @@ -131,7 +139,6 @@ The ConnectionType parameter specifies the type of connection that's used to con Type: ProtocolConnectionType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -141,13 +148,15 @@ 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,6 +166,9 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LightMode switch tells the command to perform only a test logon to the server by using the POP3 protocol. You don't need to specify a value with this switch. If you don't use this switch, the command also tests receiving a message using the POP3 protocol. @@ -165,7 +177,6 @@ If you don't use this switch, the command also tests receiving a message using t Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -175,6 +186,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test. 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). @@ -183,7 +197,6 @@ 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,6 +206,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -208,7 +224,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -218,6 +233,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -226,7 +244,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -236,6 +253,9 @@ Accept wildcard characters: False ``` ### -PerConnectionTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PerConnectionTimeout parameter specifies the amount of time, in seconds, to wait per connection for the test operation to finish. Valid values are between 0 and 120 seconds. The default value is 120 seconds. We recommend that you configure this parameter with a value of 5 seconds or more. @@ -244,7 +264,6 @@ We recommend that you configure this parameter with a value of 5 seconds or more Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -254,13 +273,15 @@ Accept wildcard characters: False ``` ### -PortClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PortClientAccessServer parameter specifies the port to use to connect to the Client Access server. The default port is 110 for POP3. The valid range is from 0 through 65,535. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -270,6 +291,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -278,7 +302,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -288,6 +311,9 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. Valid values are between 0 and 3600 seconds (1 hour). The default value is 180 seconds (3 minutes). We recommend that you configure this parameter with a value of 5 seconds or more. @@ -296,7 +322,6 @@ We recommend that you configure this parameter with a value of 5 seconds or more Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -306,6 +331,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -314,7 +342,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -324,13 +351,15 @@ 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/exchange/Test-PowerShellConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md index b418302280..b73f73686b 100644 --- a/exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-powershellconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-PowerShellConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-powershellconnectivity +schema: 2.0.0 +title: Test-PowerShellConnectivity --- # Test-PowerShellConnectivity @@ -95,6 +96,9 @@ The credentials that are used to connect to the virtual directory are stored in ## PARAMETERS ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -110,7 +114,6 @@ You can't use this parameter with the ConnectionUri parameter. Type: ServerIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -120,6 +123,9 @@ Accept wildcard characters: False ``` ### -ConnectionUri + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ConnectionUri parameter specifies the URL of the remote PowerShell virtual directory to test, for example, `https://contoso.com/powershell`. You can't use this parameter with the ClientAccessServer parameter. @@ -128,7 +134,6 @@ You can't use this parameter with the ClientAccessServer parameter. Type: Uri Parameter Sets: URL Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -138,6 +143,9 @@ Accept wildcard characters: False ``` ### -TestCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TestCredential parameter specifies the credentials to use for the test. 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). @@ -148,7 +156,6 @@ You can only use this parameter with the ConnectionUri parameter. Type: PSCredential Parameter Sets: URL Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -158,6 +165,9 @@ Accept wildcard characters: False ``` ### -Authentication + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Authentication parameter specifies the type of authentication that's used to connect. Valid values are: - Default @@ -171,7 +181,6 @@ The Authentication parameter specifies the type of authentication that's used to Type: AuthenticationMethod Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -181,6 +190,9 @@ 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`. @@ -190,7 +202,6 @@ 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 @@ -200,13 +211,15 @@ 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 @@ -216,6 +229,9 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect. You can use any value that uniquely identifies the server. For example: @@ -231,7 +247,6 @@ If you don't use this parameter, connections to all Mailbox servers in the local Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -241,6 +256,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -249,7 +267,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -259,6 +276,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -267,7 +287,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -277,6 +296,9 @@ Accept wildcard characters: False ``` ### -TestType + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal. You can only use this parameter with the ClientAccessServer parameter. @@ -285,7 +307,6 @@ You can only use this parameter with the ClientAccessServer parameter. Type: OwaConnectivityTestType Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -295,6 +316,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -303,7 +327,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -313,6 +336,9 @@ Accept wildcard characters: False ``` ### -VirtualDirectoryName + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The VirtualDirectoryName parameter specifies the name of the remote PowerShell virtual directory that you want to test. Enclose values that contain spaces in quotation marks ("). You can only use this parameter with the ClientAccessServer parameter. If you don't use this parameter, all available remote PowerShell virtual directories on the server are tested. @@ -321,7 +347,6 @@ You can only use this parameter with the ClientAccessServer parameter. If you do Type: String Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -331,13 +356,15 @@ 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/exchange/Test-ReplicationHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-ReplicationHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md index 384af71e00..29d802a53a 100644 --- a/exchange/exchange-ps/exchange/Test-ReplicationHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-replicationhealth applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ReplicationHealth -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-replicationhealth +schema: 2.0.0 +title: Test-ReplicationHealth --- # Test-ReplicationHealth @@ -50,6 +51,9 @@ This example tests the health of replication for the Mailbox server MBX1. ## 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 test. You can use any value that uniquely identifies the server. For example: - Name @@ -63,7 +67,6 @@ You can't use this parameter with the DatabaseAvailabilityGroup parameter. Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -73,13 +76,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectoryTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectoryTimeout parameter specifies the time interval in seconds that's allowed for each directory service operation before the operation times out. The default value is 15 seconds. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -89,6 +94,9 @@ 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,7 +106,6 @@ 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,6 +115,9 @@ Accept wildcard characters: False ``` ### -DatabaseAvailabilityGroup + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The DatabaseAvailabilityGroup parameter specifies whether to test all servers in the specified DAG. You can use any value that uniquely identifies the DAG. For example: - Name @@ -120,7 +130,6 @@ You can't use this parameter with the Identity parameter. Type: DatabaseAvailabilityGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -130,13 +139,15 @@ 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 @@ -146,6 +157,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -155,7 +169,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -165,13 +178,15 @@ Accept wildcard characters: False ``` ### -OutputObjects + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The OutputObjects switch specifies whether to output an array of information regarding failures. 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 @@ -181,13 +196,15 @@ Accept wildcard characters: False ``` ### -TransientEventSuppressionWindow + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The TransientEventSuppressionWindow parameter specifies the number of minutes that the queue lengths can be exceeded before the queue length tests are considered to have failed. This parameter is used to reduce the number of failures due to transient load generation. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -197,13 +214,15 @@ 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/exchange/Test-SenderId.md b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md similarity index 88% rename from exchange/exchange-ps/exchange/Test-SenderId.md rename to exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md index 53db8aa93a..4b4c20667c 100644 --- a/exchange/exchange-ps/exchange/Test-SenderId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-senderid applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-SenderId -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-senderid +schema: 2.0.0 +title: Test-SenderId --- # Test-SenderId @@ -47,13 +48,15 @@ This example checks whether the IP address 192.168.0.1 is the legitimate sender ## PARAMETERS ### -IPAddress + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IPAddress parameter specifies the originating IP address of the sending server. ```yaml Type: IPAddress Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -63,13 +66,15 @@ Accept wildcard characters: False ``` ### -PurportedResponsibleDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The PurportedResponsibleDomain parameter specifies the domain name that you want to verify with Sender ID. ```yaml Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -79,6 +84,9 @@ 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,7 +96,6 @@ 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,6 +105,9 @@ 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,7 +116,6 @@ 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,13 +125,15 @@ Accept wildcard characters: False ``` ### -HelloDomain + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The HelloDomain parameter specifies the domain address displayed in the HELO or EHLO SMTP commands from this sender. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -132,6 +143,9 @@ 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 @@ -145,7 +159,6 @@ 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 @@ -155,13 +168,15 @@ 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/exchange/Test-ServiceHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md similarity index 90% rename from exchange/exchange-ps/exchange/Test-ServiceHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md index 1016e36a2c..8d3b38a7f4 100644 --- a/exchange/exchange-ps/exchange/Test-ServiceHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-servicehealth applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-ServiceHealth -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-servicehealth +schema: 2.0.0 +title: Test-ServiceHealth --- # Test-ServiceHealth @@ -47,6 +48,9 @@ This example uses the Test-ServiceHealth command without parameters to test the ## PARAMETERS ### -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 @@ -60,7 +64,6 @@ 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: 1 @@ -70,13 +73,15 @@ Accept wildcard characters: False ``` ### -ActiveDirectoryTimeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ActiveDirectoryTimeout parameter specifies the amount of time, in seconds, allowed for each Active Directory operation to complete before the operation times out. The default value is 15 seconds. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -86,6 +91,9 @@ 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,7 +103,6 @@ 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,6 +112,9 @@ 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. @@ -113,7 +123,6 @@ 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 @@ -123,6 +132,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -132,7 +144,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -142,13 +153,15 @@ 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/exchange/Test-ServicePrincipalAuthorization.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md similarity index 94% rename from exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md rename to exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md index 896490cd63..1766466257 100644 --- a/exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-serviceprincipalauthorization applicable: Exchange Online, Exchange Online Protection -title: Test-ServicePrincipalAuthorization -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-serviceprincipalauthorization +schema: 2.0.0 +title: Test-ServicePrincipalAuthorization --- # Test-ServicePrincipalAuthorization @@ -62,6 +63,9 @@ This example tests the entitlement of the app named "DemoB", including which per ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the service principal that you want to test. You can use any value that uniquely identifies the service principal. For example: - Name @@ -74,7 +78,6 @@ The Identity parameter specifies the service principal that you want to test. Yo Type: ServicePrincipalIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: 0 @@ -84,13 +87,15 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -100,6 +105,9 @@ Accept wildcard characters: False ``` ### -Resource + +> Applicable: Exchange Online, Exchange Online Protection + The Resource parameter specifies the target mailbox where the scoped permissions apply. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -111,7 +119,6 @@ The Resource parameter specifies the target mailbox where the scoped permissions Type: UserIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -121,13 +128,15 @@ 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/exchange/Test-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md similarity index 92% rename from exchange/exchange-ps/exchange/Test-SiteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md index 249202e6e8..978787d55c 100644 --- a/exchange/exchange-ps/exchange/Test-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-sitemailbox applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-SiteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-sitemailbox +schema: 2.0.0 +title: Test-SiteMailbox --- # Test-SiteMailbox @@ -64,6 +65,9 @@ This example tests a specific user's ability to access a SharePoint site by usin ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the site mailbox that you want to test. You can use any value that uniquely identifies the site mailbox. For example: - Name @@ -79,7 +83,6 @@ You can't use this parameter with the SharePointUrl parameter. Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -89,6 +92,9 @@ 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. @@ -97,7 +103,6 @@ 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 @@ -107,6 +112,9 @@ 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`. @@ -116,7 +124,6 @@ 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 @@ -126,6 +133,9 @@ Accept wildcard characters: False ``` ### -RequestorIdentity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The RequestorIdentity parameter specifies the user to test for correct permissions to the SharePoint site mailbox. You can use any value that uniquely identifies the user. For example: - Name @@ -143,7 +153,6 @@ If you don't specify this parameter, the command uses the identification of the Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -153,6 +162,9 @@ Accept wildcard characters: False ``` ### -SharePointUrl + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SharePointUrl parameter specifies the SharePoint URL where the site mailbox is hosted, for example, "https://myserver/teams/edu". You can't use this parameter with the Identity parameter. @@ -161,7 +173,6 @@ You can't use this parameter with the Identity parameter. Type: Uri Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -171,6 +182,9 @@ Accept wildcard characters: False ``` ### -UseAppTokenOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UseAppTokenOnly switch specifies that you want to test the site mailbox by using the identity of the Exchange server. You don't need to specify a value with this switch. You can't use this switch with the RequestorIdentity parameter. @@ -179,7 +193,6 @@ You can't use this switch with the RequestorIdentity parameter. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -189,13 +202,15 @@ 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/exchange/Test-SmtpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md similarity index 93% rename from exchange/exchange-ps/exchange/Test-SmtpConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md index 68097adcaf..53741ae366 100644 --- a/exchange/exchange-ps/exchange/Test-SmtpConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-smtpconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-SmtpConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-smtpconnectivity +schema: 2.0.0 +title: Test-SmtpConnectivity --- # Test-SmtpConnectivity @@ -62,6 +63,9 @@ This example verifies SMTP connectivity for all Receive connectors on all Mailbo ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the transport server for which the cmdlet verifies SMTP connectivity . The Identity parameter specifies the transport server where you want to verify SMTP connectivity (test all Receive connectors on the specified server). You can use any value that uniquely identifies the server. For example: @@ -77,7 +81,6 @@ The Identity parameter specifies the transport server where you want to verify S Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -87,6 +90,9 @@ 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,7 +102,6 @@ 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,6 +111,9 @@ 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. @@ -114,7 +122,6 @@ 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,6 +131,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -133,7 +143,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -143,13 +152,15 @@ 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/exchange/Test-SystemHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md similarity index 93% rename from exchange/exchange-ps/exchange/Test-SystemHealth.md rename to exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md index 8248f8de34..716af4a8cc 100644 --- a/exchange/exchange-ps/exchange/Test-SystemHealth.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-systemhealth applicable: Exchange Server 2010 -title: Test-SystemHealth -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-systemhealth +schema: 2.0.0 +title: Test-SystemHealth --- # Test-SystemHealth @@ -70,6 +71,9 @@ This example saves the output data as a byte stream to the variable named $SysHe ## PARAMETERS ### -ADCredentials + +> Applicable: Exchange Server 2010 + The ADCredentials parameter specifies the username and password that's used to access Active Directory. 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). @@ -78,7 +82,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -88,13 +91,15 @@ Accept wildcard characters: False ``` ### -Analyze + +> Applicable: Exchange Server 2010 + The Analyze switch enables analysis on the data gathered. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -104,13 +109,15 @@ Accept wildcard characters: False ``` ### -Collect + +> Applicable: Exchange Server 2010 + The Collect switch enables data collection. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -120,13 +127,15 @@ Accept wildcard characters: False ``` ### -ConfigurationData + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -136,13 +145,15 @@ Accept wildcard characters: False ``` ### -ConfigurationFileLocation + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: LongPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -152,6 +163,9 @@ 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`. @@ -161,7 +175,6 @@ 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 @@ -171,13 +184,15 @@ Accept wildcard characters: False ``` ### -Description + +> Applicable: Exchange Server 2010 + The Description parameter specifies a descriptive label for the scan. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -187,13 +202,15 @@ 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 @@ -203,13 +220,15 @@ Accept wildcard characters: False ``` ### -DownloadConfigurationUpdates + +> Applicable: Exchange Server 2010 + The DownloadConfigurationUpdates switch checks for and downloads newer versions of the configuration file. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -219,6 +238,9 @@ Accept wildcard characters: False ``` ### -ExchangeCredentials + +> Applicable: Exchange Server 2010 + The ExchangeCredentials parameter specifies the username and password that's used to access Exchange servers. 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). @@ -227,7 +249,6 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com Type: PSCredential Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -237,13 +258,15 @@ Accept wildcard characters: False ``` ### -Export + +> Applicable: Exchange Server 2010 + The Export switch causes sensitive data to be removed from the output file specified. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -253,13 +276,15 @@ Accept wildcard characters: False ``` ### -GenerateEvents + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -269,13 +294,15 @@ Accept wildcard characters: False ``` ### -GenerateSQMData + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -285,13 +312,15 @@ Accept wildcard characters: False ``` ### -MaxThreads + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: Int32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -301,13 +330,15 @@ Accept wildcard characters: False ``` ### -MergeFileLocation + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: LongPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -317,6 +348,9 @@ Accept wildcard characters: False ``` ### -OutData + +> Applicable: Exchange Server 2010 + The OutData switch specifies whether the output data is sent as a byte stream. You don't need to specify a value with this switch. For example, if you run the command: `$temp = Test-SystemHealth -OutData`, `$temp` contains the byte stream of the output data, and you can covert it back to xml by using the Set-Content command. For a code sample, see "Example 2" in this topic. @@ -325,7 +359,6 @@ For example, if you run the command: `$temp = Test-SystemHealth -OutData`, `$tem Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -335,13 +368,15 @@ Accept wildcard characters: False ``` ### -OutFileLocation + +> Applicable: Exchange Server 2010 + The OutFileLocation parameter identifies the name and path to the data file to generate. ```yaml Type: LongPath Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -351,13 +386,15 @@ Accept wildcard characters: False ``` ### -Roles + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -367,13 +404,15 @@ Accept wildcard characters: False ``` ### -ScanType + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -383,13 +422,15 @@ Accept wildcard characters: False ``` ### -ServerList + +> Applicable: Exchange Server 2010 + This parameter is reserved for internal Microsoft use. ```yaml Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -399,13 +440,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010 + The Timeout parameter specifies the number of seconds before the operation times out. The default value is 300 seconds (5 minutes). ```yaml Type: EnhancedTimeSpan Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -415,13 +458,15 @@ 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/exchange/Test-TextExtraction.md b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md similarity index 92% rename from exchange/exchange-ps/exchange/Test-TextExtraction.md rename to exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md index 43b3808f00..4710108ba0 100644 --- a/exchange/exchange-ps/exchange/Test-TextExtraction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-textextraction applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance -title: Test-TextExtraction -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-textextraction +schema: 2.0.0 +title: Test-TextExtraction --- # Test-TextExtraction @@ -58,6 +59,9 @@ This example extracts the text from the email message file named "financial data ## PARAMETERS ### -FileData + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + The FileData parameter specifies the name and path of the file from which text should be extracted. 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`). @@ -66,7 +70,6 @@ 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 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: True Position: 0 @@ -76,6 +79,9 @@ Accept wildcard characters: False ``` ### -Confirm + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, 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`. @@ -85,7 +91,6 @@ 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, Security & Compliance Required: False Position: Named @@ -95,6 +100,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance + 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,7 +111,6 @@ 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, Exchange Online, Security & Compliance Required: False Position: Named @@ -113,13 +120,15 @@ Accept wildcard characters: False ``` ### -WhatIf + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, 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: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Test-UMConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md similarity index 89% rename from exchange/exchange-ps/exchange/Test-UMConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md index 7a6b3e9a41..c9f6dd7a03 100644 --- a/exchange/exchange-ps/exchange/Test-UMConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.MediaAndDevices-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-umconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -title: Test-UMConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.MediaAndDevices-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-umconnectivity +schema: 2.0.0 +title: Test-UMConnectivity --- # Test-UMConnectivity @@ -138,13 +139,15 @@ This example tests a SIP dial plan by using a SIP URI. This example can be used ## PARAMETERS ### -Phone + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Phone parameter specifies the telephone number or Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) used when the test call is redirected. The extension number should be configured in the PBX to forward calls to the UM hunt group. ```yaml Type: String Parameter Sets: TuiLogonSpecific, EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -154,13 +157,15 @@ Accept wildcard characters: False ``` ### -PIN + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The PIN parameter specifies the PIN associated with the UM-enabled mailbox. ```yaml Type: String Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -170,13 +175,15 @@ Accept wildcard characters: False ``` ### -ResetPIN + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ResetPIN parameter specifies whether to generate or regenerate a new PIN for all the test mailboxes in the current site. ```yaml Type: Boolean Parameter Sets: PinReset Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -186,13 +193,15 @@ Accept wildcard characters: False ``` ### -TUILogon + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TUILogon parameter specifies whether the cmdlet tries to log on to one or more UM-enabled mailboxes. The mailboxes must be UM-enabled and associated with the UM dial plan to which the Mailbox server running the Microsoft Exchange Unified Messaging service belongs. The default setting is $false. ```yaml Type: Boolean Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -202,13 +211,15 @@ Accept wildcard characters: False ``` ### -TUILogonAll + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The TUILogonAll parameter specifies whether to try to connect to all test mailboxes in the current Active Directory site. The default setting is $false. The accounts that are tested must be generated by calling the New-TestCasConnectivityUser.ps1 script, and the corresponding mailboxes must be UM-enabled. Otherwise, no action is taken. ```yaml Type: Boolean Parameter Sets: TuiLogonGeneral Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -218,13 +229,15 @@ Accept wildcard characters: False ``` ### -UMDialPlan + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMDialPlan parameter specifies the UM dial plan to be tested. This parameter must be used with the TUILogon parameter. ```yaml Type: UMDialPlanIdParameter Parameter Sets: TuiLogonSpecific Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -234,13 +247,15 @@ Accept wildcard characters: False ``` ### -UMIPGateway + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The UMIPGateway parameter specifies the name of the UM IP gateway or IP PBX to use for the outgoing test call. ```yaml Type: UMIPGatewayIdParameter Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: True Position: Named @@ -250,13 +265,15 @@ Accept wildcard characters: False ``` ### -CallRouter + +> Applicable: Exchange Server 2013, Exchange Server 2016 + The CallRouter switch specifies whether to test the Microsoft Exchange Unified Messaging Call Router service (front-end). You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: LocalLoop Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -266,13 +283,15 @@ Accept wildcard characters: False ``` ### -CertificateThumbprint + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The CertificateThumbprint parameter specifies the certificate thumbprint used for SIP Secured and Secured mode. ```yaml Type: String Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -282,6 +301,9 @@ 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`. @@ -291,7 +313,6 @@ 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 @@ -301,13 +322,15 @@ Accept wildcard characters: False ``` ### -DiagDtmfDurationInMilisecs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DiagDtmfDurationInMilisecs parameter specifies the duration of each digit sent. ```yaml Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -317,13 +340,15 @@ Accept wildcard characters: False ``` ### -DiagDtmfSequence + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DiagDtmfSequence parameter specifies the sequence of digits sent. ```yaml Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -333,13 +358,15 @@ Accept wildcard characters: False ``` ### -DiagInitialSilenceInMilisecs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DiagInitialSilenceInMilisecs parameter specifies the time period in milliseconds that the cmdlet pauses before the digit sequence is sent. ```yaml Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -349,13 +376,15 @@ Accept wildcard characters: False ``` ### -DiagInterDtmfDiffGapInMilisecs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DiagInterDtmfDiffGapInMilisecs parameter specifies whether to customize the time between the digits in the diagnostic sequence. This is a comma-delimited list that can accept null entries. This should include multiple values. ```yaml Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -365,13 +394,15 @@ Accept wildcard characters: False ``` ### -DiagInterDtmfGapInMilisecs + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The DiagInterDtmfGapInMilisecs parameter specifies the time in milliseconds between each digit sent in the digit sequence. This is a single value. ```yaml Type: Int32 Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -381,13 +412,15 @@ 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 @@ -397,13 +430,15 @@ Accept wildcard characters: False ``` ### -From + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The From parameter specifies the SIP URI or SIP address that the call originated from. It's used only when you use the Phone parameter. The default setting is the SIP URI specified when you use the Phone parameter. ```yaml Type: String Parameter Sets: EndToEnd Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -413,13 +448,15 @@ Accept wildcard characters: False ``` ### -ListenPort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The ListenPort parameter specifies the IP port number on which to listen. If not specified, IP port 9000 is used. ```yaml Type: Int32 Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -429,13 +466,15 @@ Accept wildcard characters: False ``` ### -MediaSecured + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MediaSecured parameter specifies whether to use Secure RTP or RTP (unsecured) mode. ```yaml Type: Boolean Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -445,6 +484,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are: - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -454,7 +496,6 @@ The MonitoringContext parameter specifies whether to include the associated moni Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -464,13 +505,15 @@ Accept wildcard characters: False ``` ### -RemotePort + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The RemotePort parameter specifies the port used for the call. If not specified, the default is port 5060 for Transmission Control Protocol (TCP) and 5061 for mutual Transport Layer Security (TLS). ```yaml Type: Int32 Parameter Sets: TuiLogonSpecific, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -480,13 +523,15 @@ Accept wildcard characters: False ``` ### -Secured + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Secured parameter specifies whether the test is run in SIP Secured mode. ```yaml Type: Boolean Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -496,13 +541,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 + The Timeout parameter specifies the length of time in seconds to wait for the test operation to finish. The default is 600 seconds. You can't set this parameter with a value of less than 60 seconds. However, we recommend that you always configure this parameter with a value of 60 seconds or more. The maximum value for this parameter is 1800 seconds. ```yaml Type: Int32 Parameter Sets: TuiLogonSpecific, EndToEnd, TuiLogonGeneral, LocalLoop Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 Required: False Position: Named @@ -512,13 +559,15 @@ 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/exchange/Test-WebServicesConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md similarity index 91% rename from exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md rename to exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md index fba4a45320..bbbe7197f1 100644 --- a/exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RemoteConnections-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/test-webservicesconnectivity applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Test-WebServicesConnectivity -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RemoteConnections-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/test-webservicesconnectivity +schema: 2.0.0 +title: Test-WebServicesConnectivity --- # Test-WebServicesConnectivity @@ -109,6 +110,9 @@ This example tests the client connection to Exchange Web Services on the server ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox to use for the test. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -128,7 +132,6 @@ When you use this parameter, you also need to use the MailboxCredential paramete Type: MailboxIdParameter Parameter Sets: AutoDiscoverServer, MonitoringContext, ClientAccessServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -138,6 +141,9 @@ Accept wildcard characters: False ``` ### -ClientAccessServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections. You can use any value that uniquely identifies the server. For example: @@ -153,7 +159,6 @@ You can't use this parameter with the AutoDiscoverServer parameter. Type: ServerIdParameter Parameter Sets: Default, ClientAccessServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: 1 @@ -163,6 +168,9 @@ Accept wildcard characters: False ``` ### -AutoDiscoverServer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The AutoDiscoverServer parameter specifies the server with the Client Access server role installed that's used for Autodiscover. You can use any value that uniquely identifies the server. For example: @@ -176,9 +184,8 @@ You can't use this parameter with the ClientAccessServer parameter. ```yaml Type: ClientAccessServerIdParameter -Parameter Sets: AutoDiscoverServer +Parameter Sets: AutoDiscoverServer, ClientAccessServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -187,20 +194,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: ServerIdParameter -Parameter Sets: ClientAccessServer -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +### -AllowUnsecureAccess -Required: False -Position: Named -Default value: None -Accept pipeline input: True -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2010 -### -AllowUnsecureAccess This parameter is available only in Exchange Server 2010. The AllowUnsecureAccess switch specifies whether to enable the command to continue to run over an unsecured channel that doesn't require Secure Sockets Layer (SSL). You don't need to specify a value with this switch. @@ -209,7 +206,6 @@ The AllowUnsecureAccess switch specifies whether to enable the command to contin Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -219,6 +215,9 @@ 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`. @@ -228,7 +227,6 @@ 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 @@ -238,6 +236,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2010 + This parameter is available only in 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. @@ -246,7 +247,6 @@ The DomainController parameter specifies the domain controller that's used by th Type: Fqdn Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -256,6 +256,9 @@ Accept wildcard characters: False ``` ### -LightMode + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The LightMode switch tells the command to perform only a subset of the tests. You don't need to specify a value with this switch. When you use this switch, the EWS: ConvertId test is run instead of the EWS: GetFolder test. @@ -264,7 +267,6 @@ When you use this switch, the EWS: ConvertId test is run instead of the EWS: Get Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -274,6 +276,9 @@ Accept wildcard characters: False ``` ### -MailboxCredential + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test. 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). @@ -284,7 +289,6 @@ This parameter is required when you use the Identity parameter. Type: PSCredential Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -294,13 +298,15 @@ Accept wildcard characters: False ``` ### -MailboxServer + +> Applicable: Exchange Server 2010 + The MailboxServer parameter specifies the identity of the Exchange Mailbox server on which the test is run. ```yaml Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -310,6 +316,9 @@ Accept wildcard characters: False ``` ### -MonitoringContext + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM). @@ -318,7 +327,6 @@ Typically, you include the monitoring events and performance counters in the res Type: SwitchParameter Parameter Sets: MonitoringContext Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -328,6 +336,9 @@ Accept wildcard characters: False ``` ### -ResetTestAccountCredentials + +> Applicable: Exchange Server 2010 + The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch. The password for the test account is typically reset every seven days. Use this switch to force a password reset any time it's required for security reasons. @@ -336,7 +347,6 @@ The password for the test account is typically reset every seven days. Use this Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -346,13 +356,15 @@ Accept wildcard characters: False ``` ### -Timeout + +> Applicable: Exchange Server 2010 + The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. The default value for the Timeout parameter is 300 seconds. You must specify a time-out value greater than 0 seconds. We recommend that you always configure this parameter with a value of 5 seconds or more. ```yaml Type: UInt32 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -362,6 +374,9 @@ Accept wildcard characters: False ``` ### -TrustAnySSLCertificate + +> Applicable: Exchange Server 2010, 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. This switch is useful for testing internal URLs, because a URL that has an associated certificate is typically an external URL. This switch lets the task check an internal URL without generating an error when the certificate doesn't match the URL. @@ -370,7 +385,6 @@ This switch is useful for testing internal URLs, because a URL that has an assoc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -380,6 +394,9 @@ Accept wildcard characters: False ``` ### -UseAutodiscoverForClientAccessServer + +> Applicable: Exchange Server 2010 + This parameter is available only in Exchange Server 2010. The UseAutodiscoverForClientAccessServer switch specifies whether the test should use the Autodiscover service to locate the Client Access server. You don't need to specify a value with this switch. @@ -388,7 +405,6 @@ The UseAutodiscoverForClientAccessServer switch specifies whether the test shoul Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -398,13 +414,15 @@ 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/exchange/Undo-SoftDeletedMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md similarity index 96% rename from exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md index 50c11224ce..52e35e1986 100644 --- a/exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/undo-softdeletedmailbox applicable: Exchange Online -title: Undo-SoftDeletedMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/undo-softdeletedmailbox +schema: 2.0.0 +title: Undo-SoftDeletedMailbox --- # Undo-SoftDeletedMailbox @@ -69,13 +70,15 @@ This example recovers the deleted mailbox for the user Brian Johnson. When this ## PARAMETERS ### -SoftDeletedObject + +> Applicable: Exchange Online + The SoftDeletedObject parameter specifies the deleted mailbox to recover. You can use the alias or the email address of the deleted mailbox for the value of this parameter. Use the Get-Mailbox -SoftDeletedMailbox command to get information for deleted mailboxes. ```yaml Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -85,6 +88,9 @@ Accept wildcard characters: False ``` ### -PublicFolder + +> Applicable: Exchange Online + The PublicFolder switch is required to recover public folder mailboxes. 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. @@ -93,7 +99,6 @@ Public folder mailboxes are specially designed mailboxes that store the hierarch Type: SwitchParameter Parameter Sets: PublicFolder Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -103,6 +108,9 @@ 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`. @@ -112,7 +120,6 @@ 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 @@ -122,13 +129,15 @@ Accept wildcard characters: False ``` ### -DisplayName + +> Applicable: Exchange Online + The DisplayName parameter specifies the new display name for the recovered mailbox. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -138,13 +147,15 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies a new value for the Name property of the recovered mailbox. Otherwise, the original value is retained when the mailbox is recovered. The new name value is also used in the DistinguishedName property. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -154,6 +165,9 @@ Accept wildcard characters: False ``` ### -Password + +> Applicable: Exchange Online + The Password parameter specifies a new password for the mailbox. You can use the following methods as a value for this parameter: @@ -168,7 +182,6 @@ You have to include the Password parameter to recover a deleted mailbox with an Type: SecureString Parameter Sets: SoftDeletedMailbox Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -178,13 +191,15 @@ 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 @@ -194,6 +209,9 @@ Accept wildcard characters: False ``` ### -WindowsLiveID + +> Applicable: Exchange Online + The WindowsLiveID parameter specifies a new Microsoft account (formerly known as a Windows Live ID) and primary SMTP address for the mailbox. The previous Microsoft account is retained as a proxy address for the mailbox. You have to include the WindowsLiveID parameter to recover a deleted mailbox with an existing Microsoft account that wasn't deleted with the mailbox. @@ -202,7 +220,6 @@ You have to include the WindowsLiveID parameter to recover a deleted mailbox wit Type: WindowsLiveId Parameter Sets: SoftDeletedMailbox Aliases: -Applicable: Exchange Online Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md similarity index 97% rename from exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md index 7402d91bdb..64abd475bb 100644 --- a/exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/undo-softdeletedunifiedgroup applicable: Exchange Online -title: Undo-SoftDeletedUnifiedGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/undo-softdeletedunifiedgroup +schema: 2.0.0 +title: Undo-SoftDeletedUnifiedGroup --- # Undo-SoftDeletedUnifiedGroup @@ -48,6 +49,9 @@ This example restores the soft-deleted Microsoft 365 Group named Marketing Depar ## PARAMETERS ### -SoftDeletedObject + +> Applicable: Exchange Online + The SoftDeletedObject parameter specifies the soft-deleted Microsoft 365 Group that you want to restore. You can use any value that uniquely identifies the Microsoft 365 Group. For example: - Name @@ -67,7 +71,6 @@ The SoftDeletedObject parameter specifies the soft-deleted Microsoft 365 Group t Type: UnifiedGroupIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -77,6 +80,9 @@ 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`. @@ -86,7 +92,6 @@ 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 @@ -96,13 +101,15 @@ 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/exchange/Uninstall-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md similarity index 91% rename from exchange/exchange-ps/exchange/Uninstall-TransportAgent.md rename to exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md index 5618a653c7..b220bfec58 100644 --- a/exchange/exchange-ps/exchange/Uninstall-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/uninstall-transportagent applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Uninstall-TransportAgent -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/uninstall-transportagent +schema: 2.0.0 +title: Uninstall-TransportAgent --- # Uninstall-TransportAgent @@ -50,13 +51,15 @@ This example uninstalls a fictitious application named Test App from the Transpo ## 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 that you want to uninstall. If the value contains spaces, enclose the value in quotation marks. ```yaml Type: TransportAgentObjectId Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -66,6 +69,9 @@ 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,7 +81,6 @@ 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 @@ -85,6 +90,9 @@ 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. @@ -93,7 +101,6 @@ 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 @@ -103,6 +110,9 @@ 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. @@ -115,7 +125,6 @@ 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 @@ -125,13 +134,15 @@ 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/exchange/Update-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md similarity index 91% rename from exchange/exchange-ps/exchange/Update-AddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md index 8c44e68434..f21b8e315d 100644 --- a/exchange/exchange-ps/exchange/Update-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-addresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-AddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-addresslist +schema: 2.0.0 +title: Update-AddressList --- # Update-AddressList @@ -43,6 +44,9 @@ This example updates the recipients of the address list named building4 that's u ## 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 update. You can use any value that uniquely identifies the address list. For example: - Name @@ -54,7 +58,6 @@ The Identity parameter specifies the address list that you want to update. You c Type: AddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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,13 +106,15 @@ 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/exchange/Update-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md similarity index 96% rename from exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md rename to exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md index dfbaff31dc..79eeabf42b 100644 --- a/exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-compliancecasemember applicable: Security & Compliance -title: Update-ComplianceCaseMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-compliancecasemember +schema: 2.0.0 +title: Update-ComplianceCaseMember --- # Update-ComplianceCaseMember @@ -50,6 +51,9 @@ This example replaces the existing members of the eDiscovery case named Case 515 ## 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. @@ -58,7 +62,6 @@ To see the available eDiscovery cases, use the Get-ComplianceCase cmdlet. Type: String Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: 1 @@ -68,6 +71,9 @@ Accept wildcard characters: False ``` ### -Members + +> Applicable: Security & Compliance + The Members parameter specifies the users that will replace the current eDiscovery case members. You can use any value that uniquely identifies the user. For example: - Name @@ -81,7 +87,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -91,6 +96,9 @@ 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`. @@ -100,7 +108,6 @@ 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,13 +117,15 @@ 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/exchange/Update-DatabaseSchema.md b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md similarity index 91% rename from exchange/exchange-ps/exchange/Update-DatabaseSchema.md rename to exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md index 1ca485d6cb..8039a2cc92 100644 --- a/exchange/exchange-ps/exchange/Update-DatabaseSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-databaseschema applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-DatabaseSchema -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-databaseschema +schema: 2.0.0 +title: Update-DatabaseSchema --- # Update-DatabaseSchema @@ -42,6 +43,9 @@ This example updates the database schema for database DB1. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox database for which you want to set one or more attributes. You can use any value that uniquely identifies the database. For example: - Name @@ -52,7 +56,6 @@ The Identity parameter specifies the mailbox database for which you want to set Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -62,13 +65,15 @@ Accept wildcard characters: False ``` ### -MajorVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: UInt16 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -78,13 +83,15 @@ Accept wildcard characters: False ``` ### -MinorVersion + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: UInt16 Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -94,6 +101,9 @@ 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`. @@ -103,7 +113,6 @@ 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 @@ -113,13 +122,15 @@ 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/exchange/Update-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md similarity index 89% rename from exchange/exchange-ps/exchange/Update-DistributionGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md index cc94a00944..ce1b5c6299 100644 --- a/exchange/exchange-ps/exchange/Update-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-distributiongroupmember applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Update-DistributionGroupMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-distributiongroupmember +schema: 2.0.0 +title: Update-DistributionGroupMember --- # Update-DistributionGroupMember @@ -45,6 +46,9 @@ This example replaces the existing members of the distribution group name Resear ## 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 modify. You can use any value that uniquely identifies the group. For example: - Name @@ -58,7 +62,6 @@ 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, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -68,6 +71,9 @@ 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: @@ -79,7 +85,6 @@ 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 @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,6 +115,9 @@ 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,7 +126,6 @@ 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 @@ -126,6 +135,9 @@ 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 will replace the current group members. You can use any value that uniquely identifies the recipient. For example: - Name @@ -145,7 +157,6 @@ 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 @@ -155,13 +166,15 @@ 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/exchange/Update-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md similarity index 89% rename from exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md index a5ab8316da..3ea09909bf 100644 --- a/exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-emailaddresspolicy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-EmailAddressPolicy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-emailaddresspolicy +schema: 2.0.0 +title: Update-EmailAddressPolicy --- # Update-EmailAddressPolicy @@ -45,6 +46,9 @@ This example applies the email address policy named Northwest Executives to all ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the email address policy that you want to apply to recipients. You can use any value that uniquely identifies the policy. For example: - Name @@ -55,7 +59,6 @@ The Identity parameter specifies the email address policy that you want to apply Type: EmailAddressPolicyIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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,13 +89,15 @@ 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 @@ -100,6 +107,9 @@ Accept wildcard characters: False ``` ### -FixMissingAlias + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FixMissingAlias switch repairs recipients that don't have an alias. The alias is generated based on the Name property of the recipient. You don't need to specify a value with this switch. You need to use this switch if you receive an error message when you attempt to update the email address policy, global address list, or address list. @@ -108,7 +118,6 @@ You need to use this switch if you receive an error message when you attempt to Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -118,6 +127,9 @@ Accept wildcard characters: False ``` ### -UpdateSecondaryAddressesOnly + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The UpdateSecondaryAddressesOnly switch specifies that only the proxy email addresses are updated for the recipients. You don't need to specify a value with this switch. The recipient's primary email address isn't updated. @@ -126,7 +138,6 @@ The recipient's primary email address isn't updated. Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -136,13 +147,15 @@ 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/exchange/Update-ExchangeHelp.md b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md similarity index 96% rename from exchange/exchange-ps/exchange/Update-ExchangeHelp.md rename to exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md index 01778dcf54..0100140df3 100644 --- a/exchange/exchange-ps/exchange/Update-ExchangeHelp.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-exchangehelp applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-ExchangeHelp -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-exchangehelp +schema: 2.0.0 +title: Update-ExchangeHelp --- # Update-ExchangeHelp @@ -44,6 +45,9 @@ This example checks for the latest available version of Help for the Exchange Ma ## PARAMETERS ### -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. By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. If you run this cmdlet within 24 hours of the last time you ran it, it won't check for updates. You can use this switch to force the cmdlet to check for updates more frequently and to display status or error messages. @@ -52,7 +56,6 @@ By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. 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/exchange/Update-FileDistributionService.md b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md similarity index 96% rename from exchange/exchange-ps/exchange/Update-FileDistributionService.md rename to exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md index 869bf696a3..016cf14ab8 100644 --- a/exchange/exchange-ps/exchange/Update-FileDistributionService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-filedistributionservice applicable: Exchange Server 2010 -title: Update-FileDistributionService -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-filedistributionservice +schema: 2.0.0 +title: Update-FileDistributionService --- # Update-FileDistributionService @@ -62,6 +63,9 @@ This example polls Server1 for changes to Group Metrics files associated with Se ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010 + 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 @@ -73,7 +77,6 @@ The Identity parameter specifies the Exchange server where you want to run this Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: 1 @@ -83,6 +86,9 @@ 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`. @@ -92,7 +98,6 @@ 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 @@ -102,13 +107,15 @@ 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,6 +125,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Server 2010 + The Type parameter specifies whether to reload OAB, Unified Messaging, or Group Metrics data. If you don't use the Type parameter when running this command, OAB, Unified Messaging, and Group Metrics data are reloaded. The Type parameter takes the following values: @@ -130,7 +140,6 @@ The Type parameter takes the following values: Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: False Position: Named @@ -140,13 +149,15 @@ 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/exchange/Update-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md similarity index 90% rename from exchange/exchange-ps/exchange/Update-GlobalAddressList.md rename to exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md index 8fe39ea94d..dcf0ad5d11 100644 --- a/exchange/exchange-ps/exchange/Update-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-globaladdresslist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-GlobalAddressList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-globaladdresslist +schema: 2.0.0 +title: Update-GlobalAddressList --- # Update-GlobalAddressList @@ -43,6 +44,9 @@ This example updates the recipients in the default GAL. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the global address list that you want to update. You can use any value that uniquely identifies the GAL. For example: - Name @@ -53,7 +57,6 @@ The Identity parameter specifies the global address list that you want to update Type: GlobalAddressListIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -63,6 +66,9 @@ 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`. @@ -72,7 +78,6 @@ 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 @@ -82,13 +87,15 @@ 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 @@ -98,13 +105,15 @@ 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/exchange/Update-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md similarity index 90% rename from exchange/exchange-ps/exchange/Update-HybridConfiguration.md rename to exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md index bb0e1ea9e9..923df16193 100644 --- a/exchange/exchange-ps/exchange/Update-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-hybridconfiguration applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Update-HybridConfiguration -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-hybridconfiguration +schema: 2.0.0 +title: Update-HybridConfiguration --- # Update-HybridConfiguration @@ -55,6 +56,9 @@ Use the last command to define the credentials that are used to update the hybri ## PARAMETERS ### -OnPremisesCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The OnPremisesCredentials parameter specifies the on-premises Active Directory account and password that's used to configure the hybrid configuration object. This account must be a member of the Organization Management role group. 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). @@ -63,7 +67,6 @@ 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: True Position: Named @@ -73,6 +76,9 @@ Accept wildcard characters: False ``` ### -TenantCredentials + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The TenantCredentials parameter specifies the Microsoft 365 organization account and password that's used to configure the hybrid configuration object. This is often the administrator account that's assigned when the Microsoft 365 organization was created. This account must be a member of the Global Administrators role. > [!IMPORTANT] @@ -84,7 +90,6 @@ 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: True Position: Named @@ -94,6 +99,9 @@ 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`. @@ -103,7 +111,6 @@ 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 @@ -113,6 +120,9 @@ 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,7 +131,6 @@ 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,6 +140,9 @@ Accept wildcard characters: False ``` ### -ForceUpgrade + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch. This confirmation prompt is displayed only when the existing HybridConfiguration Active Directory object version is Exchange 2010. @@ -139,7 +151,6 @@ This confirmation prompt is displayed only when the existing HybridConfiguration Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -149,13 +160,15 @@ Accept wildcard characters: False ``` ### -SuppressOAuthWarning + +> 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: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -165,13 +178,15 @@ 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/exchange/Update-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md similarity index 88% rename from exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md rename to exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md index b7f5614479..6f7b577709 100644 --- a/exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.ServerStatus-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-mailboxdatabasecopy applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-MailboxDatabaseCopy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.ServerStatus-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-mailboxdatabasecopy +schema: 2.0.0 +title: Update-MailboxDatabaseCopy --- # Update-MailboxDatabaseCopy @@ -121,13 +122,15 @@ This example performs a full server reseed of all of the databases on the Mailbo ## 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 mailbox database whose copy is being seeded. ```yaml Type: DatabaseCopyIdParameter Parameter Sets: CancelSeed, Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -137,13 +140,15 @@ Accept wildcard characters: False ``` ### -CancelSeed + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CancelSeed switch specifies whether to cancel an in-progress seeding operation. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: CancelSeed Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -153,13 +158,15 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter is used as part of a full server reseed operation. It can be used with the MaximumSeedsInParallel parameter to start reseeds of database copies in parallel across the specified server in batches of up to the value of the MaximumSeedsInParallel parameter copies at a time. ```yaml Type: MailboxServerIdParameter Parameter Sets: ExplicitServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -169,6 +176,9 @@ Accept wildcard characters: False ``` ### -BeginSeed + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The BeginSeed switch asynchronously starts the seeding operation and then exits the cmdlet. You don't need to specify a value with this switch. This switch is useful for scripting reseeds. @@ -177,7 +187,6 @@ This switch is useful for scripting reseeds. Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -187,13 +196,15 @@ Accept wildcard characters: False ``` ### -CatalogOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The CatalogOnly switch specifies that only the content index catalog for the database copy should be seeded. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -203,6 +214,9 @@ 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`. @@ -212,7 +226,6 @@ 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 @@ -222,13 +235,15 @@ Accept wildcard characters: False ``` ### -DatabaseOnly + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DatabaseOnly switch specifies that only the database copy should be seeded. The content index catalog isn't seeded. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -238,6 +253,9 @@ Accept wildcard characters: False ``` ### -DeleteExistingFiles + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The DeleteExistingFiles switch specifies whether to remove the existing log files at the target location. You don't need to specify a value with this switch. This switch removes only the files that it checks for and fails if other files are present. No action is taken on other files at the target location. Therefore, if database-related files are present, you must manually remove them. @@ -246,7 +264,6 @@ This switch removes only the files that it checks for and fails if other files a Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -256,13 +273,15 @@ 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 @@ -272,6 +291,9 @@ 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. @@ -280,7 +302,6 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -290,6 +311,9 @@ Accept wildcard characters: False ``` ### -ManualResume + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The ManualResume switch specifies whether to automatically resume replication on the database copy. You don't need to specify a value with this switch. With this switch, you can manually resume replication to the database copy. @@ -298,7 +322,6 @@ With this switch, you can manually resume replication to the database copy. Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -308,13 +331,15 @@ Accept wildcard characters: False ``` ### -MaximumSeedsInParallel + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The MaximumSeedsInParallel parameter is used with the Server parameter to specify the maximum number of parallel seeding operations that should occur across the specified server during a full server reseed operation. The default value is 10. ```yaml Type: Int32 Parameter Sets: ExplicitServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -324,13 +349,15 @@ Accept wildcard characters: False ``` ### -Network + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Network parameter specifies which DAG network should be used for seeding. Note that content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network. ```yaml Type: DatabaseAvailabilityGroupNetworkIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -340,13 +367,15 @@ Accept wildcard characters: False ``` ### -NetworkCompressionOverride + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NetworkCompressionOverride parameter specifies whether to override the current DAG network compression settings. ```yaml Type: UseDagDefaultOnOff Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -356,13 +385,15 @@ Accept wildcard characters: False ``` ### -NetworkEncryptionOverride + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The NetworkEncryptionOverride parameter specifies whether to override the current DAG encryption settings. ```yaml Type: UseDagDefaultOnOff Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -372,13 +403,15 @@ Accept wildcard characters: False ``` ### -NoThrottle + +> Applicable: Exchange Server 2016, Exchange Server 2019 + The NoThrottle switch prevents the seeding operation from being throttled. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -388,13 +421,15 @@ Accept wildcard characters: False ``` ### -PrimaryDatabasePartitionOnly + +> Applicable: Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -404,6 +439,9 @@ Accept wildcard characters: False ``` ### -SafeDeleteExistingFiles + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SafeDeleteExistingFiles switch specifies a seeding operation with a single copy redundancy pre-check prior to the seed. You don't need to specify a value with this switch. Because this switch includes the redundancy safety check, it requires a lower level of permissions than the DeleteExistingFiles parameter. Limited permission administrators can perform the seeding operation by using this switch. @@ -412,7 +450,6 @@ Because this switch includes the redundancy safety check, it requires a lower le Type: SwitchParameter Parameter Sets: Identity, ExplicitServer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -422,13 +459,15 @@ Accept wildcard characters: False ``` ### -SecondaryDatabasePartitionOnly + +> Applicable: Exchange Server 2019 + This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2019 Required: False Position: Named @@ -438,6 +477,9 @@ Accept wildcard characters: False ``` ### -SourceServer + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The SourceServer parameter specifies the Mailbox server with a passive copy of the mailbox database to be used as the source for the seed operation. You can use any value that uniquely identifies the server. For example: @@ -451,7 +493,6 @@ The SourceServer parameter specifies the Mailbox server with a passive copy of t Type: ServerIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -461,13 +502,15 @@ 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/exchange/Update-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md similarity index 90% rename from exchange/exchange-ps/exchange/Update-OfflineAddressBook.md rename to exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md index c9dd29eb20..eec4ce6d0a 100644 --- a/exchange/exchange-ps/exchange/Update-OfflineAddressBook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-offlineaddressbook applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-OfflineAddressBook -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-offlineaddressbook +schema: 2.0.0 +title: Update-OfflineAddressBook --- # Update-OfflineAddressBook @@ -44,6 +45,9 @@ This example updates the OAB MyOAB. ## 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 Identity so that only the OAB name or GUID is supplied. @@ -52,7 +56,6 @@ You can omit the parameter label Identity so that only the OAB name or GUID is s Type: OfflineAddressBookIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -62,6 +65,9 @@ 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`. @@ -71,7 +77,6 @@ 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 @@ -81,13 +86,15 @@ 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 @@ -97,6 +104,9 @@ 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. @@ -105,7 +115,6 @@ 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 @@ -115,13 +124,15 @@ 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/exchange/Update-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md similarity index 95% rename from exchange/exchange-ps/exchange/Update-PublicFolder.md rename to exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md index 52de562a91..d20d695c41 100644 --- a/exchange/exchange-ps/exchange/Update-PublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolder applicable: Exchange Server 2010 -title: Update-PublicFolder -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolder +schema: 2.0.0 +title: Update-PublicFolder --- # Update-PublicFolder @@ -50,6 +51,9 @@ This example also starts content replication of the public folder My Public Fold ## 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 by using the format TopLevelPublicFolder\\PublicFolder. You can omit the parameter label so that only the public folder name or GUID is supplied. @@ -58,7 +62,6 @@ 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 @@ -68,6 +71,9 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2010 + The Server parameter specifies the Mailbox server that holds the source public folder database for replication. You can use any value that uniquely identifies the server. For example: - Name @@ -79,7 +85,6 @@ The Server parameter specifies the Mailbox server that holds the source public f Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -89,6 +94,9 @@ 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`. @@ -98,7 +106,6 @@ 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 @@ -108,13 +115,15 @@ 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 @@ -124,13 +133,15 @@ 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/exchange/Update-PublicFolderHierarchy.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md similarity index 96% rename from exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md rename to exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md index c8bcc1dc98..58e8ccf740 100644 --- a/exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolderhierarchy applicable: Exchange Server 2010 -title: Update-PublicFolderHierarchy -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfolderhierarchy +schema: 2.0.0 +title: Update-PublicFolderHierarchy --- # Update-PublicFolderHierarchy @@ -43,6 +44,9 @@ This example pipes the output of the Get-MailboxServer command to the Update-Pub ## PARAMETERS ### -Server + +> Applicable: Exchange Server 2010 + The Server parameter specifies the Mailbox server that holds the source public folder database for replication. You can use any value that uniquely identifies the server. For example: - Name @@ -54,7 +58,6 @@ The Server parameter specifies the Mailbox server that holds the source public f Type: ServerIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010 Required: True Position: Named @@ -64,6 +67,9 @@ 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`. @@ -73,7 +79,6 @@ 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 @@ -83,13 +88,15 @@ 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 @@ -99,13 +106,15 @@ 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/exchange/Update-PublicFolderMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md similarity index 89% rename from exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md index cfef60bbfd..aedd2c39c3 100644 --- a/exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.WebClient-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfoldermailbox applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Update-PublicFolderMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-publicfoldermailbox +schema: 2.0.0 +title: Update-PublicFolderMailbox --- # Update-PublicFolderMailbox @@ -68,6 +69,9 @@ This example updates all public folder mailboxes. ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the public folder mailbox that you want to update. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -85,7 +89,6 @@ The Identity parameter specifies the public folder mailbox that you want to upda Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -95,13 +98,15 @@ Accept wildcard characters: False ``` ### -FolderId + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The FolderId parameter specifies the GUID or name of the public folder that you want to synchronize. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder. ```yaml Type: PublicFolderIdParameter Parameter Sets: InvokeSingleFolderSynchronizer Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -111,15 +116,17 @@ Accept wildcard characters: False ``` ### -InvokeSynchronizer + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The InvokeSynchronizer switch can only be used on secondary hierarchy public folder mailboxes and triggers hierarchy synchronization from the primary public folder mailbox to the specified secondary public folder mailbox. You don't need to specify a value with this switch. This switch should only be used for troubleshooting purposes. ```yaml Type: SwitchParameter -Parameter Sets: InvokeSingleFolderSynchronizer +Parameter Sets: InvokeSingleFolderSynchronizer, InvokeSynchronizer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: Named @@ -128,20 +135,10 @@ Accept pipeline input: False Accept wildcard characters: False ``` -```yaml -Type: SwitchParameter -Parameter Sets: InvokeSynchronizer -Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online +### -Confirm -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -### -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`. @@ -151,7 +148,6 @@ 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 @@ -161,13 +157,15 @@ Accept wildcard characters: False ``` ### -CreateAssociatedDumpster + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The CreateAssociatedDumpster switch specifies whether to create the associated dumpster before synchronizing the folder. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: InvokeSingleFolderSynchronizer Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -177,6 +175,9 @@ 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. @@ -185,7 +186,6 @@ 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 @@ -195,13 +195,15 @@ Accept wildcard characters: False ``` ### -ForceOnlineSync + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online + The ForceOnlineSync switch specifies whether to force the secondary public folder mailbox to synchronize with the primary public folder mailbox. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: InvokeSynchronizer Aliases: -Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -211,13 +213,15 @@ Accept wildcard characters: False ``` ### -FullSync + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The FullSync switch specifies that you want to perform a full synchronization of the public folder mailbox. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter Parameter Sets: InvokeSynchronizer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -227,6 +231,9 @@ Accept wildcard characters: False ``` ### -ReconcileFolders + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary will be recreated. You don't need to specify a value with this switch. In on-premises Exchange, folders that exist in the secondary public folder mailbox and not in the primary will be deleted. @@ -249,7 +256,6 @@ This example restores the public folder named "Documents" from LOST_AND_FOUND to Type: SwitchParameter Parameter Sets: InvokeSynchronizer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -259,6 +265,9 @@ Accept wildcard characters: False ``` ### -SuppressStatus + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command will run asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch. You can only use this switch with the InvokeSynchronizer switch. @@ -269,7 +278,6 @@ If you don't use this switch, the output will display status messages every 3 se Type: SwitchParameter Parameter Sets: InvokeSynchronizer Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: False Position: Named @@ -279,13 +287,15 @@ 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/exchange/Update-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md similarity index 90% rename from exchange/exchange-ps/exchange/Update-Recipient.md rename to exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md index c4b96b4b18..a4882984ae 100644 --- a/exchange/exchange-ps/exchange/Update-Recipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-recipient applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -title: Update-Recipient -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-recipient +schema: 2.0.0 +title: Update-Recipient --- # Update-Recipient @@ -57,6 +58,9 @@ In on-premises Exchange, this example updates all contacts in a specific organiz ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online + The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example: - Name @@ -70,7 +74,6 @@ The Identity parameter specifies the recipient that you want to update. You can Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online Required: True Position: 1 @@ -80,6 +83,9 @@ 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`. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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 Active Directory. 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). @@ -107,7 +115,6 @@ 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 @@ -117,6 +124,9 @@ Accept wildcard characters: False ``` ### -DomainController + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The 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. @@ -125,7 +135,6 @@ 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,13 +144,15 @@ 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/exchange/Update-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md similarity index 90% rename from exchange/exchange-ps/exchange/Update-RoleGroupMember.md rename to exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md index 8c47b09f10..5118b61358 100644 --- a/exchange/exchange-ps/exchange/Update-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-rolegroupmember applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection -title: Update-RoleGroupMember -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-rolegroupmember +schema: 2.0.0 +title: Update-RoleGroupMember --- # Update-RoleGroupMember @@ -75,13 +76,15 @@ Mail-enabled security group: If you want to add or remove a mail-enabled securit ## 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 whose membership you want to modify. If the name of the role group 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 @@ -91,6 +94,9 @@ 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: @@ -102,7 +108,6 @@ 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 @@ -112,6 +117,9 @@ 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`. @@ -121,7 +129,6 @@ 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 @@ -131,6 +138,9 @@ 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. @@ -139,7 +149,6 @@ 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,6 +158,9 @@ Accept wildcard characters: False ``` ### -Members + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection + The Members parameter specifies the mailboxes or mail-enabled USGs to add as a member of the role group. You can identify the user or group by the name, DN, or primary SMTP address value. You can specify multiple members separated by commas (`Value1,Value2,...ValueN`). If the value contains spaces, enclose the value in quotation marks (`"Value 1","Value 2",..."Value N"`). By default, the values that you specify overwrite the existing membership list of the role group. To add or remove multiple members without replacing the entire membership list, see the Examples section. @@ -157,7 +169,6 @@ By default, the values that you specify overwrite the existing membership list o 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 @@ -167,6 +178,9 @@ 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. @@ -175,7 +189,6 @@ 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/exchange/Update-SafeList.md b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md similarity index 91% rename from exchange/exchange-ps/exchange/Update-SafeList.md rename to exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md index 9b052ebd8b..6613706bcd 100644 --- a/exchange/exchange-ps/exchange/Update-SafeList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailControl-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-safelist applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-SafeList -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailControl-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-safelist +schema: 2.0.0 +title: Update-SafeList --- # Update-SafeList @@ -59,6 +60,9 @@ This example updates safelist data for all user mailboxes in your Exchange organ ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox from which you want to collect safelist aggregation data. You can use any value that uniquely identifies the mailbox. For example: - Name @@ -76,7 +80,6 @@ The Identity parameter specifies the mailbox from which you want to collect safe Type: MailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -86,6 +89,9 @@ 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,7 +101,6 @@ 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,13 +110,15 @@ 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 @@ -121,6 +128,9 @@ Accept wildcard characters: False ``` ### -EnsureJunkEmailRule + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The EnsureJunkEmailRule switch forces the junk email rule to be turned on for the mailbox if the rule isn't turned on already. You don't need to specify a value with this switch. The junk email rule can only be created after the user logs on to the mailbox. If the user has never logged on to the mailbox, this parameter can't turn on the junk email rule. @@ -129,7 +139,6 @@ The junk email rule can only be created after the user logs on to the mailbox. I Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -139,6 +148,9 @@ Accept wildcard characters: False ``` ### -IncludeDomains + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The IncludeDomains switch specifies whether to include the sender domains specified by users in Outlook in the safelist aggregation data. You don't need to specify a value with this switch. By default, domains specified by the senders aren't included. @@ -149,7 +161,6 @@ In most cases, we don't recommend that you include domains because users may inc Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -159,6 +170,9 @@ Accept wildcard characters: False ``` ### -Type + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Type parameter specifies which user-generated list is updated to the user object. Valid values for this parameter are SafeSenders, SafeRecipients, and Both. The default value is SafeSenders. The safelist aggregation feature doesn't act on Safe Recipients List data. We don't recommend running the Type parameter with the SafeRecipients or Both values. @@ -167,7 +181,6 @@ The safelist aggregation feature doesn't act on Safe Recipients List data. We do Type: UpdateType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -177,13 +190,15 @@ 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/exchange/Update-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md similarity index 91% rename from exchange/exchange-ps/exchange/Update-SiteMailbox.md rename to exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md index e56a3a732f..9e1ff9f3cc 100644 --- a/exchange/exchange-ps/exchange/Update-SiteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-sitemailbox applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-SiteMailbox -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-sitemailbox +schema: 2.0.0 +title: Update-SiteMailbox --- # Update-SiteMailbox @@ -58,6 +59,9 @@ This example updates the site mailbox WinterHoliday@tailspintoys.com and perform ## PARAMETERS ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the site mailbox that you want to update. You can use any value that uniquely identifies the site mailbox. For example: - Name @@ -71,7 +75,6 @@ The Identity parameter specifies the site mailbox that you want to update. You c Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: 1 @@ -81,6 +84,9 @@ 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. @@ -89,7 +95,6 @@ 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 @@ -99,6 +104,9 @@ 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`. @@ -108,7 +116,6 @@ 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 @@ -118,13 +125,15 @@ Accept wildcard characters: False ``` ### -FullSync + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The FullSync switch specifies full sync is expensive and will have a performance impact on the Exchange system. 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 @@ -134,13 +143,15 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: 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 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -150,13 +161,15 @@ Accept wildcard characters: False ``` ### -Server + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Server parameter specifies the fully qualified domain name (FQDN) or the Microsoft SharePoint server on which the site mailbox is located. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -166,6 +179,9 @@ Accept wildcard characters: False ``` ### -Target + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Target parameter specifies whether to update the SharePoint documents, the site mailbox's membership list or both. This parameter accepts the following values: - All @@ -178,7 +194,6 @@ If you don't specify this parameter when you run the cmdlet, this parameter valu Type: TargetType Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: False Position: Named @@ -188,13 +203,15 @@ 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/exchange/Update-StoreMailboxState.md b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md similarity index 94% rename from exchange/exchange-ps/exchange/Update-StoreMailboxState.md rename to exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md index d586e3c49e..6b7aa01030 100644 --- a/exchange/exchange-ps/exchange/Update-StoreMailboxState.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RolesAndAccess-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-storemailboxstate applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -title: Update-StoreMailboxState -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RolesAndAccess-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-storemailboxstate +schema: 2.0.0 +title: Update-StoreMailboxState --- # Update-StoreMailboxState @@ -58,6 +59,9 @@ This example updates the mailbox state for all disconnected mailboxes on the mai ## PARAMETERS ### -Database + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Database parameter specifies the mailbox database that contains the mailbox. You can use any value that uniquely identifies the database. For example: - Name @@ -68,7 +72,6 @@ The Database parameter specifies the mailbox database that contains the mailbox. Type: DatabaseIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -78,6 +81,9 @@ Accept wildcard characters: False ``` ### -Identity + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 + The Identity parameter specifies the mailbox that you want to update. Use the mailbox GUID as the value for this parameter. Run the following command to obtain the mailbox GUID and other information for all mailboxes in your organization: Get-MailboxDatabase | Get-MailboxStatistics | Format-List DisplayName,MailboxGuid,Database,DisconnectReason,DisconnectDate. @@ -86,7 +92,6 @@ Run the following command to obtain the mailbox GUID and other information for a Type: StoreMailboxIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Required: True Position: Named @@ -96,6 +101,9 @@ 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`. @@ -105,7 +113,6 @@ 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 @@ -115,13 +122,15 @@ 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/exchange/Update-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Update-VivaModuleFeaturePolicy.md similarity index 97% rename from exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md rename to exchange/exchange-ps/ExchangePowerShell/Update-VivaModuleFeaturePolicy.md index f8a3ee84e0..3f4af16692 100644 --- a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-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/update-vivamodulefeaturepolicy applicable: Exchange Online -title: Update-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 -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-vivamodulefeaturepolicy +schema: 2.0.0 +title: Update-VivaModuleFeaturePolicy --- # Update-VivaModuleFeaturePolicy @@ -108,6 +108,9 @@ This example updates a policy for the ShowAISkills feature in Viva Skills. The p ## PARAMETERS ### -FeatureId + +> Applicable: Exchange Online + The FeatureId parameter specifies the feature in the Viva module of the policy that you want to update. 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. @@ -116,7 +119,6 @@ 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 @@ -126,13 +128,15 @@ Accept wildcard characters: False ``` ### -ModuleId + +> Applicable: Exchange Online + The ModuleId parameter specifies the Viva module of the policy that you want to update. ```yaml Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -142,6 +146,9 @@ Accept wildcard characters: False ``` ### -PolicyId + +> Applicable: Exchange Online + The PolicyId parameter specifies the policy for the feature in the Viva module that you want to update. To view details about the policies for a feature in a Viva module, use the Get-VivaModuleFeaturePolicy cmdlet. The PolicyId value is returned in the output of the cmdlet. @@ -150,7 +157,6 @@ To view details about the policies for a feature in a Viva module, use the Get-V Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: Named @@ -160,6 +166,9 @@ 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`. @@ -169,7 +178,6 @@ 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 @@ -179,6 +187,9 @@ Accept wildcard characters: False ``` ### -Everyone + +> Applicable: Exchange Online + The Everyone parameter specifies that the updated policy applies to all users in the organization. Valid values are: - $true: The policy applies to all users. This is the only useful value for this parameter. @@ -192,7 +203,6 @@ Don't use this parameter with the GroupIds or UserIds parameters. Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -202,6 +212,9 @@ 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. If you don't want to update who the policy applies to, don't use this parameter. @@ -218,7 +231,6 @@ To have the updated policy apply to all users in the organization, use the Every Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -227,6 +239,9 @@ Accept pipeline input: False Accept wildcard characters: False ``` ### -IsFeatureEnabled + +> Applicable: Exchange Online + The IsFeatureEnabled parameter specifies whether the feature is enabled by the updated policy. Valid values are: - $true: The feature is enabled by the policy. @@ -238,7 +253,6 @@ If you don't want to update whether the feature is enabled by the policy, don't Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -248,6 +262,9 @@ Accept wildcard characters: False ``` ### -IsUserControlEnabled + +> Applicable: Exchange Online + **Note**: This parameter is available in version 3.3.0 or later of the module. If the feature supports user controls for opting out, make sure you set the *IsUserControlEnabled* parameter when you create the policy. Otherwise, user controls for the policy use the default state for the feature. The IsUserControlEnabled parameter specifies whether user control is enabled by the policy. Valid values are: @@ -263,7 +280,6 @@ If you don't want to update whether the user control is enabled by the policy, d Type: Boolean Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -273,6 +289,9 @@ 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: @@ -288,7 +307,6 @@ 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 @@ -298,6 +316,9 @@ Accept wildcard characters: False ``` ### -Name + +> Applicable: Exchange Online + The Name parameter specifies the updated name for 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. @@ -308,7 +329,6 @@ If you don't want to update the name of the policy, don't use this parameter. Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -318,13 +338,15 @@ 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 @@ -334,6 +356,9 @@ Accept wildcard characters: False ``` ### -UserIds + +> Applicable: Exchange Online + The UserIds parameter specifies the user principal names (UPNs) of users that the updated policy applies to. You can enter multiple values separated by commas. If you don't want to update who the policy applies to, don't use this parameter. @@ -348,7 +373,6 @@ To have the updated policy apply to all users in the organization, use the Every Type: String[] Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: False Position: Named @@ -358,13 +382,15 @@ 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/exchange/Update-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md similarity index 96% rename from exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md rename to exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md index bd36987193..54e85db698 100644 --- a/exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md +++ b/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/update-ediscoverycaseadmin applicable: Security & Compliance -title: Update-eDiscoveryCaseAdmin -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/update-ediscoverycaseadmin +schema: 2.0.0 +title: Update-eDiscoveryCaseAdmin --- # Update-eDiscoveryCaseAdmin @@ -46,6 +47,9 @@ This example replaces the existing eDiscovery Administrators with new users. ## PARAMETERS ### -Users + +> Applicable: Security & Compliance + The Users parameter specifies the users that will replace the current eDiscovery Administrators. You can use any value that uniquely identifies the user. For example: - Name @@ -59,7 +63,6 @@ You can enter multiple values separated by commas. If the values contain spaces Type: String[] Parameter Sets: (All) Aliases: -Applicable: Security & Compliance Required: True Position: Named @@ -69,6 +72,9 @@ 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,7 +84,6 @@ 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 @@ -88,13 +93,15 @@ 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/exchange/Upgrade-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md similarity index 93% rename from exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md rename to exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md index d0092da6bc..6f28f338e8 100644 --- a/exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/upgrade-distributiongroup applicable: Exchange Online, Exchange Online Protection -title: Upgrade-DistributionGroup -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/upgrade-distributiongroup +schema: 2.0.0 +title: Upgrade-DistributionGroup --- # Upgrade-DistributionGroup @@ -45,6 +46,9 @@ This example upgrades the specified distribution groups to Microsoft 365 Groups. ## PARAMETERS ### -DlIdentities + +> Applicable: Exchange Online + The DlIdentities parameter specifies the email address of the distribution group that you want to upgrade to a Microsoft 365 Group. You can specify multiple values separated by commas. @@ -53,7 +57,6 @@ You can specify multiple values separated by commas. Type: MultiValuedProperty Parameter Sets: (All) Aliases: -Applicable: Exchange Online Required: True Position: 1 @@ -63,13 +66,15 @@ Accept wildcard characters: False ``` ### -ActionType + +> 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 @@ -79,13 +84,15 @@ Accept wildcard characters: False ``` ### -ExecutingUser + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: RecipientIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -95,13 +102,15 @@ Accept wildcard characters: False ``` ### -Organization + +> Applicable: Exchange Online, Exchange Online Protection + This parameter is reserved for internal Microsoft use. ```yaml Type: OrganizationIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Validate-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md similarity index 94% rename from exchange/exchange-ps/exchange/Validate-OutboundConnector.md rename to exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md index e096f825c2..f13c596468 100644 --- a/exchange/exchange-ps/exchange/Validate-OutboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/validate-outboundconnector applicable: Exchange Online, Exchange Online Protection -title: Validate-OutboundConnector -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/validate-outboundconnector +schema: 2.0.0 +title: Validate-OutboundConnector --- # Validate-OutboundConnector @@ -49,6 +50,9 @@ This example tests the Outbound connector named Contoso.com Outbound Connector. ## PARAMETERS ### -Identity + +> Applicable: Exchange Online, Exchange Online Protection + The Identity parameter specifies the Outbound connector that you want to test. You can use any value that uniquely identifies the connector. For example: - Name @@ -59,7 +63,6 @@ The Identity parameter specifies the Outbound connector that you want to test. Y Type: OutboundConnectorIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Exchange Online Protection Required: True Position: Named @@ -69,6 +72,9 @@ Accept wildcard characters: False ``` ### -Recipients + +> Applicable: Exchange Online, Exchange Online Protection + The Recipients parameter specifies one or more email addresses to send a test message to. The email addresses need to be in the domain that's configured on the connector. 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"`. @@ -77,7 +83,6 @@ 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: True Position: Named @@ -87,6 +92,9 @@ 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`. @@ -96,7 +104,6 @@ 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 @@ -106,13 +113,15 @@ 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/exchange/Validate-RetentionRuleQuery.md b/exchange/exchange-ps/ExchangePowerShell/Validate-RetentionRuleQuery.md similarity index 96% rename from exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md rename to exchange/exchange-ps/ExchangePowerShell/Validate-RetentionRuleQuery.md index c4a8ee7175..f34502a10f 100644 --- a/exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md +++ b/exchange/exchange-ps/ExchangePowerShell/Validate-RetentionRuleQuery.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/validate-retentionrulequery applicable: Exchange Online, Security & Compliance -title: Validate-RetentionRuleQuery -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.TransportMailflow-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/validate-retentionrulequery +schema: 2.0.0 +title: Validate-RetentionRuleQuery --- # Validate-RetentionRuleQuery @@ -40,6 +41,9 @@ This example validates the specified KQL content search filter. ## PARAMETERS ### -KqlQueryString + +> Applicable: Exchange Online, Security & Compliance + The KqlQueryString parameter specifies the KQL text search string that you want to validate. 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). @@ -48,7 +52,6 @@ This parameter uses a text search string or a query that's formatted by using th Type: String Parameter Sets: (All) Aliases: -Applicable: Exchange Online, Security & Compliance Required: True Position: Named diff --git a/exchange/exchange-ps/exchange/Write-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md similarity index 89% rename from exchange/exchange-ps/exchange/Write-AdminAuditLog.md rename to exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md index 3545297054..01d5502fda 100644 --- a/exchange/exchange-ps/exchange/Write-AdminAuditLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md @@ -1,12 +1,13 @@ --- -external help file: Microsoft.Exchange.RecordsandEdge-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/write-adminauditlog applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection -title: Write-AdminAuditLog -schema: 2.0.0 author: chrisda +external help file: Microsoft.Exchange.RecordsandEdge-Help.xml +Locale: en-US +Module Name: ExchangePowerShell ms.author: chrisda -ms.reviewer: +online version: https://learn.microsoft.com/powershell/module/exchange/write-adminauditlog +schema: 2.0.0 +title: Write-AdminAuditLog --- # Write-AdminAuditLog @@ -47,6 +48,9 @@ This example adds a comment to the administrator audit log. ## PARAMETERS ### -Comment + +> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection + The Comment parameter specifies the comment to add to the administrator audit log. The maximum length is 500 characters. If the comment you specify contains spaces, enclose the comment in quotation marks ("). @@ -55,7 +59,6 @@ If the comment you specify contains spaces, enclose the comment in quotation mar 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 @@ -65,6 +68,9 @@ 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`. @@ -74,7 +80,6 @@ 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 @@ -84,6 +89,9 @@ 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,7 +100,6 @@ 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 @@ -102,13 +109,15 @@ 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